Bug 1296568
| Summary: | RHEL OSP 8 needs to be enabled for RHN/Satellite 5 | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Mike Burns <mburns> |
| Component: | openstack-tripleo-heat-templates | Assignee: | James Slagle <jslagle> |
| Status: | CLOSED ERRATA | QA Contact: | Alexander Chuzhoy <sasha> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 8.0 (Liberty) | CC: | achernet, adahms, athomas, dbecker, hbrock, jslagle, kbasil, mburns, nbarcet, rhel-osp-director-maint, sasha, sclewis, srevivo |
| Target Milestone: | ga | Keywords: | TestOnly, Triaged |
| Target Release: | 8.0 (Liberty) | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-0.8.10-1.el7ost | Doc Type: | Enhancement |
| Doc Text: |
With this update, overcloud nodes can now be registered to Satellite 5 with the Red Hat OpenStack Platform director, and Satellite 5 can now provide package updates to overcloud nodes.
To register overcloud nodes with a Satellite 5 instance, pass the following options to the "openstack overcloud deploy" command:
--rhel-reg
--reg-method satellite
--reg-org 1
--reg-force
--reg-sat-url https://<satellite-5-hostname>
--reg-activation-key <satellite-5-activation-key>
|
Story Points: | --- |
| Clone Of: | 1293473 | Environment: | |
| Last Closed: | 2016-04-20 13:04:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1293473 | ||
| Bug Blocks: | |||
|
Comment 3
James Slagle
2016-03-03 17:47:06 UTC
Verified: Environment: openstack-tripleo-heat-templates-0.8.14-7.el7ost.noarch Was able to deploy overcloud with registerting the OC nodes with sat5. Checked the yum repos post deployment - looks good. 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://rhn.redhat.com/errata/RHBA-2016-0653.html |