-
Notifications
You must be signed in to change notification settings - Fork 104
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
Conversation
There was a problem hiding this 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' |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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 ReportAll modified lines are covered by tests ✅
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
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
938df41
to
aa836ef
Compare
33c312a
to
474f86d
Compare
474f86d
to
cc0bcf8
Compare
Description of changes
References
Checklist
develop
add the branch name as prefix in the PR title (e.g.[release-3.6]
).