-
Notifications
You must be signed in to change notification settings - Fork 45
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
Bootstrap may fail if epel repo enabled with some priority #2704
Labels
complexity:medium
Something that requires one or few days to fix
kind:bug
Something isn't working
priority:medium
Medium priority issues, should only be postponed if no other option
severity:medium
Medium impact (usability) on live deployments
topic:deployment
Bugs in or enhancements to deployment stages
Comments
TeddyAndrieux
added
kind:bug
Something isn't working
topic:deployment
Bugs in or enhancements to deployment stages
complexity:medium
Something that requires one or few days to fix
priority:medium
Medium priority issues, should only be postponed if no other option
severity:medium
Medium impact (usability) on live deployments
labels
Aug 3, 2020
TeddyAndrieux
changed the title
Bootstrap may fail if epel repo enabled
Bootstrap may fail if epel repo enabled with some priority
Aug 11, 2020
TeddyAndrieux
added a commit
that referenced
this issue
Aug 11, 2020
In bootstrap and restore we install salt-minion on the node so we need to pin the salt version we want to install and not just install the one yum will find depending on various things (like available versions, priority on repos, ...) Fixes: #2704
TeddyAndrieux
added a commit
that referenced
this issue
Aug 11, 2020
In bootstrap and restore we install salt-minion on the node so we need to pin the salt version we want to install and not just install the one yum will find depending on various things (like available versions, priority on repos, ...). Also set the priority to 1 on all our repos so that our repositories has priority over others if the `yum-plugin-priorities` package is installed. NOTE: If `yum-plugin-priorities` is installed and priority is set on one repos then other repos with the same package will just be ignored (e.g.: epel installed with priority=98 we cannot install `salt-3000.3` as salt-3000.3 is excluded because a repo with some priority has the package in a different version) Fixes: #2704
TeddyAndrieux
added a commit
that referenced
this issue
Aug 11, 2020
In bootstrap and restore we install salt-minion on the node so we need to pin the salt version we want to install and not just install the one yum will find depending on various things (like available versions, priority on repos, ...). Also set the priority to 1 on all our repos so that our repositories has priority over others if the `yum-plugin-priorities` package is installed. NOTE: If `yum-plugin-priorities` is installed and priority is set on one repos then other repos with the same package will just be ignored (e.g.: epel installed with priority=98 we cannot install `salt-3000.3` as salt-3000.3 is excluded because a repo with some priority has the package in a different version) Fixes: #2704
TeddyAndrieux
added a commit
that referenced
this issue
Aug 11, 2020
In bootstrap and restore we install salt-minion on the node so we need to pin the salt version we want to install and not just install the one yum will find depending on various things (like available versions, priority on repos, ...). Also set the priority to 1 on all our repos so that our repositories has priority over others if the `yum-plugin-priorities` package is installed. NOTE: If `yum-plugin-priorities` is installed and priority is set on one repos then other repos with the same package will just be ignored (e.g.: epel installed with priority=98 we cannot install `salt-3000.3` as salt-3000.3 is excluded because a repo with some priority has the package in a different version) Fixes: #2704
bert-e
added a commit
that referenced
this issue
Aug 11, 2020
…o tmp/octopus/w/2.6/bugfix/GH-2704-pin-salt-version-in-bootstrap
bert-e
added a commit
that referenced
this issue
Aug 12, 2020
…octopus/w/2.5/bugfix/GH-2704-pin-salt-version-in-bootstrap
bert-e
added a commit
that referenced
this issue
Aug 12, 2020
…nd 'q/2734/2.5/bugfix/GH-2704-pin-salt-version-in-bootstrap' into tmp/octopus/q/2.6
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
complexity:medium
Something that requires one or few days to fix
kind:bug
Something isn't working
priority:medium
Medium priority issues, should only be postponed if no other option
severity:medium
Medium impact (usability) on live deployments
topic:deployment
Bugs in or enhancements to deployment stages
Component:
'salt'
What happened:
When running bootstrap with epel repo enable and has some yum priority https://wiki.centos.org/PackageManagement/Yum/Priorities set on it, salt from epel repository is installed (2015.x).
So bootstrap fail because some expected function not here (like
fopen
)Workaround:
Disable epel repository (as this repository is not needed at all for MetalK8s) to perform bootstrap or just unset the priority on epel repository.
What was expected:
Working bootstrap and Salt minion from our repo installed either:
Steps to reproduce
Install the yum priority plugin, enable epel repository and set priority on epel repository to something between 1 and 98 and then bootstrap
Resolution proposal (optional):
Force the salt-minion version we install in bootstrap script
The text was updated successfully, but these errors were encountered: