Skip to content

Conversation

@ricky-rav
Copy link

@ricky-rav ricky-rav commented Feb 22, 2022

This patch makes sure that non-ready nodes and deleted nodes are removed from azure load balancers.

Fixes #2040715

Signed-off-by: Riccardo Ravaioli [email protected]

@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Feb 22, 2022
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 22, 2022
@openshift-ci-robot
Copy link

@ricky-rav: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@ricky-rav ricky-rav force-pushed the dev_2040715_nodestatus branch from 59c9d0e to fdcd1d1 Compare February 22, 2022 14:58
@openshift-ci-robot
Copy link

@ricky-rav: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@deads2k
Copy link

deads2k commented Feb 22, 2022

/payload 4.10 ci blocking
/payload 4.10 nightly blocking

@openshift-ci
Copy link

openshift-ci bot commented Feb 22, 2022

@deads2k: trigger 5 jobs of type blocking for the ci release of OCP 4.10

  • periodic-ci-openshift-release-master-ci-4.10-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.10-upgrade-from-stable-4.9-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.10-upgrade-from-stable-4.9-e2e-azure-upgrade
  • periodic-ci-openshift-release-master-ci-4.10-e2e-gcp-upgrade
  • periodic-ci-openshift-release-master-ci-4.10-e2e-aws-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c92d2360-9417-11ec-9359-5b4998044e47-0

trigger 7 jobs of type blocking for the nightly release of OCP 4.10

  • periodic-ci-openshift-release-master-nightly-4.10-e2e-aws-upgrade
  • periodic-ci-openshift-release-master-ci-4.10-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.10-upgrade-from-stable-4.9-e2e-gcp-ovn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.10-e2e-aws-serial
  • periodic-ci-openshift-release-master-nightly-4.10-e2e-metal-ipi
  • periodic-ci-openshift-release-master-nightly-4.10-e2e-metal-ipi-ovn-ipv6
  • periodic-ci-openshift-release-master-nightly-4.10-e2e-metal-ipi-serial-ipv4

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c92d2360-9417-11ec-9359-5b4998044e47-1

@deads2k
Copy link

deads2k commented Feb 22, 2022

/payload 4.10 nightly blocking

@openshift-ci
Copy link

openshift-ci bot commented Feb 22, 2022

@deads2k: trigger 7 jobs of type blocking for the nightly release of OCP 4.10

  • periodic-ci-openshift-release-master-nightly-4.10-e2e-aws-upgrade
  • periodic-ci-openshift-release-master-ci-4.10-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.10-upgrade-from-stable-4.9-e2e-gcp-ovn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.10-e2e-aws-serial
  • periodic-ci-openshift-release-master-nightly-4.10-e2e-metal-ipi
  • periodic-ci-openshift-release-master-nightly-4.10-e2e-metal-ipi-ovn-ipv6
  • periodic-ci-openshift-release-master-nightly-4.10-e2e-metal-ipi-serial-ipv4

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/1e595cc0-9420-11ec-9fbc-8a55d5a5e767-0

@petr-muller
Copy link
Member

/payload 4.11 nightly blocking

@openshift-ci
Copy link

openshift-ci bot commented Feb 23, 2022

@petr-muller: trigger 7 jobs of type blocking for the nightly release of OCP 4.11

  • periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-upgrade
  • periodic-ci-openshift-release-master-ci-4.11-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.11-upgrade-from-stable-4.10-e2e-gcp-ovn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-serial
  • periodic-ci-openshift-release-master-nightly-4.11-e2e-metal-ipi
  • periodic-ci-openshift-release-master-nightly-4.11-e2e-metal-ipi-ovn-ipv6
  • periodic-ci-openshift-release-master-nightly-4.11-e2e-metal-ipi-serial-ipv4

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/449b7fa0-9487-11ec-8458-215aaa01b68f-0

@petr-muller
Copy link
Member

This is a master PR and master is 4.11

@ricky-rav ricky-rav force-pushed the dev_2040715_nodestatus branch from fdcd1d1 to 4b0b589 Compare February 23, 2022 17:17
@openshift-ci-robot
Copy link

