Bug 1312769

Summary:	Add comment warnings for puppet-managed configuration files
Product:	Red Hat Satellite	Reporter:	Lukas Zapletal <lzap>
Component:	Installation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DEFERRED	QA Contact:	Katello QA List <katello-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	bkearney, stbenjam
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-27 20:42:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lukas Zapletal 2016-02-29 09:20:37 UTC

I've encountered several upgrade errors at customers or redhatters when
DHCP and/or DNS configuration simply disappears after Satellite upgrade.

When our users add or modify subnets or domains, our installer overwrite
the configuration with the initial one. Since our installer is limited 
and only supports definition of one subnet/domain, all the others are 
deleted and users need to restore those configurations from backups.

Purpose of this BZ:

Big warning comments in both /etc/zones.conf and /etc/dhcp/dhcpd.conf
files telling users that upgrade process will rewrite these files. I 
think we already do this upstream. Unfortunately our upstream warning is 
too short IMHO:

### File managed with puppet ###

I think we need to add extra information there for Satellite. In upstream, upgrade process never calls installer again, therefore this short notice is sufficient.

Comment 1 Bryan Kearney 2016-07-26 19:03:20 UTC

Moving 6.2 bugs out to sat-backlog.

Comment 2 Stephen Benjamin 2016-08-23 17:33:24 UTC

Created redmine issue http://projects.theforeman.org/issues/16255 from this bug

Comment 3 Bryan Kearney 2016-08-23 18:13:09 UTC

Upstream bug component is Provisioning

Comment 5 Bryan Kearney 2016-08-24 08:12:55 UTC

Upstream bug component is Installer

Comment 6 Bryan Kearney 2017-03-27 20:42:23 UTC

This bug is being tracked upstream, and will no longer be tracked in the downstream product. When the upstream issue is fixed, the next Satellite release will contain the fix. I am closing this out as deferred. If you feel this is not correct, please feel free to open with additional information.