| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-12-07 | |||
| 21:23:31 | radez | | properties | {u'memory_mb': u'4096', u'cpu_arch': u'x86_64', u'local_gb': u'40', u'cpus': u'4', u'capabilities': u'boot_option:local' | |
| 21:23:35 | radez | both look liek that | |
| 21:23:40 | mriedem | yeah so check that bug | |
| 21:23:44 | mriedem | or https://review.openstack.org/#/c/609043/ | |
| 21:23:45 | radez | getting the logs... | |
| 21:23:59 | dansmith | mriedem: yeah, that's the kind of thing I was thinking of | |
| 21:24:05 | melwitt | dansmith: I didn't know that. but what you say makes sense, you're probably right | |
| 21:24:06 | dansmith | mriedem: we consume one CUSTOM_FOO, and then schedule the next one based on there looking like there's ram or something | |
| 21:24:22 | mriedem | i'm very much half assing my involvement here, | |
| 21:24:25 | mriedem | but that's something i'd check out | |
| 21:25:45 | dansmith | I have to leave soon | |
| 21:28:24 | radez | here's more of the scheduler log http://paste.openstack.org/show/736846/ | |
| 21:31:23 | dansmith | radez: okay but that's still just one instance, right? | |
| 21:31:40 | dansmith | however, it looks like whatever host it chose got successfully claimed in placement, | |
| 21:31:50 | dansmith | which can't happen if each host is exposing only one inventory item | |
| 21:32:32 | dansmith | radez: can you correlate the "Attempting to claim.." line with the relevant context in the placement log? | |
| 21:32:52 | radez | placement log is the scheduler log? | |
| 21:32:57 | mriedem | no | |
| 21:33:00 | dansmith | nope, a different service | |
| 21:33:01 | mriedem | placement-api log | |
| 21:33:12 | radez | oh, sec lemme find that log | |
| 21:33:16 | dansmith | that should (I think) show you what is being claimed for the instance | |
| 21:33:28 | dansmith | which really should be only one resource, something like CUSTOM_IRONIC_FOO=1 | |
| 21:34:56 | radez | would that coorelate on the insance uuid? | |
| 21:35:24 | dansmith | I'm not sure what the string looks like, so not sure if it dumps the consumer (instance) uuid or not | |
| 21:35:26 | mriedem | if the flavor has vcpu/ram/disk, and the compute node is reporting vcpu/ram/disk inventory - which it will be still before stein, the claim will be on vcpu/ram/disk as well | |
| 21:35:28 | dansmith | so I would go by date | |
| 21:35:51 | dansmith | mriedem: wait, what? | |
| 21:36:04 | dansmith | I thought it only reported the old resources in some compat situation? | |
| 21:36:06 | radez | kk | |
| 21:37:09 | mriedem | dansmith: no, | |
| 21:37:22 | mriedem | we didn't neuter the ironic driver until stein, right around the ptg | |
| 21:37:26 | dansmith | I think I recoiled in horror the last time we talked about this | |
| 21:37:36 | mriedem | that's why we needed https://review.openstack.org/#/c/609043/ | |
| 21:37:49 | dansmith | so maybe he just doesn't have the resource class in his flavor? | |
| 21:39:31 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Drop pre-cellsv2 compat in compute API.get() https://review.openstack.org/615347 | |
| 21:39:32 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Drop old service version check compat from _delete_while_booting https://review.openstack.org/623589 | |
| 21:39:32 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Remove "API Service Version" upgrade check https://review.openstack.org/615348 | |
| 21:39:46 | mriedem | | properties | {u'memory_mb': u'4096', u'cpu_arch': u'x86_64', u'local_gb': u'40', u'cpus': u'4', u'capabilities': u'boot_option:local' | |
| 21:39:54 | mriedem | those are extra specs? | |
| 21:40:03 | dansmith | no, | |
| 21:40:08 | mriedem | then correct the baremetal flavor doesn't have the custom resource class | |
| 21:40:10 | dansmith | node detaisl Ithink | |
| 21:40:52 | mriedem | radez: have you gone through this? https://docs.openstack.org/ironic/rocky/install/configure-nova-flavors.html | |
| 21:41:02 | mriedem | especially: openstack flavor set --property resources:CUSTOM_BAREMETAL_SMALL=1 my-baremetal-flavor | |
| 21:41:15 | dansmith | and/or.. who created your flavor? | |
| 21:41:16 | radez | http://paste.openstack.org/show/736847/ | |
| 21:41:48 | dansmith | o.O | |
| 21:42:43 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Drop old service version check compat from _delete_while_booting https://review.openstack.org/623589 | |
| 21:42:48 | radez | jlibosvar created the flavor, it looks like that custom baremetal small is not on it | |
| 21:43:13 | mriedem | CUSTOM_BAREMETAL_SMALL is an example | |
| 21:43:14 | dansmith | radez: it needs to be equal to whatever is set on the node | |
| 21:43:18 | dansmith | right | |
| 21:43:25 | radez | http://paste.openstack.org/show/736848/ | |
| 21:43:27 | mriedem | the node has a resource_class field | |
| 21:43:34 | radez | yea lemme see what's on the node | |
| 21:43:43 | mriedem | yeah that flavor isn't going to cut it | |
| 21:43:59 | dansmith | yeah | |
| 21:44:03 | mriedem | https://docs.openstack.org/ironic/rocky/install/configure-nova-flavors.html ftw | |
| 21:44:35 | radez | I don't think there is a resources property on the bm node either | |
| 21:44:55 | mriedem | resource_class | |
| 21:45:10 | mriedem | https://developer.openstack.org/api-ref/baremetal/?expanded=show-node-details-detail#show-node-details | |
| 21:45:13 | dansmith | radez: that "how to configure flavors" doc above is probably your ticket out of here, right? | |
| 21:45:21 | radez | | resource_class | None | |
| 21:45:25 | mriedem | heh "This will be used by the openstack Placement Engine in a future release." | |
| 21:45:43 | mriedem | jroll: maybe we should update the resource_class api-ref parameter description in ironic now... | |
| 21:46:17 | radez | yea maybe he's just missed some of the setup steps. Lemme regroup and try and go back through the steps that have been taken in this env and I'll circle back back next week if we're still haveing trouble | |
| 21:46:47 | dansmith | cool | |
| 21:47:01 | radez | ok, thanks for your time! | |
| 21:52:34 | dansmith | I need to remember to remember that we only closed that silly loop in stein | |
| 21:52:42 | dansmith | all that discussion at the first denver ptg ... | |
| 22:05:52 | mriedem | melwitt: thanks for hitting the stable branch reviews | |
| 22:06:31 | melwitt | np | |
| 22:29:36 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Remove allocations before setting vm_status to SHELVED_OFFLOADED https://review.openstack.org/623596 | |
| 22:29:39 | mriedem | gibi: efried_cya_jan: finally got that alternative fix up for that shelve gate race bug ^ | |
| 22:35:59 | cfriesen | in compute/api.py in the @check_instance_state() decorator, if we don't specify a task_state does that mean that we don't care what the state is? | |
| 22:36:24 | mriedem | no | |
| 22:36:34 | mriedem | not specifying a task_state means task_state must be None | |
| 22:37:36 | cfriesen | what if we have @check_instance_state(task_state=None) ? | |
| 22:38:05 | openstackgerrit | Ben Nemec proposed openstack/nova master: Migrate upgrade checks to oslo.upgradecheck https://review.openstack.org/603499 | |
| 22:38:56 | mriedem | cfriesen: if only the source code were freely available... | |
| 22:40:34 | cfriesen | mriedem: yeah, well I'm staring at it and I'm trying to wrap my head around the logic since there are no useful comments. :) | |
| 22:42:34 | cfriesen | I guess if we explicitly set it to None then we don't care, otherwise instance.task_state has to be None to pass. | |
| 22:42:51 | melwitt | yeah, was about to say the same thing | |
| 22:43:17 | melwitt | if task_state=None it isn't checking state | |
| #openstack-nova - 2018-12-08 | |||
| 14:40:30 | efried | mriedem: "before i dig into the fewer placement calls from _ensure patch, you've addressed jaypipes' ironic concerns from https://review.openstack.org/#/c/615677/9/nova/compute/resource_tracker.py@812 ?" Apparently I was supposed to address it in the is_new_compute_node path as well as the errors-in-ufpt path. The former ought to be a fair bit easier, but I'm not going to be able to get to it until next week at the earliest. | |
| 14:45:12 | mriedem | efried: ack, i saw jay hit it again yesterday | |
| 14:45:30 | mriedem | if you're poking, question about that scheduler report client singleton idea in my api patch https://review.openstack.org/#/c/623246/ | |
| 14:45:46 | leakypipes | ciao | |
| 14:45:58 | efried | mriedem: ack, will look later, I've got like five minutes, big day today for me. | |
| 14:46:15 | efried | oops, /me renames self after reconnect... | |
| #openstack-nova - 2018-12-09 | |||
| 13:02:03 | openstack | bug 1806064 in OpenStack Compute (nova) rocky "Volume remains in attaching/reserved status, if the instance is deleted after TooManyInstances exception in nova-conductor" [Medium,In progress] https://launchpad.net/bugs/1806064 - Assigned to s10 (vlad-esten) | |
| 13:02:03 | openstackgerrit | Vlad Gusev proposed openstack/nova stable/pike: Add functional regression test for bug 1806064 https://review.openstack.org/623935 | |
| 13:02:14 | openstackgerrit | Vlad Gusev proposed openstack/nova stable/pike: Create BDMs/tags in cell with instance when over-quota https://review.openstack.org/623937 | |
| 14:30:44 | openstackgerrit | Ghanshyam Mann proposed openstack/nova stable/queens: Make the nova-next job voting and gating https://review.openstack.org/620888 | |
| 14:43:46 | openstack | bug 1806064 in OpenStack Compute (nova) rocky "Volume remains in attaching/reserved status, if the instance is deleted after TooManyInstances exception in nova-conductor" [Medium,In progress] https://launchpad.net/bugs/1806064 - Assigned to s10 (vlad-esten) | |
| 14:43:46 | openstackgerrit | Vlad Gusev proposed openstack/nova stable/pike: Add functional regression test for bug 1806064 https://review.openstack.org/623935 | |
| 15:28:45 | openstackgerrit | Vlad Gusev proposed openstack/nova stable/pike: Create BDMs/tags in cell with instance when over-quota https://review.openstack.org/623937 | |
| 15:28:45 | openstack | bug 1806064 in OpenStack Compute (nova) rocky "Volume remains in attaching/reserved status, if the instance is deleted after TooManyInstances exception in nova-conductor" [Medium,In progress] https://launchpad.net/bugs/1806064 - Assigned to s10 (vlad-esten) | |
| 15:28:45 | openstackgerrit | Vlad Gusev proposed openstack/nova stable/pike: Add functional regression test for bug 1806064 https://review.openstack.org/623935 | |