Description of problem: During upgrade from OSP 11 to OSP 13, the deploy command was run without network-isolation.yaml. This caused the the current networking to be overwritten with an attempt to create a new set of networks with new uuid's. This caused the stack to go offline. There is no backup of undercloud database before the deploy command was issued. Version-Release number of selected component (if applicable): OSP 11 OSP 12 OSP 13 How reproducible: Every time the network-isolation.yaml is not in the deploy command/script Steps to Reproduce: 1. Remove network-isolation.yaml from deploy script 2. Run deploy script for upgrade from OSP 12 to OSP 13 3. Actual results: Current networking information and heat stack deleted and new networking information added. Causing stack failure. Expected results: Clean upgrade to OSP 13 Additional info: This has happened before. A RFE for a warning that the templates have changed to be issued before deploy starts needs to be submitted.
Can we close this one? You mention a RFE, but it should probably be a different issue, right? Thanks.