fresh install centos 7 problems

Bug #1642642 reported by Joep
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
New
Undecided
Unassigned

Bug Description

Half an hour ago I did an fresh install of Centos 7, after completing the installation, first thing I did is installing Percona Server.

The installation went with success, I haven't installed any other packages since, and the CentOs installation was minimal.

Now I ran yum update and I directly get loads of conflicts, bit strange for an fresh installation?

[root@web-01 ~]# yum update
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
 * base: ****
 * extras: centos.mirror.triple-it.nl
 * updates: nl.mirror.babylon.network
Resolving Dependencies
--> Running transaction check
---> Package Percona-Server-shared-55.x86_64 0:5.5.52-rel38.3.el7 will be obsoleting
---> Package Percona-Server-shared-56.x86_64 0:5.6.33-rel79.0.el7 will be obsoleting
---> Package Percona-XtraDB-Cluster-shared-55.x86_64 1:5.5.41-25.12.855.el7 will be obsoleting
---> Package Percona-XtraDB-Cluster-shared-56.x86_64 1:5.6.32-25.17.1.el7 will be obsoleting
---> Package Percona-XtraDB-Cluster-shared-57.x86_64 0:5.7.14-26.17.1.el7 will be obsoleting
---> Package Percona-XtraDB-Cluster-shared-compat-57.x86_64 0:5.7.14-26.17.1.el7 will be obsoleting
---> Package mariadb-libs.x86_64 1:5.5.50-1.el7_2 will be obsoleted
---> Package percona-release.noarch 0:0.1-3 will be updated
---> Package percona-release.noarch 0:0.1-4 will be an update
--> Processing Conflict: Percona-Server-shared-compat-57-5.7.15-9.1.el7.x86_64 conflicts Percona-Server-shared-55
--> Processing Conflict: Percona-Server-shared-compat-57-5.7.15-9.1.el7.x86_64 conflicts Percona-Server-shared-56
--> Processing Conflict: Percona-XtraDB-Cluster-shared-compat-57-5.7.14-26.17.1.el7.x86_64 conflicts Percona-XtraDB-Cluster-shared-55
--> Processing Conflict: Percona-XtraDB-Cluster-shared-compat-57-5.7.14-26.17.1.el7.x86_64 conflicts Percona-XtraDB-Cluster-shared-56
--> Processing Conflict: 1:Percona-XtraDB-Cluster-shared-55-5.5.41-25.12.855.el7.x86_64 conflicts Percona-Server-shared-55
--> Processing Conflict: 1:Percona-XtraDB-Cluster-shared-55-5.5.41-25.12.855.el7.x86_64 conflicts Percona-XtraDB-Cluster-shared-56
--> Processing Conflict: 1:Percona-XtraDB-Cluster-shared-56-5.6.32-25.17.1.el7.x86_64 conflicts Percona-Server-shared-56
--> Processing Conflict: Percona-Server-shared-56-5.6.33-rel79.0.el7.x86_64 conflicts Percona-Server-shared-55
--> Processing Conflict: Percona-XtraDB-Cluster-shared-57-5.7.14-26.17.1.el7.x86_64 conflicts Percona-Server-shared-56
--> Processing Conflict: Percona-Server-shared-55-5.5.52-rel38.3.el7.x86_64 conflicts Percona-Server-shared-56
--> Finished Dependency Resolution
Error: Percona-XtraDB-Cluster-shared-55 conflicts with 1:Percona-XtraDB-Cluster-shared-56-5.6.32-25.17.1.el7.x86_64
Error: Percona-Server-shared-55 conflicts with Percona-Server-shared-56-5.6.33-rel79.0.el7.x86_64
Error: Percona-XtraDB-Cluster-shared-57 conflicts with Percona-Server-shared-56-5.6.33-rel79.0.el7.x86_64
Error: Percona-XtraDB-Cluster-shared-compat-57 conflicts with 1:Percona-XtraDB-Cluster-shared-56-5.6.32-25.17.1.el7.x86_64
Error: Percona-Server-shared-compat-57 conflicts with Percona-Server-shared-55-5.5.52-rel38.3.el7.x86_64
Error: Percona-XtraDB-Cluster-shared-56 conflicts with Percona-Server-shared-56-5.6.33-rel79.0.el7.x86_64
Error: Percona-Server-shared-compat-57 conflicts with Percona-Server-shared-56-5.6.33-rel79.0.el7.x86_64
Error: Percona-XtraDB-Cluster-shared-55 conflicts with Percona-Server-shared-55-5.5.52-rel38.3.el7.x86_64
Error: Percona-XtraDB-Cluster-shared-compat-57 conflicts with 1:Percona-XtraDB-Cluster-shared-55-5.5.41-25.12.855.el7.x86_64
Error: Percona-Server-shared-56 conflicts with Percona-Server-shared-55-5.5.52-rel38.3.el7.x86_64
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Tags: pkg
Revision history for this message
Joep (johnmm) wrote :

