Rebuild package ruby-mysql with correct dependencies to the mysql version in current repository.

Actually, ruby-mysql package do not correspond with available MySQL version in each repository.

MOS Linux does not deal with ruby gems

Basically it could be enough just to trigger rebuild for this package versus actual mysql and actual mysql-develop.

What's a status of this bug? Is it still broken? Ruby in our mirrors was recompiled few times already.

Increased to High, as otherwise we would need to move it to 7.0

Yes it is still broken.

http://fuel-repository.mirantis.com/fwm/5.0.3/centos/os/x86_64/Packages/ruby-mysql-2.8.2-1.el6.x86_64.rpm
is linked to libmysqlclient.so.16

http://fuel-repository.mirantis.com/fwm/5.0.3/centos/os/x86_64/Packages/mysql-libs-5.1.73-3.el6_5.x86_64.rpm
provides libmysqlclient.so.16

http://fuel-repository.mirantis.com/fwm/5.0.3/centos/os/x86_64/Packages/MySQL-shared-5.5.28-7.x86_64.rpm
http://fuel-repository.mirantis.com/fwm/5.0.3/centos/os/x86_64/Packages/MySQL-shared-wsrep-5.5.28_wsrep_23.7-12.x86_64.rpm
both provide libmysqlclient.so.18

and MySQL-shared is the one that gets deployed:
https://github.com/stackforge/fuel-library/blob/stable/5.1/deployment/puppet/mysql/manifests/params.pp#L51-L56

Same ruby-mysql RPM is present in the 6.1 mirror for CentOS, so this problem didn't go anywhere since 5.0.

Ok, we need to rebuild this package against all necessary branches.
Is this list enough or do I miss something?
6.1
6.0.1
5.1.2
5.0.3

This fix will be not permanent until we have aggregated-obs-builds. So no 7.0 fixes until stable repo for this is mastered.

Related fix proposed to branch: 6.1
Change author: Artem Silenkov <email address hidden>
Review: https://review.fuel-infra.org/6443

Related fix proposed to branch: 6.0.1
Change author: Artem Silenkov <email address hidden>
Review: https://review.fuel-infra.org/6444

Related fix proposed to branch: 5.1.2
Change author: Artem Silenkov <email address hidden>
Review: https://review.fuel-infra.org/6445

Related fix proposed to branch: 5.0.3
Change author: Artem Silenkov <email address hidden>
Review: https://review.fuel-infra.org/6446

Ok, this fix couldn't pass the CI at all and requires a lot of manual intervention.

As the result we will have 4 different packages "ruby-mysql" in one repo. This will break yum completely.

- we must take care of revisions.
- some fixes to ISO make process is needed - exclude and nailed versions according to release version.

Fix is possible but hard to implement. Is it worth doing?

How does it affect our users? I would suggest to move this bug to the next milestone unless we find direct high-severe implication on our users for upcoming 6.1 release.

Artem, I completely don't understand comment #23. Why 4 different ruby-mysql packages? What kind of revisions are you referring to and what exactly we must take care of? Why are fixes to ISO make scripts necessary? And to take a step back, why is ruby-mysql even included in the ISO, what's using it? Looks very similar to bug #1403088 where seemingly trivial problem creates a snowball of problems.

Mike, I don't think severity is High. The only impact I'm aware of is that ruby-mysql package shipped in MOS is not usable with the MySQL version deployed by Fuel. Based by the fact that there's no immediate impact elsewhere in OpenStack I suspect this package isn't used and can be removed altogether, but given the timing we might as well do that after 6.1 is released.

I suggest won't fix.

1. I can't find why do we ever need this gem in ISO.
2. Customer could install this gem itself without any problems.

Our approach for automated packaging is not suitable for such situations and require manual intervention.
As for now my requests lead to situation when we have few different packages "ruby-mysql" with the same version in one pool. This breaks all stuff completely.

Similar situation:

Packages of the same version built by OBS in a different projects cannot coexist in the same pool on our mirror:

a276aebb25c2cc677669814f34068765 /srv/obs/repos/trusty-fuel-6.1-stable/ubuntu/all/python-memcache_1.53-1~u14.04+mos1_all.deb
94a0026ca07cfad160d54d7a798ef457 /srv/obs/repos/trusty-fuel-7.0-stable/ubuntu/all/python-memcache_1.53-1~u14.04+mos1_all.deb

Well - if it would work - simply remove this package at all.

We don't use this gem so won't fix either.

Customer should recompile it on it own.

Change abandoned by Artem Silenkov <email address hidden> on branch: 6.1
Review: https://review.fuel-infra.org/6443

Change abandoned by Artem Silenkov <email address hidden> on branch: 6.0.1
Review: https://review.fuel-infra.org/6444

Change abandoned by Artem Silenkov <email address hidden> on branch: 5.1.2
Review: https://review.fuel-infra.org/6445

Change abandoned by Artem Silenkov <email address hidden> on branch: 5.0.3
Review: https://review.fuel-infra.org/6446