bug 1872802: remove old MCO etcd quorum guard resources

[deads2k]

This cleans up the old mco pdb after the new one is in place. It may fight with and old MCO operator, but only until that operator gets its new deployment.

[hexfusion]

/lgtm

cc @cgwalters @kikisdeliveryservice we feel that my changes in mco#1933 exposed a failure case that is blocking CI promotion.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, hexfusion

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:

• OWNERS [deads2k,hexfusion]

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]

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

In response to this:

bug 1872802: remove old MCO etcd quorum guard resources

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-bot]

/retest

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

[kikisdeliveryservice]

/lgtm

cc @cgwalters @kikisdeliveryservice we feel that my changes in mco#1933 exposed a failure case that is blocking CI promotion.

@hexfusion
Would you prefer to go with this PR instead of the MCO PR or are we doing both?

[hexfusion]

/lgtm
cc @cgwalters @kikisdeliveryservice we feel that my changes in mco#1933 exposed a failure case that is blocking CI promotion.

@hexfusion
Would you prefer to go with this PR instead of the MCO PR or are we doing both?

this is just about to merge I am testing upgrade in clusterbot as well. I am going to raise a partial revert on #1933 in case.

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-launch-gcp/1298724636363591680

[hexfusion]

/refresh

[hexfusion]

/retest

[openshift-bot]

/retest

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

[hexfusion]

bootstrap was a success MCD was happy[1], AWS test failures were related to Prometheus[2]

[1] https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_cluster-etcd-operator/429/pull-ci-openshift-cluster-etcd-operator-master-e2e-aws/1298691217453748224/artifacts/e2e-aws/gather-extra/pods/openshift-machine-config-operator_machine-config-daemon-5jpvp_machine-config-daemon.log

[2] https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-etcd-operator/429/pull-ci-openshift-cluster-etcd-operator-master-e2e-aws/1298691217453748224

[openshift-ci-robot]

@deads2k: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/e2e-azure	ef8fd02	link	/test e2e-azure
ci/prow/e2e-aws-disruptive	ef8fd02	link	/test e2e-aws-disruptive
ci/prow/e2e-metal-ipi	ef8fd02	link	/test e2e-metal-ipi

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-bot]

/retest

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

[hexfusion]

test upgrade quay.io/openshift-release-dev/ocp-release:4.5.7-x86_64 registry.svc.ci.openshift.org/ci-op-hhyj4fic/release:latest 

Clusterbot minor upgrade was a success.

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-launch-gcp/1298724636363591680

[openshift-ci-robot]

@deads2k: Some pull requests linked via external trackers have merged:

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

• openshift/machine-config-operator#2027 is open

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state.

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

In response to this:

bug 1872802: remove old MCO etcd quorum guard resources

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.