Overcloud upgrade from ocata to Pike was failed due to missing NAT rules for VLAN10

[Artem Hrechanychenko]

Description
===========
Upgrade of Ocata overcloud was failed due to "\nhttp://mirror.centos.org/centos/7/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - \"Could not resolve host: mirror.centos.org; Unknown error\"\nTrying other mirror:

http://pastebin.test.redhat.com/492120

Overcloud nodes cannot reach any external netwoks.
Reason: NAT Rules was broken on undercloud for VLAN10
http://pastebin.test.redhat.com/492159

W/A - /overcloud-prep-network.sh

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/openstack-tripleo-heat-templates --libvirt-type qemu --control-flavor oooq_control --compute-flavor oooq_compute -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml -e /home/stack/network-environment.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/low-memory-usage.yaml

Expected result
===============
Stack successfully created

Actual result
=============
Stack creation failed

Environment
===========
1. Ocata->Pike

2. Default

3. network isolation

Logs & Configs
==============

[Jiří Stránský (jistr)]

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.

[Emilien Macchi (emilienm)]

Quite note Artem, please use public pastbin, and not internal.
Thanks!

[Artem Hrechanychenko (ahrechan)]

http://paste.openstack.org/show/612277/
http://paste.openstack.org/show/612278/

[Artem Hrechanychenko (ahrechan)]

w/a for this issue - run ./overcloud-prep-network.sh after undercloud upgrade

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE