Red Hat Bugzilla – Bug 1304838
Only Default Organization shows up on 1B. Configure Organization of new deployment
Last modified: 2016-09-13 12:26:06 EDT
Description of problem:
I've created another organization on the RHCI server. It has discovered hosts, and I've linked the capsule, subnet, domain, environment, host group, and location records to it under Administer > Organizations. If I try to create new deployment, though, the 1B. Configure Organization tab shows only the Default Organization as available. Changing the context to the new org doesn't make any difference either.
Either the Configure Organization tab is broken, or there is some undocumented configuration required to get this to work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.) Create a new organization.
2.) Start a new deployment.
The new organization doesn't show up under 1B. Configure Organization.
The new organization should be visible and selectable.
Closing this BZ as we don't plan to support more than default organization in the installer.
I'm reopening this BZ because I don't see this mentioned anywhere in the documentation. In fact, the Getting Started Guide includes creating an organization as a prerequisite. If there are no plans to support other organizations, then at the very least the documentation should reflect that.
"Create an organization, which is a logical group for hosts, you want this deployment to belong to. A default organization is already created. For more information on creating organizations, see the Red Hat Satellite User Guide, Organizations for more information."
Procedure 3.1. Deploying Red Hat Enterprise Virtualization and Red Hat CloudForms:
"Select an organization."
Verified on QCI-1.2-RHEL-7-20160621.t.0.
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.