Bug 1845657 - Openstack Compute Resource openstack_endpoint_type
Summary: Openstack Compute Resource openstack_endpoint_type
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - OpenStack
Version: 6.7.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: 6.10.0
Assignee: satellite6-bugs
QA Contact: Peter Dragun
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-09 18:22 UTC by Bharati Kailas Shahu
Modified: 2021-11-16 14:09 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 14:09:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 28311 0 Normal Ready For Testing Openstack Compute Resource openstack_endpoint_type 2021-02-18 15:29:39 UTC
Red Hat Knowledge Base (Solution) 5670241 0 None None None 2021-10-07 06:29:22 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:09:23 UTC

Description Bharati Kailas Shahu 2020-06-09 18:22:33 UTC
Description of problem:
Configuration of host provisioning on Openstack compute resources: editing existing hosts previously provisioned by Satellite on Openstack platform always times out.
 In addtion, on the page of setting up Openstack (Compute Resources -> our openstack instance -> edit), clicking the "Test Connection" button always times out with an error message "connect_write timeout reached".


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

How reproducible:
Every time

Steps to Reproduce:
1. Configuration of host provisioning on Openstack compute resources: editing existing hosts previously provisioned by Satellite on Openstack platform always times out.
2. In addtion, on the page of setting up Openstack (Compute Resources -> our openstack instance -> edit), clicking the "Test Connection" button always times out with an error message "connect_write timeout reached"
3. While analyzing communications between Satellite server and Openstack API endpoint in tcpdump, found that Satellite server has been trying to communicate over TCP port 35357.
4. It looks like fog is defaulting to the 'adminURL' over port 35357 on some actions.
5. In file /usr/share/foreman/app/models/compute_resources/foreman/model/openstack.rb
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
def url_for_fog
      u = URI.parse(url)
      "#{u.scheme}://#{u.host}:#{u.port}"
    end

    def fog_credentials
      { :provider           => :openstack,
        :openstack_api_key  => password,
        :openstack_username => user,
        :openstack_auth_url => url_for_fog,    
        :openstack_identity_endpoint => url_for_fog,  
      }.tap do |h|
        if tenant.present?
          if identity_version == 2
            h[:openstack_tenant] = tenant
          else
            h[:openstack_project_name] = tenant
          end

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Actual results: Error message "connect_write timeout reached".


Expected results: Should not through any error.


Additional info: Upstream bug: https://projects.theforeman.org/issues/28311

Comment 8 Bryan Kearney 2021-02-24 12:00:47 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/28311 has been resolved.

Comment 9 Peter Dragun 2021-09-08 14:54:28 UTC
Verified on Sat6.10 snap 16

In compute resource edit view test connection succeeded.

Editing host previously provisioned by Satellite on Openstack platform also works without any errors or timeouts.

Comment 12 errata-xmlrpc 2021-11-16 14:09:12 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 (Moderate: Satellite 6.10 Release), 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-2021:4702


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