Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1238483

Summary: RFE: mistake in networking config in undercloud.conf seems to necessitate a complete reinstall -- simply making changes and rerunning 'openstack undercloud install' will not work
Product: Red Hat OpenStack Reporter: arkady kanevsky <arkady_kanevsky>
Component: rhosp-directorAssignee: Bob Fournier <bfournie>
Status: CLOSED NOTABUG QA Contact: Shai Revivo <srevivo>
Severity: medium Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: arkady_kanevsky, cdevine, christopher_dearborn, dtantsur, jcoufal, jdonohue, kurt_hey, mburns, morazi, racedoro, randy_perryman, rhel-osp-director-maint, rsussman, smerrow
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1389435, 1394885    

Description arkady kanevsky 2015-07-02 00:24:52 UTC 
Description of problem:
Any mistake in networking config in instack.answers seems to necessitate a complete reinstall -- simply making changes and rerunning instack-install-undercloud will not work

Puppetize networking for undecloud. just update puppet parameters and rerun puppet rather than full undercloud reinstall.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 chris alfonso 2015-08-04 18:33:58 UTC 
We're working on a network validation tool that might help get ahead of similar issues, which we plan to include in the product shortly after GA. But the feature request you've made here is certainly valid.
Comment 6 Dmitry Tantsur 2016-10-04 16:43:56 UTC 
Hi!

This was reported back in Kilo, is it still a problem? I believe we got quite a few improvements around os-net-config. If so, please provide a few examples, as I believe at least some network variables can be updated (e.g. introspection IP range is driven by puppet nowadays).
Comment 7 arkady kanevsky 2016-11-14 15:12:18 UTC 
This impacts previous JS-5.0 and current JS-6.0 (OSP9).
Had not checked on OSP10.
Comment 8 Sean Merrow 2016-12-12 19:16:30 UTC 
Updating trackers since target has been updated to OSP 12.
Comment 9 Red Hat Bugzilla Rules Engine 2017-01-27 19:06:03 UTC 
This bugzilla has been removed from the release and needs to be reviewed for targeting another release.
Comment 10 Dmitry Tantsur 2017-02-06 15:11:28 UTC 
Proposing for 12
Comment 11 Randy Perryman 2017-02-06 15:16:14 UTC 
Does --force-postconfig fix this?
Comment 12 Bob Fournier 2017-03-08 15:22:28 UTC 
Would like to see if this is still an issue in OSP10 and some examples of what would make it easier. As noted, network variables like inspection_iprange are now driven by puppet.
Comment 13 arkady kanevsky 2017-03-08 15:28:38 UTC 
Randy is in better position to answer that question.
Comment 15 Randy Perryman 2017-05-16 19:13:33 UTC 
--THis is working much better now--
Comment 16 Randy Perryman 2017-05-16 19:13:33 UTC 
--THis is working much better now--