Bug 1450677
Summary: | Fail to execute neutron functional metadata_proxy tests | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Arie Bregman <abregman> |
Component: | openstack-neutron | Assignee: | Daniel Alvarez Sanchez <dalvarez> |
Status: | CLOSED ERRATA | QA Contact: | Toni Freger <tfreger> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 12.0 (Pike) | CC: | abregman, amuller, chrisw, dalvarez, ihrachys, mburns, nyechiel, sclewis, srevivo |
Target Milestone: | Upstream M2 | Keywords: | AutomationBlocker, Triaged |
Target Release: | 12.0 (Pike) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-neutron-11.0.0-0.20170521040619.3f2e22a.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-13 21:27:05 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Arie Bregman
2017-05-14 14:53:19 UTC
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release. Is 'haproxy' dependency not installed in functional testing? It is a dep in the spec file. In test log, we see: InvalidUserOrGroupException: Invalid user/uid: '65534' Apparently the nobody user is not there, or it does have a different number. Current neutron functional tests assumes that there's a user with uid 65534 [0]. This, apparently, is always true upstream for the ubuntu xenial deployment in the gate. However, it's not in RHEL as the uuid 65534 is created by package nfs-utils which is not installed by default in our CI [1]: $ rpm -q --scripts nfs-utils [...] # Create nfsnobody uid as long as it does not already exist. cat /etc/passwd | cut -d':' -f 1 | grep --quiet nfsnobody 2>/dev/null if [ "$?" -eq 1 ]; then /usr/sbin/useradd -l -c "Anonymous NFS User" -r -g 65534 \ -s /sbin/nologin -u 65534 -d /var/lib/nfs nfsnobody >/dev/null 2>&1 || : else /usr/sbin/usermod -u 65534 -g 65534 nfsnobody >/dev/null 2>&1 || : We should modify the functional tests so that it doesn't make that assumption. I'll open a bug in launchpad and try to come up with a fix. [0] https://github.com/openstack/neutron/blob/stable/ocata/neutron/tests/functional/agent/l3/test_metadata_proxy.py#L133 [1] https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DFG/view/network/view/neutron/job/DFG-network-neutron-dsvm-functional-rhos/240/artifact/infrared/9795f228d997b171ef31983a4c7bf782-tester-0/home/cloud-user/logs/installed-rpms.log Apparently, nfs-utils package gets installed as a dependency for libvirt: $ repoquery --requires --recursive --resolve libvirt | grep nfs-utils nfs-utils-1:1.3.0-0.33.el7_3.x86_64 Once nfs-utils is installed it creates the nfsnobody user with uid 65534 that allows functional tests to pass. In our CI we're not installing libvirt for functional tests [0] and since it's not a dependency either I guess we shouldn't relay on this uid to exist on the system for the tests. [0] https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DFG/view/network/view/neutron/job/DFG-network-neutron-dsvm-functional-rhos/240/artifact/infrared/9795f228d997b171ef31983a4c7bf782-tester-0/home/cloud-user/logs/installed-rpms.log nfs-utils has been added as a requirement to python-neutron-tests [0] and it's already in RDO promotion that happened today. It should be auto-imported to OSP in a few days. I'll update the fields accordingly. [0] https://review.rdoproject.org/r/#/c/6708/ The fix landed in RDO, we are waiting for OSP sync to happen to close the bug. Verified per comment 12. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462 |