Skip to content
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

[develop][fix] Add mock munge key logic in compute setup recipe during kitchen tests #2487

Merged
merged 2 commits into from
Oct 12, 2023

Conversation

hehe7318
Copy link
Contributor

@hehe7318 hehe7318 commented Oct 9, 2023

Description of changes

  • Fix Kitchen tests on compute nodes caused by not existed Munge Key

References

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.

Copy link
Contributor

@jdeamicis jdeamicis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have to pass a binary blob to the munge key, otherwise the munge service will fail.

@@ -6,6 +6,7 @@
end

file "#{munge_dir}/.munge.key" do
mode '0600'
content 'munge-key'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

munge-key is not a good content for a munge key :D

The content must be binary, and at least 32 bytes long. Please find a way to pass a binary blob to this file.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done! I use the same logic as the rotation script does(which means the config and update process do).

@codecov
Copy link

codecov bot commented Oct 10, 2023

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (02fa532) 76.06% compared to head (cc0bcf8) 76.06%.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #2487   +/-   ##
========================================
  Coverage    76.06%   76.06%           
========================================
  Files           13       13           
  Lines         1876     1876           
========================================
  Hits          1427     1427           
  Misses         449      449           
Flag Coverage Δ
unittests 76.06% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@hehe7318 hehe7318 force-pushed the wip/munge-key-fix-compute branch from 938df41 to aa836ef Compare October 10, 2023 04:29
@hehe7318 hehe7318 force-pushed the wip/munge-key-fix-compute branch 2 times, most recently from 33c312a to 474f86d Compare October 12, 2023 13:28
@hehe7318 hehe7318 enabled auto-merge (squash) October 12, 2023 13:35
@hehe7318 hehe7318 force-pushed the wip/munge-key-fix-compute branch from 474f86d to cc0bcf8 Compare October 12, 2023 17:39
@hehe7318 hehe7318 merged commit 3f6c7e6 into aws:develop Oct 12, 2023
29 of 31 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants