containers-multinode in stein is failing most of the NetworkBasicOps tests

[wes hayutin]

https://6b63700c3069ae489bdc-bb4a5eff936c7c436b2d6f585c15ca69.ssl.cf2.rackcdn.com/periodic/opendev.org/openstack/tripleo-quickstart-extras/master/tripleo-ci-centos-7-containers-multinode-stein/df61f01/logs/undercloud/var/log/tempest/stestr_results.html

https://e29864d8017a43b5dd67-658295aea286d472989a3acc71bbfe02.ssl.cf5.rackcdn.com/periodic/opendev.org/openstack/tripleo-ci/master/tripleo-ci-centos-7-containers-multinode-stein/fae0b86/logs/undercloud/var/log/tempest/stestr_results.html

https://zuul.openstack.org/builds?job_name=tripleo-ci-centos-7-containers-multinode-stein

Perhaps we add some tests to featureset010 and bug and skip the failing tests in stein?

[Rabi Mishra (rabi)]

I suspect this is happening after we bumped cirros image from 0.4 to 0.5.2 with https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/785575

    9.622237] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[ 9.626346] Please append a correct "root=" boot option; here are the available partitions:
[ 9.630361] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 9.636865] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.3.0-26-generic #28~18.04.1-Ubuntu
[ 9.641243] Hardware name: RDO OpenStack Compute, BIOS 1.11.0-2.el7 04/01/2014
[ 9.646542] Call Trace:
[ 9.650449] dump_stack+0x6d/0x95
[ 9.652654] panic+0xfe/0x2d4
[ 9.653897] mount_block_root+0x1f4/0x2db
[ 9.656515] ? set_debug_rodata+0x17/0x17
[ 9.659383] mount_root+0x38/0x3a
[ 9.661726] prepare_namespace+0x139/0x18e
[ 9.664803] kernel_init_freeable+0x245/0x26d
[ 9.667451] ? rest_init+0xb0/0xb0
[ 9.669304] kernel_init+0xe/0x110
[ 9.671465] ret_from_fork+0x35/0x40
[ 9.674373] Kernel Offset: 0xda00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[ 9.682789] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

[Rabi Mishra (rabi)]

Stein and before is using python2-tempestconf-2.4.0

And the flavors don't have minimum ram required[1].

[1] https://opendev.org/osf/python-tempestconf/src/tag/2.4.0/config_tempest/constants.py#L30

[Rabi Mishra (rabi)]

Why didn't we run stein/before jobs with https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/785575 to not get these issues?

[Rabi Mishra (rabi)]

RDO patch https://review.rdoproject.org/r/c/rdoinfo/+/33646

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/790377

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/790377
Committed: https://opendev.org/openstack/tripleo-quickstart-extras/commit/1cc28a6886633c53ab163e2c89101f2fbaac0744
Submitter: "Zuul (22348)"
Branch: master

commit 1cc28a6886633c53ab163e2c89101f2fbaac0744
Author: Chandan Kumar (raukadah) <email address hidden>
Date: Mon May 10 13:06:10 2021 +0530

    Set flavor_min_mem as a tempestconf overrides

    For older release like queens and stein, tempestconf-2.4.0
    is used and in all the branches we are using cirros-0.5.2
    image which requires DEFAULT_FLAVOR_RAM to 128 not 64( which
    is defined in older release of tempestconf).

    We cannot bump the tempestconf version to latest as older
    branches depends on py2 and tempestconf uses py3.

    In order to fix the issue, we can pass the
    flavor_min_mem value via tempestconf profile to 128 to
    fix the issue.

    https://review.rdoproject.org/r/c/testproject/+/33649
    getting tested here.

    Closes-Bug: #1927739

    Signed-off-by: Chandan Kumar (raukadah) <email address hidden>
    Change-Id: I21824bc14f4c1d55235d7b80870bac7f7edff5d4