Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionBharati 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
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.
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
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