Skip to content

SREP-3640: add dry run option and link to logs to output for CAD run …#846

Open
rolandmkunkel wants to merge 1 commit intoopenshift:masterfrom
rolandmkunkel:SREP-3640-add-dry-run-and-link-to-logs
Open

SREP-3640: add dry run option and link to logs to output for CAD run …#846
rolandmkunkel wants to merge 1 commit intoopenshift:masterfrom
rolandmkunkel:SREP-3640-add-dry-run-and-link-to-logs

Conversation

@rolandmkunkel
Copy link
Contributor

…command

  • Added --dry-run flag to the osdctl cluster cad run command, allowing users to test investigations without creating backplane reports
    
  • Enhanced output to include a direct Grafana link to view TaskRun pod logs for troubleshooting
    

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 17, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 17, 2026

@rolandmkunkel: This pull request references SREP-3640 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

…command

  • Added --dry-run flag to the osdctl cluster cad run command, allowing users to test investigations without creating backplane reports
    
  • Enhanced output to include a direct Grafana link to view TaskRun pod logs for troubleshooting
    

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-ci openshift-ci bot requested review from Tafhim and petrkotas February 17, 2026 14:16
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 17, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rolandmkunkel

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 17, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 17, 2026

@rolandmkunkel: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments