Changes to Lustre installation (v5) #42
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tpdownes
force-pushed
the
fix_v5_lustre
branch
3 times, most recently
from
4e068f9
to
7c3f72e
Compare
The existing solution breaks whenever new point releases of Rocky linux are made. The new solution makes the assumption that, after upgrading the kernel and package for /etc/os-release, that we are running the latest version of Rocky Linux AND that the latest-release of DDN's packaged lustre supports the latest version of Rocky linux.
tpdownes
force-pushed
the
fix_v5_lustre
branch
from
7c3f72e
to
56bdf68
Compare
nick-stroud
reviewed
Feb 14, 2024
nick-stroud
approved these changes
Feb 14, 2024
mr0re1
approved these changes
Feb 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The existing solution for installing lustre breaks whenever new point releases of Rocky linux are made because it upgrades the kernel packages without also upgrading rocky-release (which is what tells the OS whether it is 8.8 or 8.9 via the /etc/os-release file).
The new solution makes the assumption that, after upgrading the kernel and rocky-release packages that:
This solution is "less unsafe" because, if DDN has not yet packaged a version of lustre for the latest Rocky, then Ansible will fail. The current solution will successfully install lustre, but for the older kernel it is no longer booting. So the failure mode will not be detected during image build.