Bug 1331550

Summary: When selecting openstack as a compute resource, with no credentials, clicking "load tenants" implies a successful connection.
Product: Red Hat Satellite Reporter: Matthew York <myork>
Component: Compute ResourcesAssignee: Tomas Strachota <tstrachota>
Status: CLOSED ERRATA QA Contact: orabin
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.0CC: bbuckingham, bkearney, jcallaha, myork, oprazak, orabin, pcfe, sjagtap
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:51:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
A screenshot of the openstack compute resource screen.
none
Libvirt-compute resource
none
VMWare compute resource
none
libvirt without url
none
vmware without url
none
openstack without url none

Description Matthew York 2016-04-28 19:01:13 UTC
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:

Comment 1 Matthew York 2016-04-28 19:08:37 UTC
Created attachment 1152041 [details]
Libvirt-compute resource

Comment 2 Matthew York 2016-04-28 19:10:48 UTC
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.

Comment 3 Matthew York 2016-04-28 19:11:28 UTC
Created attachment 1152042 [details]
VMWare compute resource

Comment 4 Matthew York 2016-04-28 19:50:33 UTC
Given this is copuld mislead the customer, and it affects multiple compute resources, i've bumped the severity up to medium.

Comment 6 Ondřej Pražák 2016-08-18 11:26:56 UTC
Created redmine issue http://projects.theforeman.org/issues/16164 from this bug

Comment 7 Bryan Kearney 2016-08-29 16:16:14 UTC
Upstream bug assigned to tstrachota

Comment 8 Bryan Kearney 2016-08-29 16:16:17 UTC
Upstream bug assigned to tstrachota

Comment 9 Bryan Kearney 2016-09-01 12:16:39 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16164 has been resolved.

Comment 12 orabin 2017-08-16 08:19:38 UTC
Created attachment 1313989 [details]
libvirt without url

Comment 13 orabin 2017-08-16 08:20:10 UTC
Created attachment 1313990 [details]
vmware without url

Comment 14 orabin 2017-08-16 08:20:50 UTC
Created attachment 1313991 [details]
openstack without url

Comment 15 orabin 2017-08-16 08:24:49 UTC
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.

Comment 16 Satellite Program 2018-02-21 16:51:07 UTC
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