Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 858154 - [RFE] Firstboot should provide an option to setup rhsm.conf for SAM
Summary: [RFE] Firstboot should provide an option to setup rhsm.conf for SAM
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Asset Manager (SAM)
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel72
TreeView+ depends on / blocked
 
Reported: 2012-09-18 07:40 UTC by Hui Wang
Modified: 2016-07-29 12:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-29 12:50:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Hui Wang 2012-09-18 07:40:21 UTC 
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:
Comment 1 Adrian Likins 2014-02-06 15:37:52 UTC 
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?
Comment 4 Bryan Kearney 2014-07-30 19:20:27 UTC 
Acking 7.1
Comment 7 William Poteat 2015-05-08 17:27:14 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.