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 1988425: Change to use mountPath: /host #1169

Merged
merged 1 commit into from Aug 12, 2021

Conversation

mccv1r0
Copy link
Contributor

@mccv1r0 mccv1r0 commented Jul 30, 2021

Change iptables chain names to not conflict with existing workaround(s)

Signed-off-by: Michael Cambria mcambria@redhat.com
(cherry picked from commit 32d72e5)

Change iptables chain names to not conflict with existing workaround(s)

Signed-off-by: Michael Cambria <mcambria@redhat.com>
(cherry picked from commit 32d72e5)
@openshift-ci openshift-ci bot requested review from danwinship and dcbw July 30, 2021 13:32
@mccv1r0 mccv1r0 changed the title Change to use mountPath: /host Bug 1988425: Change to use mountPath: /host Jul 30, 2021
@openshift-ci openshift-ci bot added bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent 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 Jul 30, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 30, 2021

@mccv1r0: This pull request references Bugzilla bug 1988425, 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.

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

Requesting review from QA contact:
/cc @zhaozhanqi

In response to this:

Bug 1988425: Change to use mountPath: /host

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 zhaozhanqi July 30, 2021 14:04
@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Jul 30, 2021

/test e2e-gcp-ovn

@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Jul 30, 2021

/test e2e-metal-ipi-ovn-ipv6
/test e2e-agnostic-upgrade

Copy link
Contributor

@danwinship danwinship left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's confusing that the commit message summary only describes one of the two things the commit does. Either split it into two commits, or else make the summary more generic ("fixes to azure iptables setup script" etc) and describe both fixes in the commit message body, rather than one in the summary and one in the body

iptables -F AZURE_ICMP_ACTION
iptables -A AZURE_ICMP_ACTION -j LOG
iptables -A AZURE_ICMP_ACTION -j DROP
/host/usr/bin/oc observe pods -n openshift-sdn -l app=sdn -a '{ .status.hostIP }' -- /var/run/add_iptables.sh
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems not safe; is oc statically linked, but is it guaranteed to always be statically linked? I think you have to do chroot /host oc ... though of course then you also have to write the script out to /home/var/run rather than /var/run

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we've glossed over this so far but due to FIPS needing openssl for Go, we can't rely on these things being fully static.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The other pattern is to use e.g. systemd-run -qPG -- oc observe pods -n openshift-sdn -l app=sdn -a '{ .status.hostIP }' -- /var/run/add_iptables.sh.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The commit message already describes:

  1. Change to use mountPath: /host
  2. Change iptables chain names to not conflict with existing workaround(s)

For SDN, I'll probably need to change upstream to use systemd-run (or whatever ends up being used) and back port.

The OVN version of this fix will start with whatever consensus decides is best.

@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Jul 30, 2021

/test e2e-gcp-ovn
/test e2e-metal-ipi-ovn-ipv6

@Makdaam
Copy link
Member

Makdaam commented Aug 2, 2021

/retest

1 similar comment
@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 3, 2021

/retest

@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 3, 2021

/test e2e-gcp-ovn
/test e2e-agnostic-upgrade

@abhat
Copy link
Contributor

abhat commented Aug 4, 2021

/retest-required

2 similar comments
@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 4, 2021

/retest-required

@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 4, 2021

/retest-required

@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 4, 2021

/test e2e-gcp-ovn

4 similar comments
@Makdaam
Copy link
Member

Makdaam commented Aug 5, 2021

/test e2e-gcp-ovn

@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 5, 2021

/test e2e-gcp-ovn

@Makdaam
Copy link
Member

Makdaam commented Aug 6, 2021

/test e2e-gcp-ovn

@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 6, 2021

/test e2e-gcp-ovn

@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 6, 2021

@knobunc Can you override this required gcp test? As you know this PR changes yaml that runs on Azure only.

@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 6, 2021

/test e2e-gcp-ovn

1 similar comment
@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 9, 2021

/test e2e-gcp-ovn

@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 9, 2021

/test e2e-openstack-ovn
/test e2e-gcp-ovn-upgrade

@brenton
Copy link

