Bug 1784201: lib/resourcemerge: set AdditionalTrustBundle

[runcom]

Proxy day2 wasn't working because the MCO wasn't rolling the additionalTrustBundle to nodes. Now it does and day2 proxy is deployed.

Signed-off-by: Antonio Murdaca runcom@linux.com

[openshift-ci-robot]

@runcom: This pull request references Bugzilla bug 1784201, 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.5.0) matches configured target release for branch (4.5.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 1784201: lib/resourcemerge: set AdditionalTrustBundle

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]

@runcom: This pull request references Bugzilla bug 1784201, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.5.0) matches configured target release for branch (4.5.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 1784201: lib/resourcemerge: set AdditionalTrustBundle

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.

[runcom]

cc @danehans

[runcom]

Tested on a cluster, working as expected now, kube-controller-manager is stuck at Available=True,Progressing=True,Degraded=True which looks totally unrelated to this as all other operators are doing just fine after the proxy rollout. This patch might have exposed a bug there (or it's just slow rn) or since my test uses 4.5.latest something else is going on. Let's see if tests pass here also.

[runcom]

/test e2e-proxy

[openshift-ci-robot]

@runcom: The specified target(s) for /test were not found.
The following commands are available to trigger jobs:

• /test e2e-aws
• /test e2e-aws-disruptive
• /test e2e-aws-scaleup-rhel7
• /test e2e-gcp-op
• /test e2e-gcp-upgrade
• /test e2e-metal-ipi
• /test e2e-openstack
• /test e2e-ovirt
• /test e2e-vsphere
• /test images
• /test unit
• /test verify

Use /test all to run all jobs.

In response to this:

/test e2e-proxy

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.

[runcom]

@runcom: The specified target(s) for /test were not found.
The following commands are available to trigger jobs:

right.... we need to enable that perhaps - this change is so tiny it's clear it's not affecting that tho 🤷‍♂️

[runcom]

/skip

[danehans]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danehans, runcom

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 [runcom]

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

[openshift-bot]

/retest

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

[runcom]

/skip
/refresh

[openshift-ci-robot]

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

Test name	Commit	Details	Rerun command
ci/prow/e2e-aws-scaleup-rhel7	a52b1f6	link	/test e2e-aws-scaleup-rhel7
ci/prow/e2e-metal-ipi	a52b1f6	link	/test e2e-metal-ipi

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

[runcom]

/skip

[openshift-bot]

/retest

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

[openshift-ci-robot]

@runcom: All pull requests linked via external trackers have merged: openshift/machine-config-operator#1714. Bugzilla bug 1784201 has been moved to the MODIFIED state.

In response to this:

Bug 1784201: lib/resourcemerge: set AdditionalTrustBundle

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.

[runcom]

/cherry-pick release-4.4

[openshift-cherrypick-robot]

@runcom: new pull request created: #1843

In response to this:

/cherry-pick release-4.4

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.