TRT-1193: Revert "IR-373: remove node-ca daemon" #899
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@sjenning: This pull request references IR-373 which is a valid jira issue. DetailsIn response to this:
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. |
|
/payload-job periodic-ci-openshift-hypershift-release-4.14-periodics-e2e-aws-ovn-conformance |
|
@sjenning: This pull request references IR-373 which is a valid jira issue. DetailsIn response to this:
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. |
|
@sjenning: trigger 1 job(s) for the /payload-(job|aggregate) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/af838cd0-3c48-11ee-82e4-07dfbfb33df5-0 |
|
@sjenning: This pull request references IR-373 which is a valid jira issue. DetailsIn response to this:
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. |
|
@csrwng found that this is the likely cause openshift/machine-config-operator#3770 Hypershift does not run the MCO and thus nothing is laying down certs for the registry. |
sjenning
changed the title
|
@sjenning: This pull request references TRT-1193 which is a valid jira issue. DetailsIn response to this:
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. |
|
/override ci/prow/e2e-aws-operator |
|
/label approved |
openshift-ci
bot
added
the
approved
|
@dgoodwin: Overrode contexts on behalf of dgoodwin: ci/prow/e2e-aws-operator, ci/prow/e2e-aws-ovn, ci/prow/e2e-aws-ovn-image-registry, ci/prow/e2e-aws-ovn-upgrade, ci/prow/e2e-hypershift DetailsIn response to this:
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. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dgoodwin, sjenning The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
openshift-ci
bot
removed
the
approved
|
/label approved |
openshift-ci
bot
added
approved
|
/override ci/prow/e2e-aws-operator |
|
@dgoodwin: Overrode contexts on behalf of dgoodwin: ci/prow/e2e-aws-operator, ci/prow/e2e-aws-ovn-upgrade DetailsIn response to this:
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. |
|
@sjenning: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
4 participants
Reverts #867
I think Hypershift conformance is breaking on this https://issues.redhat.com/browse/TRT-1193 blocking nightlies
https://testgrid.k8s.io/redhat-hypershift#4.14-aws-ovn-conformance&width=20
Images failing to pull from the local registry during conformance tests.
registrypod logs show lots ofremote error: tls: bad certificatewhere there were none before.