Bug 1431778 - Composite Content View shows incorrect total number of included repos
Summary: Composite Content View shows incorrect total number of included repos
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Views   
(Show other bugs)
Version: 6.2.7
Hardware: x86_64
OS: Linux
medium vote
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: Ales Dujicek
Keywords: Triaged
Depends On:
TreeView+ depends on / blocked
Reported: 2017-03-13 17:50 UTC by Rick Dixon
Modified: 2019-04-01 20:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-02-21 17:07:43 UTC
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
repositories count should be 1 (58.04 KB, image/png)
2017-08-09 13:22 UTC, Djebran Lezzoum
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 18983 None None None 2017-03-22 13:29 UTC

Comment 4 Brad Buckingham 2017-03-22 13:27:35 UTC
Note: currently it is showing 'all' instances of the repository based upon the component versions associated with the composite.  

Example scenario:
1. component version 2.0 is associated with the composite
2. the component version (2.0) has 4 repositories associated with it
3. the component version (2.0) has been promoted to 3 lifecycle environments (dev, test & prod)

The result will be:
4 repos to represent the 2.0 version (archived repos)
4 repos in dev
4 repos in test
4 repos in prod
16 repos

The correct result should be 4 representing only the archived repos.

Comment 5 Brad Buckingham 2017-03-22 13:29:23 UTC
Created redmine issue http://projects.theforeman.org/issues/18983 from this bug

Comment 6 Brad Buckingham 2017-03-22 13:43:19 UTC
Proposed solution in upstream katello PR: https://github.com/Katello/katello/pull/6694

Comment 7 Djebran Lezzoum 2017-08-09 13:21:29 UTC
The bug still affecting satellite

* candlepin-2.0.40-1.el7.noarch
* candlepin-selinux-2.0.40-1.el7.noarch
* foreman-1.15.2-1.el7sat.noarch
* foreman-cli-1.15.2-1.el7sat.noarch
* foreman-compute-1.15.2-1.el7sat.noarch
* foreman-debug-1.15.2-1.el7sat.noarch
* foreman-discovery-image-3.1.1-22.el7sat.noarch
* foreman-ec2-1.15.2-1.el7sat.noarch
* foreman-gce-1.15.2-1.el7sat.noarch
* foreman-installer-1.15.2-1.el7sat.noarch
* foreman-installer-katello-3.4.4-1.el7sat.noarch
* foreman-libvirt-1.15.2-1.el7sat.noarch
* foreman-openstack-1.15.2-1.el7sat.noarch
* foreman-ovirt-1.15.2-1.el7sat.noarch
* foreman-postgresql-1.15.2-1.el7sat.noarch
* foreman-proxy-1.15.2-1.el7sat.noarch
* foreman-rackspace-1.15.2-1.el7sat.noarch
* foreman-selinux-1.15.2-1.el7sat.noarch
* foreman-vmware-1.15.2-1.el7sat.noarch
* katello-3.4.4-2.el7sat.noarch
* katello-ca-consumer-sat-r220-02.lab.eng.rdu2.redhat.com-1.0-4.noarch
* katello-certs-tools-2.4.0-1.el7sat.noarch
* katello-client-bootstrap-1.4.0-1.el7sat.noarch
* katello-common-3.4.4-2.el7sat.noarch
* katello-debug-3.4.4-2.el7sat.noarch
* katello-default-ca-1.0-1.noarch
* katello-installer-base-3.4.4-1.el7sat.noarch
* katello-selinux-3.0.2-1.el7sat.noarch
* katello-server-ca-1.0-1.noarch
* katello-service-3.4.4-2.el7sat.noarch
* openldap-2.4.44-5.el7.x86_64
* pulp-client-1.0-1.noarch
* pulp-docker-plugins-2.3.0-1.el7sat.noarch
* pulp-katello-1.0.2-1.el7sat.noarch
* pulp-ostree-plugins-1.2.1-1.el7sat.noarch
* pulp-puppet-plugins-2.12.2-1.el7sat.noarch
* pulp-puppet-tools-2.12.2-1.el7sat.noarch
* pulp-rpm-plugins-2.12.2-2.el7sat.noarch
* pulp-selinux-2.12.2-2.el7sat.noarch
* pulp-server-2.12.2-2.el7sat.noarch
* python-ldap-2.4.15-2.el7.x86_64
* tfm-rubygem-ldap_fluff-0.4.6-1.el7sat.noarch
* tfm-rubygem-net-ldap-0.15.0-1.el7sat.noarch

see attached screen repos should be 1

Comment 8 Djebran Lezzoum 2017-08-09 13:22 UTC
Created attachment 1311217 [details]
repositories count should be 1

Comment 9 Brad Buckingham 2017-08-22 19:58:50 UTC
Hi Djebran, 

I am unable to reproduce the failure on my Satellite 6.3 SNAP 11 environment. I have tried both with the original description and comment 4.

Can you provide the steps for your test scenario?
Also, would it be possible for me to log in to your server to take a peak as well?


Comment 20 Bryan Kearney 2018-02-21 17:07:43 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.