[release-4.16] OCPEDGE-791: Automate RapiDAST in LVMS

[openshift-cherrypick-robot]

This is an automated cherry-pick of #2178

/assign mmakwana30

[openshift-ci-robot]

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: OCPEDGE-791

Details

In response to this:

This is an automated cherry-pick of #2178

/assign mmakwana30

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.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: ce4b2dba-7fb4-4354-9b14-3c424031d640

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign jeff-roche for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.31%. Comparing base (795891a) to head (31fe3c8).
⚠️ Report is 20 commits behind head on release-4.16.

Additional details and impacted files

@@               Coverage Diff                @@
##           release-4.16    #2736      +/-   ##
================================================
+ Coverage         77.11%   77.31%   +0.19%     
================================================
  Files                28       28              
  Lines              2067     2067              
================================================
+ Hits               1594     1598       +4     
+ Misses              342      340       -2     
+ Partials            131      129       -2     

see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[pacevedom]

/jira refresh
/retest

[openshift-ci-robot]

@pacevedom: This pull request references OCPEDGE-791 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.16.z" version, but no target version was set.

Details

In response to this:

/jira refresh
/retest

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.

[pacevedom]

/retest

[pacevedom]

/retest

[openshift-ci]

@openshift-cherrypick-robot: The following tests 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/e2e-aws-single-node	31fe3c8	link	true	/test e2e-aws-single-node
ci/prow/e2e-aws	31fe3c8	link	true	/test e2e-aws
ci/prow/images	31fe3c8	link	true	/test images
ci/prow/ci-index-lvm-operator-bundle	31fe3c8	link	true	/test ci-index-lvm-operator-bundle

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.