Earlier  
Posted Nick Remark
#openstack-nova - 2018-08-01
19:42:37 melwitt just found that but it doesn't work for requesting a later placement API microversion?
19:42:39 mriedem because novaclient's python API bindings default to no microversion, so 2.1
19:42:50 mriedem novaclient != placement...
19:42:58 mriedem there is no 2.1 in placement
19:43:00 mriedem there is 1.0
19:43:08 mriedem osc-placement doesn't have anything to do with novaclient
19:43:26 dansmith the passthrough is of the version,
19:43:29 dansmith not the CLI opt
19:43:34 dansmith since osc is its own client
19:43:39 melwitt oh, right. so how do we do microversions with it? it's saying I can't 'resource class list' because 1.0 doesn't support it. but it's in the command list
19:43:53 dansmith there's an option to specify the version
19:44:18 dansmith --os-compute-api-version I think
19:44:26 mriedem openstack --os-placement-api-version 1.7 resource class list
19:44:30 mriedem something like that,
19:44:37 mriedem it's not 'compute' because it's not nova
19:44:39 mriedem in the service catalog
19:44:49 mriedem the --os-<service-type>-api-version is based on the service catalog
19:45:06 mriedem https://docs.openstack.org/osc-placement/latest/cli/index.html#resource-class-list
19:45:09 mriedem This command requires at least –os-placement-api-version 1.2.
19:45:19 mriedem so, openstack --os-placement-api-version 1.2 resource class list
19:45:37 mriedem if you know you're at some max version of placement, you could just set an env var
19:45:43 mriedem export OS_PLACEMENT_API_VERSION=1.7
19:45:45 dansmith yeah, she said novaclient so I assumed she was hitting nova
19:45:49 dansmith but placement for placement obviously
19:45:49 melwitt thanks, I just couldn't find that option --os-placement-api-version anywhere
19:45:54 melwitt yeah, sorry
19:45:54 mriedem and then don't have to worry about per-call mv
19:46:08 mriedem melwitt: should be in the help output for the command
19:46:17 mriedem and https://docs.openstack.org/osc-placement/latest/user/index.html#microversion-usage
19:46:28 melwitt I got confused when I started thinking about passthrough of microversions when using osc
19:46:41 melwitt and it made me think of novaclient and the --os-compute-api-version thing
19:47:00 mriedem yeah, it would be the same if there was a python-placementclient thing
19:47:11 mriedem but we've intentionally always avoided that
19:47:15 melwitt ok yeah, I see now 'openstack resource class list -h'
19:47:29 mriedem b/c we have osc for cli and openstacksdk for sdk
19:48:05 melwitt "Return a list of all resource classes. This command requires at least --os-
19:48:06 melwitt placement-api-version 1.2."
19:48:28 melwitt thanks
20:18:16 openstackgerrit Merged openstack/nova master: Nix unused raise_if_custom_resource_class_pre_v1_1 https://review.openstack.org/575847
20:42:32 openstack bug 1784705 in OpenStack Compute (nova) queens "ResourceTracker.stats can leak across multiple ironic nodes" [High,In progress] https://launchpad.net/bugs/1784705 - Assigned to Matt Riedemann (mriedem)
20:42:32 openstackgerrit Matt Riedemann proposed openstack/nova stable/ocata: Add recreate test for RT.stats bug 1784705 https://review.openstack.org/588076
20:42:33 openstackgerrit Matt Riedemann proposed openstack/nova stable/ocata: Make ResourceTracker.stats node-specific https://review.openstack.org/588077
21:03:42 mriedem ooo goody 5 new bugs in triage
21:04:48 melwitt nooo
21:04:57 mriedem well one is against mitaka so....
21:05:49 melwitt yeah, just opened that one
21:06:21 melwitt I've noticed a fair bit of bugs being added to nova that used to be on other projects lately
21:06:45 melwitt or something. really old bugs coming back as new
21:15:59 melwitt mnaser: have you ever used evacuate with ceph-backed instances? looking at this bug and wondering if evacuate doesn't work with ceph period or if it's only if you've enabled the ceph "exclusive-lock" feature on a disk https://bugs.launchpad.net/nova/+bug/1781878
21:16:00 openstack Launchpad bug 1781878 in OpenStack Compute (nova) "VM fails to boot after evacuation when it uses ceph disk" [Undecided,New]
21:16:55 melwitt the way the bug is worded, I'm not certain whether they're saying evacuate is broken with ceph out-of-the-box
21:17:09 mnaser i am almost certain this is a manifestation of another bug
21:17:13 melwitt so I was wondering if you've ever done evacuate successfully
21:17:14 mnaser of a poorly upgraded ceph cluster
21:17:15 mnaser one second
21:17:19 melwitt k
21:17:20 mnaser yes, evacuate works all the time, but one second
21:18:00 openstackgerrit Eric Fried proposed openstack/nova master: Compute: Handle reshaped provider trees https://review.openstack.org/576236
21:18:08 mnaser melwitt: http://lists.ceph.com/pipermail/ceph-users-ceph.com/2017-September/020722.html
21:18:10 mnaser alongside doc there
21:18:39 melwitt thanks
21:18:42 mnaser saaame exact behaviour afaik as original reported issue
21:19:36 melwitt oh, this is familiar ... I remember an internal bug we had about this
21:19:55 mnaser a lot of people were affected by this because the step to tell you to do this was forgotten in the original ceph upgrade docs
21:20:23 melwitt a-ha
21:21:24 melwitt going to try to find that internal bug, the conclusion was to add something to a config? to allow the blacklist command
21:21:48 melwitt and I had first seen the idea on an upstream cinder bug
21:23:52 mnaser melwitt: http://docs.ceph.com/docs/master/releases/luminous/#upgrade-from-jewel-or-kraken
21:23:58 mnaser specifically #6
21:27:15 melwitt ty
21:29:42 openstack Launchpad bug 1760065 in kolla-ansible "ceph luminous insufficient nova caps " [Undecided,New]
21:29:42 melwitt https://bugs.launchpad.net/kolla-ansible/+bug/1760065
21:31:04 openstack Launchpad bug 1773449 in tripleo "VM rbd backed block devices inconsistent after unexpected host outage" [High,Fix released] - Assigned to Giulio Fidente (gfidente)
21:31:04 melwitt I think I found the bug I was thinking of, it wasn't for cinder though https://bugs.launchpad.net/nova/+bug/1773449
21:31:49 melwitt particularly comment #31
21:33:40 openstackgerrit Eric Fried proposed openstack/nova master: [placement] Add /reshaper handler for POST https://review.openstack.org/576927
21:33:41 openstackgerrit Eric Fried proposed openstack/nova master: reshaper: Look up provider if not in inventories https://review.openstack.org/585033
21:33:42 openstackgerrit Eric Fried proposed openstack/nova master: Make get_allocations_for_resource_provider sane https://review.openstack.org/584598
21:33:43 openstackgerrit Eric Fried proposed openstack/nova master: Report client: Real get_allocs_for_consumer https://review.openstack.org/584599
21:33:44 openstackgerrit Eric Fried proposed openstack/nova master: Report client: get_allocations_for_provider_tree https://review.openstack.org/584648
21:33:45 openstackgerrit Eric Fried proposed openstack/nova master: Report client: _reshape helper, placement min bump https://review.openstack.org/585034
21:33:46 openstackgerrit Eric Fried proposed openstack/nova master: Report client: update_from_provider_tree w/reshape https://review.openstack.org/585049
21:33:47 openstackgerrit Eric Fried proposed openstack/nova master: Compute: Handle reshaped provider trees https://review.openstack.org/576236
21:35:15 efried melwitt: FYI, this series is "finished" (ready for review) ^
21:35:38 melwitt efried: coolness, thanks for the heads up
21:35:47 mriedem time to slot up stein runways etherpad it looks like
21:36:19 melwitt yeah, I need to make some etherpads. need a retro one too for the PTG. and probably another one I'm forgetting
21:38:24 mriedem stein review priorities?
21:44:11 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: Rollback failed evacuated guest https://review.openstack.org/588087
21:44:16 mriedem mdbooth and the red hat gang would probably love to punch holes in ^
21:49:30 sean-k-mooney mriedem: you -w it so im guessing your not to keen on its current state either
21:49:46 mriedem no, rollback is tricky
21:49:53 mriedem plus see the todo about bdm attachments
21:50:38 sean-k-mooney mriedem: how many states can a vm in a failed evecuate be in by the way. in theor the compute service on teh host you were evacuating from is down so can we even check the current status of the vm
21:52:44 mriedem unless the source came back up and changed the state on the instance in the db which is why the evac on the dest failed in the first place
21:53:49 sean-k-mooney right if this rollback is happening the vm is not running on the dest, may or may not be running on the source, and the source node may or may not be up
21:55:29 sean-k-mooney just reading the commit and bug for context but ya the rollback is non trivial
22:00:25 openstack Launchpad bug 1784782 in OpenStack Compute (nova) "API: flavors - Cannot list all public and private flavors by default" [Undecided,New]
22:00:25 mriedem https://bugs.launchpad.net/nova/+bug/1784782 is news to me that you can pass GET /flavors?is_public=None as admin to list all flavors
22:02:11 sean-k-mooney mriedem: am ya that seams unintentional that is_public=None would have that effect

Earlier   Later