Bug 1134587
| Summary: | Rubygem-Staypuft: After running liveinst (LiveCD) and booting from the HardDrive - running "rhel-osp-installer" results in error: "Something went wrong! Check the log for ERROR-level output" | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Alexander Chuzhoy <sasha> |
| Component: | rhel-osp-installer LiveCD | Assignee: | Jiri Stransky <jstransk> |
| Status: | CLOSED ERRATA | QA Contact: | Alexander Chuzhoy <sasha> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0 (RHEL 7) | CC: | aberezin, ajeain, dnavale, jstransk, lzap, mburns, morazi, rhos-maint, sasha, sclewis, sgordon, yeylon |
| Target Milestone: | z1 | Keywords: | Triaged |
| Target Release: | Installer | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | rhelosp-installer-live-20140912.1.iso | Doc Type: | Bug Fix |
| Doc Text: |
Red Hat Enterprise Linux OpenStack Platform Installer, the SELinux module was not enabled. As a result, after installing the operating system from the RHEL-OSP Installer Live CD to disk, running the rhel-osp-installer resulted in a "Something went wrong! Check the log for ERROR-level output" message.
With this update, RHEL-OSP Installer SELinux module is enabled on both the Live CD and the system installed to disk. As a result, the error message due to the missing SELinux module no longer appears.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-02 12:56:31 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: | |||
Created attachment 931680 [details]
/var/log/foreman/production.log from the staypuft machine
Marek, any chance you've seen this? I haven't seen this before but it seems that it can't find foreman. How does the livecd installation work? Does it use new answer file? There may be some bad URLs in it if it was used for installation on livecd.example.com. Sasha does this happen every time or is it intermittent? Created attachment 934528 [details]
/var/log/rhel-osp-installer/rhel-osp-installer.log from the staypuft machine created after running liveinst from LiveCD.
Happens every time. Just reproduced. This looks like an SELinux policy issue which was already fixed in upstream foreman-selinux, we'll need to port the changes downstream. Details follow. In /var/log/httpd/error_log: [Tue Sep 09 09:45:02 2014] [error] *** Passenger could not be initialized because of this error: Unable to start the Phusion Passenger watchdog (/usr/lib64/ruby/site_ruby/1.8/x86_64-linux/agents/PassengerWatchd\ og): Permission denied (errno=13) After "setenforce 0" and "service httpd restart", passenger initialized fine. [root@livecd ~]# yum list installed | grep selinux This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. foreman-selinux.noarch 1.6.0.3-2.el6sat @koji-override-0/$releasever libselinux.x86_64 2.0.94-5.3.el6_4.1 @koji-override-1/$releasever libselinux-python.x86_64 2.0.94-5.3.el6_4.1 @koji-override-1/$releasever libselinux-ruby.x86_64 2.0.94-5.3.el6_4.1 @koji-override-1/$releasever libselinux-utils.x86_64 2.0.94-5.3.el6_4.1 @koji-override-1/$releasever selinux-policy.noarch 3.7.19-231.el6_5.3 @koji-override-0/$releasever selinux-policy-targeted.noarch 3.7.19-231.el6_5.3 @koji-override-0/$releasever I enabled selinux again, tried with foreman-selinux-1.6.0.14-1 from poodle 2014-09-08.2 but the issue persisted. Tried with foreman-selinux-1.7.0-0.develop.201408202047gitd5e80cf from upstream nightly and the issue was gone, passenger worked fine and i went through the whole rhel-osp-installer process. There still was a denial in audit.log but it didn't seem to affect the functionality. I'll attach audit.log output of restarting httpd for all three attempts (re-ran in permissive mode to log all denials). Created attachment 935602 [details]
foreman-selinux-1.6.0.3-2-audit.log
Created attachment 935614 [details]
foreman-selinux-1.6.0.14-1-audit.log
Created attachment 935615 [details]
foreman-selinux-1.7.0-0.develop.201408202047gitd5e80cf-audit.log
Lukas Can you look at this? Is this something we can easily get into downstream foreman-selinux? Actually, after looking at foreman-selinux a bit closer, i was able to work around the issue without updating RPMs, just by running "foreman-selinux-enable", then "foreman-selinux-relabel" and "service httpd restart". So probably no updating of foreman-selinux will be necessary. Verified: rhelosp-installer-live-6.5-20140912.1.iso The reported issue doesn't reproduce. 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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1350.html |
Created attachment 931679 [details] /var/log/rhel-osp-installer/rhel-osp-installer.log from the staypuft machine. Rubygem-Staypuft: After running liveinst (LiveCD) and booting from the HardDrive - running "rhel-osp-installer" results in error: "Something went wrong! Check the log for ERROR-level output" Environment:rhelosp-installer-live-6.5-20140820.1.iso rhel-osp-installer-0.1.10-2.el6ost.noarch Steps to reproduce: 1. Boot the system from the LiveCD. 2. Run liveinst to install the LiveCD on the hard drive. 3. Boot the system from the hard drive. 4. After some preparations (Configured public/private IP, ensured hostname resolution is configured) run rhel-osp-installer. Result: ... Please set a default root password for newly provisioned machines. If you choose not to set a password, it will be generated randomly. The password must be a minimum of 8 characters. You can also set a public ssh key which will be deployed to newly provisioned machines. How would you like to proceed?: 1. Proceed with the above values 2. Change SSH public key 3. Change Root password 4. Toggle Root password visibility 1 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[livecd.example.com]: Could not evaluate: 404 Resource Not Found: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> 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 result: The run of rhel-osp-installer should complete with no errors.