| Summary: | RHEL 7.3 upgrades fails on upgrade because of mariadb-libs package conflict. | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Michael Bayer <mbayer> |
| Component: | mariadb-galera | Assignee: | Michael Bayer <mbayer> |
| Status: | CLOSED ERRATA | QA Contact: | Shai Revivo <srevivo> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0 (RHEL 7) | CC: | dciabrin, fdinitto, hhorak, jschluet, mbayer, mburns, mcornea, mrunge, nlevinki, rhel-osp-director-maint, rhos-flags, sathlang, sclewis, slong, srevivo |
| Target Milestone: | Upstream M3 | Keywords: | ZStream |
| Target Release: | 5.0 (RHEL 7) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | mariadb-galera-5.5.42-1.1.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: |
Previously, both the mariadb-server and mariadb-galera-server packages shipped the client-facing libraries, dialog.so and mysql_clear_password.so. As a result, the mariadb-galera-server package would fail to install because of package conflicts. With this update, these libraries have been moved from mariadb-galera-server to mariadb-libs, and the mariadb-galera-server package installs successfully.
|
Story Points: | --- |
| Clone Of: | 1373598 | Environment: | |
| Last Closed: | 2016-10-13 14:14:25 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: | |
| Bug Depends On: | 1373598 | ||
| Bug Blocks: | |||
|
Comment 5
Summer Long
2016-10-05 05:10:33 UTC
Ignore that needInfo, Michael. Just took it from the other clone. Automation passed https://rhos-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/RHOS/view/RHOS5/job/rhos-jenkins-rhos-5.0-puddle-rhel-7.2-multi-node-packstack-neutron-ml2-gre-rabbitmq-tempest-git-all/35/ the rpm is in the puddle 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://rhn.redhat.com/errata/RHSA-2016-2059.html |