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 1415025

Summary: Choose different org will result in the same org's host number change in organizations page
Product: Red Hat Satellite Reporter: Liushihui <shihliu>
Component: Organizations and LocationsAssignee: Daniel Lobato Garcia <dlobatog>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.7CC: bbuckingham, dlobatog, hsun, jcallaha, sgao, yuefliu
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
URL: http://projects.theforeman.org/issues/18260
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:49:54 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
correct-org1.jpeg
none
wrong-org1.jpeg none

Description Liushihui 2017-01-20 01:29:01 UTC
Description of problem:
In organizations page, when you select a org, the other org's host number is wrong.

Version-Release number of selected component (if applicable):
Satellite6.2.7-sp2
candlepin-0.9.54.15-1.el7.noarch
foreman-1.11.0.65-1.el7sat.noarch
katello-3.0.0-15.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. In satellite webUI, Create a new org named org1.
2. Registered 7 hosts to org1, make sure no host on Default_organization.
3. Go to "Management organization", choose org1, it's correct to show org1's host number is 7, please see screenshot org1.jpeg.
4. Go to "Management organization", choose Default_organization, check the org1's host number.

Actual results:
It will show org1's host number is 0. please see screenshot default_org.jpeg

Expected results:
No matter what org is choosen in organization page, the host's number in the same org shouldn't change. the host's number in org1 should always 7.

Additional info:

Comment 1 Liushihui 2017-01-20 01:30:12 UTC
Created attachment 1242645 [details]
correct-org1.jpeg

Comment 2 Liushihui 2017-01-20 01:30:42 UTC
Created attachment 1242646 [details]
wrong-org1.jpeg

Comment 4 Daniel Lobato Garcia 2017-01-26 15:23:11 UTC
I see this on Foreman nightly too.. working on a fix.

Comment 5 Daniel Lobato Garcia 2017-01-26 15:23:36 UTC
Created redmine issue http://projects.theforeman.org/issues/18260 from this bug

Comment 6 Satellite Program 2017-01-26 17:06:46 UTC
Upstream bug assigned to dlobatog

Comment 7 Satellite Program 2017-01-26 17:06:50 UTC
Upstream bug assigned to dlobatog

Comment 8 Satellite Program 2017-01-30 17:06:52 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18260 has been resolved.

Comment 9 Liushihui 2017-07-21 06:07:05 UTC
It hasn't this problem on satellite6.3.0-sp7, Therefore, verify it.

Comment 10 Satellite Program 2018-02-21 16:49:54 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.

https://access.redhat.com/errata/RHSA-2018:0336