| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2019-03-21 | |||
| 15:24:34 | NobodyCam | just that message repeating itself several times | |
| 15:24:57 | dansmith | NobodyCam: that message is not an error | |
| 15:25:14 | NobodyCam | yea I not seeing nt errors | |
| 15:25:25 | dansmith | NobodyCam: it means that the scheduler picked that host but never got so far as to give it to the host to start, so the message is saying that it's ignoring that assuming the boot request will be coming in soon | |
| 15:25:29 | dansmith | that means it's finding it in the DB | |
| 15:25:31 | NobodyCam | conductor only has two messages with that uuis | |
| 15:25:35 | dansmith | so look elsewhere for logs, likely conductor | |
| 15:25:37 | NobodyCam | uuids | |
| 15:26:08 | NobodyCam | http://paste.openstack.org/show/hrQOgRtlb6g0GbZN1mfa/ | |
| 15:26:59 | sean-k-mooney | NobodyCam: what state is the instance in by the way? is it still building or in error? | |
| 15:27:14 | NobodyCam | building | |
| 15:27:34 | sean-k-mooney | and the task is still block_device_mapping? | |
| 15:27:47 | sean-k-mooney | or something similar | |
| 15:28:48 | NobodyCam | task-state is scheduling | |
| 15:29:52 | NobodyCam | http://paste.openstack.org/show/g2rPJbBSCo4Aj2KufVFN/ | |
| 15:31:14 | sean-k-mooney | that does not really make sense. https://docs.openstack.org/nova/rocky/reference/vm-states.html#create-instance-states | |
| 15:31:46 | sean-k-mooney | the condoctor is showing that it is creating the block device mappings in this case you were booting with epherial storage form an image | |
| 15:32:49 | dansmith | we really should have a condoctor service | |
| 15:32:53 | sean-k-mooney | so the vm shoudl be in in task state Block_device_mapping or spawning | |
| 15:33:23 | openstackgerrit | Surya Seetharaman proposed openstack/nova-specs master: Support server power state update through external event https://review.openstack.org/636132 | |
| 15:33:40 | sean-k-mooney | and a super condoctor | |
| 15:33:44 | NobodyCam | yea, there is not ethereal requested with at flavor | |
| 15:33:45 | NobodyCam | http://paste.openstack.org/show/y7eD1LLJIlvkldWKOqFd/ | |
| 15:34:13 | NobodyCam | *ephemeral | |
| 15:34:52 | sean-k-mooney | NobodyCam: no what i ment is you are not usign boot from volume as the block device mappings show the root disk is local | |
| 15:35:13 | NobodyCam | ahh yes! | |
| 15:35:16 | sean-k-mooney | and from the flavor i can now see you have a root disk of 10G | |
| 15:35:55 | NobodyCam | yes! | |
| 15:36:18 | tssurya | dansmith: whenever you have some time, your opinion on https://review.openstack.org/#/c/636132/ would be highly valued/needed :) thanks in advance | |
| 15:38:12 | sean-k-mooney | anyway form the sequence diagarm of the boot state transition there is definetly somthing wrong. the only time the task state shoudl be in Schduling after the conductor started setting up the disk would be a rechedule after a failed spawn i think | |
| 15:38:32 | sean-k-mooney | unfortunetly the diagram does not capture the error paths | |
| 15:44:07 | efried | stephenfin: You seem like an obvious choice for nova/docs liaison https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation -- can I put you down? | |
| 15:44:22 | dansmith | tssurya: ack | |
| 15:44:35 | stephenfin | efried: I've already been appointed the oslo one so why not | |
| 15:45:07 | efried | stephenfin: you mean the oslo/docs liaison or the oslo/nova liaison? Cause I could totally put you down for that too. | |
| 15:45:17 | NobodyCam | thank you sean-k-mooney :) I will attempt to redeploy nova | |
| 15:45:23 | stephenfin | oslo/docs | |
| 15:45:36 | stephenfin | but sure, oslo/nova maybe makes sense too | |
| 15:45:41 | efried | k | |
| 15:47:45 | efried | Kevin_Zheng, nicolasbock: Y'all are currently down as the nova/docs liaisons https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation -- are you wanting to continue in that capacity? | |
| 15:48:36 | mriedem | efried: i think you could replace | |
| 15:49:16 | efried | ight | |
| 15:50:38 | efried | it seems pretty clear this list isn't used much for some of the categories. Not sure how much I ought to care about it. | |
| 15:59:03 | openstackgerrit | Merged openstack/nova stable/rocky: ironic: check fresh data when sync_power_state doesn't line up https://review.openstack.org/640772 | |
| 15:59:12 | openstackgerrit | Merged openstack/nova stable/rocky: pass endpoint interface to Ironic client https://review.openstack.org/643098 | |
| 15:59:15 | efried | jackding: Did you send out a ML post for https://review.openstack.org/#/c/621646/ warning of the ComputeDriver interface change? | |
| 15:59:26 | openstackgerrit | Merged openstack/nova master: Documentation for bandwidth support https://review.openstack.org/642064 | |
| 15:59:35 | openstackgerrit | Merged openstack/nova master: Add a prelude release note for the 19.0.0 Stein GA https://review.openstack.org/644412 | |
| 15:59:49 | efried | mriedem: looks like ready to cut rocky --^ ? | |
| 16:00:49 | mriedem | efried: yup i'll propose a release | |
| 16:00:57 | efried | k | |
| 16:02:51 | sean-k-mooney | jackding: the change you ping about before still looks good to me by the way | |
| 16:02:58 | gibi | efried: do you need anything else regarding https://review.openstack.org/#/c/645084/ ? | |
| 16:03:14 | jackding | efried: no. Do I need to? it's an optional parameter that has a default value. | |
| 16:03:50 | jackding | efried: not invoked by default | |
| 16:03:54 | efried | gibi: nope, just forgot. +A now | |
| 16:04:08 | gibi | efried: coolio | |
| 16:04:17 | efried | jackding: Any time the signature changes, even for an optional kwarg, it breaks OOT drivers. | |
| 16:04:34 | efried | jackding: We're not supposed to care about them, but I still have a soft spot in my heart. | |
| 16:05:20 | efried | gibi: Should we wait for that --^ for RC1? | |
| 16:05:33 | efried | I guess so, since it's renos | |
| 16:07:43 | efried | mriedem: you see anything else we should hold rc1 for? | |
| 16:08:03 | mriedem | efried: https://review.openstack.org/#/c/642863/ | |
| 16:08:41 | gibi | efried: yeah it is fixing the renos | |
| 16:08:48 | gibi | efried: so I would wait for that | |
| 16:10:20 | mriedem | the release patch can depends-on the known stuff you want to hold up for and then just adjust the hash when they land | |
| 16:11:34 | efried | don't see a lot of value in the depends-on if the content needs to be updated anyway. Just to stop them from automerging it? | |
| 16:11:44 | mriedem | yup | |
| 16:41:37 | openstackgerrit | Merged openstack/nova master: Fix links to neutron QoS minimum bandwidth doc https://review.openstack.org/645084 | |
| 17:01:00 | mdbooth | Could this be a source of random SSH failures in the gate: https://bugzilla.redhat.com/show_bug.cgi?id=1689933 ? | |
| 17:01:02 | openstack | bugzilla.redhat.com bug 1689933 in openstack-nova "[RFE] Add a simple way to enable random number generator on all flavor/image" [Unspecified,New] - Assigned to nova-maint | |
| 17:04:46 | kashyap | bauzas: mdbooth: efried: When you get a minute, please put this one out of its misery: https://review.openstack.org/#/c/641981/ (libvirt: Use 'writeback' QEMU cache mode when 'none' is not viable) | |
| 17:05:08 | efried | kashyap: did you want that in RC1? | |
| 17:05:09 | bauzas | I'm just wrapping my head with devstack atm | |
| 17:05:22 | efried | Cause that's all we're gonna merge today. | |
| 17:05:24 | kashyap | efried: Would certainly be useful to get some initial testing | |
| 17:05:37 | mdbooth | kashyap: That's a no ;) | |
| 17:05:40 | efried | mriedem: RC1 candidate? | |
| 17:05:41 | kashyap | The sooner the better, as we'd be doing a bit of a disservice to the users | |
| 17:05:51 | kashyap | mdbooth: Hehe | |
| 17:06:38 | mdbooth | I think it's a backport candidate, though. We'll almost certainly take it downstream. It's not a regression, though, and it won't cause dataloss or any kind of error. It's just unnecessarily slow. | |
| 17:06:49 | mdbooth | s/I *don't* think/ | |
| 17:06:58 | mdbooth | Erm, I do think. | |
| 17:08:24 | sean-k-mooney | kashyap: that is not a regression so it normally would not qualify for an rc right? | |
| 17:08:28 | kashyap | mdbooth: Thanks for the review so far! Appreciate it | |
| 17:09:12 | kashyap | sean-k-mooney: Not a regression; but why inflict needless slowness? This patch can (positively) impact all new instances | |
| 17:09:23 | sean-k-mooney | kashyap: im also not sure its technically a bug. it sound more like a specless blueprint. | |
| 17:09:50 | sean-k-mooney | kashyap: well you can just set the config option too | |
| 17:11:05 | sean-k-mooney | anyway this just feels like a feature that is filed as a bug which can be worked around via a config already so im not sure if it qualifes for RC incution but i also dont think you will be breaking anything | |
| 17:11:09 | kashyap | This is fixing existing tech debt. The more it is delayed, the more I lose motivation to fix it. | |
| 17:11:41 | sean-k-mooney | sure but when i looked at this earilar i assume this was targeting train not stien | |
| 17:11:50 | kashyap | sean-k-mooney: Also, Huh? This is not a "specless blueprint". This is actually a misuse/bug. | |
| 17:12:07 | sean-k-mooney | everything working but being slow is not a bug | |
| 17:12:20 | kashyap | sean-k-mooney: True. But I won't cry into my pillow if it doesn't make it to Stein, though | |
| 17:12:50 | kashyap | Just that I'd "strongly suggest" to get this in -- also because the "other patch" (for `qemu-img convert` case) merged. | |
| 17:13:13 | sean-k-mooney | kashyap: didnt that merge before feature freeze | |
| 17:13:14 | kashyap | And it's not nice to have these splatter over two releases. | |
| 17:13:18 | kashyap | sean-k-mooney: Yep | |
| 17:13:38 | kashyap | Frankly, I was just so buried in actually digging the issue, that I lost track of all this time. Most deadlines are arbitrary in my mind. | |
| 17:14:20 | kashyap | (As in, wasn't paying attention whether it was merged before or after RC1) | |