Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nightly-builds: install latest centos-release-gluster package #50

Merged
merged 1 commit into from Dec 10, 2018

Conversation

nixpanic
Copy link
Member

@nixpanic nixpanic commented Dec 8, 2018

With the update to CentOS 7.1810 it seems that yum changed behaviour a
little. For some (unclear at the moment) reason yum decides to install
centos-release-gluster-legacy instead of centos-release-gluster5.

By installing centos-release-storage-common before requesting to
install centos-release-gluster, yum picks the right version.

This is a workaround as installing centos-release-gluster on a cleanly
installed system should get the latest maintained Gluster release.

With the update to CentOS 7.1810 it seems that yum changed behaviour a
little. For some (unclear at the moment) reason yum decides to install
centos-release-gluster-legacy instead of centos-release-gluster5.

By installing centos-release-storage-common *before* requesting to
install centos-release-gluster, yum picks the right version.

This is a workaround as installing centos-release-gluster on a cleanly
installed system should get the latest maintained Gluster release.
@nigelbabu
Copy link
Contributor

Does this work when it's done all in one step?

@nigelbabu
Copy link
Contributor

Anyway, for future, you don't have to wait on me for review, please merge away.

@nigelbabu nigelbabu merged commit ebb1c5e into gluster:master Dec 10, 2018
@nixpanic
Copy link
Member Author

More details are in https://lists.gluster.org/pipermail/ci-results/2018-December/000000.html

Installing the packages with a single yum command works, but the order of the packages is important...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants