Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2023-01-13
17:31:03 sean-k-mooney httplib_response = conn.getresponse(buffering=True)
17:31:05 sean-k-mooney TypeError: getresponse() got an unexpected keyword argument 'buffering'
17:31:26 sean-k-mooney so it looks likethere si an issue wit urllib3
17:31:28 sean-k-mooney as well
17:31:31 kashyap Right, the first one is the cause of the 2nd one
17:31:52 kashyap (If I'm parsin it correctly)
17:32:44 sean-k-mooney i dont see how urllib3 is for http requests not the db unless this is form parsing the db connection url
17:35:25 sean-k-mooney oh look urllib3 had a release 2 days ago...
17:37:03 sean-k-mooney hum ok but we have not change uc to allow it in 4 months
17:38:39 kashyap You mean upper-constraints?
17:38:54 kashyap Thanks for digging that.
17:39:19 sean-k-mooney ya so there has been a release but i dont think its in use
17:39:34 sean-k-mooney upper-constraits is still clamping to an older one on master
17:39:37 kashyap sean-k-mooney: As of now, just to show the "randomness" of the failures: all the jobs that failed in the previous run succeeded now - nova-live-migration, nova-multi-cell, nova-ovs-hybrid-plug, and nova-grenade-multinode jobs
17:39:51 kashyap (Except the new one above in the tox-functional-py38)
17:40:02 kashyap sean-k-mooney: Should we bump it?
17:40:09 kashyap Does it make sense to do so?
17:40:28 sean-k-mooney we have automation to bump it
17:40:48 sean-k-mooney that runs a set of jobs to check compatiablity with most of the projects
17:41:32 kashyap Oh, right; I forgot the bot; that's much safer
17:45:11 sean-k-mooney it ran with urllib3-1.26.12
17:45:27 sean-k-mooney which is what i have locally and that works
17:45:44 sean-k-mooney my guess isthe two exceptions are somehow related
17:45:58 sean-k-mooney but i can see show directly
18:51:52 opendevreview Dan Smith proposed openstack/nova master: Persist existing node uuids locally https://review.opendev.org/c/openstack/nova/+/863918
18:51:53 opendevreview Dan Smith proposed openstack/nova master: Make resource tracker use UUIDs instead of names https://review.opendev.org/c/openstack/nova/+/863919
18:51:53 opendevreview Dan Smith proposed openstack/nova master: WIP: Detect host renames and abort startup https://review.opendev.org/c/openstack/nova/+/863920
20:07:26 opendevreview Artom Lifshitz proposed openstack/nova master: Microversion 2.94: FQDN in hostname https://review.opendev.org/c/openstack/nova/+/869812
20:37:44 gmann sean-k-mooney: bauzas: gibi: reminder for osc-placement gate fixes review https://review.opendev.org/q/I4e3e5732411639054baaa9211a29e2e2c8210ac0
21:34:49 sean-k-mooney[m] gmann im not sure that is what we should be doing
21:35:39 sean-k-mooney[m] i was suggesting continng to use master on master and using the stable branch release or stable
21:36:21 gmann sean-k-mooney[m]: ok for stable. I was thinking we do the same way the Nova testing on master
21:37:02 sean-k-mooney[m] im not sure what that iss of the top of my head but ill take a look
21:37:27 gmann ok. let me know and I can update those accordingly.
21:38:21 sean-k-mooney[m] i guess if it works as it says in the comment that is ok
21:38:36 sean-k-mooney[m] i dont know how that works however
21:39:02 sean-k-mooney[m] i would not expect that to be how it works unless we are doing something special with tox siblings in the jobs
21:39:41 sean-k-mooney[m] the tox ini does not hve the described behavior on its own
21:39:55 clarkb siblings only take effect if you set the project as a required project on the zuul job (that pulls in the git repo and the tox role uses it as a single to install it from source)
21:40:45 sean-k-mooney[m] right so osc-placemnt would need to declarae placemnt as a required project
21:41:05 sean-k-mooney[m] and we would need the tox siblings stuff to overried whats in the tox ini
21:41:19 sean-k-mooney[m] and install placemtn form the git repo prepared by zuul
21:41:41 sean-k-mooney[m] is that how we have the functional job configured in nova/osc-placement
21:41:57 gmann if we change it to test with master only then we should have another job to test with the released version
21:42:20 sean-k-mooney[m] well its testing with master only now
21:42:24 gmann as comments says, we can test the master placement by replacing the deps line
21:42:38 gmann yes, in osc-placement and released version in nova
21:42:47 sean-k-mooney[m] so your propeosing change to using the released version
21:42:56 sean-k-mooney[m] yep
21:43:07 sean-k-mooney[m] so it would be nice for depends-on to work
21:43:19 sean-k-mooney[m] and in generall im fine with used the released verison
21:43:40 sean-k-mooney[m] but im questioning if the tox job in osc-placment will give the depends on behavior today
21:43:58 gmann While doing it for stable branch and I checked how Nova does I thought of doing the same for osc-placement also
21:45:15 sean-k-mooney[m] ok so we have the required projec tin the zuul.yaml
21:45:16 sean-k-mooney[m] https://github.com/openstack/osc-placement/blob/master/.zuul.yaml
21:45:38 gmann yeah
21:45:45 sean-k-mooney[m] yep i know i was just checking if we were using the jobs from the default template or if we had already overriden it
21:46:00 sean-k-mooney[m] since i did not see that in the patch you linked
21:46:11 sean-k-mooney[m] i was expecting both in the same patch
21:47:58 sean-k-mooney[m] ok this should be fine as is
21:48:59 gmann ack
21:52:55 clarkb I'm not sure the comment is correct though since siblings will be used
21:53:10 clarkb it will always be the latest version of the branch in the gate not the release
23:22:37 dansmith cripes, we're never going to get the rpc spam thing landed
23:22:44 dansmith seen this a few times now as well: https://zuul.opendev.org/t/openstack/build/f5aa5edd4d354c2685fc1f3e13d0ef77
23:22:59 dansmith saying one of the tempest workers crashed
23:23:06 dansmith seems unlikely to me
#openstack-nova - 2023-01-14
01:55:42 opendevreview Merged openstack/nova master: libvirt: Add encryption support to qemu-img create command https://review.opendev.org/c/openstack/nova/+/826752
01:55:50 opendevreview Merged openstack/nova master: libvirt: Report ephemeral encryption traits based on imagebackend https://review.opendev.org/c/openstack/nova/+/826753
13:11:02 opendevreview Artom Lifshitz proposed openstack/nova master: Microversion 2.94: FQDN in hostname https://review.opendev.org/c/openstack/nova/+/869812
13:18:54 opendevreview Artom Lifshitz proposed openstack/nova master: Microversion 2.94: FQDN in hostname https://review.opendev.org/c/openstack/nova/+/869812
#openstack-nova - 2023-01-16
07:39:50 opendevreview Merged openstack/nova stable/ussuri: [compute] always set instance.host in post_livemigration https://review.opendev.org/c/openstack/nova/+/864007
07:42:23 opendevreview Amit Uniyal proposed openstack/nova stable/train: Adds a repoducer for post live migration fail https://review.opendev.org/c/openstack/nova/+/863806
07:42:24 opendevreview Amit Uniyal proposed openstack/nova stable/train: [compute] always set instance.host in post_livemigration https://review.opendev.org/c/openstack/nova/+/864055
08:48:10 gibi dansmith: I saw such interpreter crashes before. It is really a segfault of the python interpreter based on dmesg. Unfortunately it happens randomly afais.
08:53:47 gibi dansmith: hm, but this time it was OOM
09:16:02 viks__ hi, is there a way to set say `/var/lib/nova1` instead of `/var/lib/nova` ? i could not find any configuration to do that in `nova.conf`
09:43:08 gibi viks__: https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.instances_path and https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.state_path are the way I think
09:48:43 viks__ gibi: thanks... got it.. actually i was searching for `/var/lib/nova` in sample conf so i did not find it before... anyway can i set multiple values for it say for eg: `/var/lib/nova,/var/lib/nova1` where they are differnt 2 mount points ?
09:50:54 gibi viks__: you can only set a single path
09:52:48 viks__ gibi: ok.. thanks.. one more thing.. when to use `instances_path` if `state_path` itself will do the job? any suggestions?
09:55:18 gibi viks__: if you want to store the instance local disks in a different place then the nova lock files then instances_path will let you separate the instance disk from the lock files
10:04:32 viks__ gibi: ok.. thanks
10:14:46 opendevreview Sahid Orentino Ferdjaoui proposed openstack/nova master: compute: enhance compute evacuate instance to support target state https://review.opendev.org/c/openstack/nova/+/858383
10:14:46 opendevreview Sahid Orentino Ferdjaoui proposed openstack/nova master: api: extend evacuate instance to support target state https://review.opendev.org/c/openstack/nova/+/858384
10:32:43 gibi dansmith: opened the bug for the OOM https://bugs.launchpad.net/nova/+bug/2002951
10:54:17 sean-k-mooney viks__: if you cant use a single mount path for soem reason you could fake it using lvm voluems to combine multipel disk into one or do it at thte file system level instead of block level using mergerfs https://manpages.ubuntu.com/manpages/impish/man1/mergerfs.1.html
10:55:38 sean-k-mooney nova need everything to be in a single directory on the file system but we dont really care where that folder comes form or how you created it
10:56:31 bauzas auniyal: so, about what we discussed for https://bugs.launchpad.net/nova/+bug/1996732
10:57:11 bauzas auniyal: what you need to do first is to check how to look at the host_state.failed_builds value
10:58:16 sean-k-mooney all you need to do is add a new exception that inherits form the existign one and then where we incremente the value skip it if its the new excpetion
10:58:36 sean-k-mooney the late affinity failure will use the new expction and not be counted
10:58:54 sean-k-mooney but because it inherits form the orginal any clean up that was previousl done will still be done
10:59:36 sean-k-mooney so ya one of the first steps is find out where we modify the build failure value
10:59:51 sean-k-mooney and also where we raise the current excetption for the affinity check
11:00:29 sean-k-mooney after that you can add the new expction and modify both to use it
11:00:34 bauzas sean-k-mooney: the concern of auniyal was how to test iut
11:04:06 sean-k-mooney out side of functional tests it would be tricky to do end to end but unit test for the excption raising and functional test for the end to end interaction. there is no point doing tepest type testing since fault inject will be needed and that is not somethign tempest is good for
11:06:07 bauzas sean-k-mooney: I think it's possible to have a functest for it
11:06:19 bauzas but we need to be able to verify the stats

Earlier   Later