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:

Firstly we must reset the rhsm.conf via installing http://[fqdn_sam]/pub/candlepin-cert-consumer-[fqdn_sam]-1.0-1.noarch.rpm, then we can register to SAM.

Pls provide an option to install the rpm in the firstboot to set the rhsm.conf if we choose "register to SAM" in firstboot.





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





  

Actual results:

We can't set rhsm.conf when choosing "register to SAM" via firstboot.





Expected results:

Provide an option to set the rhsm.conf when choosing "register to SAM" via firstboot.





Additional info:

Not sure I understand the request.

If the package is installed with kickstart, the rhsm config should be pointing to the right place.

If the package isn't being installed via kickstart/anaconda, then I'm not sure.

Would the assumption be that the correct repos were setup in kickstart/anaconda?


Concerns are:
  1) installing rpms in the startup config (firstboot and/or the rhel7 stuff) is kind of unusual.

  2) how do we bootstrap enough info to install the package securely. We would need at least repo url, repo ssl/ca certs, GPG key.


What could we assume is installed on the system at this point?
  SAM repos configs?
  SAM repo ssl/ca certs?
  SAM repo entitlement certs?
  SAM repo gpg key?

Acking 7.1

Not a base RHEL firstboot problem. We are not adding any new firstboot modules to our solution. We are moving to a new intial-setup module.

Deferring to Satellite product.