brenton commented Aug 10, 2021

Is this PR opened against the correct branch? I would have expected it to merge into release-4.8. When I look now the master, release-4.10 and release-4.9 branches all already have the fix from https://bugzilla.redhat.com/show_bug.cgi?id=1984449.

@abhat
Copy link
Contributor

abhat commented Aug 10, 2021

@mccv1r0 since this is a master branch PR, the bz needs retitling?

@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 10, 2021

@mccv1r0 since this is a master branch PR, the bz needs retitling?

The PR needs to be against 4.8

It's a cherry-pick from master

@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 11, 2021

/test e2e-azure-ovn-dualstack

@openshift-bot
Copy link
Contributor

/retest-required

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

@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 11, 2021

Must we hold up an SDN only change due to an OVN flake?

@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 11, 2021

/test e2e-azure-ovn-dualstack

1 similar comment
@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 11, 2021

/test e2e-azure-ovn-dualstack

@bparees bparees added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Aug 11, 2021
@openshift-bot
Copy link
Contributor

/retest-required

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

4 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@mffiedler
Copy link

mffiedler commented Aug 11, 2021

Verified as with #1160. 4.8.z cluster-bot Azure cluster built from this PR. ssh into node works fine both before and after boot. Without this PR ssh just hangs.

/lgtm
/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Aug 11, 2021
@mccv1r0
Copy link
Contributor Author

mccv1r0 commented Aug 11, 2021

/test e2e-azure-ovn-dualstack

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 11, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dcbw, mccv1r0, mffiedler

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

/retest-required

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

9 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@openshift-bot
Copy link
Contributor

/retest-required

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

@dcbw
Copy link
Member

dcbw commented Aug 12, 2021

/override ci/prow/e2e-azure-ovn-dualstack

Error on cloud setup:
level=error msg=Error: updating Load Balancer "ci-op-5hhdw15j-f5292-k6tnt" (Resource Group "ci-op-5hhdw15j-f5292-k6tnt-rg") for Probe "api-internal-probe": network.LoadBalancersClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: Code="PrivateIPAddressVersionCannotBeModified" Message="Load balancer frontend IP configuration /subscriptions/d38f1e38-4bed-438e-b227-833f997adf6a/resourceGroups/ci-op-5hhdw15j-f5292-k6tnt-rg/providers/Microsoft.Network/loadBalancers/ci-op-5hhdw15j-f5292-k6tnt/frontendIPConfigurations/public-lb-ip-v6 has an existing private IP address version IPv6 and the request has private IP address version IPv4, which do not match. Private IP address version cannot be modified once the resource is created." Details=[]

@openshift-ci openshift-ci bot merged commit f7e31c5 into openshift:release-4.8 Aug 12, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 12, 2021

@dcbw: Overrode contexts on behalf of dcbw: ci/prow/e2e-azure-ovn-dualstack

In response to this:

/override ci/prow/e2e-azure-ovn-dualstack

Error on cloud setup:
level=error msg=Error: updating Load Balancer "ci-op-5hhdw15j-f5292-k6tnt" (Resource Group "ci-op-5hhdw15j-f5292-k6tnt-rg") for Probe "api-internal-probe": network.LoadBalancersClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: Code="PrivateIPAddressVersionCannotBeModified" Message="Load balancer frontend IP configuration /subscriptions/d38f1e38-4bed-438e-b227-833f997adf6a/resourceGroups/ci-op-5hhdw15j-f5292-k6tnt-rg/providers/Microsoft.Network/loadBalancers/ci-op-5hhdw15j-f5292-k6tnt/frontendIPConfigurations/public-lb-ip-v6 has an existing private IP address version IPv6 and the request has private IP address version IPv4, which do not match. Private IP address version cannot be modified once the resource is created." 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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 12, 2021

@mccv1r0: All pull requests linked via external trackers have merged:

Bugzilla bug 1988425 has been moved to the MODIFIED state.

In response to this:

Bug 1988425: Change to use mountPath: /host

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/severity-urgent Referenced Bugzilla bug's severity is urgent 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. 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. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

10 participants