-
Notifications
You must be signed in to change notification settings - Fork 260
fix: [NPM] v2 backwards compatibility #1154
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
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
| // and flushes and deletes all NPM Chains. | ||
| func (pMgr *PolicyManager) removeNPMChains() error { | ||
| // 1.1 delete the deprecated jump rule from FORWARD chain to AZURE-NPM chain, if it exists | ||
| deprecatedDeleteErrCode, deprecatedDeleteErr := pMgr.runIPTablesCommand(util.IptablesDeletionFlag, deprecatedJumpFromForwardToAzureChainArgs...) |
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.
Does this mean we will suppress any other kind of error without log ? we should at least log it!
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.
Oh, I meant to do the negated version of that boolean. Updating to do a switch statement for all possible error codes
Delete the old jump to azure chain (without ctstate new) so that we can destroy azure chain on reset.
Prior to this fix, deploying v2 after v1 caused a CrashLoopBackOff.