Overcloud upgrade from ocata to Pike was failed due to missing NAT rules for VLAN10
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Expired
|
Undecided
|
Unassigned |
Bug Description
Description
===========
Upgrade of Ocata overcloud was failed due to "\nhttp:
http://
Overcloud nodes cannot reach any external netwoks.
Reason: NAT Rules was broken on undercloud for VLAN10
http://
W/A - /overcloud-
Steps to reproduce
==================
1)Deploy undercloud and perform introspection , --release Ocata
bash quickstart.sh --teardown all -release ocata $HOST
2) deploy overcloud
openstack overcloud deploy --templates /usr/share/
Expected result
===============
Stack successfully created
Actual result
=============
Stack creation failed
Environment
===========
1. Ocata->Pike
2. Default
3. network isolation
Logs & Configs
==============
Changed in tripleo: | |
status: | New → Triaged |
Changed in tripleo: | |
milestone: | pike-3 → pike-rc1 |
Changed in tripleo: | |
milestone: | pike-rc1 → queens-1 |
Changed in tripleo: | |
milestone: | queens-1 → queens-2 |
Changed in tripleo: | |
milestone: | queens-2 → queens-3 |
Changed in tripleo: | |
milestone: | queens-3 → queens-rc1 |
Changed in tripleo: | |
milestone: | queens-rc1 → rocky-1 |
Changed in tripleo: | |
milestone: | rocky-1 → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
It's likely that undercloud upgrade does something that nullifies the effects of ./overcloud- prep-network. sh.
Adding a quickstart tag as well. I wonder if it's possible to do the vlan10 forwarding setup on undercloud in a somewhat more permanent fashion.