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:
In the content page, there is possible to compare two different versions of one content view. However, the result is always wrong, as it shows the same amount of packages/erratas in both columns. Moreover, if you add a repository into a CV, then the link "Show 25 More" doesn't work and if you click on it, then you receive a message "Couldn't find Katello::KTEnvironment without an ID".
Version-Release number of selected component (if applicable):
6.1.2
How reproducible + steps to Reproduce:
1) Create a content view, add repository and publish it. Next add another repository and publish new version. Promote the new version to another Lifecycle environment afterwards,
2) Go to Content -> Content Search,
3) Click on search,
4) Add another lifecycle environment using the plus button in the top right corner of the table with compare results,
5) Select the content view versions and click on "Compare selected",
6) You should be able to see two columns comparing the versions.
7) To see the error message mentioned above click on the repository, scroll down and click on the "Show 25 More" link.
Actual results:
The comparison shows no difference between the versions
Expected results:
There will be visible differences in the comparison
Additional info:
Possible related BZ:
#1212450
#1262371
#1241500
Content search was removed in Satellite 6.2; however, there is a bugzilla tracking the need to provide comparison of content view versions. I am going to close this one as a duplicate of it, so that the requests can be tracked together.
*** This bug has been marked as a duplicate of bug 1212450 ***
Description of problem: In the content page, there is possible to compare two different versions of one content view. However, the result is always wrong, as it shows the same amount of packages/erratas in both columns. Moreover, if you add a repository into a CV, then the link "Show 25 More" doesn't work and if you click on it, then you receive a message "Couldn't find Katello::KTEnvironment without an ID". Version-Release number of selected component (if applicable): 6.1.2 How reproducible + steps to Reproduce: 1) Create a content view, add repository and publish it. Next add another repository and publish new version. Promote the new version to another Lifecycle environment afterwards, 2) Go to Content -> Content Search, 3) Click on search, 4) Add another lifecycle environment using the plus button in the top right corner of the table with compare results, 5) Select the content view versions and click on "Compare selected", 6) You should be able to see two columns comparing the versions. 7) To see the error message mentioned above click on the repository, scroll down and click on the "Show 25 More" link. Actual results: The comparison shows no difference between the versions Expected results: There will be visible differences in the comparison Additional info: Possible related BZ: #1212450 #1262371 #1241500