-
Notifications
You must be signed in to change notification settings - Fork 4
fix: Opaal not included in bootstrap or cert update #29
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
Conversation
Opaal was not included in the certificate update, there is a place where opaal is used and needs the update FQDN and IP Signed-off-by: Travis Powell <[email protected]>
|
Thanks. Has this been tested? |
Signed-off-by: Travis Powell <[email protected]>
Signed-off-by: Travis Powell <[email protected]>
Updated the path to the opaal.container file, was pointed at openchami/config instad of containers/systemd Signed-off-by: Travis Powell <[email protected]>
|
The opaal sed had a mis-configuration, it has now been updated to the right path to the container file. |
Signed-off-by: Travis Powell <[email protected]>
Signed-off-by: Travis Powell <[email protected]>
Signed-off-by: Travis Powell <[email protected]>
Signed-off-by: Travis Powell <[email protected]>
synackd
left a comment
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.
Just a couple of things, but I think after these this is ready to merge.
Signed-off-by: Travis Powell <[email protected]>
Signed-off-by: Travis Powell <[email protected]>
synackd
left a comment
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.
LGTM! 🚀
Opaal was not included in the certificate update, there is a place where opaal is used and needs the update FQDN and IP