Actually this is a regression in devstack introduced by
https://review.openstack.org/636078 , but your workaround seems sensible
anyway. But since this will affect other jobs as well, we should fix it
in devstack, too.
** Also affects: devstack
Importance: Undecided
Status: New
** Changed in: devstack
Status: New => Triaged
** Changed in: devstack
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1822453
Title:
neutron-tempest-plugin-designate-scenario is broken
Status in devstack:
Triaged
Status in neutron:
In Progress
Bug description:
It looks that since few days neutron-tempest-plugin-designate-scenario
job is failing every time on spawning devstack stage.
Error looks like:
2019-03-30 19:20:14.016 | + ./stack.sh:main:767 :
PYPI_ALTERNATIVE_URL=
2019-03-30 19:20:14.019 | + ./stack.sh:main:767 :
/opt/stack/devstack/tools/install_pip.sh
2019-03-30 19:20:15.172 | /opt/stack/devstack/.localrc.auto: line 78:
/opt/stack/neutron-tempest-plugin: Is a directory
2019-03-30 19:20:15.176 | ++ ./stack.sh:main:767 :
err_trap
2019-03-30 19:20:15.178 | ++ ./stack.sh:err_trap:563 :
local r=126
2019-03-30 19:20:15.182 | stack.sh failed: full log in
/opt/stack/logs/devstacklog.txt.2019-03-30-191759
2019-03-30 19:20:15.183 | Error on exit
Example: http://logs.openstack.org/45/638645/11/check/neutron-tempest-
plugin-designate-scenario/e76e442/controller/logs/devstacklog.txt.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1822453/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
