| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-03-28 | |||
| 15:57:50 | melwitt | yeah, I remember | |
| 16:00:00 | melwitt | I'll mail the list about the vmware CI, see if anyone responds this time | |
| 16:01:48 | openstackgerrit | Claudiu Belu proposed openstack/nova master: vmware: Fixes _detach_instance_volumes method https://review.openstack.org/557377 | |
| 16:02:26 | openstackgerrit | Matt Riedemann proposed openstack/nova master: vmware: log quality warning on startup https://review.openstack.org/557398 | |
| 16:04:27 | openstackgerrit | Eric Fried proposed openstack/nova master: Make generation optional in ProviderTree https://review.openstack.org/539324 | |
| 16:12:32 | mriedem | edleafe: nvm, the docs thing for placement and 1.21 can be fixed in https://review.openstack.org/#/c/554357/ | |
| 16:13:05 | edleafe | mriedem: heh, I was just about to push a fix | |
| 16:13:33 | edleafe | I'll just combine them | |
| 16:18:33 | lyarwood | dansmith: https://review.openstack.org/#/c/557348/ - would you mind looking at this retry_on_request removal backport to stable/pike that came up internally earlier? | |
| 16:18:58 | dansmith | lyarwood: I assume we don't need to do that in upstream stable because of g-r right? | |
| 16:19:12 | dansmith | (if it's not already broken I mean) | |
| 16:19:54 | lyarwood | dansmith: well upstream outside of TripleO no we don't need to do this | |
| 16:20:04 | lyarwood | dansmith: but even with g-r I think this is broken for TripleO | |
| 16:20:16 | dansmith | I would defer to mriedem on that | |
| 16:20:36 | dansmith | if it's capped by u-c I think we're fine as-is, and if not, we broke ourselves | |
| 16:21:02 | dansmith | I would suspect maybe upstream tripleo isn't honoring u-c? | |
| 16:21:15 | lyarwood | very likely | |
| 16:21:37 | lyarwood | it's all RPMs there and I don't recall seeing the same u-c rules in the specs | |
| 16:23:04 | mriedem | - | |
| 16:23:06 | mriedem | -1 | |
| 16:23:08 | mriedem | -5 | |
| 16:23:14 | mriedem | b/c of what dan said | |
| 16:23:25 | mriedem | the decorator was removed in oslo.db 4.30, | |
| 16:23:32 | mriedem | stable/pike is capped at 4.25.1 https://github.com/openstack/requirements/blob/stable/pike/upper-constraints.txt#L433 | |
| 16:23:41 | mriedem | so tripleo should be relying on u-c | |
| 16:23:52 | lyarwood | mriedem: nice thanks | |
| 16:24:08 | edleafe | ugh, heavy lightning around here - power drops have kicked me off the internet 3 times already. | |
| 16:25:30 | dansmith | mriedem: oh they're special alright | |
| 16:28:13 | cdent | mriedem, melwitt: all I'm able to update on the vmware sitiuation is that you've got their attention, so reasonable strategy | |
| 16:29:29 | melwitt | cdent: ack | |
| 16:29:45 | openstackgerrit | Merged openstack/nova stable/queens: Preserve multiattach flag when refreshing connection_info https://review.openstack.org/555029 | |
| 16:30:53 | mriedem | dansmith: tssurya: melwitt: i assume we're having a cells meeting today? | |
| 16:30:59 | mriedem | there is at least one new bug i wanted to talk about | |
| 16:31:25 | dansmith | mriedem: I was going to ask if we needed to | |
| 16:31:28 | dansmith | sounds like we do | |
| 16:31:40 | melwitt | yeah, if we have topics, we can meet | |
| 16:32:12 | mriedem | unless we just want to skip and talk about the specific bug here | |
| 16:32:40 | melwitt | either way wfm | |
| 16:33:42 | dansmith | I'm good to skip if it's just one bug | |
| 16:33:45 | dansmith | I got nothing else | |
| 16:37:04 | mriedem | wait to see what tssurya says, she's the busy one | |
| 16:37:57 | tssurya | I am good to skip too | |
| 16:38:02 | mriedem | hot dog | |
| 16:38:19 | openstack | Launchpad bug 1759316 in OpenStack Compute (nova) queens "pre-cells_v2 nova-osapi_compute service in database breaks instance lookup" [Medium,Confirmed] | |
| 16:38:19 | mriedem | ok so just wanted to talk about options for https://bugs.launchpad.net/nova/+bug/1759316 | |
| 16:38:39 | mriedem | basically an upgrade issue for someone that was hard to figure out since there are no logs | |
| 16:38:39 | dansmith | okay | |
| 16:38:48 | mriedem | upgrading newton->ocata | |
| 16:39:16 | mriedem | at this point, if you're not using cells v1 and you get here, https://github.com/openstack/nova/blob/ed55dcad83d5db2fa7e43fc3d5465df1550b554c/nova/compute/api.py#L2269 - i think we should log a warning | |
| 16:39:25 | mriedem | ^ was added in newton | |
| 16:39:33 | mriedem | so if you're hitting that in ocata+ it likely means you're going to have issues | |
| 16:39:34 | dansmith | so, I thought we removed some of this recently | |
| 16:39:37 | dansmith | when I did the instance list bit | |
| 16:40:00 | mriedem | i've had some patches to try and remove some things from the cells v2 transition but they are in limbo, | |
| 16:40:21 | mriedem | there was also a thing i tried removing from the local delete flow and was hitting weird errors, but i forget the details | |
| 16:40:43 | dansmith | but on ocata we can't eliminate that check just yet | |
| 16:40:53 | dansmith | so yeah, you want to warn if we take that path and we're not on cellsv1 right? | |
| 16:40:57 | mriedem | i'm not saying remove it, | |
| 16:40:59 | mriedem | yes | |
| 16:41:02 | mriedem | warn and backport that warning | |
| 16:41:03 | dansmith | yeah I think that makes sense | |
| 16:41:04 | melwitt | yeah, warning makes sense | |
| 16:41:06 | mriedem | ok | |
| 16:41:14 | mriedem | they were also asking if nova-status could check for this, | |
| 16:41:20 | mriedem | which isn't unreasonable | |
| 16:41:28 | dansmith | if you will do the nova-status change I'll do the warning :D | |
| 16:41:33 | mriedem | ha | |
| 16:41:52 | openstack | Launchpad bug 1759316 in OpenStack Compute (nova) queens "pre-cells_v2 nova-osapi_compute service in database breaks instance lookup" [Medium,Confirmed] | |
| 16:41:52 | mriedem | i'm ok with nova-status, but need input on how the check is going to work, see 2nd paragraph in https://bugs.launchpad.net/nova/+bug/1759316/comments/1 | |
| 16:42:53 | openstackgerrit | Ed Leafe proposed openstack/nova master: Address issues raised in adding member_of to GET /a-c https://review.openstack.org/554357 | |
| 16:43:13 | edleafe | jaypipes-away: mriedem: ^^ Addressed the outstanding issues | |
| 16:43:17 | dansmith | you can just return "maybe a problem" with basically that text right? "I found an old entry in cell foo and it might be a problem or might not, but fyi" | |
| 16:43:37 | mriedem | dansmith: yeah that's what i was thinking, we have ok, warning and error for nova-status | |
| 16:43:39 | mriedem | so this would be a warning | |
| 16:43:43 | mriedem | since we aren't sure how you've configured the api | |
| 16:43:46 | dansmith | righ | |
| 16:44:14 | mriedem | alright i can work up a nova-status patch for that | |
| 16:44:19 | mriedem | or die trying | |
| 16:44:27 | dansmith | cool | |
| 16:44:32 | melwitt | lol, pls don't die | |
| 16:45:35 | tssurya | melwitt: https://review.openstack.org/#/c/557369/ | |
| 16:45:44 | tssurya | Just informing | |
| 16:47:23 | melwitt | okay, cool. spec for handling a down cell, we can start reviewing that. and I can depend on it for my related quotas-from-placement-and-instance-mappings spec | |
| 16:47:31 | melwitt | thanks | |
| 16:49:28 | tssurya | dansmith: this is the re-rebase after the UUID shift revert, https://review.openstack.org/#/c/539501/ , whenever you have the time have a look | |
| 16:49:57 | dansmith | okay | |
| 16:51:02 | mriedem | bhagyashris: so i guess we don't send notifications for createBackup? | |
| 16:52:40 | openstackgerrit | Merged openstack/nova stable/queens: Add --by-service to discover_hosts https://review.openstack.org/554600 | |
| 16:53:41 | mriedem | bhagyashris: replies in https://review.openstack.org/#/c/511825/ | |
| 16:54:02 | openstackgerrit | Mathieu Gagné proposed openstack/nova-specs master: Multiple Fixed-IPs support in network information https://review.openstack.org/312626 | |
| 16:58:43 | melwitt | mriedem, dansmith: on this spec ^ it's about changing 'ip_address' in the metadata API to 'ip_addresses' to include all available interfaces for the guest, in a new metadata API version. there was a related issue about changing the metadata API to to show IP addresses even if there is a DHCP server present (currently it does not). there was a question on the spec about whether those two issues should be combined in one spec and one | |
| 16:58:44 | melwitt | new metadata API version or if they should be separated into two specs and versions | |
| 16:59:21 | melwitt | I had been thinking they two things would be separate specs and metadata API versions, but more input would be helpful | |
| 16:59:35 | dansmith | metadata changes have to be purely additive, | |
| 16:59:43 | dansmith | and in the past we've only ever had one metadata version per release AFAIK | |
| 17:00:35 | melwitt | okay, I wasn't aware of that. so it would not be allowed to change ip_address -> ip_addresses, but instead the possibility would be to add ip_addresses | |
| 17:00:43 | dansmith | right | |
| 17:01:47 | melwitt | okay. and then on the "show IP addresses even if DHCP server is present", is that type of change never allowed then? or maybe it would be because that is technically additive. that is, the behavior in the past would be "didn't show IP addresses if DHCP server" and it changes to "shows IP addresses if DHCP server" | |
| 17:02:19 | melwitt | (the use case there is, there is a DHCP server present but it's not being leveraged and IPs were statically configured) | |
| 17:02:33 | melwitt | currently, the presence of the DHCP server makes the API hide the static IP addresses | |