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.
DescriptionVedashree Deshpande
2022-11-30 11:12:34 UTC
Description of problem:
capsule-certs-generate modifies a file foreman-proxy-certs.yaml under /usr/share making rpm verify fail.
Before:
~~~
~# ls -l /usr/share/foreman-installer/katello-certs/scenarios.d/foreman-proxy-certs.yaml
-rw-r--r--. 1 root root 912 Sep 6 20:22 /usr/share/foreman-installer/katello-certs/scenarios.d/foreman-proxy-certs.yaml
:~# rpm -V foreman-installer-katello
S.5....T. c /etc/foreman-installer/scenarios.d/foreman-proxy-content.yaml
S.5....T. c /etc/foreman-installer/scenarios.d/katello.yaml
~~~
Create certs for a dummy capsule
~~~
~# CAPSULE="dummy.example.com"; capsule-certs-generate --foreman-proxy-fqdn "$CAPSULE" --certs-tar "/root/$CAPSULE-certs.tar"
Preparing installation Done
Success!
To finish the installation, follow these steps:
If you do not have the Capsule registered to the Satellite instance, then please do the following:
1. yum -y localinstall http://example.satellite.com/pub/katello-ca-consumer-latest.noarch.rpm
2. subscription-manager register --org "Default_Organization"
Once this is completed run the steps below to start the Capsule installation:
1. Ensure that the satellite-capsule package is installed on the system.
2. Copy the following file /root/dummy.example.com-certs.tar to the system dummy.example.com at the following location /root/dummy.example.com-certs.tar
scp /root/dummy.example.com-certs.tar root.com:/root/dummy.example.com-certs.tar
3. Run the following commands on the Capsule (possibly with the customized
parameters, see satellite-installer --scenario capsule --help and
documentation for more info on setting up additional services):
satellite-installer \
--scenario capsule \
--certs-tar-file "/root/dummy.example.com-certs.tar"\
--foreman-proxy-register-in-foreman "true"\
--foreman-proxy-foreman-base-url "https://example.satellite.com"\
--foreman-proxy-trusted-hosts "example.satellite.com"\
--foreman-proxy-trusted-hosts "dummy.example.com"\
--foreman-proxy-oauth-consumer-key "fWVNkiLBSUbjwWHfXZRSEmAuYDMQUhp5"\
--foreman-proxy-oauth-consumer-secret "U925QwN4taN8EBKvBvaMu7MhyDuPs2b4"
~~~
After rpm validate is failing, the file scenarios.d/foreman-proxy-certs.yaml in /usr/share is modifed and also written with 600 instead of the rpm defoined 644
~~~
:~# rpm -V foreman-installer-katello
S.5....T. c /etc/foreman-installer/scenarios.d/foreman-proxy-content.yaml
S.5....T. c /etc/foreman-installer/scenarios.d/katello.yaml
SM5....T. /usr/share/foreman-installer/katello-certs/scenarios.d/foreman-proxy-certs.yaml
~# ls -l /usr/share/foreman-installer/katello-certs/scenarios.d/foreman-proxy-certs.yaml
-rw-------. 1 root root 998 Nov 25 11:20 /usr/share/foreman-installer/katello-certs/scenarios.d/foreman-proxy-certs.yaml
~~~
Version-Release number of selected component (if applicable):
6.11
Actual results:
File is modified and permissions are changed.
Expected results:
File should not be modified and permission should remain intact.
Additional info:
Comment 3Ewoud Kohl van Wijngaarden
2023-08-03 13:25:25 UTC
Minimal development reproducer:
git clone https://github.com/theforeman/foreman-installer
cd foreman-installer
bundle install
bundle exec rake build
bundle exec ./bin/foreman-proxy-certs-generate --help
Now you'll see katello_certs/config/foreman-proxy-certs.yaml has been modified.
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.