Bug 1312769 - Add comment warnings for puppet-managed configuration files
Summary: Add comment warnings for puppet-managed configuration files
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installer
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-29 09:20 UTC by Lukas Zapletal
Modified: 2019-09-26 13:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-27 20:42:23 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16255 0 None None None 2016-08-23 17:33:26 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.