Earlier  
Posted Nick Remark
#openstack-nova - 2018-04-19
17:32:46 edleafe The Foundation doesn't think that developer productivity is worth spending money on
17:33:01 jaypipes apparently the train honking situation has been fixed.
17:33:31 mriedem "All aboard! Next stop Denver!" is pretty funny though
17:33:38 jaypipes indeed.
17:37:55 mriedem well this doesn't look good http://grafana.openstack.org/dashboard/db/zuul-status?panelId=19&fullscreen
17:38:46 efried if you say so
17:38:59 mriedem is the total drop out normal? maybe it is.
17:39:02 melwitt what does taht mean
17:39:13 mriedem i've just been noticing that stuff is sitting in the queue for awhile
17:39:36 mriedem i'm watching lee's revert on ocata
17:41:51 melwitt yeah, online vs accepting. I would have thought online means "has the ability to accept" so the drop means things no longer being accepted. but why
17:42:45 efried Oh, I would have thought 0 means "we're all busy doing stuff right now" and the worrisome part would be when the line is all the way at the top ("there's nothing in the gate at the moment" - which does that ever happen, ever??)
17:48:50 melwitt asking in -infra. inquiring minds want to know
17:57:44 efried dansmith: Not sure if you've been following the ML thread, but you're one likely to have a strong opinion, so can I pester you for the second nod? https://review.openstack.org/#/c/562687/
17:58:36 dansmith efried: honestly I'm a little worn out on that stuff
17:59:36 efried dansmith: Aren't we all
18:10:00 mriedem arvindn05: done https://review.openstack.org/#/c/560718/
18:11:31 openstackgerrit Merged openstack/nova stable/pike: ironic: Get correct inventory for deployed node https://review.openstack.org/561925
18:17:52 melwitt this looks like something we might want to get in before novaclient release https://review.openstack.org/#/c/424256
18:19:12 melwitt not sure if all the concerns from the -1 got answered, but it was updated this morning
18:33:31 melwitt mriedem: wanna double check this osc-placement release patch pls? https://review.openstack.org/#/c/56278
18:35:41 mriedem melwitt: wrong patch
18:35:47 mriedem https://review.openstack.org/#/c/562787/
18:35:54 mriedem RIP hartsocks
18:36:07 melwitt aw
18:36:29 melwitt I failed at copy-pate
18:36:32 melwitt *paste
18:36:34 melwitt and typing
18:37:54 melwitt efried, jaypipes: did y'all want to get these two things in before os-traits release today? https://review.openstack.org/546713 and https://review.openstack.org/553277
18:38:21 melwitt or is it cool to just go ahead
18:38:56 efried It looks like we want gibi to sign off on the former
18:43:48 openstackgerrit Matt Riedemann proposed openstack/python-novaclient master: [CLI] Fix token auth type https://review.openstack.org/424256
18:44:01 mriedem melwitt: +2 on ^
18:44:23 melwitt ack
18:47:18 jaypipes melwitt: can't merge https://review.openstack.org/#/c/546713/ until mriedem signs off in. The proposed supports_recreate capability would be changed to supports_evacuate by mdbooth's patch.
18:47:48 mriedem there is no supports_recreate capability in that os-traits patch
18:47:49 jaypipes melwitt: never mind... I forgot I didn't put supports_recreate in there.
18:48:39 jaypipes melwitt: either way, since I proposed the patch, someone else needs to +2.
18:49:17 jaypipes melwitt: as for the CPU max display heads one, I'm already +2 on it.
18:49:21 jaypipes GPU...
18:49:56 melwitt yeah, I mean, were those two things important for the release today or are they fine to wait till a future release
18:50:27 jaypipes melwitt: I wouldn't mind having them merged.
18:50:58 openstackgerrit Matt Riedemann proposed openstack/nova master: Move some tests into nova.tests.unit.notifications.objects.test_instance https://review.openstack.org/562793
18:55:46 mriedem jroll: does https://bugs.launchpad.net/nova/+bug/1765334 sound familiar to you as something we might have fixed already outside of https://review.openstack.org/#/c/518294/ ?
18:55:47 openstack Launchpad bug 1765334 in OpenStack Compute (nova) "Ironic resource class may not be put into inventory in Pike" [Undecided,New]
18:55:51 mriedem johnthetubaguy_: ^
19:02:41 mriedem looks like https://github.com/openstack/nova/commit/9ed692bf8c84e0a702536101cd6cb084d33e1c26#diff-6243ddf138dd43ec84fc716722531cb8
19:06:19 jroll mriedem: sounds like 518294 might need a backport to pike?
19:07:12 mriedem eh, idk
19:07:23 jroll mriedem: or it's a race against the resource tracker
19:07:36 melwitt mriedem: novaclient release patch https://review.openstack.org/#/c/562804
19:07:45 mriedem https://review.openstack.org/#/c/518294/ is specifically about resource inventory that's not in the compute node, only placement
19:08:00 jroll ah
19:08:04 mriedem in the case of this ironic bug on pike, it's a custom resource class that gets proxied into the node later
19:08:27 mriedem so rather than create the ironic node with a custom resource class, they create the node, then add the resource class, and that doesn't get reported, via nova (RT) into placement
19:08:55 jroll mriedem: don't think it's the commit you linked, though, that one is about nodes with instances, the bug is before an instance is places
19:08:56 mriedem because nova doesn't think that custom resource classes are something worth reporting for inventory i guess, unless a *known* inventory class changes, like VCPU, MEMORY_MB and DISK_GB
19:09:20 mriedem ah yeah
19:09:36 mriedem that's what i asked in the bug, is the node deployed or not which might make it different from dtantsur|pto's patch
19:09:52 mriedem "1. Always reporting the custom resource class for deployed nodes, if present."
19:10:08 mriedem so they need to always report custom resource class inventory regardless of node state
19:10:22 mriedem bleh, yay proxy fun
19:14:39 mriedem melwitt: was there something specifically in the novaclient changelog that made you think we should do a major version bump?
19:15:10 melwitt mriedem: the addition of the 2.61 microversion support. is that not necessarily a major version?
19:15:16 mriedem no, that's a feature
19:15:21 mriedem minor version bump
19:16:00 melwitt oh, guh. okay.
19:19:58 openstack Launchpad bug 1765144 in OpenStack Compute (nova) "[keystone_authtoken] auth_url = http://controller:35357 port error, it should be 5000" [Undecided,New]
19:19:58 mriedem lbragstad: is this right? https://bugs.launchpad.net/nova/+bug/1765144
19:20:39 lbragstad mriedem: yes and no
19:20:55 lbragstad technically we removed the legacy v2.0 app in queens, so we no longer require two ports
19:21:04 lbragstad but it certainly don't have to be port 5000, or 35357
19:21:23 mriedem yeah looking in http://logs.openstack.org/20/554920/12/check/tempest-full/df42a0d/controller/logs/etc/nova/nova_conf.txt.gz
19:21:27 mriedem we don't specify a port at all
19:21:50 lbragstad oh - sure v
19:21:52 lbragstad https://github.com/openstack/releases/blob/master/deliverables/queens/keystoneauth.yaml#L17
19:22:07 lbragstad auth_url = https://198.72.124.213/identity
19:22:16 mriedem and auth_uri isn't specified at all
19:22:44 mriedem was auth_uri keystone v1/v2 only?
19:23:38 lbragstad you should use auth_url
19:23:52 lbragstad auth_url and auth_uri was causing a lot of confusion
19:23:56 lbragstad so we renamed it https://github.com/openstack/keystonemiddleware/commit/409b482253dec248ed828e92e52b09d4c02e51dd
19:24:32 lbragstad it was ultimately a side-effect of integrating keystoneauth into keystonemiddleware
19:27:01 mriedem ok so the note at step 5 here https://docs.openstack.org/keystone/latest/install/keystone-install-ubuntu.html#install-and-configure-components
19:27:09 mriedem "Before the Queens release, keystone needed to be run on two separate ports to accommodate the Identity v2 API which ran a separate admin-only service commonly on port 35357. With the removal of the v2 API, keystone can be run on the same port for all interfaces."
19:28:28 openstackgerrit Merged openstack/nova stable/ocata: Clean up volumes on boot failure https://review.openstack.org/545086
19:28:42 mriedem lbragstad: and i'm assuming that keystone-manage bootstrap creates the identity service endpoint in the catalog?
19:28:50 lbragstad it does
19:29:01 mriedem so if hte docs say "--bootstrap-public-url http://controller:5000/v3/"
19:29:12 mriedem then that's probably what the nova docs should use
19:29:25 mriedem or internal url i guess, but they are the same in the docs
19:30:16 mriedem ok i'll push a change to fix the nova install guide docs to remove auth_uri and change auth_url to use port 5000
19:30:20 mriedem thanks
19:32:11 lbragstad mriedem: cool - that's a good idea..
19:32:16 lbragstad i just left a comment on that bug
19:32:51 lbragstad the only things is that people started noticing this when moving from one installation guide to another (and different services were referencing different ports)
19:38:06 mriedem yeah. i've also always been confused by auth_uri and auth_url, glad i wasn't the only one
19:38:25 melwitt mriedem: nova queens 17.0.3 release patch https://review.openstack.org/#/c/562806
19:40:40 mriedem lgtm
19:48:10 jaypipes lol. turning off @safe_connect blows up unit tests but functional tests work just fine...

Earlier   Later