-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[BUG] salt v3007.1 onedir rpm package dependencies break the system #66604
Comments
Looks like similar issue happens when running bootstrap script on Ubuntu 24 fails as well with:
Also as Im new to Salt, I have to add that I ran |
It is not the same, the bootstrap script doesn't support Ubuntu 24 yet. There is an open pull request to implement that: saltstack/salt-bootstrap#2001 |
Ah ok, thank you, just starting out using Salt and this bootstrap script ⚡ |
This problem also effects v3006.8 ... No idea how something as fundamental as this got past QA ??? |
We are seeing this as well in 3006.8 when we were staging it for an upgrade. |
The update in #66403 changes the regexs from i.e. is it matching filenames of the type Or if matching files in a |
Description
The salt 3007.1 onedir rpm package comes with a big list of provides:
However these dependencies are hidden in the onedir structure and therefore not really available for the OS after installation of the salt package.
In fact, whenever an OS package is installed that requires one of the dependencies that salt claims to fulfill in this list of "provides", the salt package is installed instead of the OS package. This leads to a broken system. Especially when salt is installed together with the other OS packages during the kickstart phase of a new OS installation, it then even breaks the rpm command itself.
Setup
Tested both on both older and newer OS versions: CentOS 7, Almalinux 9
Steps to Reproduce the behavior
Expected behavior
The onedir rpm package should not claim to "provide" all kinds of libraries that are not available for the OS.
Versions Report
salt v3007.1
Additional context
Maybe this change is related: 975c2a4
The text was updated successfully, but these errors were encountered: