Bug 1429465
| Summary: | Tempest init throwing traceback on latest RHOS11 puddle due to Octavia Tempest plugin bug | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Anshul Behl <abehl> |
| Component: | openstack-octavia | Assignee: | Nir Magnezi <nmagnezi> |
| Status: | CLOSED ERRATA | QA Contact: | Alexander Stafeyev <astafeye> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 11.0 (Ocata) | CC: | abehl, abregman, amuller, apevec, dsariel, dschoenb, ihrachys, lhh, lpeer, majopela, mburns, mkopec, nyechiel, oblaut, slinaber, ssbarnea |
| Target Milestone: | rc | ||
| Target Release: | 11.0 (Ocata) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-octavia-0.10.0-6.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-05-17 20:05:37 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
Anshul Behl
2017-03-06 12:37:41 UTC
This works fine if I don't install openstack-tempest-all, however we will have to check which tempest plugin is exactly causing the above issue. I tried without openstack-tempest-all and it desn't work for me. Is there an ETA? I seems it could be related to python-octavia-tests package. When the package was removed, tempest init finished without a traceback. Based on investigation, we found that tempest init cli is failing due to extra comma and wrong method used in python-octavia-tests (Octavia tempest plugin). Here is the upstream bug: https://bugs.launchpad.net/octavia/+bug/1681405 and related fix https://review.openstack.org/455260 is already merged in master and here is the stable/ocata backport patch: https://review.openstack.org/455405. So changing the component from openstack-tempest to openstack-octavia. According to the bug description we cannot currently run Tempest. The fix has already been merged in stable/ocata, the next step is to cherry pick to OSP 11. I don't see https://review.openstack.org/#/c/455405/ in any RPM we ship in any puddle. Looks like we'll need to cherry pick. This issue was reported in March and is still not fixed in latest puddles, can you please find out what is the scope of the issue? When does the issue manifest? (In reply to Assaf Muller from comment #6) > I don't see https://review.openstack.org/#/c/455405/ in any RPM we ship in > any puddle. Looks like we'll need to cherry pick. This issue was reported in > March and is still not fixed in latest puddles, can you please find out what > is the scope of the issue? When does the issue manifest? Yes. I cherry-picked it to see how CI behaves. I will also try to manually reproduce comment #0 and apply the fix to verify this is indeed the patch that resolves the issue. Hi Anshul, Could you please try to use this[1] package and report? [1] https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=552120 Latest package on Brew has a fix for this patch, it was rebased in. Fix is already in, flags not relevant anymore. Checked with # rpm -qa | grep openstack-tempest openstack-tempest-15.0.0-2.el7ost.noarch openstack-tempest-all-15.0.0-2.el7ost.noarch # rpm -qa | grep octavia python-octavia-0.10.0-6.el7ost.noarch python-octavia-tests-0.10.0-6.el7ost.noarch Works fine, bug can be verified. Thanks, Anshul Behl Thanks Anshul Hi Anshul, Do you have an option to verify this one with the same steps you saw this bug? BR Hi Alexander, I think this has been verified already by me, you can mark it as done accordingly. BR (In reply to Anshul Behl from comment #20) > Hi Alexander, > > I think this has been verified already by me, you can mark it as done > accordingly. > > BR Verified by Anshul Behl tnx 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:1245 |