Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
Satellite 6.2 is missing the kickstart trees for Red Hat Atomic Host. This means we cannot provision Atomic host nodes directly from satellite using DHCP/PXE.
Version-Release number of selected component (if applicable):
Satellite 6.2.0
How reproducible:
Repeatedly
Steps to Reproduce:
1. Look at Red Hat repositories
2. Under kickstart trees
3. No kickstart content available for atomic host.
Actual results:
This means I'm unable to provision Atomic host from Satellite using DHCP/PXE
Expected results:
I expected to find a kickstart tree so I could provision hosts.
Additional info:
I was able to work around this by copying the content into /var/www/html/pub/atomic then creating a custom installation media that points to this URL.
Comment 4pulp-infra@redhat.com
2016-08-26 01:08:18 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 5pulp-infra@redhat.com
2016-08-26 01:08:21 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 6pulp-infra@redhat.com
2016-08-26 17:30:24 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
I'm associating another pulp issue that is a critical bug fix that must be cherry-picked with the original change, to ensure that mirrorlist support during sync continues to work.
Comment 8pulp-infra@redhat.com
2016-09-13 15:31:34 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 9pulp-infra@redhat.com
2016-09-13 15:31:38 UTC
The Pulp upstream bug priority is at Urgent. Updating the external tracker on this bug.
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/RHBA-2016:1993
Comment 16pulp-infra@redhat.com
2016-10-26 05:01:18 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 17pulp-infra@redhat.com
2016-10-26 05:01:26 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 18pulp-infra@redhat.com
2016-12-13 16:01:32 UTC
The Pulp upstream bug status is at VERIFIED. Updating the external tracker on this bug.
Comment 19pulp-infra@redhat.com
2016-12-19 16:01:31 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 20pulp-infra@redhat.com
2016-12-19 16:01:38 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.