Bug 1326465 - Need a method of specifying associated org when installing a capsule
Summary: Need a method of specifying associated org when installing a capsule
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Stephen Benjamin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On: 1339711
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-12 18:12 UTC by Corey Welton
Modified: 2021-03-11 14:32 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 18:02:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 15164 0 None None None 2016-05-24 14:09:48 UTC

Description Corey Welton 2016-04-12 18:12:02 UTC
Description of problem:

When I install a capsule, I should have a way to specify what org this capsule should be associated with upon install.  Currently it is a manual step and it is not at all intuitive since it remains pigeonholed away in the no org context, after installation.

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

SNAP 7.1

How reproducible:
every time

Steps to Reproduce:

1. Follow all the normal steps to install a capsule:

* Register host to satellite; register to org "Default Organization"
* generate capsule cert on satellite
* install capsule rpms on target host
* follow steps listed upon generating capsule cert to install capsule on target host.

2. In Satellite UI, set/assume context to be Default Organization 
3. navigate to Infrastructure > Capsules
4. Look for your capsule
5. set context to "Any Context"
6. REPEAT STEPS 3-4.

Actual results:

After successful creation of capsule, it is not intuitive as to where that capsule is, and at a minimum, a second step is required to set the org after installing capsule.

Expected results:

There should be a way to determine associated org at install time, just like when registering the box.

I am unsure whether assuming we want to use the registered org as a default is a correct assumption, but it's an example.  We shouldn't have to install the capsule and subsequently then go and assign an org.

When a capsule is not associated with any org, it sort of falls into a "black hole" and is not immediately seen. So user actually has to do multiple steps to assign the org:

1. install capsule
2. change context to find newly installed capsule
3. associate capsule with org.


Additional info:

Some might argue this is an RFE.  I would argue that it it's a critical shortcoming in how we're installing a capsule.

Comment 2 Brad Buckingham 2016-04-14 14:19:10 UTC
I am triaging this one in for GA for usability; however, we need to investigate the feasibility of addressing it.

Ivan, do you know if this one is possible to address?  I can certainly see how it would help Satellite users given that we ship with taxonomy support.  Do you have someone that could investigate?  This could be change to installer or proxy or both.

Comment 3 Ivan Necas 2016-04-15 08:18:52 UTC
I see the issue and feel pretty similar about the usability concern (I started thinking about the best way to fix it even prior seeing this BZ). There are two approaches I can think of:

1. an installer option to specify the org/location to capsule installer
2. determining the initial defaults form content host in https://github.com/Katello/katello/blob/master/app/models/katello/concerns/smart_proxy_extensions.rb#L86

I lean towards the 2nd option, as we already need to register the capsule host and in kind-of makes sense to keep the assignment consistent. Ideal solution would be both, but just one of them should be enough to resolve the original issue.

Comment 4 Stephen Benjamin 2016-05-24 12:06:24 UTC
Why is this all private comments? Default to open please!

The capsule isn't required to be registered as a content host anymore so #2 isn't a good option.  Most capsules probably are registered but because it's not required, option 1 is better.


This is definitely a feature even though it's a big usability win.  I really think it should go to a z-Stream when we're so close to GA...

Comment 5 Mike McCune 2016-05-24 13:33:30 UTC
updated to public comments

Comment 6 Stephen Benjamin 2016-05-24 14:09:46 UTC
Created redmine issue http://projects.theforeman.org/issues/15164 from this bug

Comment 7 Bryan Kearney 2016-05-24 16:15:58 UTC
Upstream bug component is Installer

Comment 8 Stephen Benjamin 2016-05-24 16:32:28 UTC
Thanks, per discussion on IRC we'll try for 6.2 since it's pretty frustrating for end-users.  PR's open upstream

https://github.com/theforeman/puppet-foreman/pull/448
https://github.com/theforeman/puppet-foreman_proxy/pull/253

Comment 10 Bryan Kearney 2018-09-04 18:02:53 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


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