This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 1459729 - Compute resource for Openstack uses adminURL instead of publicURL for accessing Openstack
Compute resource for Openstack uses adminURL instead of publicURL for accessi...
Status: NEW
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Compute Resources - OpenStack (Show other bugs)
Unspecified Unspecified
medium Severity medium (vote)
: GA
: --
Assigned To: satellite6-bugs
Katello QA List
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2017-06-07 20:54 EDT by Graeme Gillies
Modified: 2017-08-15 16:12 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Graeme Gillies 2017-06-07 20:54:45 EDT
Description of problem:
When adding an openstack compute resource to Satellite, it will throw errors connecting to some Openstack resources (such as cinder) because it defaults to connecting to Openstack services on the adminURL instead of the publicURL. This is because the ruby fog library it uses defaults to adminURL. See

This causes issues because by default, RHOS and RDO TripleO installations always put adminURLs on internal networks that aren't publicly accessible. This is valid because for most non-keystone services, the public and admin urls have the same functionality, and the adminURL is not needed.

Version-Release number of selected component (if applicable):
Satellite 6.2

How reproducible:
Reproducable easily with Satellite 6.2 against RHOS 11

Steps to Reproduce:
1. Do a standard RHOS 11 installation with TripleO
2. Configure compute provider in satellite to point to RHOS 11 installation
3. Attempt to create an instance backed onto a cinder volume

Actual results:
Get an error failing to connect to (cinder internal url)

Expected results:
instance is created successfully

Additional info:
We need to update

to expose the option openstack_endpoint_type to the user (or default it to publicURL)

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