| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-01-17 | |||
| 17:07:10 | bauzas | correct | |
| 17:07:19 | sean-k-mooney | so that is only used for openvz | |
| 17:07:43 | sean-k-mooney | that not what we do for qemu/kvm | |
| 17:08:21 | bauzas | indeed | |
| 17:08:22 | bauzas | https://github.com/openstack/nova/blob/b8a5961161da4a33c4d9c80e3025d9ff6eaf5326/nova/privsep/fs.py#L299-L302 | |
| 17:08:40 | sean-k-mooney | https://github.com/openstack/nova/blob/9e2ca01988b8889738eba3c9af336ad82d214e1b/nova/privsep/fs.py#L257-L259 | |
| 17:08:59 | bauzas | yup | |
| 17:09:10 | sean-k-mooney | so for qemu/kvm we default to vfat | |
| 17:09:11 | bauzas | anyway, the behaviour of None seems consistent | |
| 17:09:29 | sean-k-mooney | its virt driver and virt_type dependent | |
| 17:09:36 | sean-k-mooney | so ya a new option is what we want | |
| 17:09:41 | sean-k-mooney | well value | |
| 17:09:44 | bauzas | this is just saying "let the virt driver decide for me or the os type" | |
| 17:09:44 | sean-k-mooney | of unformatted | |
| 17:09:53 | sean-k-mooney | yep | |
| 17:10:04 | sean-k-mooney | ok will ill update the docs text to call that out | |
| 17:10:07 | bauzas | correct, we need an extra explicit value | |
| 17:10:32 | bauzas | if we just want an unformatted partition | |
| 17:10:33 | sean-k-mooney | i breifly looked at this this morning but didnt have time to fully get to the bottom of it | |
| 17:10:54 | sean-k-mooney | not even a partion a blank file | |
| 17:11:17 | sean-k-mooney | so if we set unformatted we will jsut get the empty disk | |
| 17:11:26 | sean-k-mooney | and its up to the user to partion and format it as they see fit | |
| 17:11:31 | sean-k-mooney | just like a blank cinder volume | |
| 17:11:42 | bauzas | I see | |
| 17:50:26 | opendevreview | Merged openstack/osc-placement master: Use pypi released version of placement in functional tests https://review.opendev.org/c/openstack/osc-placement/+/869755 | |
| 17:53:55 | sean-k-mooney | sigh... https://review.opendev.org/c/openstack/nova/+/869900 will never merge | |
| 18:14:14 | sean-k-mooney | bauzas: summerised usecase here https://blueprints.launchpad.net/nova/+spec/default-ephemeral-format-unformated | |
| 18:14:21 | sean-k-mooney | in the whiteboard | |
| 18:14:27 | bauzas | sean-k-mooney: all good thanks | |
| 18:43:02 | dansmith | yeah looking at the latest ceph-multistore oom, one of tempest's workers is using >900MiB of ram, where the others are <10 | |
| 18:43:09 | dansmith | so something is clearly going haywire | |
| 18:43:33 | dansmith | gmann: you're aware of this right? | |
| 18:43:52 | dansmith | I assume if you knew of any recent tempest changes that could be responsible, you'd have spoken up by now :) | |
| 18:57:01 | gmann | dansmith: no, I cannot recall any relevant change happened in tempest | |
| 18:57:15 | dansmith | yeah I looked too, and nothing much lately | |
| 18:59:49 | gmann | and no stestr version change recently | |
| 19:01:33 | dansmith | I'm trying to stack for the first time this year so I can repro and I'm getting this failure to install pbr.build when it tries to install os-testr | |
| 19:01:38 | dansmith | ModuleNotFoundError: No module named 'pbr.build' | |
| 19:01:45 | dansmith | is this known? | |
| 19:01:52 | dansmith | gmann: ^ | |
| 19:03:33 | gmann | no, i did not see this before | |
| 19:04:01 | sean-k-mooney | stephenfin: fixed a pbr issues recently not sure if its releaed | |
| 19:05:22 | sean-k-mooney | this https://review.opendev.org/q/topic:pep-517 but that looks more tox 4 related | |
| 19:06:46 | dansmith | blargh | |
| 19:06:56 | dansmith | I can install os-testr without constraints, but it fails like this otherwise | |
| 19:07:08 | sean-k-mooney | wait os-testr | |
| 19:07:11 | gmann | yeah I think those were tox4 related | |
| 19:07:13 | sean-k-mooney | what is using that | |
| 19:07:22 | dansmith | sean-k-mooney: +./stack.sh:main:803 pip_install -U os-testr | |
| 19:07:24 | sean-k-mooney | we shoud not be using os-testr anywhere anymore | |
| 19:07:35 | sean-k-mooney | everthing should be using stestr | |
| 19:07:41 | gmann | that is installed successfully in gate I think that is using constraint? | |
| 19:07:59 | gmann | https://zuul.opendev.org/t/openstack/build/0fc9dc8ecbe748498c941c6f21cbf057/log/job-output.txt#4367 | |
| 19:08:23 | dansmith | yeah I dunno why I can't install it | |
| 19:08:31 | sean-k-mooney | its in uc ya https://opendev.org/openstack/requirements/src/branch/master/openstack_requirements/tests/files/upper-constraints.txt#L359 | |
| 19:08:37 | dansmith | unless it's a mirror sync thing? | |
| 19:08:57 | sean-k-mooney | https://opendev.org/openstack/devstack/src/branch/master/stack.sh#L803 | |
| 19:09:04 | sean-k-mooney | comment ou tthat line | |
| 19:09:26 | gmann | not this week but last week i stack successfully | |
| 19:09:53 | clarkb | note contraints don't pick what is installed. Only what version to install if something is to be installed | |
| 19:09:56 | dansmith | sean-k-mooney: heh, yeah, I could but.. | |
| 19:10:27 | sean-k-mooney | clarkb: yep i know just pointing out that it would be constrained if it was installed for other projects | |
| 19:10:39 | dansmith | I purged pbr and os-testr locally, which might have gotten past it | |
| 19:10:59 | sean-k-mooney | pip_install -U os-testr | |
| 19:11:04 | sean-k-mooney | so that is unconstiaed in devstack | |
| 19:11:18 | sean-k-mooney | unless pip_install in devstack add uc by default | |
| 19:12:23 | gmann | https://zuul.opendev.org/t/openstack/build/0fc9dc8ecbe748498c941c6f21cbf057/log/job-output.txt#4367 | |
| 19:12:37 | dansmith | sean-k-mooney: it does | |
| 19:12:47 | dansmith | I could install it myself without uc | |
| 19:12:58 | dansmith | but just purging those two packages locally seems to have worked | |
| 19:13:06 | dansmith | so maybe some not-so-correct version deps | |
| 19:13:28 | sean-k-mooney | what os are you using out of interest | |
| 19:13:29 | gmann | maybe | |
| 19:13:51 | dansmith | sean-k-mooney: focal | |
| 19:13:55 | sean-k-mooney | you said you had not stacked this year yet is it 20.04 | |
| 19:14:08 | sean-k-mooney | ok that should also work | |
| 19:14:21 | sean-k-mooney | well for the next 4-6 weeks | |
| 19:14:54 | gmann | focal should all work for latest master/constraints | |
| 19:15:03 | sean-k-mooney | yep | |
| 19:15:20 | sean-k-mooney | i just ment that after RC1 and we reopen master for bobcat | |
| 19:15:30 | sean-k-mooney | then it wont be in the testing runtime | |
| 19:15:35 | sean-k-mooney | nor wil python 3.8 | |
| 19:15:45 | sean-k-mooney | so it will proably be fine but it could start breaking | |
| 20:02:57 | opendevreview | Sofia Enriquez proposed openstack/nova master: Check NFS protocol https://review.opendev.org/c/openstack/nova/+/854030 | |
| 20:05:22 | opendevreview | Dan Smith proposed openstack/nova master: WIP: Detect host renames and abort startup https://review.opendev.org/c/openstack/nova/+/863920 | |
| #openstack-nova - 2023-01-18 | |||
| 10:01:01 | ierdem | Hi folks, is there any way to boot a signed image from volume? I am testing image validation, I can create VM by using signed images on ephemeral disks but when I try boot from volume, it throws an excepiton (https://paste.openstack.org/show/blZen5ID7OIbi47TN8ib/). I am currently working on OpenStack Ussuri, and image backend is Ceph | |
| 10:10:11 | bauzas | gibi: so, there are many ways tricking stestr scheduling | |
| 10:10:43 | bauzas | gibi: but given we directly call tempest which eventually calls stestr, the quickiest way to change the test scheduling is about renaming the testname | |
| 10:11:09 | bauzas | https://stestr.readthedocs.io/en/latest/MANUAL.html#test-scheduling | |
| 10:11:26 | bauzas | "By default stestr schedules the tests by first checking if there is any historical timing data on any tests. It then sorts the tests by that timing data loops over the tests in order and adds one to each worker that it will launch. For tests without timing data, the same is done, except the tests are in alphabetical order instead of based on timing data. If a group regex is used the same algorithm is used with groups instead of | |
| 10:11:26 | bauzas | individual tests." | |
| 10:20:12 | bauzas | gibi: https://review.opendev.org/c/openstack/tempest/+/870913 | |
| 10:20:44 | bauzas | gibi: could I modify https://review.opendev.org/c/openstack/nova/+/869900/ to be Depending on ^ ? | |
| 10:24:25 | gibi | lets keep https://review.opendev.org/c/openstack/nova/+/869900/ alone. as I want to land that regardless of our troubleshooting here. As I think some of the other problems might go away after we remove the excessive logging by that. | |
| 10:25:32 | gibi | about https://review.opendev.org/c/openstack/tempest/+/870913 why we are trying to move the test to the front? I thought we wanted to moved it later or even disable it temporarily to see if other tests are triggering the same OOM behavior and hence trying to establish a pattern causing the OOM | |
| 10:32:25 | bauzas | gibi: OK, then I'll add a DNM on nova, np | |
| 10:32:45 | bauzas | gibi: good question, I was wanting to see whether it was due to this test or not | |
| 10:33:03 | bauzas | if we call it first, and if this is due to this test, it would be killed earlier, right? | |
| 10:39:53 | opendevreview | Sylvain Bauza proposed openstack/nova master: DNM: Testing the killed test https://review.opendev.org/c/openstack/nova/+/870924 | |
| 10:44:42 | kashyap | gibi: Can you have a quick look at this workaround patch when you can (for a change all CI have passed): https://review.opendev.org/c/openstack/nova/+/870794 | |