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.
Created attachment 1404935[details]
satellite-installer log
Description of problem:
Upgrade from Satellite 6.2.14 to 6.3 failed throwing following error.
*Complete installation log attached.
========
[DEBUG 2018-02-28 16:28:14 main] Exit with status code: 1 (signal was 1)
[ERROR 2018-02-28 16:28:14 main] Errors encountered during run:
[ERROR 2018-02-28 16:28:14 main] Could not find dependency Class[Puppet::Server::Install] for File[/etc/pki/katello/puppet] at /usr/share/katello-installer-base/modules/certs/manifests/puppet.pp:50
[ERROR 2018-02-28 16:28:14 main] /usr/share/ruby/vendor_ruby/puppet/util/errors.rb:106:in `fail'
========
Puppet is installed on this host BUT is installed under a SEPARATE PATH to the puppet version installed and used by Satellite 6. (Update: Now removed Puppet based on our suggestion still same errors).
original Satellite 6.2 install was done with the following arguments:
--capsule-puppet false
--foreman-proxy-dhcp false
--foreman-proxy-dns false
--foreman-proxy-puppetrun false
--foreman-proxy-puppetca false
" i.e. don't need puppet as part of our Satellite install. "
following options noticed as true in satellite-answers.yaml
============ /etc/foreman-installer/scenarios.d/satellite-answers.yaml
foreman_proxy_content:
puppet: true
puppet:
manage_packages: true
agent: true
============
Version-Release number of selected component (if applicable):
6.3
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Failed with "Could not find dependency Class[Puppet::Server::Install] for File[/etc/pki/katello/puppet] at /usr/share/katello-installer-base/modules/certs/manifests/puppet.pp:50"
Expected results:
Upgrade should complete without any issue.
Additional info:
Please let us know if there is any update on this issue.
Comment 17Ewoud Kohl van Wijngaarden
2018-06-26 12:19:48 UTC
The --foreman-proxy-content-puppet parameter controls whether it should install the certificates for the puppet server <-> foreman integration. If you disable the puppet server in the installation then it fails because we chain puppet server installation -> certs. However, you don't need the certs for the integration if there's nothing to integrate with.
This is a side effect of some internals on how to couple modules.
tl;dr: if you have disabled puppet server (--puppet-server false) then you also need to disable the integration (--foreman-proxy-content-puppet false).
Comment 19Ewoud Kohl van Wijngaarden
2018-06-27 10:56:05 UTC
In Satellite 6.2 the module was called capsule. To install without puppet was then --capsule-pupppet false. In 6.3 this was split and the puppet module is now exposed as a top level module. It looks like the answer file migration doesn't properly migrate the answer which is probably the root cause of this showing up a lot and I missed that part.
Comment 20Ewoud Kohl van Wijngaarden
2018-06-27 11:10:58 UTC
I am hiding the workaround again because for upgrades it doesn't work. Right now I can't think of a workaround that works with foreman-maintain.
Comment 21Johannes Grumböck
2018-08-02 12:06:47 UTC
Hello,
I'm also facing this problem when upgraden RHEL7/Satellite 6.2.15 to 6.3 (like Karol Kania) and we have also disabled the puppet feature in 6.2.15.
What helped as a workaround for me was the following:
- run "foreman-maintain upgrade run --target-version 6.3" as mentioned in [0]
this will run into the mentioned error "Could not find dependency" while upgrading puppet
- run "satellite-installer --scenario satellite --foreman-proxy-content-puppet false --puppet-server false" as mentioned in comment 17.
this should run fine
- rerun "foreman-maintain upgrade run --target-version 6.3"
Upgrade was successful afterwards.
Best regards,
Johannes
[0] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html-single/upgrading_and_updating_red_hat_satellite/index#upgrading_a_connected_satellite_server
Comment 22Satellite Program
2018-08-31 12:07:55 UTC
Upstream bug assigned to ekohlvan
Comment 23Satellite Program
2018-08-31 12:08:00 UTC
VERIFIED
Version tested:
Satellite 6.5 snap 16
Steps:
1. Installed satellite 6.4 with puppet and puppet ca features disabled.
# satellite-installer --no-enable-puppet --foreman-proxy-puppet false --foreman-proxy-puppetca false --foreman-proxy-content-puppet false --foreman-proxy-manage-puppet-group false
2. Upgrade it to 6.5
3. Successful upgrade.
1. Update existing satellite 6.5 to disable puppet and puppetca feature and works fine.
Same scenarios for capsule works fine.
Installing 6.5 with puppet and puppetca feature disabled gives error as per #comment 27. We are tracking it here https://bugzilla.redhat.com/show_bug.cgi?id=1679886
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-2019:1222
Created attachment 1404935 [details] satellite-installer log Description of problem: Upgrade from Satellite 6.2.14 to 6.3 failed throwing following error. *Complete installation log attached. ======== [DEBUG 2018-02-28 16:28:14 main] Exit with status code: 1 (signal was 1) [ERROR 2018-02-28 16:28:14 main] Errors encountered during run: [ERROR 2018-02-28 16:28:14 main] Could not find dependency Class[Puppet::Server::Install] for File[/etc/pki/katello/puppet] at /usr/share/katello-installer-base/modules/certs/manifests/puppet.pp:50 [ERROR 2018-02-28 16:28:14 main] /usr/share/ruby/vendor_ruby/puppet/util/errors.rb:106:in `fail' ======== Puppet is installed on this host BUT is installed under a SEPARATE PATH to the puppet version installed and used by Satellite 6. (Update: Now removed Puppet based on our suggestion still same errors). original Satellite 6.2 install was done with the following arguments: --capsule-puppet false --foreman-proxy-dhcp false --foreman-proxy-dns false --foreman-proxy-puppetrun false --foreman-proxy-puppetca false " i.e. don't need puppet as part of our Satellite install. " following options noticed as true in satellite-answers.yaml ============ /etc/foreman-installer/scenarios.d/satellite-answers.yaml foreman_proxy_content: puppet: true puppet: manage_packages: true agent: true ============ Version-Release number of selected component (if applicable): 6.3 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Failed with "Could not find dependency Class[Puppet::Server::Install] for File[/etc/pki/katello/puppet] at /usr/share/katello-installer-base/modules/certs/manifests/puppet.pp:50" Expected results: Upgrade should complete without any issue. Additional info: