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.
Created attachment 898050[details]
foreman production log detailing back-end error
Description of problem:
After creating a lifecycle environment and publishing/promoting a content view to it, you cannot change the environment where a content host is attached.
Version-Release number of selected component (if applicable):
[root@satellite ~]# rpm -qa | grep -E "katello|foreman|pulp" | sort
createrepo-0.9.9-21.2.pulp.el6sat.noarch
foreman-1.6.0.9-1.el6sat.noarch
foreman-compute-1.6.0.9-1.el6sat.noarch
foreman-gce-1.6.0.9-1.el6sat.noarch
foreman-libvirt-1.6.0.9-1.el6sat.noarch
foreman-ovirt-1.6.0.9-1.el6sat.noarch
foreman-postgresql-1.6.0.9-1.el6sat.noarch
foreman-proxy-1.6.0.6-1.el6sat.noarch
foreman-vmware-1.6.0.9-1.el6sat.noarch
katello-1.5.0-24.el6sat.noarch
katello-ca-1.0-1.noarch
katello-certs-tools-1.5.5-1.el6sat.noarch
katello-installer-0.0.40-1.el6sat.noarch
m2crypto-0.21.1.pulp-8.el6sat.x86_64
mod_wsgi-3.4-1.pulp.el6sat.x86_64
pulp-katello-plugins-0.3-1.el6sat.noarch
pulp-nodes-common-2.4.0-0.17.beta.el6sat.noarch
pulp-nodes-parent-2.4.0-0.17.beta.el6sat.noarch
pulp-puppet-plugins-2.4.0-0.17.beta.el6sat.noarch
pulp-puppet-tools-2.4.0-0.17.beta.el6sat.noarch
pulp-rpm-plugins-2.4.0-0.17.beta.el6sat.noarch
pulp-selinux-2.3.1-1.el6.noarch
pulp-server-2.4.0-0.17.beta.el6sat.noarch
python-isodate-0.5.0-1.pulp.el6sat.noarch
python-kombu-3.0.15-5.pulp.el6sat.noarch
python-pulp-bindings-2.4.0-0.17.beta.el6sat.noarch
python-pulp-common-2.4.0-0.17.beta.el6sat.noarch
python-pulp-puppet-common-2.4.0-0.17.beta.el6sat.noarch
python-pulp-rpm-common-2.4.0-0.17.beta.el6sat.noarch
ruby193-rubygem-foreman_bootdisk-2.0.6-1.1.el6sat.noarch
ruby193-rubygem-foreman_discovery-1.3.0-0.1.rc2.el6sat.noarch
ruby193-rubygem-foreman_hooks-0.3.5-2.el6sat.noarch
ruby193-rubygem-foreman-redhat_access-0.0.3-1.el6sat.noarch
ruby193-rubygem-foreman-tasks-0.5.4-2.el6sat.noarch
ruby193-rubygem-katello-1.5.0-44.el6sat.noarch
rubygem-hammer_cli_foreman-0.1.0-13.el6sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.2-6.el6sat.noarch
rubygem-hammer_cli_katello-0.0.3-24.el6sat.noarch
How reproducible:
100%
Steps to Reproduce:
1. Create new lifecycle environment.
2. Create, publish and promote content view into it.
3. Register a content host to Library.
4. Visit that content host's details page.
5. Click to change the environment.
Actual results:
A back-end error occurs and the UI never completes loading the list of content views.
Expected results:
You should be able to change the environment/view.
Additional info:
Comment 1RHEL Program Management
2014-05-21 15:45:25 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Created attachment 898050 [details] foreman production log detailing back-end error Description of problem: After creating a lifecycle environment and publishing/promoting a content view to it, you cannot change the environment where a content host is attached. Version-Release number of selected component (if applicable): [root@satellite ~]# rpm -qa | grep -E "katello|foreman|pulp" | sort createrepo-0.9.9-21.2.pulp.el6sat.noarch foreman-1.6.0.9-1.el6sat.noarch foreman-compute-1.6.0.9-1.el6sat.noarch foreman-gce-1.6.0.9-1.el6sat.noarch foreman-libvirt-1.6.0.9-1.el6sat.noarch foreman-ovirt-1.6.0.9-1.el6sat.noarch foreman-postgresql-1.6.0.9-1.el6sat.noarch foreman-proxy-1.6.0.6-1.el6sat.noarch foreman-vmware-1.6.0.9-1.el6sat.noarch katello-1.5.0-24.el6sat.noarch katello-ca-1.0-1.noarch katello-certs-tools-1.5.5-1.el6sat.noarch katello-installer-0.0.40-1.el6sat.noarch m2crypto-0.21.1.pulp-8.el6sat.x86_64 mod_wsgi-3.4-1.pulp.el6sat.x86_64 pulp-katello-plugins-0.3-1.el6sat.noarch pulp-nodes-common-2.4.0-0.17.beta.el6sat.noarch pulp-nodes-parent-2.4.0-0.17.beta.el6sat.noarch pulp-puppet-plugins-2.4.0-0.17.beta.el6sat.noarch pulp-puppet-tools-2.4.0-0.17.beta.el6sat.noarch pulp-rpm-plugins-2.4.0-0.17.beta.el6sat.noarch pulp-selinux-2.3.1-1.el6.noarch pulp-server-2.4.0-0.17.beta.el6sat.noarch python-isodate-0.5.0-1.pulp.el6sat.noarch python-kombu-3.0.15-5.pulp.el6sat.noarch python-pulp-bindings-2.4.0-0.17.beta.el6sat.noarch python-pulp-common-2.4.0-0.17.beta.el6sat.noarch python-pulp-puppet-common-2.4.0-0.17.beta.el6sat.noarch python-pulp-rpm-common-2.4.0-0.17.beta.el6sat.noarch ruby193-rubygem-foreman_bootdisk-2.0.6-1.1.el6sat.noarch ruby193-rubygem-foreman_discovery-1.3.0-0.1.rc2.el6sat.noarch ruby193-rubygem-foreman_hooks-0.3.5-2.el6sat.noarch ruby193-rubygem-foreman-redhat_access-0.0.3-1.el6sat.noarch ruby193-rubygem-foreman-tasks-0.5.4-2.el6sat.noarch ruby193-rubygem-katello-1.5.0-44.el6sat.noarch rubygem-hammer_cli_foreman-0.1.0-13.el6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.2-6.el6sat.noarch rubygem-hammer_cli_katello-0.0.3-24.el6sat.noarch How reproducible: 100% Steps to Reproduce: 1. Create new lifecycle environment. 2. Create, publish and promote content view into it. 3. Register a content host to Library. 4. Visit that content host's details page. 5. Click to change the environment. Actual results: A back-end error occurs and the UI never completes loading the list of content views. Expected results: You should be able to change the environment/view. Additional info: