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:
Registering system by activation key which has content view shows error "No such environment: 203-197".
Version-Release number of selected component (if applicable):
katello-glue-elasticsearch-1.3.14-1.git.1008.69128af.el6.noarch
katello-cli-1.3.5-1.git.43.2d17ef1.el6.noarch
katello-configure-1.3.6-1.git.838.2dc1245.el6.noarch
katello-glue-pulp-1.3.14-1.git.1008.69128af.el6.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-agent-1.3.1-1.git.476.f8f2f08.el6.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-certs-tools-1.1.9-1.el6.noarch
katello-common-1.3.14-1.git.1008.69128af.el6.noarch
katello-glue-foreman-1.3.14-1.git.1008.69128af.el6.noarch
katello-1.3.14-1.git.1008.69128af.el6.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-repos-1.3.2-1.el6.noarch
katello-selinux-1.3.1-1.el6.noarch
katello-all-1.3.14-1.git.1008.69128af.el6.noarch
katello-cli-common-1.3.5-1.git.43.2d17ef1.el6.noarch
katello-glue-candlepin-1.3.14-1.git.1008.69128af.el6.noarch
How reproducible:
always
Steps to Reproduce:
1. Create an organization with environment "dev"
2. Create a custom provider
3. Create a product
4. Add a repository to the product, for example "zoo"
5. Synch and promote the repository to the first environment
6. Add a few more products with respective repositories to the same provider
7. Create a new Content View Definition
8. Add the product created in the setup to it
9. Publish content view and Promote the content view definition to environment by changeset.
10. Create a new activation key
11. Add the published content view definition to the activation key and save it
12. Register client by that activation key "subscription-manager register --org ACME_Corporation --activationkey key --force". You will see error here: "No such environment: 203-197"
Actual results:
error is shown while registering
Expected results:
system should be registered
Additional info:
registering system by activation key which does not have content view works OK