Skip to content

Conversation

himani2411
Copy link
Contributor

PR -> #2388

References

  • Link to impacted open issues.
  • Link to related PRs in other packages (i.e. cookbook, node).
  • Link to documentation useful to understand the changes.

Checklist

  • Make sure you are pointing to the right branch.
  • If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
  • Check all commits' messages are clear, describing what and why vs how.
  • Make sure to have added unit tests or integration tests to cover the new/modified code.
  • Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

dreambeyondorange and others added 13 commits July 25, 2023 10:15
This failure causes cluster creation failure. It happened about once every 200 times.

Signed-off-by: Hanwen <hanwenli@amazon.com>
Co-authored-by: Hanwen <hanwenli@amazon.com>
The gcc compiler used to build the kernel on Ubuntu 22.04 images we use is 11.3, but the gcc apt package seems to install 11.4 for use
in the terminal.  This flag will prevent the NVIDIA driver from failing to install due to the minor version difference in gcc.
…via override_server_template (aws#2391)

The override_server_template function runs during bootstrapping to set the parameter needed for the OS specific config file.
The setup action works locally since that action runs during local tests, but does not work during bootstrapping when the
node attributes from the setup action are not present
… to the config (aws#2393)

Until now ulimit -Sn was used in the config step to confirm the changes in the install
step are reflected in the running OS.  This is no longer working in Ubuntu 22 because
for whatever reason, the session that is created for Ubuntu 22 doesn't have the
changes reflected, even though the files are in place.  After launching an instance
from the AMI however, the changes are there.  To improve this test, we need to move
it to the install step and check it immediately by switching users and forcing the
loading of the limits.
The hash of the installer can be retrieved here https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/efa-verify.html

Signed-off-by: Hanwen <hanwenli@amazon.com>
Signed-off-by: Jacopo De Amicis <jdamicis@amazon.it>
… and the blocks to start Chronyd and Munge services.

Signed-off-by: Giacomo Marciani <mgiacomo@amazon.com>
@himani2411 himani2411 requested review from a team as code owners August 9, 2023 20:52
@himani2411 himani2411 closed this Aug 9, 2023
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.

5 participants