Bug 1267347 - Provider status displays URI error an SCVMM instance has an ESX host added to the Fabric
Summary: Provider status displays URI error an SCVMM instance has an ESX host added to...
Keywords:
Status: CLOSED DUPLICATE of bug 1153706
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.6.0
Assignee: Bronagh Sorota
QA Contact: Jeff Teehan
URL:
Whiteboard: scvmm:ems_refresh
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-29 17:45 UTC by Jeff Teehan
Modified: 2016-10-03 16:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-19 13:26:08 UTC
Category: ---
Cloudforms Team: Unknown
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jeff Teehan 2015-09-29 17:45:02 UTC
Description of problem:


Version-5.5.0.2


How reproducible:Always


Steps to Reproduce:
1.  Open SCVMM instance, select Fabric and add a vCenter Server
2.  Click VM tab and add vCenter Cluster as a Host
3.  In appliance, refresh the provider Relationships

Actual results:

In Status:Last Refresh you will see an error message stating the URI (example: "esx-55-01") invalid.

When this occurs, nothing from the provider updates and the provider is unusable.


Expected results:

I don't know if we want to actually manage cross-vendor hosts, but at a minimum it would be nice if we simply ignored it or perhaps placed it in a read-only state.

Additional info:

This takes a while to setup and it disrupts all appliances that use the SCVMM instance, so please contact me (jeff teehan) when you need to reproduce it and I'll get it all setup.  It takes about 10-15 to set it up and another 10 to tear it down.

I don't know how common it is to do this, except that I've always put ESX hosts on my SCVMM instances and my Hyper-V hosts on my vCenter instances so that I could do simple stuff without having to fire up another management system.

Comment 2 Bronagh Sorota 2016-02-19 13:26:08 UTC

*** This bug has been marked as a duplicate of bug 1153706 ***


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