Skip to content

[release-4.20] OCPBUGS-67017: ABI UI should have Tech Preview badge instead of Dev Preview#3296

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:release-4.20from
ElayAharoni:backport-pr-420
Dec 9, 2025
Merged

[release-4.20] OCPBUGS-67017: ABI UI should have Tech Preview badge instead of Dev Preview#3296
openshift-merge-bot[bot] merged 1 commit intoopenshift-assisted:release-4.20from
ElayAharoni:backport-pr-420

Conversation

@ElayAharoni
Copy link
Contributor

No description provided.

Signed-off-by: Elay Aharoni <elayaha@gmail.com>
@openshift-ci openshift-ci bot requested review from batzionb and celdrake December 9, 2025 12:51
@coderabbitai
Copy link

coderabbitai bot commented Dec 9, 2025

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.

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

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Dec 9, 2025
@ElayAharoni ElayAharoni requested review from rawagner and removed request for batzionb and celdrake December 9, 2025 12:51
@ElayAharoni ElayAharoni changed the title [backport 4.20] Adding TechPreview Budge for Assisted installer and agent [release-4.20] Adding TechPreview Budge for Assisted installer and agent Dec 9, 2025
@ElayAharoni ElayAharoni changed the title [release-4.20] Adding TechPreview Budge for Assisted installer and agent [release-4.20] OCPBUGS-67017: ABI UI should have Tech Preview badge instead of Dev Preview Dec 9, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Dec 9, 2025
@openshift-ci-robot
Copy link

@ElayAharoni: This pull request references Jira Issue OCPBUGS-67017, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-67017 to depend on a bug targeting a version in 4.21.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

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.

@rawagner
Copy link
Member

rawagner commented Dec 9, 2025

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 9, 2025

@rawagner: This pull request references Jira Issue OCPBUGS-67017, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • dependent bug AGENT-1388 is not in the required OCPBUGS project

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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.

@rawagner
Copy link
Member

rawagner commented Dec 9, 2025

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 9, 2025

@rawagner: This pull request references Jira Issue OCPBUGS-67017, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • dependent bug AGENT-1388 is not in the required OCPBUGS project

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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.

@rawagner
Copy link
Member

rawagner commented Dec 9, 2025

/jira refresh

@openshift-ci-robot
Copy link

@rawagner: This pull request references Jira Issue OCPBUGS-67017, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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.

@rawagner
Copy link
Member

rawagner commented Dec 9, 2025

/jira refresh

@openshift-ci-robot
Copy link

@rawagner: This pull request references Jira Issue OCPBUGS-67017, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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.

@rawagner
Copy link
Member

rawagner commented Dec 9, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Dec 9, 2025
@openshift-ci-robot
Copy link

@rawagner: This pull request references Jira Issue OCPBUGS-67017, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.z) matches configured target version for branch (4.20.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-67018 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-67018 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (mburman@redhat.com), skipping review request.

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.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Dec 9, 2025
@rawagner
Copy link
Member

rawagner commented Dec 9, 2025

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 9, 2025
@openshift-ci
Copy link

openshift-ci bot commented Dec 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ElayAharoni, rawagner

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 Dec 9, 2025
@bfournie
Copy link
Contributor

bfournie commented Dec 9, 2025

/label backport-risk-assessed

@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 Dec 9, 2025
@pawanpinjarkar
Copy link
Contributor

/verified by @ElayAharoni by running the UI locally and also the results are documented in the original PR #3293

@openshift-ci-robot
Copy link

@pawanpinjarkar: This PR has been marked as verified by @ElayAharoni by running the UI locally and also the results are documented in the original PR https://github.com/openshift-assisted/assisted-installer-ui/pull/3293.

Details

In response to this:

/verified by @ElayAharoni by running the UI locally and also the results are documented in the original PR #3293

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-merge-bot openshift-merge-bot bot merged commit 8c6aaeb into openshift-assisted:release-4.20 Dec 9, 2025
4 checks passed
@openshift-ci-robot
Copy link

@ElayAharoni: Jira Issue Verification Checks: Jira Issue OCPBUGS-67017
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-67017 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

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.

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. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. verified

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants