Skip to content

[release-4.19] USHIFT-6692: Updating jira with atlassian#6363

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.19from
kasturinarra:local-4.19
Mar 17, 2026
Merged

[release-4.19] USHIFT-6692: Updating jira with atlassian#6363
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.19from
kasturinarra:local-4.19

Conversation

@kasturinarra
Copy link
Contributor

@coderabbitai
Copy link

coderabbitai bot commented Mar 16, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 4b318f8b-e9f0-4641-b7c4-83b48bc6d60b

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
📝 Coding Plan
  • Generate coding plan for human review comments

Comment @coderabbitai help to get the list of available commands and usage tips.

@kasturinarra
Copy link
Contributor Author

@agullon could you please help review ? thanks !!

@openshift-ci openshift-ci bot requested review from agullon and vanhalenar March 16, 2026 17:49
@kasturinarra kasturinarra changed the title Updating jira with atlassian USHIFT-6692: Updating jira with atlassian Mar 16, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 16, 2026

@kasturinarra: This pull request references USHIFT-6692 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 task to target the "4.19.z" version, but no target version was set.

Details

In response to this:

Manual cherry pick of https://github.com/openshift/microshift/pull/6359/changes

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 16, 2026
@kasturinarra
Copy link
Contributor Author

/retest

@kasturinarra kasturinarra marked this pull request as draft March 17, 2026 09:20
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 17, 2026
@kasturinarra kasturinarra marked this pull request as ready for review March 17, 2026 09:20
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 17, 2026
@openshift-ci openshift-ci bot requested a review from pmtk March 17, 2026 09:21
@agullon
Copy link
Contributor

agullon commented Mar 17, 2026

/rename "[release-4.19] USHIFT-6692: Updating jira with atlassian"

@agullon
Copy link
Contributor

agullon commented Mar 17, 2026

/lgtm

@agullon
Copy link
Contributor

agullon commented Mar 17, 2026

/override ci/prow/e2e-aws-tests-arm
/override ci/prow/e2e-aws-tests

@kasturinarra kasturinarra changed the title USHIFT-6692: Updating jira with atlassian [release-4.19] USHIFT-6692: Updating jira with atlassian Mar 17, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 17, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 17, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, kasturinarra

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 Mar 17, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 17, 2026

@agullon: Overrode contexts on behalf of agullon: ci/prow/e2e-aws-tests, ci/prow/e2e-aws-tests-arm

Details

In response to this:

/override ci/prow/e2e-aws-tests-arm
/override ci/prow/e2e-aws-tests

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 17, 2026

@kasturinarra: 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-tests-arm 6ac0320 link true /test e2e-aws-tests-arm
ci/prow/e2e-aws-tests 6ac0320 link true /test e2e-aws-tests

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.

@agullon
Copy link
Contributor

agullon commented Mar 17, 2026

/label backport-risk-assessed
/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 17, 2026

@agullon: This pull request references USHIFT-6692 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 task to target the "4.19.z" version, but no target version was set.

Details

In response to this:

/label backport-risk-assessed
/jira refresh

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 added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 17, 2026
@agullon
Copy link
Contributor

agullon commented Mar 17, 2026

/verified by @agullon

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 17, 2026
@openshift-ci-robot
Copy link

@agullon: This PR has been marked as verified by @agullon.

Details

In response to this:

/verified by @agullon

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.

@agullon
Copy link
Contributor

agullon commented Mar 17, 2026

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 17, 2026

@agullon: This pull request references USHIFT-6692 which is a valid jira issue.

Details

In response to this:

/jira refresh

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.

@agullon
Copy link
Contributor

agullon commented Mar 17, 2026

/label jira/valid-bug

@openshift-ci openshift-ci bot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Mar 17, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit 1562ea8 into openshift:release-4.19 Mar 17, 2026
11 checks passed
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants