Skip to content
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

OCPBUGS-2176: add endpointSlice informer in master process #1302

Merged
merged 1 commit into from Oct 14, 2022

Conversation

zshi-redhat
Copy link
Contributor

@zshi-redhat zshi-redhat commented Oct 11, 2022

In MicroShift, ovnkube-master and ovnkube-node run in a single process/container
which acts as both master and node roles. The NewMasterWatchFactory needs to
initialize a new watch factory for both, otherwise it results in panic watching
endpointSlice which only existed in node watch factory.

This PR creates endpointSlices in master watch factory even it is not used when
master and node are deployed separately, this will be fixed by upstream PR:
ovn-org/ovn-kubernetes#3193.

Signed-off-by: Zenghui Shi zshi@redhat.com
(cherry picked from commit b6c1b08)

Signed-off-by: Zenghui Shi <zshi@redhat.com>
(cherry picked from commit b6c1b08)
@zshi-redhat zshi-redhat changed the title USHIFT-438: add endpointSlice informer in master process OCPBUGS-2176: add endpointSlice informer in master process Oct 11, 2022
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Oct 11, 2022
@openshift-ci-robot
Copy link
Contributor

@zshi-redhat: This pull request references Jira Issue OCPBUGS-2176, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.0) matches configured target version for branch (4.12.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @anuragthehatter

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Signed-off-by: Zenghui Shi zshi@redhat.com
(cherry picked from commit b6c1b08)

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.

@zshi-redhat
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@zshi-redhat: This pull request references Jira Issue OCPBUGS-2176, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.0) matches configured target version for branch (4.12.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @anuragthehatter

In response to this:

/jira 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.

@zshi-redhat
Copy link
Contributor Author

/retest

1 similar comment
@zshi-redhat
Copy link
Contributor Author

/retest

@zshi-redhat
Copy link
Contributor Author

@jcaamano @trozet PTAL.

@jcaamano
Copy link
Contributor

@zshi-redhat can you explain a bit why we need this in the commit message or PR message or the bug? There is no info anywhere. Might be obvious for some but not all.

@openshift-ci-robot
Copy link
Contributor

@zshi-redhat: This pull request references Jira Issue OCPBUGS-2176, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.0) matches configured target version for branch (4.12.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @anuragthehatter

In response to this:

In MicroShift, ovnkube-master and ovnkube-node run in a single process/container
which acts as both master and node roles. The NewMasterWatchFactory needs to
initialize a new watch factory for both, otherwise it results in panic watching
endpointSlice which only existed in node watch factory.

Signed-off-by: Zenghui Shi zshi@redhat.com
(cherry picked from commit b6c1b08)

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.

@zshi-redhat
Copy link
Contributor Author

@zshi-redhat can you explain a bit why we need this in the commit message or PR message or the bug? There is no info anywhere. Might be obvious for some but not all.

@jcaamano sure, I updated the PR message.

@openshift-ci-robot
Copy link
Contributor

@zshi-redhat: This pull request references Jira Issue OCPBUGS-2176, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.0) matches configured target version for branch (4.12.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @anuragthehatter

In response to this:

In MicroShift, ovnkube-master and ovnkube-node run in a single process/container
which acts as both master and node roles. The NewMasterWatchFactory needs to
initialize a new watch factory for both, otherwise it results in panic watching
endpointSlice which only existed in node watch factory.

This PR creates endpointSlices in master watch factory even it is not used when
master and node are deployed separately, this will be fixed by upstream PR:
ovn-org/ovn-kubernetes#3193.

Signed-off-by: Zenghui Shi zshi@redhat.com
(cherry picked from commit b6c1b08)

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.

@jcaamano
Copy link
Contributor

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 13, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 13, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcaamano, zshi-redhat

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 13, 2022
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD ecd74ad and 2 for PR HEAD 55bb05b in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 13, 2022

@zshi-redhat: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-vsphere-windows 55bb05b link false /test e2e-vsphere-windows
ci/prow/e2e-aws-ovn-windows 55bb05b link false /test e2e-aws-ovn-windows
ci/prow/e2e-openstack-ovn 55bb05b link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-hypershift 55bb05b link false /test e2e-aws-ovn-hypershift

Full PR test history. Your PR dashboard.

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.

@zshi-redhat
Copy link
Contributor Author

/retest-required

@openshift-merge-robot openshift-merge-robot merged commit 1992b7d into openshift:master Oct 14, 2022
@openshift-ci-robot
Copy link
Contributor

@zshi-redhat: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-2176 has been moved to the MODIFIED state.

In response to this:

In MicroShift, ovnkube-master and ovnkube-node run in a single process/container
which acts as both master and node roles. The NewMasterWatchFactory needs to
initialize a new watch factory for both, otherwise it results in panic watching
endpointSlice which only existed in node watch factory.

This PR creates endpointSlices in master watch factory even it is not used when
master and node are deployed separately, this will be fixed by upstream PR:
ovn-org/ovn-kubernetes#3193.

Signed-off-by: Zenghui Shi zshi@redhat.com
(cherry picked from commit b6c1b08)

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants