Bug 1003961
| Summary: | installer (katello-configure) fails to report some errors | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Mike McCune <mmccune> |
| Component: | Installation | Assignee: | Ivan Necas <inecas> |
| Status: | CLOSED WONTFIX | QA Contact: | Og Maciel <omaciel> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.2 | CC: | ehelms, jmontleo, omaciel, sthirugn |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://github.com/Katello/katello-installer/pull/60 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-04-11 16:51:46 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: | |||
|
Description
Mike McCune
2013-09-03 14:59:04 UTC
An example would be this bug: https://bugzilla.redhat.com/show_bug.cgi?id=995986 if you search through the katello-debug you will note that in db_migrate.log file there is: rake aborted! cannot load such file -- ./engines/bastion/lib/bastion /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' yet katello-configure failed without any error indication. some options we talked about on the phone: * Check the service status at the end of the run * Check the puppet exit code * Possibly grep the log file for errors but this may show things that are non-fatal *** Bug 1012068 has been marked as a duplicate of this bug. *** Proposed fix in https://github.com/Katello/katello-installer/pull/60. There was change in log output format for newer puppet, that we needed to accomodate. Also there is a check at the end to make sure all the required services are running. The exit code from puppet was not usable because it was 0 even when something failed. We could go for puppet --detailedexitcode, but since the katello-configure is going to get replaced with node-installer, it doesn't make much sense to do so, as the current checks should be sufficient for the time being. Merged Could not reproduce it anymore. Please re-open it if needed. I was testing SAM 1.4 compose. I tried katello-configure in free_ipa mode. the katello-configure exited with no errors. But: # katello-service status tomcat6 (pid 142911) is running...[ OK ] httpd (pid 143373) is running... thumbslug (pid 143164) is running... elasticsearch (pid 142723) is running... katello is not running. delayed_job is not running. delayed_job_monitor is not running. katello-configure should report failure if it failed to start any of the required katello-services isnt it? Reopening the bug based on my comment above For SAM 2.0 and Sat6 GA we have an entirely re-written installer that does a better job of notification upon installation failure. I'd be hesitant to go back and enhance any of the error reporting on the old katello-configure routines. Should consider CLOSED:WONTFIX Agreed to Mike McCune's comment above. |