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.
The commit just prevents hammer-cli-import to fail. Just preventing creation of composite content views, in case the component content views are not available yet ...
hammer-cli-import.git: 389bcf01c386ee0dbbd1a885ce361df2f63d8baf
VERIFIED.
rubygem-hammer_cli_import-0.10.17-1.el7sat.noarch
@Satellite-6.1.0-RHEL-7-20150612.0
# hammer import activation-key --verbose --csv-file /tmp/exports/activation-keys.csv
Importing from /tmp/exports/activation-keys.csv
Creating new activation key: 1-key
Can't find content view for channel ID [103] for key [1-key]
Can't find content view for channel ID [106] for key [1-key]
Creating new activation key: 2-key
Associating activation key [2] with host collections [1]
Skipping content view association for activation key [1]. Dependent content views not ready.
Creating new ak content view: ak_2
Publishing content view: 19
Associating activation key [2] with content view [19]
Updating activation key with id: 2
Summary
Created 2 activation_keys.
Created 1 ak content view.
>>> fixed >>> Skipping content view association for activation key [1]. Dependent content views not ready.