Red Hat Bugzilla – Bug 1272224
Discovery of vCenter 5.5 fails for some configurations
Last modified: 2015-12-08 08:38:48 EST
Description of problem:
Attempted discovery of VSCA 5.5 results in "NOT DISCOVERED"
Version-Release number of selected component (if applicable):
100% for specific configurations
Steps to Reproduce:
1. Infrastructure > Providers
2. Configuration > Discover Infrastructure Provider
3. Discover: VMware vCenter
4. Enter IP range
5. Click Start
"NOT DISCOVERED" messages in evm.log
"DISCOVERED" messages in evm.log
Manual adding is successful
CloudForms is looking for ports 7444 and 2014. In this configuration, VMware is actually listening on ports 7444 and 2012. We believe ports 2012, 2013, and 2014 may be chosen, depending on SSO configuration.
Reproducer environment can be made available
Pull Request https://github.com/ManageIQ/manageiq/pull/5041
New commit detected on ManageIQ/manageiq/master:
Author: Adam Grare <firstname.lastname@example.org>
AuthorDate: Wed Oct 21 17:01:57 2015 -0400
Commit: Adam Grare <email@example.com>
CommitDate: Wed Oct 21 17:01:57 2015 -0400
Check for all VC SSO ports during discovery
When performing a port scan of a VC for provider discovery not all
SSO ports were being checked so that depending on configuration
not all VCs were being detected.
gems/pending/discovery/modules/VMwareEsxVcProbe.rb | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
Checked against 3 of our environments and all were discovered
Verified in 18.104.22.168
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.