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 1302515 - need option in the webui to set location as default post-install
Summary: need option in the webui to set location as default post-install
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Organizations and Locations
Version: Nightly
Hardware: x86_64
OS: Linux
low
low
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: 1268012
TreeView+ depends on / blocked
 
Reported: 2016-01-28 03:13 UTC by Chris Roberts
Modified: 2017-01-13 20:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-13 20:59:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Chris Roberts 2016-01-28 03:13:14 UTC
Description of problem:

BZ 1268012 states that we can not delete a default location as long as katello_default is set to true. This is fine if a customer put in a location during install, but if they did not post install we need an option to set a newly created location as katello_default so we can delete the default_location created by the installer.

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


How reproducible:


Steps to Reproduce:
1. run katello-installer without any args
2. Try to delete the default_location
3. try to set default location to false with rails even after setting the new location to true results in a rollback.

Actual results:


Expected results:


Additional info:

1268012 is blocked on this

Comment 2 Bryan Kearney 2016-07-26 19:05:43 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 3 Bryan Kearney 2017-01-13 20:59:57 UTC
I do not envision this bug being addressed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.


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