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.

Bug 1205379

Summary:

Trying to remove a content view indicates "affected hosts" that do not use said CV

Product:

Red Hat Satellite

Reporter:

Corey Welton <cwelton>

Component:

Content Management

Assignee:

David Davis <daviddavis>

Status:

CLOSED CURRENTRELEASE

QA Contact:

Tazim Kolhar <tkolhar>

Severity:

high

Docs Contact:

Priority:

unspecified

Version:

Unspecified

CC:

bkearney, cwelton, daviddavis, tkolhar

Target Milestone:

Unspecified

Target Release:

Unused

Hardware:

Unspecified

OS:

Unspecified

URL:

http://projects.theforeman.org/issues/9890

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2015-08-12 13:59:32 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
affected content host	none

Description Corey Welton 2015-03-24 19:34:03 UTC

Description of problem:

When you have two parallel content paths - say, RHEL6 and RHEL7 - and systems registered using each, subsequently trying to remove one of the paths, indicates "affected hosts" that do not actually consume content from that CV.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  Sync RHEL6 content; create RHEL6 CV/pub/promote; add RHEL6CV to ak
2.  Register RHEL6 box(es)
3.  Sync RHEL7 content; create RHEL7 CV/pub/promote; add RHEL67V to ak
4.  Register RHEL7 box(es)
5.  Attempt to remove RHEL6 CV (first remove rhel6 AK, etc., I think?)
  * Remove View > Remove Version > Next
  * Show Affected Content Hosts

Actual results:

Hosts that show up in "Affected Content Hosts" that are not RHEL6 and/or should not be affected.

Expected results:
We should not show hosts that are not affected
 
Additional info:
This is more critical than it looks because I am forced to move those hosts somewhere else (even though they don't need to be) in order to remove the view.

Comment 2 Partha Aji 2015-03-24 20:53:54 UTC

Created redmine issue http://projects.theforeman.org/issues/9890 from this bug

Comment 3 David Davis 2015-03-25 20:10:33 UTC

By the way, you don't have to sync RHEL content to reproduce. You can reproduce with a content view that even has no content at all.

Comment 4 Bryan Kearney 2015-03-25 22:05:33 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/9890 has been closed
-------------
David Davis
Applied in changeset commit:katello|b27e0a422acf2d81475af5c806798f3b11c0f228.

Comment 6 Tazim Kolhar 2015-04-30 09:03:21 UTC

VERIFIED:

# rpm -qa | grep foreman
ruby193-rubygem-foreman_docker-1.2.0.10-1.el6_6sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch
foreman-debug-1.7.2.18-1.el6_6sat.noarch
foreman-vmware-1.7.2.18-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.6-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.8-1.el6_6sat.noarch
puppet-foreman_scap_client-0.3.3-8.el6_6sat.noarch
foreman-1.7.2.18-1.el6_6sat.noarch
foreman-libvirt-1.7.2.18-1.el6_6sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.12-1.el6_6sat.noarch
rubygem-hammer_cli_foreman-0.1.4.10-1.el6_6sat.noarch
foreman-postgresql-1.7.2.18-1.el6_6sat.noarch
foreman-selinux-1.7.2.13-1.el6_6sat.noarch
qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch
foreman-compute-1.7.2.18-1.el6_6sat.noarch
foreman-gce-1.7.2.18-1.el6_6sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.12-1.el6_6sat.noarch
foreman-proxy-1.7.2.4-1.el6_6sat.noarch
qe-sat6-rhel66.usersys.redhat.com-foreman-client-1.0-1.noarch
qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-ovirt-1.7.2.18-1.el6_6sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el6_6sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.4-1.el6_6sat.noarch

steps:
1.  Sync RHEL6 content; create RHEL6 CV/pub/promote; add RHEL6CV to ak
2.  Register RHEL6 box(es)
3.  Sync RHEL7 content; create RHEL7 CV/pub/promote; add RHEL67V to ak
4.  Register RHEL7 box(es)
5.  Attempt to remove RHEL6 CV (first remove rhel6 AK, etc., I think?)
  * Remove View > Remove Version > Next
  * Show Affected Content Hosts

only hosts that are affected is shown 

screenshot attached

Comment 7 Tazim Kolhar 2015-04-30 09:04:10 UTC

Created attachment 1020469 [details]
affected content host

Comment 8 Bryan Kearney 2015-08-11 13:34:22 UTC

This bug is slated to be released with Satellite 6.1.

Comment 9 Bryan Kearney 2015-08-12 13:59:32 UTC

This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.