| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-10-12 | |||
| 16:53:22 | bauzas | gmann: you had thoughts ? | |
| 16:53:29 | gibi | and I do belive this causing https://opendev.org/zuul/zuul-jobs/commit/c02c28a982da8d5a9e7b4ca38d30967f6cd1531d | |
| 16:53:34 | gmann | I think this is because of https://opendev.org/zuul/zuul-jobs/commit/c02c28a982da8d5a9e7b4ca38d30967f6cd1531d | |
| 16:53:35 | gibi | that we include the regexp to the call | |
| 16:53:41 | gmann | gibi: ah you are fast | |
| 16:53:59 | gibi | we simply not need the regexp in that call | |
| 16:54:03 | gibi | or we need to quote it | |
| 16:54:30 | gibi | but I don't know how to feed this back to zuul | |
| 16:54:49 | gibi | gmann: :) | |
| 16:55:12 | gmann | I think bext way is not to include the test regex in tox_extra_args and instead add it as part of command itself | |
| 16:55:15 | gmann | best | |
| 16:55:34 | gmann | let me try that | |
| 16:56:14 | gibi | gmann: ack, we can even left out the regexp param that is not needed for the --showconfig call I think | |
| 16:56:35 | bauzas | gmann: gibi: thanks for the findings | |
| 16:56:46 | gmann | yeah, tox_extra_args purpose is completely separate then test regex | |
| 16:56:46 | gibi | I have nothing else for today | |
| 16:56:52 | gibi | gmann: ack | |
| 16:57:09 | sean-k-mooney | we normally do that with posargs like this https://github.com/openstack/placement/blob/master/tox.ini#L40 | |
| 16:57:21 | gmann | yeah | |
| 16:57:40 | sean-k-mooney | then invoke tox like "tox -e fucntional -- <regex goes here>" | |
| 16:59:04 | sean-k-mooney | i think we can likely close the meeting there | |
| 16:59:14 | bauzas | yeah I was about to say | |
| 16:59:20 | bauzas | we can continue off meeting | |
| 16:59:36 | bauzas | let me call it done | |
| 16:59:40 | opendevmeet | Meeting ended Tue Oct 12 16:59:40 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 16:59:40 | bauzas | #endmeeting | |
| 16:59:41 | opendevmeet | Log: https://meetings.opendev.org/meetings/nova/2021/nova.2021-10-12-16.00.log.html | |
| 16:59:41 | opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/nova/2021/nova.2021-10-12-16.00.txt | |
| 16:59:41 | opendevmeet | Minutes: https://meetings.opendev.org/meetings/nova/2021/nova.2021-10-12-16.00.html | |
| 16:59:46 | bauzas | thanks all | |
| 16:59:56 | gibi | bauzas: thanks! | |
| 17:00:15 | sean-k-mooney | gibi: for https://bugs.launchpad.net/nova/+bug/1946339 i think we are getting to here but i never see log lings corresponding to https://github.com/openstack/nova/blob/a8d3ab2513c39aeac3393b2154988316dfa2db3a/nova/tests/functional/test_servers_resource_request.py#L2568-L2574 | |
| 17:00:25 | bauzas | gibi: thanks for spotting the root cause while I was deblatering for some paperwork :) | |
| 17:06:38 | gibi | sean-k-mooney: yeah but that becuase we fail at the assert https://github.com/openstack/nova/blob/a8d3ab2513c39aeac3393b2154988316dfa2db3a/nova/tests/functional/test_servers_resource_request.py#L2560\ | |
| 17:08:35 | sean-k-mooney | are you sure about that we might be | |
| 17:08:46 | sean-k-mooney | i did not see that in the log as explcitly failing | |
| 17:08:52 | sean-k-mooney | did i miss that | |
| 17:09:15 | gibi | I'm looking at this https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_b15/713498/27/check/nova-tox-functional-py38/b1582a8/job-output.txt | |
| 17:09:23 | gibi | it has | |
| 17:09:24 | gibi | 2021-10-08 01:21:54.733579 | ubuntu-focal | testtools.matchers._impl.MismatchError: 'UnexpectedResourceProviderNameForPCIRequest' != 'DBNonExistentTable' | |
| 17:09:59 | sean-k-mooney | ah right | |
| 17:11:38 | sean-k-mooney | error_notification = self.notifier.wait_for_versioned_notifications( | |
| 17:11:39 | sean-k-mooney | 'compute.exception')[0] | |
| 17:11:44 | sean-k-mooney | we are just takign the first error | |
| 17:11:45 | gibi | yepp | |
| 17:11:57 | gibi | I have to drop for today | |
| 17:12:03 | sean-k-mooney | could it be the order of the excption could change and we get more then one | |
| 17:12:08 | sean-k-mooney | ok | |
| 17:12:09 | gibi | I pushed a small patch with an extra log seeing what triggers the reschedule | |
| 17:12:26 | gibi | https://review.opendev.org/c/openstack/nova/+/813674 | |
| 17:12:38 | sean-k-mooney | im not sure there is a reschdule | |
| 17:12:48 | sean-k-mooney | but cool lets see what that shows | |
| 17:12:53 | sean-k-mooney | ill play with a bit locally | |
| 17:13:19 | gibi | this line in the stack trace File "/home/zuul/src/opendev.org/openstack/nova/nova/compute/manager.py", line 2263, in _do_build_and_run_instance | |
| 17:13:26 | gibi | points to a reschedule for me | |
| 17:14:30 | gibi | anyhow leaving now. thanks for the shared thinking | |
| 17:14:35 | gibi | o/ | |
| 17:19:45 | sean-k-mooney | hum | |
| 17:19:48 | sean-k-mooney | ERROR: Cannot install jsonschema>=3.2.0, openstack-placement==1.0.0 and openstack-placement==1.1.0 because these package versions have conflicting dependencies. | |
| 17:19:50 | sean-k-mooney | The conflict is caused by: | |
| 17:19:52 | sean-k-mooney | The user requested jsonschema>=3.2.0 | |
| 17:19:54 | sean-k-mooney | openstack-placement 1.1.0 depends on jsonschema<3.0.0 and >=2.6.0 | |
| 17:19:56 | sean-k-mooney | The user requested jsonschema>=3.2.0 | |
| 17:19:58 | sean-k-mooney | openstack-placement 1.0.0 depends on jsonschema<3.0.0 and >=2.6.0 | |
| 17:20:00 | sean-k-mooney | The user requested (constraint) jsonschema===3.2.0 | |
| 17:20:11 | sean-k-mooney | that was form trying to run nova func test on master | |
| 17:20:17 | sean-k-mooney | it cant create the pip env | |
| 17:21:35 | sean-k-mooney | placmenet required >=3.2.0 | |
| 17:21:36 | sean-k-mooney | https://github.com/openstack/placement/blob/master/requirements.txt#L10 | |
| 17:23:00 | sean-k-mooney | which is the same as uc https://github.com/openstack/requirements/blob/master/upper-constraints.txt#L547 | |
| 17:24:18 | sean-k-mooney | oh | |
| 17:24:30 | sean-k-mooney | this is the same suds-jurko issue | |
| 17:25:31 | sean-k-mooney | ok i just need to locally comment out oslo.vmware in our test-requirements.txt until that is fixed | |
| 17:33:17 | opendevreview | Ghanshyam proposed openstack/nova master: Define new functional test tox env for placement gate to run https://review.opendev.org/c/openstack/nova/+/813679 | |
| 17:36:12 | opendevreview | Ghanshyam proposed openstack/placement master: Use 'placement-nova-functional-py38' tox env for placement nova job https://review.opendev.org/c/openstack/placement/+/813680 | |
| 18:11:13 | opendevreview | Ghanshyam proposed openstack/nova master: Define new functional test tox env for placement gate to run https://review.opendev.org/c/openstack/nova/+/813679 | |
| 18:13:23 | opendevreview | Ghanshyam proposed openstack/nova master: Define new functional test tox env for placement gate to run https://review.opendev.org/c/openstack/nova/+/813679 | |
| 19:06:01 | gmann | gibi: bauzas these fix the placement-nova functional job - https://review.opendev.org/q/topic:%22fix-placement-gate%22+(status:open%20OR%20status:merged) | |
| 19:08:30 | opendevreview | sean mooney proposed openstack/nova master: [WIP] adress intermitent failure of functional tests https://review.opendev.org/c/openstack/nova/+/813695 | |
| 19:09:15 | sean-k-mooney | gibi: i think ^ would fix https://bugs.launchpad.net/nova/+bug/1946339 | |
| 21:09:00 | simondodsley | How would I achieve full disaster recovery of nova instances from one OS cluster to another? I can replicate Cinder volumes to another cluster (sort of), but I can't find a way to replicate the nova instances? I know Stratoscale used to do something like this, but they are dead now. Any other ways to do this? | |
| 21:21:49 | melwitt | simondodsley: I can't answer your question, I'm sure there are a lot of ways to do it, but you might get some ideas from this project https://docs.openstack.org/freezer/latest/ this is/was the openstack project for disaster recovery. it hasn't had activity for the past year or so, it may no longer be maintained https://github.com/openstack/freezer-dr | |
| 21:53:46 | opendevreview | Ade Lee proposed openstack/nova master: Add check job for FIPS https://review.opendev.org/c/openstack/nova/+/790519 | |
| 22:04:50 | gmann | melwitt: dansmith please check these two to unblock the placement gate https://review.opendev.org/q/topic:%22fix-placement-gate%22+(status:open%20OR%20status:merged) | |
| 22:29:38 | melwitt | gmann: hm, not sure I understand the solution. it doesn't seem right to define any placement env in the nova repo? I also don't understand why the current setup is failing | |
| 22:31:01 | gmann | melwitt: as it is used in nova-placement job we can move the job definition also on nova side but that run only in placement | |
| 22:32:05 | melwitt | gmann: I don't understand why the current thing is no longer working, it was intended to be able to use the nova-tox-functional-py38 in other projects right? as a parent job? | |
| 22:32:32 | melwitt | why do we need to add nova-placement in the nova or placement repo now? | |
| 22:35:28 | melwitt | let me read the commit message and referenced zuul commit again | |
| 22:35:30 | gmann | melwitt: placement-nova-tox-functional-py38 job is only needed to skip the sample and db tests otherwise same as nova-tox-functional-py38 | |
| 22:35:52 | gmann | and I think these tests are skipped as they do not use placement_fixture | |
| 22:36:00 | melwitt | yeah, I see that ... trying to understand the bug and why we can't use the parent job as intended | |
| 22:37:17 | melwitt | so a recent commit added tox_extra_args back, apparently previously it wasn't being used even though it was defined in the placement .zuul.yaml I guess | |
| 22:37:29 | melwitt | and now that it's being used, there's a syntax error happening | |
| 22:37:39 | gmann | melwitt: it is now started failing because test regex to skip the test is defined in tox_extra_args which is now added in 'Get tox envlist config; tasks https://opendev.org/zuul/zuul-jobs/commit/c02c28a982da8d5a9e7b4ca38d30967f6cd1531d | |
| 22:37:48 | gmann | yes | |
| 22:38:29 | gmann | I do not think tox_extra_args should be used for tests regex formation instead we should define the test path/regex etc in tox env command itself | |
| 22:39:08 | gmann | and as tox env has to live in nova and job is defined in placement, we need these two repo changes to fix it | |
| 22:39:44 | melwitt | oh... at least to me it looks like it makes sense for the regex string to be an extra arg to tox | |
| 22:40:36 | gmann | but that fail when we take tox_extra_args in tox env with no tests run like this https://opendev.org/zuul/zuul-jobs/commit/c02c28a982da8d5a9e7b4ca38d30967f6cd1531d | |