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 716986[details]
Changeset Error
Description of problem:
Promoting content view via changeset shows PGError "ERROR: column content_view_environments.environment does not exist LINE 1".
Full error log attached.
Version-Release number of selected component (if applicable):
katello-glue-elasticsearch-1.3.14-1.git.1068.0eebc5e.el6.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-cli-common-1.3.5-1.git.51.6e92fb1.el6.noarch
katello-certs-tools-1.1.9-1.el6.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-cli-1.3.5-1.git.51.6e92fb1.el6.noarch
katello-glue-pulp-1.3.14-1.git.1068.0eebc5e.el6.noarch
katello-glue-candlepin-1.3.14-1.git.1068.0eebc5e.el6.noarch
katello-agent-1.3.1-1.git.476.f8f2f08.el6.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-repos-1.3.2-1.el6.noarch
katello-configure-1.3.6-1.git.1057.a78a564.el6.noarch
katello-common-1.3.14-1.git.1068.0eebc5e.el6.noarch
katello-selinux-1.3.1-1.el6.noarch
katello-1.3.14-1.git.1068.0eebc5e.el6.noarch
katello-all-1.3.14-1.git.1068.0eebc5e.el6.noarch
katello-glue-foreman-1.3.14-1.git.1068.0eebc5e.el6.noarch
How reproducible:
always
Steps to Reproduce:
1. Create an organization with environments
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
10. Create Changeset, add published content view into it and try to promote. Here PGError will be shown.
Actual results:
error is shown
Expected results:
changeset should be promoted successfully
This will be addressed by the following (once merged):
katello pull request:
https://github.com/Katello/katello/pull/1811
katello commits:
29793da9ab38541ea83676ad61bf2f669198e833
0cf3d81b98b5d13c114381b6069e233fdec96cbf
Created attachment 716986 [details] Changeset Error Description of problem: Promoting content view via changeset shows PGError "ERROR: column content_view_environments.environment does not exist LINE 1". Full error log attached. Version-Release number of selected component (if applicable): katello-glue-elasticsearch-1.3.14-1.git.1068.0eebc5e.el6.noarch katello-qpid-client-key-pair-1.0-1.noarch katello-cli-common-1.3.5-1.git.51.6e92fb1.el6.noarch katello-certs-tools-1.1.9-1.el6.noarch katello-candlepin-cert-key-pair-1.0-1.noarch katello-cli-1.3.5-1.git.51.6e92fb1.el6.noarch katello-glue-pulp-1.3.14-1.git.1068.0eebc5e.el6.noarch katello-glue-candlepin-1.3.14-1.git.1068.0eebc5e.el6.noarch katello-agent-1.3.1-1.git.476.f8f2f08.el6.noarch katello-qpid-broker-key-pair-1.0-1.noarch katello-repos-1.3.2-1.el6.noarch katello-configure-1.3.6-1.git.1057.a78a564.el6.noarch katello-common-1.3.14-1.git.1068.0eebc5e.el6.noarch katello-selinux-1.3.1-1.el6.noarch katello-1.3.14-1.git.1068.0eebc5e.el6.noarch katello-all-1.3.14-1.git.1068.0eebc5e.el6.noarch katello-glue-foreman-1.3.14-1.git.1068.0eebc5e.el6.noarch How reproducible: always Steps to Reproduce: 1. Create an organization with environments 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 10. Create Changeset, add published content view into it and try to promote. Here PGError will be shown. Actual results: error is shown Expected results: changeset should be promoted successfully