Project

General

Profile

Actions

Bug #15164

open

Need a method of specifying associated org when registering a smart proxy

Added by Stephen Benjamin almost 8 years ago. Updated about 7 years ago.

Status:
New
Priority:
Normal
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1326465
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.


Related issues 2 (0 open2 closed)

Related to Katello - Feature #15167: Inform the user they can register their proxy to org/location with the installer commandRejectedStephen BenjaminActions
Related to Foreman - Feature #26092: When only one taxonomy of specific type is defined, api should default to that taxonomyClosedTomer BriskerActions
Actions #1

Updated by Stephen Benjamin almost 8 years ago

  • Project changed from Foreman to Installer
  • Subject changed from Need a method of specifying associated org when installing a capsule to Need a method of specifying associated org when registeringa smart proxy
  • Category changed from Smart Proxy to Foreman modules
Actions #2

Updated by Stephen Benjamin almost 8 years ago

  • Subject changed from Need a method of specifying associated org when registeringa smart proxy to Need a method of specifying associated org when registering a smart proxy
Actions #3

Updated by Stephen Benjamin almost 8 years ago

  • Related to Feature #15167: Inform the user they can register their proxy to org/location with the installer command added
Actions #5

Updated by Tomer Brisker about 5 years ago

  • Related to Feature #26092: When only one taxonomy of specific type is defined, api should default to that taxonomy added
Actions

Also available in: Atom PDF