- 
                Notifications
    
You must be signed in to change notification settings  - Fork 205
 
feat: Troubleshooting test failures in CI #3528
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
base: main
Are you sure you want to change the base?
Conversation
| 
           Skipping CI for Draft Pull Request.  | 
    
| 
           [APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. 
Needs approval from an approver in each of these files:
 
      Approvers can indicate their approval by writing   | 
    
| 
           Hey there and thank you for opening this pull request! 👋🏼 We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted. Details:  | 
    
| 
           /ok-to-test  | 
    
| 
           The image is available at:  | 
    
| 
           This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 21 days.  | 
    
| 
           /test e2e-ocp-helm  | 
    
| 
           You are above your monthly Qodo Merge usage quota. For more information, please visit here.  | 
    
| 
           @y-first: The following test failed, say  
 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.  | 
    
| 
           This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 21 days.  | 
    
Description
Testing some failures in RHDH CI related to orchestrator deployment.
Which issue(s) does this PR fix
PR acceptance criteria
Please make sure that the following steps are complete:
How to test changes / Special notes to the reviewer