Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1331550 - When selecting openstack as a compute resource, with no credentials, clicking "load tenants" implies a successful connection.
Summary: When selecting openstack as a compute resource, with no credentials, clicking...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources
Version: 6.2.0
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Tomas Strachota
QA Contact: orabin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-28 19:01 UTC by Matthew York
Modified: 2019-09-26 15:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:51:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
A screenshot of the openstack compute resource screen. (43.26 KB, image/png)
2016-04-28 19:01 UTC, Matthew York 		no flags Details
Libvirt-compute resource (48.30 KB, image/png)
2016-04-28 19:08 UTC, Matthew York 		no flags Details
VMWare compute resource (43.88 KB, image/png)
2016-04-28 19:11 UTC, Matthew York 		no flags Details
libvirt without url (47.93 KB, image/png)
2017-08-16 08:19 UTC, orabin 		no flags Details
vmware without url (58.06 KB, image/png)
2017-08-16 08:20 UTC, orabin 		no flags Details
openstack without url (51.88 KB, image/png)
2017-08-16 08:20 UTC, orabin 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16164 0 Normal Closed Testing connection gives false positives for multiple compute resources 2020-02-17 11:38:25 UTC

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
Note You need to log in before you can comment on or make changes to this bug.