@ricky-rav: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@ricky-rav ricky-rav force-pushed the dev_2040715_nodestatus branch from 4b0b589 to a0223b5 Compare February 23, 2022 17:27
@openshift-ci-robot
Copy link

@ricky-rav: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@ricky-rav ricky-rav changed the title [WIP] [DNM] exclude non-ready nodes from azure load balancer Bug 2040715: UPSTREAM: 108284: fix: exclude non-ready nodes from azure load balancer Feb 23, 2022
@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. and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Feb 23, 2022
@openshift-ci
Copy link

openshift-ci bot commented Feb 23, 2022

@ricky-rav: This pull request references Bugzilla bug 2040715, which is valid. 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.11.0) matches configured target release for branch (4.11.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @anuragthehatter

In response to this:

Bug 2040715: UPSTREAM: 108284: fix: exclude non-ready nodes from azure load balancer

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.

@deads2k
Copy link

deads2k commented Feb 23, 2022

/lgtm
/approve

discussed with @tkashem and we'll allow these to merge first.

@deads2k deads2k removed the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Feb 23, 2022
@deads2k deads2k added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 23, 2022
@ricky-rav ricky-rav force-pushed the dev_2040715_nodestatus branch from 47506ad to fed1a03 Compare February 24, 2022 17:53
@openshift-ci-robot
Copy link

@ricky-rav: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci
Copy link

openshift-ci bot commented Feb 24, 2022

@ricky-rav: This pull request references Bugzilla bug 2040715, which is valid.

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

Requesting review from QA contact:
/cc @anuragthehatter

In response to this:

Bug 2040715: UPSTREAM: 108284: fix: exclude non-ready nodes from azure load balancer

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.

@deads2k
Copy link

deads2k commented Feb 24, 2022

/lgtm

@deads2k deads2k removed the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Feb 24, 2022
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 24, 2022
@openshift-bot
Copy link

/retest-required

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

2 similar comments
@openshift-bot
Copy link

/retest-required

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

@openshift-bot
Copy link

/retest-required

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

@openshift-bot
Copy link

/retest-required

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

@ricky-rav ricky-rav force-pushed the dev_2040715_nodestatus branch from fed1a03 to 82abbb6 Compare February 24, 2022 21:52
@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Feb 24, 2022
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 24, 2022
@openshift-ci-robot
Copy link

@ricky-rav: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

… azure load balancers

Exclude from Azure load balancers nodes that are not in the ready state and nodes that are being deleted from the cluster.

Signed-off-by: Riccardo Ravaioli <[email protected]>
(cherry picked from commit 5b9150b247d129b5444ca7a432a71a712a00dfc1)
@ricky-rav ricky-rav force-pushed the dev_2040715_nodestatus branch from 82abbb6 to a59fd94 Compare February 24, 2022 22:58
@openshift-ci-robot
Copy link

@ricky-rav: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@deads2k
Copy link

deads2k commented Feb 24, 2022

/lgtm

@deads2k deads2k removed the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Feb 24, 2022
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 24, 2022
@openshift-ci
Copy link

openshift-ci bot commented Feb 24, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, ricky-rav

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

/retest-required

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

4 similar comments
@openshift-bot
Copy link

/retest-required

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

@openshift-bot
Copy link

/retest-required

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

@openshift-bot
Copy link

/retest-required

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

@openshift-bot
Copy link

/retest-required

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

@openshift-ci
Copy link

openshift-ci bot commented Feb 25, 2022

@ricky-rav: The following test 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-agnostic-cmd a59fd94 link false /test e2e-agnostic-cmd

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.

@openshift-merge-robot openshift-merge-robot merged commit 7478cf2 into openshift:master Feb 25, 2022
@openshift-ci
Copy link

openshift-ci bot commented Feb 25, 2022

@ricky-rav: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with /bugzilla refresh.

Bugzilla bug 2040715 has not been moved to the MODIFIED state.

In response to this:

Bug 2040715: UPSTREAM: 108284: fix: exclude non-ready nodes from azure load balancer

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. lgtm Indicates that a PR is ready to be merged. vendor-update Touching vendor dir or related files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants