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.

Description of problem:

Unable to generate or force generate a new katello-ca-consumer-latest package using satellite-installer


Version-Release number of selected component (if applicable):

Satellite 6.9

How reproducible:

Always

Steps to Reproduce:
1. Remove /var/www/html/pub/katello-server-ca.crt and /var/www/html/pub/katello-rhsm-consumer from satellite server.
2. Run "satellite-installer"


Actual results:

 - No new "katello-ca-consumer-latest" package is generated as it should generate as it does for earlier versions of satellite releases.

Expected results:

 - A new version of the "katello-ca-consumer-latest" package gets generated.
Additional info:

The behavior:

1. Remove /var/www/html/pub/katello-server-ca.crt and /var/www/html/pub/katello-rhsm-consumer from satellite server.

causing a new katello-consumer RPM to be generated is not a feature and with changes we've made makes sense why you are not seeing a new RPM generated (because nothing changed therefore the system does not see a need to generate a new one). I would prefer to get at the heart of the issue which to me is:


What is the situation for which you need a new katello-consumer RPM generated?
What changed in the environment that should have resulted in a new katello-consumer RPM and did not? What workflow did not work correctly? (e.g. did you change some certificates?)

I think this should be closed as not a bug. The conditions under which a new RPM will get generated are:

 * User deletes the current bootstrap RPM from /var/www/html/pub
 * A new server CA certificate is presented to the installer
 * The FQDN of the server changes and installer ran