Bug 1302377 - rhel-osp-installer fail to install due to 'Could not evaluate: Could not load data from https://xxx/'
Summary: rhel-osp-installer fail to install due to 'Could not evaluate: Could not load...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhel-osp-installer
Version: Foreman (RHEL 6)
Hardware: All
OS: Linux
high
high
Target Milestone: ---
: 8.0 (Liberty)
Assignee: Mike Burns
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-27 16:23 UTC by Jaison Raju
Modified: 2019-09-12 09:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-29 13:25:13 UTC
Target Upstream Version:


Attachments (Terms of Use)

Comment 4 Faiaz Ahmed 2016-01-29 00:03:02 UTC
I notice the it was stopped at the stage

~~~~~~~~~~~~~~~~~~~~~~
Networking setup has finished
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[test.test.com]: Could not evaluate: Could not load data from https://test.test.com
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[test.test.com]: Failed to call refresh: Could not load data from https://test.test.com
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[test.test.com]: Could not load data from https://test.test.com
Installing             Done                                               [100%] [........................................................................................................................]
Not running provisioning configuration since installation encountered errors, exit code was 6
  Something went wrong! Check the log for ERROR-level output
  The full log is at /var/log/rhel-osp-installer/rhel-osp-installer.log
~~~~~~~~~~~~~~~~~~~~~~

So asked customer to disable SeLinux. After SeLinux disable,  the installation was successful and started the configuration.

Comment 5 Pavel Moravec 2016-06-08 13:15:43 UTC
Trivially reproducible:

- have a Content Host registered to a Capsule
- on Satellite, stop qdrouterd service
- monitor memory usage of goferd on the Content Host

Stopping qdrouterd on Capsule instead of Satellite does _not_ cause the leak. So it seems to be a bug in qpid-proton library since just link fails, not (TCP+AMQP) connection.

Comment 6 Pavel Moravec 2016-06-08 13:16:24 UTC
(In reply to Pavel Moravec from comment #5)
> Trivially reproducible:
> 
> - have a Content Host registered to a Capsule
> - on Satellite, stop qdrouterd service
> - monitor memory usage of goferd on the Content Host
> 
> Stopping qdrouterd on Capsule instead of Satellite does _not_ cause the
> leak. So it seems to be a bug in qpid-proton library since just link fails,
> not (TCP+AMQP) connection.

Please disregard, wrong BZ.

Comment 7 Jaromir Coufal 2016-09-29 13:25:13 UTC
Closing list of bugs for RHEL OSP Installer since its support cycle has already ended [0]. If there is some bug closed by mistake, feel free to re-open.

For new deployments, please, use RHOSP director (starting with version 7).

-- Jaromir Coufal
-- Sr. Product Manager
-- Red Hat OpenStack Platform

[0] https://access.redhat.com/support/policy/updates/openstack/platform


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