Red Hat Bugzilla – Bug 1254192
[RFE] Take a set of default credentials for RHEV Provider Hosts
Last modified: 2018-01-29 07:36:41 EST
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install CloudForms Management Engine
2. Configure a RHEV Provider
3. Potentially many Hypervisors/Hosts will be automatically created.
Each one requires manual configuration of credentials
It would be nice if there were a way to configure a default set of credentials for new hosts so that they don't need to be configured manually.
I was attempting to use mechanize to create the Hosts for the provider with the correct credentials and then configure the Provider, letting the relationship be updated at which time everything works, but I hit https://bugzilla.redhat.com/show_bug.cgi?id=944685
After talking to the CloudForms team I was told this isn't really supported and it's a bug that I can create a non-ESXi Host.
My apologies for leaving the description empty.
If it's not clear what I am seeing is that we have to manually add the credentials to a potentially large set of discovered hosts. It would be nice if we could provider a set of default credentials for discovered Hosts so they don't require any manual configuration.
Sorry, I just realized my last two updates were not meant for this BZ...
Greg - it sounds like a general issue, and not a rhev one.
What am I missing?
@Oved, yeah, I think you're probably correct. In fact, I don't even know how this would be done without a decent amount of general UX help to determine when/how a user would enter default host credentials.
I'm removing the rhev whiteboard. I'll ask @johnhardy about the priority of this.
John, is this something we should put on our backlog? If so, where does it sit in priority considering it may be something we'd implement for both RHEV and VMWare. And, also considering I don't know of any customer requests for this type of feature.
Based on comment #7 this isn't RHEV specific. Removing rhev from the whiteboard.
This bug has been open for more than a year and is assigned to an older release of CloudForms.
If you would like to keep this Bugzilla open and if the issue is still present in the latest version of the product, please file a new Bugzilla which will be added and assigned to the latest release of CloudForms.