Enable 4.3.16 in candidate channel(s)

[openshift-bot]

Please merge immediately. This PR does not need to wait for an advisory to ship, but the associated advisory is https://access.redhat.com/errata/RHBA-2020:1529 .

This PR will also enable upgrades from 4.3.16 to releases in candidate-4.4

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-bot
To complete the pull request process, please assign jwforres
You can assign the PR to them by writing /assign @jwforres in a comment when ready.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[wking]

Waiting until the release-controller accepts the build.

/hold

[wking]

Sanity check on the channels: looks good.

$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.3.16-x86_64 | grep Upgrades
  Upgrades: 4.2.21, 4.2.22, 4.2.23, 4.2.25, 4.2.26, 4.2.27, 4.2.28, 4.2.29, 4.2.30, 4.3.0, 4.3.1, 4.3.2, 4.3.3, 4.3.5, 4.3.8, 4.3.9, 4.3.10, 4.3.11, 4.3.12, 4.3.13, 4.3.14, 4.3.15

(and same for s390x and ppc64le).

[sdodson]

There are potential build problems with this build. Lets hold this until we have resolution on that even if it's been accepted.

[vrutkovs]

ovn container also has a unsigned RPMs, so perpaps this should be dropped in favor of a respin?

[sdodson]

/close
yup, 4.3.16 is dead

[openshift-ci-robot]

@sdodson: Closed this PR.

Details

In response to this:

/close
yup, 4.3.16 is dead

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.