Bug 1425207
| Summary: | deployments sometimes fail and sometimes succeeds. | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Jeremy <jmelvin> |
| Component: | puppet-tripleo | Assignee: | Michele Baldessari <michele> |
| Status: | CLOSED ERRATA | QA Contact: | nlevinki <nlevinki> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 10.0 (Newton) | CC: | aschultz, chhudson, chjones, dbecker, dhill, djuran, jjoyce, jschluet, mburns, mcornea, michele, morazi, pkomarov, rhel-osp-director-maint, slinaber, sreichar, tvignaud |
| Target Milestone: | z7 | Keywords: | Triaged, ZStream |
| Target Release: | 10.0 (Newton) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | puppet-tripleo-5.6.4-3.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Prior to this update, a missing puppet relationship could have caused puppet to create a mysql user before the database was fully up. Consequently, deployment would fail with the following error: `Error: Could not prefetch mysql_user provider 'mysql'`. This update adds a proper puppet relationship so that users are only created when the database is fully up.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-02-27 16:50:40 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
Jeremy
2017-02-20 20:29:39 UTC
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release. *** Bug 1446797 has been marked as a duplicate of this bug. *** Since bug 1446797 was closed as a duplicate of this one, do note that the issue does not require HyperConverged, or even Ceph to occur. Also see this, captured sosreport at: http://refarch.cloud.lab.eng.bos.redhat.com/pub/tmp/bz1446797/ Unsure if this matters, but this config is vlan based versus vxlan. FYI, using the same equipment and equivalent config files have not seen with with OSP11 on 7.4. Verified ,
#puppet-tripleo version check :
$ ansible overcloud -m shell -b -a 'rpm -qa|grep puppet-tripleo'
overcloud-compute-0 | SUCCESS | rc=0 >>
puppet-tripleo-5.6.4-3.el7ost.noarch
overcloud-compute-1 | SUCCESS | rc=0 >>
puppet-tripleo-5.6.4-3.el7ost.noarch
overcloud-controller-0 | SUCCESS | rc=0 >>
puppet-tripleo-5.6.4-3.el7ost.noarch
overcloud-controller-1 | SUCCESS | rc=0 >>
puppet-tripleo-5.6.4-3.el7ost.noarch
overcloud-controller-2 | SUCCESS | rc=0 >>
puppet-tripleo-5.6.4-3.el7ost.noarch
#code check :
$ ansible overcloud -m shell -b -a 'grep Mysql_user /usr/share/openstack-puppet/modules/tripleo/manifests/profile/pacemaker/database/mysql.pp'
overcloud-compute-1 | SUCCESS | rc=0 >>
Exec['galera-ready'] -> Mysql_user<||>
overcloud-controller-1 | SUCCESS | rc=0 >>
Exec['galera-ready'] -> Mysql_user<||>
overcloud-controller-0 | SUCCESS | rc=0 >>
Exec['galera-ready'] -> Mysql_user<||>
overcloud-compute-0 | SUCCESS | rc=0 >>
Exec['galera-ready'] -> Mysql_user<||>
overcloud-controller-2 | SUCCESS | rc=0 >>
Exec['galera-ready'] -> Mysql_user<||>
#Re-deployed 3 times with the alternating features :
- 1 X default roles for 3 controller and 2 computes
- 2 X default roles for 3 controllers with hyperconverged-ceph role for the computes.
results :
- success rate of 100% on all three deployments :
#from overcloud_install.log :
2018-02-22 13:19:10 |
2018-02-22 13:19:10 | Stack overcloud CREATE_COMPLETE
2018-02-22 13:19:10 |
2018-02-22 13:19:10 | Overcloud Endpoint: http://10.0.0.12:5000/v2.0
2018-02-22 13:19:10 | Overcloud Deployed
2018-02-22 13:19:10 | + status_code=0
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. https://access.redhat.com/errata/RHBA-2018:0364 |