Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1414993 - Bootstrap does not (re)start rhsmcertd upon completion
Bootstrap does not (re)start rhsmcertd upon completion
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Bootstrap (Show other bugs)
6.2.6
Unspecified Unspecified
medium Severity medium (vote)
: GA
: Unused
Assigned To: Rich Jerrido
Ondřej Pražák
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-01-19 17:22 EST by Rich Jerrido
Modified: 2018-02-21 12:30 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-02-21 12:30:35 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github https://github.com/Katello/katello-client-bootstrap/pull/147 None None None 2017-01-19 17:25 EST

  None (edit)
Description Rich Jerrido 2017-01-19 17:22:00 EST
Description of problem:


As many users of the bootstrap script will be registering systems that are not registered (at all) or previously registered to sat5/rhn classic, it is important the rhsmcertd daemon is enabled AND started. Otherwise check-in times in the UI will not be updated and the other functions that rhsmcertd provide will not be available. 


Version-Release number of selected component (if applicable):
rpm -q katello-client-bootstrap
katello-client-bootstrap-1.2.2-1.el7sat.noarch



How reproducible:
100%

Steps to Reproduce:
1. run bootstrap on a system where rhsmcertd is disabled and not running. 
2.
3.

Actual results:
rhsmcertd is not enabled on startup and not running

Expected results:
rhsmcertd should be enabled on startup and running

Additional info:
Comment 4 Ondřej Pražák 2017-08-23 07:39:57 EDT
Verified.

6.3.0 snap 12
Comment 5 Bryan Kearney 2018-02-21 12:30:35 EST
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-2018:0336

Note You need to log in before you can comment on or make changes to this bug.