Deployment of Zabbix Fails with Mysql client dependancy

Bug #1424855 reported by Dave Johnston
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Stanislaw Bogatkin
6.0.x
Invalid
High
Stanislaw Bogatkin

Bug Description

Deploying Zabbix with Fuel 6.0 on Ubunut fails.

Puppet logs complain that mysql-client-core-5.6 : Breaks: mysql-client-5.5 but 5.5.40-0ubuntu0.12.04.1 is to be installed

2015-02-23 20:27:53 ERR
 (/Stage[main]/Mysql/Package[mysql-client]/ensure) E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
2015-02-23 20:27:53 ERR
 (/Stage[main]/Mysql/Package[mysql-client]/ensure) Breaks: mysql-client-core-5.5 but 5.5.40-0ubuntu0.12.04.1 is to be installed
2015-02-23 20:27:53 ERR
 (/Stage[main]/Mysql/Package[mysql-client]/ensure) mysql-client-core-5.6 : Breaks: mysql-client-5.5 but 5.5.40-0ubuntu0.12.04.1 is to be installed
2015-02-23 20:27:53 ERR
 (/Stage[main]/Mysql/Package[mysql-client]/ensure) Breaks: virtual-mysql-client
2015-02-23 20:27:53 ERR
 (/Stage[main]/Mysql/Package[mysql-client]/ensure) mysql-client-5.6 : Breaks: mysql-client-5.5 but 5.5.40-0ubuntu0.12.04.1 is to be installed
2015-02-23 20:27:53 ERR
 (/Stage[main]/Mysql/Package[mysql-client]/ensure) The following packages have unmet dependencies:
2015-02-23 20:27:53 ERR
 (/Stage[main]/Mysql/Package[mysql-client]/ensure) You might want to run 'apt-get -f install' to correct these:
2015-02-23 20:27:53 ERR
 (/Stage[main]/Mysql/Package[mysql-client]/ensure) mysql-client-5.5 is already the newest version.
2015-02-23 20:27:53 ERR
 (/Stage[main]/Mysql/Package[mysql-client]/ensure) Reading state information...
2015-02-23 20:27:53 ERR
 (/Stage[main]/Mysql/Package[mysql-client]/ensure) Building dependency tree...
2015-02-23 20:27:53 ERR
 (/Stage[main]/Mysql/Package[mysql-client]/ensure) change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install mysql-client-5.5' returned 100: Reading package lists...

Andrew Woodward (xarses)
tags: added: customer-found
Changed in fuel:
importance: Undecided → Medium
milestone: none → 6.0.1
Changed in fuel:
assignee: nobody → Fuel OSCI Team (fuel-osci)
status: New → Confirmed
Roman Vyalov (r0mikiam)
Changed in fuel:
assignee: Fuel OSCI Team (fuel-osci) → MOS Linux (mos-linux)
Revision history for this message
Aleksander Mogylchenko (amogylchenko) wrote :

Roman, where did we get mysql-client-5.6?

It was introduced in Trusty, but our mirrors contain both versions (5.5 and 5.6):
http://mirror.fuel-infra.org/fwm/6.0/ubuntu/pool/main/

There is no precise git repo for mysql, so it looks like you've mixed precise and trusty mirrors?

Changed in fuel:
assignee: MOS Linux (mos-linux) → Fuel OSCI Team (fuel-osci)
Roman Vyalov (r0mikiam)
Changed in fuel:
assignee: Fuel OSCI Team (fuel-osci) → Stanislaw Bogatkin (sbogatkin)
Changed in fuel:
importance: Medium → High
Revision history for this message
Dave Johnston (dave-johnston) wrote :

Is this something that could be fixed/patched in delpoyment by updating the ubuntu repo (removing unnecessary versions of the software ?)

Revision history for this message
Stanislaw Bogatkin (sbogatkin) wrote :

As I know - no. We have 2 versions of mysql in repos (and as I know they both needed for some reasons). In 6.1 that problem was solved in process of granular deployment, so it cannot just be cherry-picked to 6.0 branch. I'll create new patch as fast as I can.

Changed in fuel:
status: Confirmed → Triaged
Changed in fuel:
milestone: 6.0.1 → 6.1
status: Triaged → New
Changed in fuel:
status: New → Invalid
Revision history for this message
Stanislaw Bogatkin (sbogatkin) wrote :

I cannot actually reproduce this bug in 6.0.
Dave, can you give us some more information to reproduce this bug?

Revision history for this message
Dave Johnston (dave-johnston) wrote :

Hi Stanislaw,

Sure - what do you need. I still have the system in place.

This started of as a Fuel 5.1, then was upgraded to Fuel 5.1.1, and finally upgrade to Fuel 6.0
The delpoyment is the only one there, and it is a fresh 6.0 deployment.

Revision history for this message
Stanislaw Bogatkin (sbogatkin) wrote :

Can you attach a diagnostic snapshot from this env, please?

Revision history for this message
Dave Johnston (dave-johnston) wrote :

I've uploaded the diagnostic snapshot to my dropbox:
You can retrieve it from here: https://www.dropbox.com/s/ju60p4r9vchlxcg/fuel-snapshot-2015-01-17_23-16-10.tgz?dl=0

Revision history for this message
Dave Johnston (dave-johnston) wrote :

I noticed that on my controller, the sources.list contains

deb http://10.20.122.10:8080/2014.1.3-5.1.1/ubuntu/x86_64 precise main
deb http://10.20.122.10:8080/2014.2-6.0/ubuntu/x86_64 precise main

Could there be an issue that both the 5.1.1 and 6.0 repositories are listed ?

Revision history for this message
Alexander Rubtsov (arubtsov) wrote :

Stanislaw,

Dave clarified in a support request that the error is observed in new 6.0 deployment (that is deployed from scratch) as well
So, it seems upgrade from 5.1 isn't the reason

Revision history for this message
Stanislaw Bogatkin (sbogatkin) wrote :

Alexander, we need more tries to reproduce. I just cannot reproduce it.

Revision history for this message
Michael Petersen (mpetason) wrote :

What else is needed for us to try to reproduce?

Revision history for this message
Dave Johnston (dave-johnston) wrote :

Guys,
I realise this is a tricky one, but I can consistently reproduce it, using two separate servers.

What I have observed is that the issue only seems to occur on Sun hardware. I have two Sun x86 machines - both 64 bit CPUs.

The Sun X2200 and SunFire X4150 both fail with the seem error.
If I add a HP DL360 G7 to the deployment, and provision Zabbix on that it passes.

I can repeatedly add/remove the nodes, and everytime it fails on the Sun boxes and passes on the HP.

This is odd because the error seems to indicate an issue with packages, so I don't see it being an issue. The only think I can guess is that there is another error somewhere in the logs, that points to the real issue.

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.