Skip to content

Bug 1870373: Ingress Operator reports available when DNS fails to provision#495

Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
candita:BZ-1870373
Dec 4, 2020
Merged

Bug 1870373: Ingress Operator reports available when DNS fails to provision#495
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
candita:BZ-1870373

Conversation

@candita
Copy link
Contributor

@candita candita commented Nov 23, 2020

BZ-1870373: Ingress Operator reports available when DNS fails to provision

  • Check DNSReady and LoadBalancerReady when determining Availability in computeIngressAvailableCondition
  • Call computeIngressAvailableCondition after computing other conditions in syncIngressControllerStatus
  • Change unit tests for computeIngressAvailableCondition
  • Refactor the checks for conditions into checkConditions, to share between computeIngressAvailable and computeIngressDegraded

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 23, 2020
@candita
Copy link
Contributor Author

candita commented Nov 23, 2020

/do-not-merge

@candita candita changed the title BZ-1870373: [WIP] Ingress Operator reports available when DNS fails to prov… Bug 1870373: [WIP] Ingress Operator reports available when DNS fails to prov… Nov 23, 2020
@openshift-ci-robot openshift-ci-robot added bugzilla/severity-low Referenced Bugzilla bug's severity is low 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 Nov 23, 2020
@openshift-ci-robot
Copy link
Contributor

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

In response to this:

Bug 1870373: [WIP] Ingress Operator reports available when DNS fails to prov…

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.

@candita candita changed the title Bug 1870373: [WIP] Ingress Operator reports available when DNS fails to prov… Bug BZ-1870373: [WIP] Ingress Operator reports available when DNS fails to prov… Nov 23, 2020
@openshift-ci-robot
Copy link
Contributor

@candita: 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 BZ-1870373: [WIP] Ingress Operator reports available when DNS fails to prov…

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 bugzilla/severity-low Referenced Bugzilla bug's severity is low 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 Nov 23, 2020
@candita
Copy link
Contributor Author

candita commented Nov 23, 2020

/retest

@candita candita force-pushed the BZ-1870373 branch 3 times, most recently from 1bad1d5 to 8ad1609 Compare November 24, 2020 01:11
@sgreene570
Copy link
Contributor

/retitle [WIP] Bug 1870373: Ingress Operator reports available when DNS fails to provision

@openshift-ci-robot openshift-ci-robot changed the title Bug BZ-1870373: [WIP] Ingress Operator reports available when DNS fails to prov… [WIP] Bug 1870373: Ingress Operator reports available when DNS fails to provision Nov 24, 2020
@openshift-ci-robot openshift-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. bugzilla/severity-low Referenced Bugzilla bug's severity is low 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 Nov 24, 2020
@openshift-ci-robot
Copy link
Contributor

@candita: This pull request references Bugzilla bug 1870373, which is valid.

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

In response to this:

[WIP] Bug 1870373: Ingress Operator reports available when DNS fails to provision

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.

@candita candita changed the title [WIP] Bug 1870373: Ingress Operator reports available when DNS fails to provision Bug 1870373: [WIP] Ingress Operator reports available when DNS fails to provision Nov 24, 2020
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 24, 2020
@candita
Copy link
Contributor Author

candita commented Nov 24, 2020

/retitle [WIP] Bug 1870373: Ingress Operator reports available when DNS fails to provision

@openshift-ci-robot openshift-ci-robot changed the title Bug 1870373: [WIP] Ingress Operator reports available when DNS fails to provision [WIP] Bug 1870373: Ingress Operator reports available when DNS fails to provision Nov 24, 2020
@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 24, 2020
@openshift-ci-robot
Copy link
Contributor

@candita: The /retest command does not accept any targets.
The following commands are available to trigger jobs:

  • /test e2e-aws
  • /test e2e-aws-operator
  • /test e2e-azure
  • /test e2e-upgrade
  • /test images
  • /test unit
  • /test verify

Use /test all to run the following jobs:

  • pull-ci-openshift-cluster-ingress-operator-master-e2e-aws
  • pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-operator
  • pull-ci-openshift-cluster-ingress-operator-master-e2e-upgrade
  • pull-ci-openshift-cluster-ingress-operator-master-images
  • pull-ci-openshift-cluster-ingress-operator-master-unit
  • pull-ci-openshift-cluster-ingress-operator-master-verify
Details

In response to this:

/retest e2e-aws

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.

@candita
Copy link
Contributor Author

candita commented Dec 1, 2020

/test e2e-aws

@sgreene570
Copy link
Contributor

/retest

@openshift-ci-robot
Copy link
Contributor

@candita: This pull request references Bugzilla bug 1870373, which is valid.

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

In response to this:

Bug 1870373: Ingress Operator reports available when DNS fails to provision

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.

@Miciah
Copy link
Contributor

Miciah commented Dec 2, 2020

The fix looks correct, and you've added some really nice clean-ups and test coverage improvements as well. Thanks!
/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 2, 2020
@candita
Copy link
Contributor Author

candita commented Dec 2, 2020

/test e2e-aws-operator

@candita
Copy link
Contributor Author

candita commented Dec 2, 2020

/test e2e-upgrade

@candita
Copy link
Contributor Author

candita commented Dec 2, 2020

/test e2e-aws-operator

@candita
Copy link
Contributor Author

candita commented Dec 3, 2020

/retest

@openshift-bot
Copy link
Contributor

/retest

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

@candita
Copy link
Contributor Author

candita commented Dec 3, 2020

/hold
Allow #493 to get in ASAP to meet deadline.

@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 Dec 3, 2020
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Dec 3, 2020
@sgreene570
Copy link
Contributor

/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 Dec 3, 2020
@sgreene570
Copy link
Contributor

Rebase looks good.
/lgtm
/honk

@openshift-ci-robot
Copy link
Contributor

@sgreene570:
goose image

Details

In response to this:

Rebase looks good.
/lgtm
/honk

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 lgtm Indicates that a PR is ready to be merged. label Dec 3, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: candita, Miciah, sgreene570

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 [Miciah,candita,sgreene570]

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

@openshift-merge-robot openshift-merge-robot merged commit 22bc95c into openshift:master Dec 4, 2020
@openshift-ci-robot
Copy link
Contributor

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

Bugzilla bug 1870373 has been moved to the MODIFIED state.

Details

In response to this:

Bug 1870373: Ingress Operator reports available when DNS fails to provision

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-low Referenced Bugzilla bug's severity is low 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants