Fix cancel update for nova server with defined port
This particular patch fixes a behaviour of cancel update for nova
server with defined port, so there are no ports manageable by nova.
We have these issues while restoring ports after rollback:
1) We doesn't detach any ports from current server, because we
doesn't save them to resoruce data. (we store this data after
succesfull create of the server)
2) Detaching an interface from current server will fail, if the
server will be in building state, so we need to wait until server
will be in active or in error state.
Refresh ports list to solve problem (1).
Wait until nova moves to active/error state to solve (2).
Reviewed: https:/ /review. fuel-infra. org/20997
Submitter: Pkgs Jenkins <email address hidden>
Branch: 9.0/mitaka
Commit: 95493e5e431275b 259b4a8d8b137c0 2bdb388d4c
Author: Oleksii Chuprykov <email address hidden>
Date: Fri May 20 14:23:00 2016
Fix cancel update for nova server with defined port
This particular patch fixes a behaviour of cancel update for nova
server with defined port, so there are no ports manageable by nova.
We have these issues while restoring ports after rollback:
1) We doesn't detach any ports from current server, because we
doesn't save them to resoruce data. (we store this data after
succesfull create of the server)
2) Detaching an interface from current server will fail, if the
server will be in building state, so we need to wait until server
will be in active or in error state.
Refresh ports list to solve problem (1).
Wait until nova moves to active/error state to solve (2).
Closes-Bug: #1570825 d9ac67b8878bc40 ca6b3ea4674
Partial-Bug: #1570908
Change-Id: I737736f572aae4