Closed mateusoliveira43 closed 4 weeks ago
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
Test images available! 🧪🚀 To test operator with them, run
operator-sdk run bundle \
quay.io/pelorus/rc-pelorus-operator-bundle:vpr1137-1b3c69d \
--namespace test-pelorus-operator
To clean up environment afterwards, run
operator-sdk cleanup pelorus-operator --namespace test-pelorus-operator
@mateusoliveira43: The following test 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/4.13-e2e-openshift | 3c99aced27a82b7c0b884cc05699441370901911 | link | true | /test 4.13-e2e-openshift |
Full PR test history. Your PR dashboard.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: etsauer
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Linked Issues
related to #1134
Pelorus Operator 0.0.9 release
Release for version 0.0.9 of Pelorus Operator.
How changes were made
To create this PR, https://pelorus.readthedocs.io/en/latest/Development/#create-a-release was followed and run
./scripts/update_projects_version.py -f -l patch patch
Testing Instructions
To test the release candidate, run the command the CI posted in this PR.
Also, read, review and update release body marked as drafted.