Closed Patryk-Stefanski closed 1 month ago
@Patryk-Stefanski: This pull request references HOSTEDCP-1791 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 bug to target the "4.17.0" version, but no target version was set.
/retest-required
@Patryk-Stefanski: The /retest
command does not accept any targets.
The following commands are available to trigger required jobs:
/test e2e-aws
/test e2e-kubevirt-aws-ovn-reduced
/test images
/test unit
/test verify
The following commands are available to trigger optional jobs:
/test e2e-aks
/test e2e-aws-metrics
/test e2e-azure
/test e2e-azure-ovn-conformance
/test e2e-conformance
/test e2e-ibmcloud-iks
/test e2e-ibmcloud-roks
/test e2e-kubevirt-aws-ovn
/test e2e-kubevirt-azure-ovn
/test e2e-kubevirt-metal-conformance
/test e2e-openstack
/test okd-scos-images
Use /test all
to run the following jobs that were automatically triggered:
pull-ci-openshift-hypershift-main-e2e-aks
pull-ci-openshift-hypershift-main-e2e-aws
pull-ci-openshift-hypershift-main-e2e-azure
pull-ci-openshift-hypershift-main-e2e-kubevirt-aws-ovn-reduced
pull-ci-openshift-hypershift-main-images
pull-ci-openshift-hypershift-main-unit
pull-ci-openshift-hypershift-main-verify
/test e2e-aks
/test e2e-azure
/lgtm
Please default to not rendering sensitive info once the relevant jobs have been updated. fwiw this won't be an issue when moving to msi /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: enxebre, Patryk-Stefanski
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/lgtm
/lgtm
/retest-required
Remaining retests: 0 against base HEAD 933f5f2810a6f6ee3704716e9d0a77107edf7d3e and 2 for PR HEAD 13c4722ce8f1e14fdf6d99772d848de056fdf5ed in total
/test all
/test all
/retest
for konflux
/retest-required
/retest
/lgtm
Please default to not rendering sensitive info ...
@enxebre wouldn't this break every consumer of --render
that uses the output as a self-contained mechanism to install HostedClusters
on a management plane?
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)
format, where issue_number might be a GitHub issue, or a Jira story: Fixes #Checklist