ETCD-517: run certsignercontroller for bootstrap render #1186
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@tjungblu: This pull request references ETCD-517 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set. In 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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
openshift-ci
bot
added
the
approved
|
/test e2e-operator |
|
/hold |
openshift-ci
bot
added
do-not-merge/hold
|
/payload 4.16 nightly blocking |
|
@tjungblu: trigger 8 job(s) of type blocking for the nightly release of OCP 4.16
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b46a29a0-bb9d-11ee-86bb-243669c9c991-0 |
|
/retest |
tjungblu
force-pushed
the
installer
branch
2 times, most recently
from
a59ac13
to
6dc03d8
Compare
|
/retest |
|
/payload 4.16 nightly blocking |
|
@tjungblu: trigger 8 job(s) of type blocking for the nightly release of OCP 4.16
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/058a8820-c1cf-11ee-8982-0895265cce0b-0 |
|
there's one failure which is a bit odd, I'll investigate further: |
openshift-merge-robot
added
the
needs-rebase
|
@tjungblu: This pull request references ETCD-517 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set. In 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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-merge-robot
removed
the
needs-rebase
|
/payload 4.16 nightly blocking |
|
@tjungblu: trigger 8 job(s) of type blocking for the nightly release of OCP 4.16
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ade16df0-c5a2-11ee-987a-94cf2e47702c-0 |
|
/test e2e-aws-ovn-single-node |
|
/payload 4.16 nightly blocking |
|
@hasbro17: trigger 8 job(s) of type blocking for the nightly release of OCP 4.16
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/19fd89b0-c9f9-11ee-86fe-82e1a5dd7e74-0 |
|
/payload 4.16 nightly blocking |
|
@tjungblu: trigger 8 job(s) of type blocking for the nightly release of OCP 4.16
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/584cc5b0-ca43-11ee-8f1e-0e62dda891d5-0 |
|
/hold Whenever the blocking payload turns green on those upgrade jobs. Lots of infra failures right now it seems. /lgtm |
openshift-ci
bot
added
do-not-merge/hold
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hasbro17, tjungblu 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:
Approvers can indicate their approval by writing |
|
/payload 4.16 nightly blocking |
|
/retest |
|
@tjungblu: An error was encountered. No known errors were detected, please see the full error message for details. Full error message.
could not check if the user tjungblu is trusted for pull request openshift/cluster-etcd-operator#1186: error checking tjungblu for trust: failed to check if comment came from myself: fetching userdata from GitHub: Get "http://ghproxy/app": dial tcp 172.30.229.2:80: i/o timeout
Please contact an administrator to resolve this issue. |
|
/payload 4.16 nightly blocking |
|
@tjungblu: An error was encountered. No known errors were detected, please see the full error message for details. Full error message.
could not check if the user tjungblu is trusted for pull request openshift/cluster-etcd-operator#1186: error checking tjungblu for trust: failed to check if comment came from myself: fetching userdata from GitHub: Get "http://ghproxy/app": dial tcp 172.30.229.2:80: i/o timeout
Please contact an administrator to resolve this issue. |
|
/payload 4.16 nightly blocking |
|
@tjungblu: trigger 8 job(s) of type blocking for the nightly release of OCP 4.16
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/beaa9d10-ca79-11ee-8e4f-828f98ccd672-0 |
|
/hold cancel The failures in the payloads match the errors in the recent nightly builds, it seems not caused by anything in this PR. |
openshift-ci
bot
removed
the
do-not-merge/hold
|
/retest |
|
/override ci/prow/e2e-gcp-qe-no-capabilities |
|
@tjungblu: Overrode contexts on behalf of tjungblu: ci/prow/e2e-gcp-qe-no-capabilities In 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-gcp-qe-no-capabilities |
|
@tjungblu: Overrode contexts on behalf of tjungblu: ci/prow/e2e-gcp-qe-no-capabilities In 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. |
|
haha this is retest hell |
|
might as well run another payload test if I have to wait for 3h anyway: /payload 4.16 nightly blocking |
|
@tjungblu: trigger 8 job(s) of type blocking for the nightly release of OCP 4.16
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/50e77eb0-cb1e-11ee-8894-e72dd5fbaf6a-0 |
|
[ART PR BUILD NOTIFIER] This PR has been included in build cluster-etcd-operator-container-v4.16.0-202402141610.p0.g0d203dd.assembly.stream.el9 for distgit cluster-etcd-operator. |
No description provided.