Seems like this got accidentally from Won't Fix state to InProgress
without explanation why and any further work. Therefore I'm gonna move
it back to Won't Fix. If you feel like this should be addressed , please
provide the current info (as the bug is ~2 years old -> tempest code
base has changed
** Changed in: tempest
Status: Won't Fix => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1631872
Title:
Not all neutron ports are ACTIVE after the
As I mentioned on https://review.openstack.org/#/c/383049/ , we don't
need to change Tempest side for this.
** Changed in: tempest
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
Reviewed: https://review.openstack.org/399001
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=00fdf284085866c77590255059ae74b672dd5a85
Submitter: Jenkins
Branch:master
commit 00fdf284085866c77590255059ae74b672dd5a85
Author: Claudiu Belu
This needs to be fixed in the hyper-v driver in nova also, anything
using neutron should have the code that waits for the vif plugged event
before making the server as ACTIVE. Clients expect that once the server
is ACTIVE they can ssh into it and perform other operations on it.
** Also affects:
5 matches
Mail list logo