-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Bugfix kops update always detecting changes when using ExecContainerAction. #3790
Bugfix kops update always detecting changes when using ExecContainerAction. #3790
Conversation
…en HookSpecs have ExecContainerAction defined.
/assign @chrislovecnm @justinsb @gambol99 |
Any word @blakebarnett |
First test worked, need to setup the exact same scenario again to re-verify. |
👍 LGTM |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chrislovecnm The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test all [submit-queue is verifying that this PR is safe to merge] |
/test pull-kops-e2e-kubernetes-aws |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. |
ExecContainerAction
is referenced as a pointer in theHookSpec
. When the bootstrapscript is run, it fingerprints the content here and stores it on-top of the existingExecContainerAction
within the Hook being parsed. The bootstrapscript is called for every Instance Group, and so the fingerprinted content gets passed and re-parsed.This PR fixes the issue by creating a new
ExecContainerAction
object and assigning it to the hook being processed. Tests should now cover this case by running theResourceNodeUp
fn multiple times.Fixes #3516