Bug 1740731: Initializing runningPods on SDN bootup for 4.x

[alexanderConstantinescu]

This is a fix for BUG 1723924

FIX for 4.X on origin, see linked PR's in

SDN:

openshift/sdn#20

3.11:

#23522

The problem:

As mentioned in the link above, when the openshift networking process dies, the "podManager" object and its attribute "runningPods" is wiped for memory, which can lead to stateful inconsistencies
with openflow ports concerning pods from a multicast-enabled namespaces

The fix:

We now initialize the "podManager" with the initial state of all running pods when the process is booted, as such we will have a synchronized state.

[openshift-ci-robot]

@alexanderConstantinescu: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

Initializing runningPods on SDN bootup for 4.x

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alexanderConstantinescu]

/assign @danwinship @dcbw

[openshift-ci-robot]

@alexanderConstantinescu: This pull request references an invalid Bugzilla bug:

• expected the bug to target the "4.1.z" release, but it targets "3.11.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1723924: Initializing runningPods on SDN bootup for 4.x

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alexanderConstantinescu]

/bugzilla refresh

[openshift-ci-robot]

@alexanderConstantinescu: This pull request references an invalid Bugzilla bug:

• expected the bug to target the "4.1.z" release, but it targets "3.11.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci-robot]

@alexanderConstantinescu: This pull request references an invalid Bugzilla bug:

• expected the bug to target the "4.1.z" release, but it targets "3.11.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1723924: Initializing runningPods on SDN bootup for 4.x

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alexanderConstantinescu]

/retitle Bug 1740731: Initializing runningPods on SDN bootup for 4.x

[openshift-ci-robot]

@alexanderConstantinescu: This pull request references an invalid Bugzilla bug:

• expected dependent Bugzilla bug to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is POST instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1740731: Initializing runningPods on SDN bootup for 4.x

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alexanderConstantinescu]

/bugzilla refresh

[openshift-ci-robot]

@alexanderConstantinescu: This pull request references an invalid Bugzilla bug:

• expected the bug to target the "4.1.z" release, but it targets "4.1.0" instead
• expected dependent Bugzilla bug to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is POST instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alexanderConstantinescu]

/bugzilla refresh
/retest

[openshift-ci-robot]

@alexanderConstantinescu: This pull request references an invalid Bugzilla bug:

• expected dependent Bugzilla bug to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is POST instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh
/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alexanderConstantinescu]

/bugzilla refresh

[openshift-ci-robot]

@alexanderConstantinescu: This pull request references Bugzilla bug 1740731, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

/bugzilla refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[eparis]

The PR requires the engineering team to review/lgtm/approve

[alexanderConstantinescu]

Can I get some eyes on this again? @squeed @danwinship

FYI : 4.2 PR has been merged and verified

[squeed]

/lgtm
/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alexanderConstantinescu, squeed

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/network/OWNERS [squeed]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@alexanderConstantinescu: All pull requests linked via external trackers have merged. Bugzilla bug 1740731 has been moved to the MODIFIED state.

In response to this:

Bug 1740731: Initializing runningPods on SDN bootup for 4.x

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci-robot]

@alexanderConstantinescu: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/prow/e2e-aws-upgrade	7709564	link	/test e2e-aws-upgrade

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.