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

Bug 1820975: oVirt, fix disable tx checksum offload for workers #1628

Merged

Conversation

Gal-Zaidman
Copy link
Contributor

We need to disable tx checksum offload on worker nodes due to BZ#1794714.
This is currenly a workaround and is tracked for removal on BZ#18.

Signed-off-by: Gal Zaidman gzaidman@redhat.com

- What I did

- How to verify it

- Description for the changelog

We need to disable tx checksum offload on worker nodes due to BZ#1794714.
This is currenly a workaround and is tracked for removal on BZ#18.

Signed-off-by: Gal Zaidman <gzaidman@redhat.com>
@openshift-ci-robot
Copy link
Contributor

@Gal-Zaidman: 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:

Bug 1820975, oVirt: fix disable tx checksum offload for workers

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.

@Gal-Zaidman
Copy link
Contributor Author

/cc rgolangh

@rgolangh
Copy link
Contributor

rgolangh commented Apr 7, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 7, 2020
@Gal-Zaidman
Copy link
Contributor Author

/retitle Bug 1820975: oVirt, fix disable tx checksum offload for workers

@Gal-Zaidman
Copy link
Contributor Author

/test e2e-ovirt

@openshift-ci-robot openshift-ci-robot changed the title Bug 1820975, oVirt: fix disable tx checksum offload for workers Bug 1820975: oVirt, fix disable tx checksum offload for workers Apr 7, 2020
@openshift-ci-robot openshift-ci-robot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Apr 7, 2020
@openshift-ci-robot
Copy link
Contributor

@Gal-Zaidman: This pull request references Bugzilla bug 1820975, which is invalid:

  • expected dependent Bugzilla bug 1821005 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA 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 1820975: oVirt, fix disable tx checksum offload for workers

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.

@Gal-Zaidman
Copy link
Contributor Author

/bugzilla refresh

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Apr 7, 2020
@openshift-ci-robot
Copy link
Contributor

@Gal-Zaidman: This pull request references Bugzilla bug 1820975, 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.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.4.0) matches configured target release for branch (4.4.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1821005 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1821005 targets the "4.5.0" release, matching the expected (4.5.0) release
  • bug has dependents

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 openshift-ci-robot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Apr 7, 2020
@ashcrow
Copy link
Member

ashcrow commented Apr 7, 2020

Is this a backport or was it fixed differently in master?

@yuqi-zhang
Copy link
Contributor

/hold

So generally the proper way is to fix it in 4.5 first by making a PR against master, and once that merges and passes QA, have the bot backport to 4.4.

I see you instead duplicated the bug for 4.5, and hand modified that to "Verified" to pass the bot check. I am not sure if you should be doing that unless this is a critical urgent fix. For now please open a PR against 4.5 first (unless this is only something that needs to be fixed for 4.4?).

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 7, 2020
@kikisdeliveryservice
Copy link
Contributor

This was already fixed in master via: #1606

@ashcrow
Copy link
Member

ashcrow commented Apr 7, 2020

This was already fixed in master via: #1606

@kikisdeliveryservice is right -- there is a fix in master. The BZ being invalid is fine as it should be invalid until the original PR is verified by QE.

@ashcrow
Copy link
Member

ashcrow commented Apr 7, 2020

/bugzilla refresh

@openshift-ci-robot openshift-ci-robot removed the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Apr 7, 2020
@openshift-ci-robot
Copy link
Contributor

@ashcrow: This pull request references Bugzilla bug 1820975, which is invalid:

  • expected dependent Bugzilla bug 1821005 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ASSIGNED 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 openshift-ci-robot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Apr 7, 2020
@ashcrow
Copy link
Member

ashcrow commented Apr 7, 2020

The bugs should be in the right state now:

  • 1821005: ON_QA
  • 1820975: POST

Once 1821005 is verified by QE then this can be refreshed and move forward.

@yuqi-zhang
Copy link
Contributor

Oh I see, the context is in #1617
/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 7, 2020
@sinnykumari
Copy link
Contributor

/retest

@sinnykumari
Copy link
Contributor

/approve

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Gal-Zaidman, rgolangh, sinnykumari

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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 8, 2020
@sinnykumari
Copy link
Contributor

/skip e2e-aws-scaleup-rhel7

@sinnykumari
Copy link
Contributor

/skip

@rgolangh
Copy link
Contributor

rgolangh commented Apr 8, 2020

/bugzilla refresh

@openshift-ci-robot
Copy link
Contributor

@rgolangh: This pull request references Bugzilla bug 1820975, which is invalid:

  • expected dependent Bugzilla bug 1821005 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.

@rgolangh
Copy link
Contributor

rgolangh commented Apr 8, 2020

/bugzilla refresh

@openshift-ci-robot openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Apr 8, 2020
@openshift-ci-robot
Copy link
Contributor

@rgolangh: This pull request references Bugzilla bug 1820975, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.4.0) matches configured target release for branch (4.4.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1821005 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1821005 targets the "4.5.0" release, matching the expected (4.5.0) release
  • bug has dependents

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.

@ashcrow ashcrow added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Apr 8, 2020
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Apr 8, 2020

@Gal-Zaidman: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws-scaleup-rhel7 3c5cb66 link /test e2e-aws-scaleup-rhel7

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.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@sdodson
Copy link
Member

sdodson commented Apr 8, 2020

Why are we only doing this for workers? In compact clusters (no workers) masters would also need this, no?

@openshift-merge-robot openshift-merge-robot merged commit 5d4cb5a into openshift:release-4.4 Apr 8, 2020
@openshift-ci-robot
Copy link
Contributor

@Gal-Zaidman: All pull requests linked via external trackers have merged: openshift/machine-config-operator#1628. Bugzilla bug 1820975 has been moved to the MODIFIED state.

In response to this:

Bug 1820975: oVirt, fix disable tx checksum offload for workers

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.

@ashcrow
Copy link
Member

ashcrow commented Apr 8, 2020

@Gal-Zaidman can you answer @sdodson's question above?

@Gal-Zaidman
Copy link
Contributor Author

Why are we only doing this for workers? In compact clusters (no workers) masters would also need this, no?

This fix is to make NodePort work.
NodePort is used to exposes services which should run on worker nodes.
I know that you can use NodePort with masters as well but this is not the "usual/recommended use case" and disabling checksum by default is a workaround and not a solution.
So we decided to apply this only to worker nodes

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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

10 participants