Bug 892249
| Summary: | Puppet modules return success even if critical packages cannot be installed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Perry Myers <pmyers> | ||||
| Component: | openstack-packstack | Assignee: | RHOS Maint <rhos-maint> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Nir Magnezi <nmagnezi> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 2.0 (Folsom) | CC: | aortega, derekh, ykaul | ||||
| Target Milestone: | ga | ||||||
| Target Release: | 2.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-01-10 21:07: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: |
|
||||||
Already Fixed Dup of https://bugzilla.redhat.com/show_bug.cgi?id=887956 *** This bug has been marked as a duplicate of bug 887956 *** |
Created attachment 673243 [details] mysql puppet log Description of problem: I ran a vanilla all-in-one Packstack install, unfortunately my VM was not configured with the proper yum repositories so that mysql could be installed as part of the mysql.pp step (which is at the very beginning of the install) The mysql.pp.log file shows the error, that yum is unable to install the dependent package, and there are errors throughout the log file, but Packstack still reports that the puppet module applied correctly: Applying /var/tmp/a2d51d0c-dd0e-41c6-9073-01bd1e58ef09/manifests/127.0.0.1_mysql.pp Testing if puppet apply is finished : 127.0.0.1_mysql.pp.log Testing if puppet apply is finished : 127.0.0.1_mysql.pp.log OK And overall the installation succeeds vs. fails. I didn't notice anything amiss until I tried to run some keystone commands after the install completed and found that the core issue was that keystone wasn't able to communicate to the database because it wasn't there Desired behavior would be that if there are failures in a puppet module being applied, that this is shown to the user in packstack and that for some failures (like the database or any other core prereqs) that the install should abort vs. proceed.