origin
origin copied to clipboard
openshift
[release-4.17] OCPBUGS-38835: Try also user CA for getting openshift-tests image
This is an automated cherry-pick of #28990
/assign tiraboschi
@openshift-cherrypick-robot: Jira Issue OCPBUGS-38792 has been cloned as Jira Issue OCPBUGS-38835. Will retitle bug to link to clone. /retitle [release-4.17] OCPBUGS-38835: Try also user CA for getting openshift-tests image
In response to this:
This is an automated cherry-pick of #28990
/assign tiraboschi
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-cherrypick-robot: This pull request references Jira Issue OCPBUGS-38835, which is invalid:
- release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
- expected dependent Jira Issue OCPBUGS-38792 to target a version in 4.18.0, but it targets "4.18.z" instead
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
This is an automated cherry-pick of #28990
/assign tiraboschi
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.
@tiraboschi: This pull request references Jira Issue OCPBUGS-38835, which is invalid:
- release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
- expected dependent Jira Issue OCPBUGS-38792 to target a version in 4.18.0, but it targets "4.18.z" instead
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
/jira refresh
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-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-aws-ovn-ipsec-serial | 737605385dba1938b9c415ad3c2aad049c51de6c | link | false | /test e2e-aws-ovn-ipsec-serial |
| ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 | 737605385dba1938b9c415ad3c2aad049c51de6c | link | false | /test e2e-vsphere-ovn-dualstack-primaryv6 |
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-sigs/prow repository. I understand the commands that are listed here.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@tiraboschi: This pull request references Jira Issue OCPBUGS-38835, which is invalid:
- release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
/jira refresh
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.
@tiraboschi: This pull request references Jira Issue OCPBUGS-38835, which is valid. The bug has been moved to the POST state.
7 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.17.0) matches configured target version for branch (4.17.0)
- bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
- release note type set to "Release Note Not Required"
- dependent bug Jira Issue OCPBUGS-38792 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
- dependent Jira Issue OCPBUGS-38792 targets the "4.18.0" version, which is one of the valid target versions: 4.18.0
- bug has dependents
In response to this:
/jira refresh
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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: davidvossel, openshift-cherrypick-robot, xueqzhan
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [xueqzhan]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@jupierce @deads2k can you please take a look for backport-risk-assessed?
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
We have some Hypershift 4.17 CI jobs requires this PR to get passed.
{
s: "unable to determine openshift-tests image oc wrapper with cluster ps: Error running /usr/bin/oc adm release info virthost.xxx.xxx.xxx.org:5000/localimages/local-release-image@sha256:74bf8863820544ffb4b189eea586e6c03d169b0f5117868c723235f1a08faafb --image-for=tests --registry-config /tmp/image-pull-secret2700026741:\nStdOut>\nerror: unable to read image virthost.xxx.xxx.xxx.org:5000/localimages/local-release-image@sha256:74bf8863820544ffb4b189eea586e6c03d169b0f5117868c723235f1a08faafb: Get \"https://virthost.xxx.xxx.xxx.org5000/v2/\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nStdErr>\nerror: unable to read image virthost.xxx.xxx.xxx.org:5000/localimages/local-release-image@sha256:74bf8863820544ffb4b189eea586e6c03d169b0f5117868c723235f1a08faafb: Get \"https://virthost.xxx.xxx.xxx.org:5000/v2/\": tls: failed to verify certificate: x509: certificate signed by unknown authority\nexit status 1\n",
}
occurred
/retest-required
Remaining retests: 0 against base HEAD 73c604144fd0ddfcd98205ca9ce64453a7205096 and 2 for PR HEAD 737605385dba1938b9c415ad3c2aad049c51de6c in total
@openshift-cherrypick-robot: Jira Issue OCPBUGS-38835: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-38835 has been moved to the MODIFIED state.
In response to this:
This is an automated cherry-pick of #28990
/assign tiraboschi
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.
[ART PR BUILD NOTIFIER]
Distgit: openshift-enterprise-tests This PR has been included in build openshift-enterprise-tests-container-v4.17.0-202503042036.p0.g0525d4a.assembly.stream.el9. All builds following this will include this PR.
@wangke19: new pull request created: #29578
In response to this:
/cherry-pick release-4.16
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-sigs/prow repository.