Bug 1241687
| Summary: | Errors during upgrade do not get properly reported | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Mike McCune <mmccune> | ||||
| Component: | Upgrades | Assignee: | Stephen Benjamin <stbenjam> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jitendra Yejare <jyejare> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.1.0 | CC: | bkearney, jyejare, mmccune, sghai, sthirugn | ||||
| Target Milestone: | Unspecified | ||||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://projects.theforeman.org/issues/11086 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-08-12 16:05:33 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
Mike McCune
2015-07-09 19:42:46 UTC
The only errors occur in the post hook, and we're not checking the status of those, so we need to add the same checks we have in the pre section. The actual upgrade itself (the puppet run) was successful, however it appears some of the underlying services are in a bad state which is why the post tasks failed. Can we see the foreman-debug to maybe understand the underlying cause? Or do we care? If I understand correctly you were doing a lot of testing with the box? Created attachment 1050437 [details]
foreman-debug
I think we should care if steps in the upgrade fail and report back even if the Satellite is in a bad state before the upgrade is ran. Created redmine issue http://projects.theforeman.org/issues/11086 from this bug > I think we should care if steps in the upgrade fail and report back even if the Satellite is in a bad state before the upgrade is ran. Right, I understand, the PR is open upstream to fix the hooks: https://github.com/Katello/katello-installer/pull/239 My question was if you want me to look into the *reason* your Katello upgrade failed, or if you already know or don't care. I'm not that concerned why the upgrade failed, myself and others had been doing some qpid load testing, stopping services and leaving things in a generally bad state so in this case I'm not concerned *why* it failed, just want to note that it did. Moving to POST since upstream bug http://projects.theforeman.org/issues/11086 has been closed ------------- Anonymous Applied in changeset commit:katello-installer|28f2c8b80a3b00f8b8f078bdaf56e5c688669fd0. Verified VERIFIED. This bug with latest GA Snap 14. There are no evidence of such errors observed. But there are errors of HTTPD service failed to restart is present, for which the bug is logged at BZ1245998. Which is out of scope of this bug. So moving it to verified. This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015. |