Bug 1117342

Summary: Default location detection broke with name change
Product: Red Hat Satellite Reporter: Justin Sherrill <jsherril>
Component: Content ManagementAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: Tazim Kolhar <tkolhar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.4CC: bbuckingham, cperry, cwelton, dcleal, dlobatog, dmitri, jmontleo, jsherril, mmccune, stbenjam, sthirugn, tkolhar
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/6523
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 05:10:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Justin Sherrill 2014-07-08 13:32:35 UTC
Previously the default location looked up based on its name 'Default'.  That recently changed to "Default_Location" and can now be set in the installer. We should set this as a flag on the location itself.

Comment 1 Justin Sherrill 2014-07-08 13:32:36 UTC
Created from redmine issue http://projects.theforeman.org/issues/6523

Comment 2 Justin Sherrill 2014-07-08 13:32:37 UTC
Upstream bug assigned to jsherril

Comment 4 Bryan Kearney 2014-07-09 14:03:36 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/6523 has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|60c6a3cc79b5983262036181a5119ce74abf74f6.

Comment 7 Justin Sherrill 2014-08-25 19:57:02 UTC
To verify this:

1.  Install Katello with --foreman-initial-location="Some_non_standard_name"
2.  Go to Infrastructure > capsules
3.  Verify the premade capsule is in the default location, no matter what its name is.

Comment 9 sthirugn@redhat.com 2014-09-02 15:40:18 UTC
Failed when trying to verify as per Comment 7.

# katello-installer -v --foreman-admin-password='changeme' --foreman-initial-location='newtestorg'
ERROR: Unrecognised option '--foreman-initial-location'

See: 'katello-installer --help'


Version Tested:
GA Snap 7 - Satellite-6.0.4-RHEL-6-20140829.0

Comment 10 Justin Sherrill 2014-10-14 18:16:54 UTC
This option wasn't actually in the installer for GA, but is there for 6.1, moving to Modified

Comment 13 Tazim Kolhar 2015-03-26 10:28:02 UTC
VERIFIED :

# rpm -qa  | grep foreman
foreman-debug-1.7.2.13-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.6-1.el7sat.noarch
foreman-ovirt-1.7.2.13-1.el7sat.noarch
foreman-proxy-1.7.2.4-1.el7sat.noarch
dhcp201-150.englab.pnq.redhat.com-foreman-client-1.0-1.noarch
dhcp201-150.englab.pnq.redhat.com-foreman-proxy-1.0-2.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.3-1.el7sat.noarch
foreman-compute-1.7.2.13-1.el7sat.noarch
foreman-libvirt-1.7.2.13-1.el7sat.noarch
ruby193-rubygem-foreman_docker-1.2.0.6-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.0.9-1.el7sat.noarch
foreman-selinux-1.7.2.8-1.el7sat.noarch
dhcp201-150.englab.pnq.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-discovery-image-2.1.0-9.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el7sat.noarch
foreman-vmware-1.7.2.13-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.3-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.9-1.el7sat.noarch
foreman-gce-1.7.2.13-1.el7sat.noarch
foreman-1.7.2.13-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.8-1.el7sat.noarch
foreman-postgresql-1.7.2.13-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el7sat.noarch

location now is "Default_Location"

Comment 14 Bryan Kearney 2015-08-11 13:26:53 UTC
This bug is slated to be released with Satellite 6.1.

Comment 15 errata-xmlrpc 2015-08-12 05:10:09 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-2015:1592