-
Notifications
You must be signed in to change notification settings - Fork 440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
operator digitalai-deploy-operator (v24.3.0) #4779
operator digitalai-deploy-operator (v24.3.0) #4779
Conversation
operator digitalai-deploy-operator (v24.3.0) |
Pipeline SummaryPipeline: operator-hosted-pipeline Tasks
Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/d2074a0bd0406cef6dc0688fa0ab1ee6 ❌ Not mergedPR cannot be merged for the following reasons: TroubleshootingPlease refer to the troubleshooting guide. Run |
Pipeline SummaryPipeline: operator-hosted-pipeline Tasks
Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/4feb5b0a90ccf51b361c7ba9ee1691a5 TroubleshootingPlease refer to the troubleshooting guide. Run |
/pipeline restart operator-hosted-pipeline |
Pipeline SummaryPipeline: operator-hosted-pipeline Tasks
Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/7cc2f82ce36fba8d3e52e7f2ab247615 TroubleshootingPlease refer to the troubleshooting guide. Run |
Pipeline SummaryPipeline: operator-hosted-pipeline Tasks
Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/83f0ede76aeb778c8c92baf2ba3e67ea TroubleshootingPlease refer to the troubleshooting guide. Run |
1d7b244
into
redhat-openshift-ecosystem:main
Pipeline SummaryPipeline: operator-release-pipeline Tasks
Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/925fb1fe67d2d528c82f9205227ccc55 TroubleshootingPlease refer to the troubleshooting guide. Run |
There is nothing that needs to be done for this PR, the below PR was also raised for this issue. The reason this PR shows 0 commits and 0 changes, is due to the force push to the forks main, and two users sharing the same fork. @Murugesan-30795 @shivadigitalai Please only have one PR open at a time, and if you are trying to collaborate, it's best to do so in your own forks and before PR's are raised. Thanks. |
Thanks for the note @acornett21 Yes, we realised the mistake and raised separate PRs for the two operators that we maintain ( #4790 & #4792 ) . Failed to close this PR since requestor went on vacation. Thanks again for taking time to explain it to us |
No description provided.