Log of installation

Revision history for this message
Justin (jricci) wrote :

I am sitting here doing the exact same thing. yum update on a fresh percona 5.7 install and am getting the exact same conflicts as you. Hoping to a resolution here.... I'm not sure how to proceed, keep us updated! I'll let you know as well if I figure it out.

Revision history for this message
Justin (jricci) wrote :

I tried this:
yum --exclude=*cluster*,*shared-55*,*shared-56* update
and got it to successfully skip the bad dependencies, since i'm using percona 5.7

It attempts to update percona-release 'noarch' but gives me this error:
percona-release-0.1-4.noarch.r FAILED
http://repo.percona.com/release/7/RPMS/noarch/percona-release-0.1-4.noarch.rpm: [Errno -1] Package does not match intended download.

tags: added: pkg
Revision history for this message
Justin (jricci) wrote :

I believe I got around the issue by doing this:

yum remove mariadb-libs
yum remove percona-release
yum install http://www.percona.com/downloads/percona-release/redhat/0.1-4/percona-release-0.1-4.noarch.rpm

yum update

<< all clear! >>

I'm not sure what originally installed mariadb-libs but nothing depended on it.

Revision history for this message
CJ (rcj1) wrote :

For us, percona-toolkit requires perl-DBD-MySQL, which subsequently requires mariadb-libs.

Seems like we either would need to find another source for DBD or find a way to bypass the mariadb-libs requirement.

# yum install percona-toolkit
Loaded plugins: priorities, ulninfo
526 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package percona-toolkit.x86_64 0:3.0.2-1.el6 will be installed
--> Processing Dependency: perl(DBD::mysql) >= 1.0 for package: percona-toolkit-3.0.2-1.el6.x86_64
--> Running transaction check
---> Package perl-DBD-MySQL.x86_64 0:4.023-5.0.1.el7 will be installed
--> Processing Dependency: libmysqlclient.so.18(libmysqlclient_18)(64bit) for package: perl-DBD-MySQL-4.023-5.0.1.el7.x86_64
--> Processing Dependency: libmysqlclient.so.18()(64bit) for package: perl-DBD-MySQL-4.023-5.0.1.el7.x86_64
--> Running transaction check
---> Package mariadb-libs.x86_64 1:5.5.52-1.el7 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

========================================================================================================================================================================
 Package Arch Version Repository Size
========================================================================================================================================================================
Installing:
 percona-toolkit x86_64 3.0.2-1.el6 percona-release 4.9 M
Installing for dependencies:
 mariadb-libs x86_64 1:5.5.52-1.el7 ol7_latest 761 k
 perl-DBD-MySQL x86_64 4.023-5.0.1.el7 ol7_latest 140 k

Transaction Summary
========================================================================================================================================================================
Install 1 Package (+2 Dependent packages)

Total size: 5.7 M
Installed size: 23 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test

Transaction check error:
  file /usr/lib64/mysql/plugin/dialog.so from install of mariadb-libs-1:5.5.52-1.el7.x86_64 conflicts with file from package Percona-Server-server-57-5.7.17-13.1.el6.x86_64

Error Summary
-------------

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

CJ, could you please file a new bug with Percona Toolkit?

Revision history for this message
Jervin R (revin) wrote :

This is also true on 5.7, if you remove mariadb-libs, some packages like Perl-DBI requires libmysqlclient. To workaround, I installed both Percona-*-shared-56|57 and Percona-*shared-compat-56|57 after removing mariadb-libs.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3602

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.