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 1506591 - Location where new subscribed hosts will put upon registration is not updated after renaming location
Summary: Location where new subscribed hosts will put upon registration is not updated...
Keywords:
Status: CLOSED DUPLICATE of bug 1502505
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Registration
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-26 11:24 UTC by Nikhil Kathole
Modified: 2017-10-27 12:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-27 12:18:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Nikhil Kathole 2017-10-26 11:24:49 UTC 
Description of problem: We renamed the location and registered a host. But registered host didn't get associated to renamed location.


Version-Release number of selected component (if applicable): satellite 6.3 snap 21


How reproducible: always


Steps to Reproduce:
1. Create location "apple"
2. Navigate to Administer -> settings -> content 
3. Set Default Location subscribed hosts parameter to "apple"
4. Rename the location "apple"
5. Register the content host 

Actual results:
Subscribed hosts was not put under renamed location upon registration and Default Location subscribed hosts parameter under settings showed "Empty" in UI and hammer settings list showed old name of location.  

Expected results:
Subscribed host should put in renamed location upon registration and Default Location subscribed hosts parameter under settings in UI and hammer settings list should show correct renamed location.  


Additional info:
Comment 2 Brad Buckingham 2017-10-27 02:05:44 UTC 
Justin, would this happen to be solved by the solution for bug 1502505?
Comment 3 Brad Buckingham 2017-10-27 02:06:02 UTC 
i.e. is this a duplicate?
Comment 4 Justin Sherrill 2017-10-27 12:18:00 UTC 
Yes, i would consider it a duplicate

*** This bug has been marked as a duplicate of bug 1502505 ***
Note You need to log in before you can comment on or make changes to this bug.