Skip to content

Conversation

@huntergregory
Copy link
Contributor

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.

@huntergregory huntergregory added the npm Related to NPM. label Dec 3, 2021
@huntergregory
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

vakalapa
vakalapa previously approved these changes Dec 7, 2021
@huntergregory
Copy link
Contributor Author

/azp run

@azure-pipelines
Copy link

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...)
Copy link
Contributor

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!

Copy link
Contributor Author

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

@huntergregory huntergregory merged commit 6a47391 into master Dec 14, 2021
@huntergregory huntergregory deleted the npm-backwards-compatibility branch December 14, 2021 01:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

npm Related to NPM.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants