Earlier  
Posted Nick Remark
#openstack-nova - 2020-02-24
13:56:17 aarents bauzas: got the same issue since this morning
13:56:31 bauzas aarents: was due to some bug, see the change
13:57:31 aarents bauzas: ok
14:02:23 bauzas mmm, removed my local pip cache, the URL was cached
14:07:10 stephenfin merged now, thankfully
14:11:13 bauzas okay, still puzzled by stestr not knowing the run command
14:11:30 bauzas stephenfin: looks like 'run' is a pbr entrypoint
14:11:40 bauzas https://github.com/mtreinish/stestr/blob/master/setup.cfg#L40
14:11:48 bauzas and stestr relies on cliff
14:12:10 bauzas so I suspect something messed up with entrypoints when I use develop
14:12:19 stephenfin bauzas: '--remote_debug-port' is a nova config option though
14:12:50 bauzas stephenfin: sorry, where ?
14:12:56 stephenfin http://paste.openstack.org/show/789922/
14:12:59 stephenfin from that
14:13:15 stephenfin what seems to be happening is arguments from some command are being registered against others
14:13:30 stephenfin it's like argparse is maintaining some kind of global state
14:14:31 stephenfin bauzas: As proof, try this: virtualenv .venv; source .venv; pip install stestr; stestr -h
14:14:35 bauzas oh, you're right
14:14:42 stephenfin you'll get a totally different output
14:14:47 bauzas I can't see any of the usual stestr options
14:14:51 stephenfin exactly
14:15:01 stephenfin I just haven't figured out why
14:15:41 bauzas I'm just creating a venv as a tox target
14:15:43 stephenfin We worked around it in glance with some patch that I'll need to go root for, but the ultimate issue is that there is some kind of global state being maintained by cliff or oslo.config that there shouldn't be
14:15:49 bauzas to see whether stestr is messed up too
14:16:39 stephenfin bauzas: I assume you're not seeing this issue on master?
14:16:54 bauzas I'm seeing it on any branches
14:16:55 bauzas but,
14:17:18 bauzas if I reclone nova to another directory, it then works
14:17:31 bauzas so the issue is only on the main git repo
14:17:34 stephenfin Backup anything you want and 'git clean -xfd' ?
14:17:56 stephenfin Maybe you have a hangover pyc file that the interpreter is loading
14:18:04 stephenfin I've seen that cause other issues in the past
14:18:24 bauzas maybe
14:18:41 stephenfin ('git clean -xfd' will wipe all untracked files including those ignored by '.gitgnore' files, btw)
14:18:56 stephenfin (I know you probably know that already)
14:21:31 bauzas indeed, but haven't thought about it
14:23:15 bauzas it does fix the problem
14:23:36 bauzas have no f*** idea what the issue was, but now stestr works with develop mode
14:23:57 bauzas (which is understandable, since I asked to delete all pyc's)
14:36:09 efried I'm going to take at least the morning, possibly the day. Email if anything needs my attention. o/
14:36:20 gibi efried_pto: o/
15:06:58 openstackgerrit Stephen Finucane proposed openstack/nova master: Functional test for UnexpectedDeletingTaskStateError https://review.opendev.org/689278
15:06:58 openstackgerrit Stephen Finucane proposed openstack/nova master: Unplug VIFs as part of cleanup of networks https://review.opendev.org/663382
15:06:59 openstackgerrit Stephen Finucane proposed openstack/nova master: Fix incorrect vm and task state after build failure race https://review.opendev.org/689388
15:08:04 stephenfin gibi: Think you could take a look at ^ this week?
15:10:04 elod lyarwood: hi, do we need to wait for any patch in Rocky (for final release before Extended Maintenance transition?)
15:11:02 lyarwood elod: there's nothing from my side that can't wait until after EM
15:11:24 lyarwood elod: RH isn't shipping Rocky anymore FWIW
15:12:22 elod lyarwood: i see, good. Then I guess we could create a release patch
15:12:31 gibi stephenfin: queued
15:12:50 elod lyarwood: i can try to do that (i've never done before)
15:13:31 gibi stephenfin: I will start with those tomorrow (currently deep in a pike re-schedule bug downstream)
15:13:40 elod lyarwood: is that enough for the release or are there anything else that need to be done?
15:14:20 lyarwood elod: that's it AFAIK, efried_pto will need to bless it as PTL but that's about it
15:16:30 elod lyarwood: sounds good \o/ then i'll create the patch and add you then efried_pto as reviewer
15:18:00 lyarwood elod: awesome thanks
15:34:06 elod lyarwood: here it is: https://review.opendev.org/#/c/709554/ i think 18.2.4 will be fine, but please double check
15:53:22 bauzas efried_pto: stephenfin: thanks for reviewing https://review.opendev.org/#/c/589085/
15:53:50 bauzas FWIW, I haven't yet provided a ML thread about this because I also want to fix the resize revert
15:53:59 bauzas so, I'll provide two other changes
15:54:14 bauzas once it's done, I'll also provide a ML thread
17:27:03 openstackgerrit Merged openstack/nova master: Allow TLS ciphers/protocols to be configurable for console proxies https://review.opendev.org/679502
19:48:40 openstackgerrit melanie witt proposed openstack/nova stable/pike: Fix os-simple-tenant-usage result order https://review.opendev.org/709600
20:00:32 openstackgerrit melanie witt proposed openstack/nova stable/ocata: Fix os-simple-tenant-usage result order https://review.opendev.org/709603
#openstack-nova - 2020-02-25
00:49:49 sean-k-mooney dansmith: i think https://review.opendev.org/#/c/709641/2 will create a tempest full multi node job with a cyborg flavor. it will take a while too run but it should be close if it does not fully work so ill take a look at it agian tomorow
02:11:11 openstackgerrit wangjiajing proposed openstack/nova master: Perfect parameter of method. https://review.opendev.org/709652
03:18:09 openstackgerrit Merged openstack/nova master: Deprecate base rules in favor of new rules https://review.opendev.org/701624
05:28:38 openstackgerrit Arthur Dayne proposed openstack/nova master: libvirt:driver:Disallow AIO=native when 'O_DIRECT' is not available https://review.opendev.org/682772
05:29:03 openstackgerrit MIKI Nobuhiro proposed openstack/nova master: Enable instance to be booted with neutron SR-IOV ports https://review.opendev.org/709658
06:05:43 rm_work ileixe: hey, thanks for your review of my routed_segments filter
06:06:09 ileixe rm_work: :)
06:06:12 rm_work ileixe: do you think I should remove the doc/source/user/ change since it is intended for admin use only?
06:06:40 rm_work I was just following the previous set examples, i didn't see a case where a filter was not in both
06:07:37 rm_work and, I am not sure about how this filter would interact with Ironic, as we are not using it with Ironic (godaddy does not deploy Ironic, and Verizon Media has a TON of Ironic usage, but never needing this filter)
06:08:12 rm_work on the patch I mentioned: The main two use-cases are for the Octavia service to keep Loadbalancer VMs on the same segment for failover purposes, and for Live Migrate in routed-networks (I'll be pushing a followup patch for that soon). Users generally will not have a need to use this.
06:09:18 ileixe rm_work: um.. i think yes, if you thought it's only for the use-cases.
06:09:48 rm_work OK, then I will remove that user-facing doc piece
06:09:52 ileixe Do you plan to use the filter for extended usecases?
06:10:12 rm_work it could be used for any number of things, but as you point out, non-admin users can't see segment-ids
06:10:21 rm_work so it would be limited in usefulness
06:10:55 ileixe Yep then I think it's better to abstract the use for normal user
06:11:04 rm_work I could add a thing maybe to allow a user to pass in a port-id or subnet-id? and we could fetch the port/subnet and get the segment?
06:11:37 ileixe Do you see the previous work for routed network? (https://review.opendev.org/#/c/656885/)
06:11:39 rm_work is it possible to do this just the first time and cache that data in the request_spec?
06:11:40 ileixe Did you see
06:12:21 rm_work i looked briefly but it is a lot more complicated, and it seemed it was not moving forward really
06:13:02 rm_work it's been open for almost a year and now missed another spec freeze...
06:13:15 rm_work this filter seems like it should be a much simpler thing to merge
06:13:53 ileixe Honestly, I think maybe it's better to add the functionality like that (make resource provider and use request_spec from neutron) for normal user.
06:14:05 ileixe But for admin, I think simple filter is also userful
06:14:09 ileixe *useful
06:14:42 rm_work ok, so limit this filter for admin like it is now, and let people add more advanced user functionality to the patch you linked (or a followup)?
06:14:53 ileixe Yes that's what I thought
06:15:29 ileixe So I wonder how others operate now since it seems to be open question
06:15:37 ileixe Are you working with GoDaddy?
06:15:58 rm_work i was there for two years previously, but now I have been at Verizon Media for a year
06:16:09 rm_work coincidentally, both use routed networks everywhere :D
06:16:23 ileixe Yes, I assume both of them are using a lot
06:16:26 rm_work probably because both are very large deployments

Earlier   Later