Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1152351

Summary: rhel-osp-installer fails with "Could not load data from" staypuft host
Product: Red Hat OpenStack Reporter: John Eckersberg <jeckersb>
Component: rhel-osp-installerAssignee: Mike Burns <mburns>
Status: CLOSED EOL QA Contact: Omri Hochman <ohochman>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: Foreman (RHEL 6)CC: mburns, rhos-maint, srevivo
Target Milestone: ---Keywords: ZStream
Target Release: Installer   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ruby193-rubygem-staypuft-0.4.5-1.el6ost ruby193-rubygem-ipaddress-0.8.0-6.el6ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-29 13:23:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
installer log none

Description John Eckersberg 2014-10-14 01:31:38 UTC
Description of problem:
I continue to be unable to run rhel-osp-installer successfully on a freshly installed host.

Version-Release number of selected component (if applicable):
[root@staypuft ~]# rpm -qa | grep -e staypuft -e foreman -e osp -e puppet | sort
foreman-1.6.0.44-4.el6ost.noarch
foreman-discovery-image-7.0-20140905.0.2.el7sat.noarch
foreman-installer-1.6.0-0.2.RC1.el6ost.noarch
foreman-mysql2-1.6.0.44-4.el6ost.noarch
foreman-postgresql-1.6.0.44-4.el6ost.noarch
foreman-proxy-1.6.0.30-2.el6ost.noarch
foreman-selinux-1.6.0.14-1.el6sat.noarch
openstack-foreman-installer-2.0.29-1.el6ost.noarch
openstack-puppet-modules-2014.1-24.el6ost.noarch
puppet-3.6.2-1.1.el6.noarch
puppet-server-3.6.2-1.1.el6.noarch
rhel-osp-installer-0.4.3-1.el6ost.noarch
ruby193-rubygem-foreman_discovery-1.3.0-2.2.el6ost.noarch
ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch
ruby193-rubygem-foreman-tasks-0.6.9-1.1.el6sat.noarch
ruby193-rubygem-staypuft-0.4.5-1.el6ost.noarch
rubygem-foreman_api-0.1.11-6.el6sat.noarch


How reproducible:
Always


Steps to Reproduce:
1. Run rhel-osp-installer
2. Answer initial questions
3. Failure in puppet run after "Networking setup has finished"

Actual results:
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[staypuft.example.org]: Could not evaluate: Could not load data from https://staypuft.example.org
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[staypuft.example.org]: Failed to call refresh: Could not load data from https://staypuft.example.org
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[staypuft.example.org]: Could not load data from https://staypuft.example.org
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


Expected results:
Glorious success

Additional info:

Comment 1 John Eckersberg 2014-10-14 01:36:00 UTC
Created attachment 946638 [details]
installer log

Here's the installer log.  Note that it's trying to access:

https://staypuft.example.org/apidoc/v2.json

Which gives a 404.  There is no apidoc under the public directory:

[root@staypuft ~]# ls /usr/share/foreman/public/
404.html  422.html  500.html  apipie-cache  assets  blank.html  robots.txt

However there is an apidoc under apipie-cache which does have the v2.json file:

[root@staypuft ~]# ls /usr/share/foreman/public/apipie-cache/apidoc/
v1  v1.html  v1.json  v2  v2.html  v2.json

Comment 2 John Eckersberg 2014-10-14 01:38:40 UTC
Also relevant bits from httpd logs:

[root@staypuft ~]# cat /var/log/httpd/foreman-ssl_access_ssl.log 
192.168.200.2 - - [13/Oct/2014:21:22:19 -0400] "GET /apidoc/v2.json HTTP/1.1" 404 185 "-" "OAuth gem v0.4.7"
192.168.200.2 - - [13/Oct/2014:21:22:19 -0400] "GET /apidoc/v2.json HTTP/1.1" 404 185 "-" "OAuth gem v0.4.7"
[root@staypuft ~]# cat /var/log/httpd/foreman-ssl_error_ssl.log 
[Mon Oct 13 21:22:19 2014] [error] [client 192.168.200.2] File does not exist: /usr/share/foreman/public/apidoc
[Mon Oct 13 21:22:19 2014] [error] [client 192.168.200.2] File does not exist: /usr/share/foreman/public/apidoc

Comment 5 Mike Burns 2014-10-14 13:38:18 UTC
This was a missing dependency and package.  Built and added 

ruby193-rubygem-ipaddress-0.8.0-6.el6ost

and added dependency to 

ruby193-rubygem-staypuft-0.4.5-1.el6ost

Comment 6 John Eckersberg 2014-10-14 13:56:34 UTC
I had ruby193-rubygem-staypuft-0.4.5-1.el6ost installed, and still had the same error.  I will reproduce to make sure I had the right version of the ipaddress gem as well, but I'm assuming the dependency pulled it as expected.

Comment 7 John Eckersberg 2014-10-14 14:08:42 UTC
Confirmed, still get the error with:

[root@staypuft ~]# rpm -q ruby193-rubygem-staypuft ruby193-rubygem-ipaddress
ruby193-rubygem-staypuft-0.4.5-1.el6ost.noarch
ruby193-rubygem-ipaddress-0.8.0-6.el6ost.noarch

Comment 8 Jaromir Coufal 2016-09-29 13:23:52 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