Hide Forgot
Created attachment 1152040 [details] A screenshot of the openstack compute resource screen. Description of problem: Under "Infrastructure" -> "Compute resources" -> "New compute resource", before I add any details about my openstack compute resource, if I click load tenants I get a green box in the top right hand corner saying "Success: Test connection was successful". I don't have an openstack instance, so this message is at best misleading. Version-Release number of selected component (if applicable): Sat 6.2.0 Beta - How reproducible: Every time. Steps to Reproduce: 1.Log into Sat 6 2. Select "Infrastructure" -> "Compute resources" -> "New compute resource", 3.click load tenants 4. Observe success message. Actual results: False success message on screen. Expected results: Error message, or nothing at all. Additional info:
Created attachment 1152041 [details] Libvirt-compute resource
After further testing, this affects the RHEV, libvirt and vmware compute resources as well. However docker, ec2 and google compute resources seem to behave correctly.
Created attachment 1152042 [details] VMWare compute resource
Given this is copuld mislead the customer, and it affects multiple compute resources, i've bumped the severity up to medium.
Created redmine issue http://projects.theforeman.org/issues/16164 from this bug
Upstream bug assigned to tstrachota
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16164 has been resolved.
Created attachment 1313989 [details] libvirt without url
Created attachment 1313990 [details] vmware without url
Created attachment 1313991 [details] openstack without url
Verified. Version Tested: Satellite-6.3 Snap 11. Steps to verify: 1. Go to "Infrastructure" -> "Compute resources" 2. Click "Create compute resource" 3. Choose "Provider" libvirt/vmware/openstack 4. Click "Test Connection"/"Load Tenants"/"Load Datacenters" 5. Check if a success message appears There was no success message, see screenshots attached.
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. > > https://access.redhat.com/errata/RHSA-2018:0336