Created attachment 1229593 [details] IPv6 error on Add Provider - SCVMM This same provider works just find with IPv4
Log shows identical errors whether its vmware or scvmm. I used the same vmware provided that was used before per an email from dajo. My appliance has an IPv6 address on eth0. [----] I, [2016-12-08T14:48:00.077711 #24906:bad22c] INFO -- : MIQ(MiqFaultTolerantVim._connect) EMS: [vs56] Connecting with address: [https://[fe80::20c:29ff:fe46:38e3]], userid: [root]... [----] W, [2016-12-08T14:48:00.077970 #24906:bad22c] WARN -- : MIQ(ManageIQ::Providers::Vmware::InfraManager#verify_credentials) #<URI::InvalidComponentError: bad component(expected host component): [https://[fe80::20c:29ff:fe46:38e3]]> [----] W, [2016-12-08T14:48:00.078201 #24906:bad22c] WARN -- : MIQ(ManageIQ::Providers::Vmware::InfraManager#authentication_check_no_validation) type: ["default"] for [] [vs56] Validation failed: error, Unexpected response returned from Cloud/Infrastructure Providers, see log for details [----] E, [2016-12-08T14:48:00.078384 #24906:bad22c] ERROR -- : MIQ(ems_infra_controller-create): Credential validation was not successful: Unexpected response returned from Cloud/Infrastructure Providers, see log for details [----] I, [2016-12-08T14:48:02.657494 #23281:47f130] INFO -- : MIQ(MiqServer#monitor_loop) Server Monitoring Complete - Timings: {:server_dequeue=>0.002899169921875, :worker_monitor=>1.1296374797821045, :worker_dequeue=>0.01294088363647461, :total_time=>1.1456718444824219} Worked with Aparna and we think this could be a different error given the bad component issue above. If possible, we should kick it to 5.7.1. We agreed to leave it ONQA for now given the priority. My suggestion is to move it to 5.7.1 as I don't see any associated customer tickets.
midair collision reset the status.