-
Notifications
You must be signed in to change notification settings - Fork 362
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
Update RAID array name after scheduling its creation #6185
Conversation
This is unblocked as our newest container builds are failing on missing newest pykickstart version: |
/kickstart-test --testtype smoke |
The unit test failure is expected because our workflow will not build new container with a new pykickstart. |
/packit build |
Merging and doing directly a container rebuild. |
Actually let's put the change in the spec file, and let unit tests build a new container here. |
Blivet can change the name for multiple reasons (invalid chars, name conflict etc.) so we need to make sure we have both the old and new name saved in case it is used in other kickstart commands like volgroup for example.
ade2c7a
to
280a8cc
Compare
/kickstart-tests --waive run already smoke tests |
Ignore Web UI tests, and RPM tests, known issues. |
Blivet can change the name for multiple reasons (invalid chars,
name conflict etc.) so we need to make sure we have both the old
and new name saved in case it is used in other kickstart commands
like volgroup for example.
We already do the same for the volgroup command in
_execute_volgroup_data
. This is currently blocked by related pykickstart fix for RAID names, see pykickstart/pykickstart#534