Skip to content

OCPBUGS-6908: 4.12 Avoid firewalld flush of iptables#1309

Merged
openshift-merge-robot merged 2 commits intoopenshift:release-4.12from
mangelajo:backport-USHIFT-789
Feb 9, 2023
Merged

OCPBUGS-6908: 4.12 Avoid firewalld flush of iptables#1309
openshift-merge-robot merged 2 commits intoopenshift:release-4.12from
mangelajo:backport-USHIFT-789

Conversation

@mangelajo
Copy link
Contributor

@mangelajo mangelajo commented Jan 31, 2023

cherry pick from #1300 (automatic cherry
pick failed with conflict on the microshift.spec file changelog entries)

Avoid firewalld flush of iptables

https://issues.redhat.com/browse/NP-641
https://issues.redhat.com/browse/USHIFT-789
https://issues.redhat.com/browse/OCPBUGS-6860

Disables firewalld access to iptables related nftables translator,
this avoids firewalld flush of iptables under any circumstance,
firewalld will work at nftables level, while MicroShift/OVN can
continue to work at iptables level (translated to nft) under the hood.

(cherry picked from commit f51d031)
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 31, 2023

@mangelajo: 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.

Details

In response to this:

4.12 Avoid firewalld flush of iptables

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 openshift-ci bot requested review from oglok and sallyom January 31, 2023 14:23
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 31, 2023
@dhellmann
Copy link
Contributor

If the automated cherry-pick had been successful, I think it would have cloned the bug for you, too. I think you'll have to do that by hand now, though to have a valid Jira ticket.

@dhellmann
Copy link
Contributor

@jogeo do you have enough information to create a test plan for this PR?

@mangelajo
Copy link
Contributor Author

That was my next question, so I need to clone the JIRA ticket and target it to 4.12 I guess, let me try that. I am still not familiar enough to do it by heart.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 1, 2023

@mangelajo: 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.

Details

In response to this:

4.12 Avoid firewalld flush of iptables

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.

@mangelajo
Copy link
Contributor Author

@dhellmann but https://issues.redhat.com/browse/OCPBUGS-6860 is targeted to 4.12, do I need anything in addition to that?

@mangelajo mangelajo changed the title 4.12 Avoid firewalld flush of iptables BUG OCPBUGS-6860 4.12 Avoid firewalld flush of iptables Feb 1, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 1, 2023

@mangelajo: 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.

Details

In response to this:

BUG OCPBUGS-6860 4.12 Avoid firewalld flush of iptables

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.

@mangelajo
Copy link
Contributor Author

/bugzilla refresh

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 1, 2023

@mangelajo: 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.

Details

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.

@mangelajo mangelajo changed the title BUG OCPBUGS-6860 4.12 Avoid firewalld flush of iptables Bug OCPBUGS-6860 4.12 Avoid firewalld flush of iptables Feb 1, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 1, 2023

@mangelajo: 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.

Details

In response to this:

Bug OCPBUGS-6860 4.12 Avoid firewalld flush of iptables

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.

@mangelajo mangelajo changed the title Bug OCPBUGS-6860 4.12 Avoid firewalld flush of iptables OCPBUGS-6860: 4.12 Avoid firewalld flush of iptables Feb 1, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 1, 2023

@mangelajo: 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.

Details

In response to this:

OCPBUGS-6860: 4.12 Avoid firewalld flush of iptables

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 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 1, 2023
@openshift-ci-robot
Copy link

@mangelajo: This pull request references Jira Issue OCPBUGS-6860, which is invalid:

  • expected the bug to target the "4.12.z" version, but no target version was set
  • expected Jira Issue OCPBUGS-6860 to depend on a bug targeting a version in 4.13.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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

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

Details

In response to this:

cherry pick from #1300 (automatic cherry
pick failed with conflict on the microshift.spec file changelog entries)

Avoid firewalld flush of iptables

https://issues.redhat.com/browse/NP-641
https://issues.redhat.com/browse/USHIFT-789
https://issues.redhat.com/browse/OCPBUGS-6860

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.

@mangelajo
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

@mangelajo: This pull request references Jira Issue OCPBUGS-6860, which is invalid:

  • expected Jira Issue OCPBUGS-6860 to depend on a bug targeting a version in 4.13.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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

Details

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.

@mangelajo mangelajo changed the title OCPBUGS-6860: 4.12 Avoid firewalld flush of iptables OCPBUGS-6908: 4.12 Avoid firewalld flush of iptables Feb 1, 2023
@openshift-ci-robot
Copy link

@mangelajo: This pull request references Jira Issue OCPBUGS-6908, which is invalid:

  • expected dependent Jira Issue OCPBUGS-6860 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is New instead
  • expected dependent Jira Issue OCPBUGS-6860 to target a version in 4.13.0, but it targets "4.13" instead

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

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

Details

In response to this:

cherry pick from #1300 (automatic cherry
pick failed with conflict on the microshift.spec file changelog entries)

Avoid firewalld flush of iptables

https://issues.redhat.com/browse/NP-641
https://issues.redhat.com/browse/USHIFT-789
https://issues.redhat.com/browse/OCPBUGS-6860

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

openshift-ci bot commented Feb 1, 2023

@mangelajo: 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.

Details

In response to this:

OCPBUGS-6908: 4.12 Avoid firewalld flush of iptables

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.

@mangelajo
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Feb 1, 2023
@openshift-ci-robot
Copy link

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

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.z) matches configured target version for branch (4.12.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-6860 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-6860 targets the "4.13.0" version, which is one of the valid target versions: 4.13.0
  • bug has dependents

Requesting review from QA contact:
/cc @jogeo

Details

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.

@openshift-ci openshift-ci bot requested a review from jogeo February 1, 2023 12:02
@jogeo
Copy link
Contributor

jogeo commented Feb 1, 2023

@dhellmann The original issue was easy to recreate and surfaced by a couple existing test cases. So, QE has the all the test plan information we need.

@dhellmann
Copy link
Contributor

Thanks, @jogeo. Handing this off to QE, then.

/label backport-risk-assessed
/lgtm

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 1, 2023
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 1, 2023
@ggiguash
Copy link
Contributor

ggiguash commented Feb 5, 2023

/retest

1 similar comment
@zshi-redhat
Copy link
Contributor

/retest

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 8, 2023
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 9, 2023
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 9, 2023
@dhellmann
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 9, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 9, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhellmann, mangelajo

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

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [dhellmann,mangelajo]

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 9, 2023

@mangelajo: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@jogeo
Copy link
Contributor

jogeo commented Feb 9, 2023

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Feb 9, 2023
@openshift-merge-robot openshift-merge-robot merged commit 932074d into openshift:release-4.12 Feb 9, 2023
@openshift-ci-robot
Copy link

@mangelajo: Jira Issue OCPBUGS-6908 is in an unrecognized state (Verified) and will not be moved to the MODIFIED state.

Details

In response to this:

cherry pick from #1300 (automatic cherry
pick failed with conflict on the microshift.spec file changelog entries)

Avoid firewalld flush of iptables

https://issues.redhat.com/browse/NP-641
https://issues.redhat.com/browse/USHIFT-789
https://issues.redhat.com/browse/OCPBUGS-6860

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. 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. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.