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

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1610970

Summary:	Puppet Enterprise conflict during satellite-installer --upgrade
Product:	Red Hat Satellite	Reporter:	Mike McCune <mmccune>
Component:	Puppet	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Nikhil Kathole <nkathole>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.3.2	CC:	bkearney, cmarinea, dgross, ekohlvan, ktordeur, nkathole, sghai, spetrosi, tbrisker
Target Milestone:	Unspecified	Keywords:	Reopened, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Release Note
Doc Text:	Puppet Enterprise is not supported on Satellite Server. If you have it installed, perform the following actions to avoid conflicts after the upgrade: . Move the cache from `/var/lib/puppet/foreman_cache_data` to `/opt/puppetlabs/puppet/cache/`: + ---- # mkdir -p /opt/puppetlabs/puppet/cache/ # cp -r /var/lib/puppet/foreman_cache_data /opt/puppetlabs/puppet/cache/ ---- . Run the `satellite-installer --upgrade` script to apply changes.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-01 13:31:48 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 Mike McCune 2018-08-01 18:28:03 UTC

NOTE: Puppet Enterprise is not supported to be installed on the same host as Satellite 6. This bug is to document the workaround in case this situation occurs.

If a user has Puppet Enterprise installed on Satellite 6 in conjunction with Puppet 3/4/5 installed from Satellite 6 there may be an error during the execution of:

satellite-installer --upgrade
...
stderr: stty: standard input: Inappropriate ioctl for device
/usr/share/ruby/vendor_ruby/puppet/vendor/safe_yaml/lib/safe_yaml.rb:188:in `initialize': No such file or directory - /opt/puppetlabs/puppet/cache/foreman_cache_data/candlepin_db_password (Errno::ENOENT)

The issue comes from the fact that Puppet Enterprise installs files in 
/opt/puppetlabs/bin/puppet then that will be used by the installer. 

Puppet can't distinguish between PE and Puppet 4 because they are packaged in
the same way. Also note that if PE packages are Puppet 5 then it will
fail because we miss 2 patches in the installer.

Beware that satellite-installer --upgrade-puppet will probably behave in
unexpected ways and it's recommended to do this manually.
hooks/init/31-upgrade-puppet.rb should be very readable.

WORKAROUND:

1) move the cache from /var/lib/puppet/foreman_cache_data to /opt/puppetlabs/puppet/cache/ 

2) place a symlink in /var/lib/puppet to  /opt/puppetlabs/puppet/cache/ 

3) re-run satellite-installer --upgrade

Comment 2 Bryan Kearney 2018-08-01 18:42:10 UTC

This is really a tracker bug for a release note. I am moving this to ON_QA for verification with the workaround.

Comment 4 Nikhil Kathole 2018-09-12 09:52:50 UTC

VERIFIED

performed upgrade from 6.3.3 to 6.4 snap 21 using provided workaround for db clone and upgrade.

The provided workaround worked.

Steps performed:
1. mkdir -p /opt/puppetlabs/puppet/cache/
2. cp -r /var/lib/puppet/foreman_cache_data /opt/puppetlabs/puppet/cache/
3. satellite-installer --upgrade

Comment 9 Bryan Kearney 2018-10-16 19:00:46 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927

Comment 11 Mike McCune 2018-11-16 22:17:08 UTC

This is not closed as there is no baked-in method to prevent the error outlined in the original comment in the bug. I'm going to re-open this.

Comment 13 Bryan Kearney 2020-05-01 13:31:48 UTC

Satellite 6.4 is now End of Life. These bus will not be fixed on the 6.4 stream. Users of Satellite should upgrade to the latest version of Satellite to get access to the most current set of bugfixes and feature improvements.

Comment 14 Red Hat Bugzilla 2023-09-15 00:11:15 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days