Skip to content

Conversation

ggiguash
Copy link
Contributor

@ggiguash ggiguash commented Mar 9, 2025

We expect RHEL documentation to cover this process in great detail.
The current PR attempts to provide a minimal MicroShift-specific context. The mentioned workaround is currently tested / used in MicroShift CI.

@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 9, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 9, 2025

@ggiguash: This pull request references USHIFT-3839 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.19.0" version, but no target version was set.

In response to this:

We expect RHEL documentation to cover this process in great detail.
The current PR attempts to provide a minimal MicroShift-specific context. The mentioned workaround is currently tested / used in MicroShift CI.

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 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 9, 2025
Copy link
Contributor

openshift-ci bot commented Mar 9, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 9, 2025
@ggiguash ggiguash force-pushed the rpm-ostree-to-bootc-docs branch from 9f12ac3 to e7a3c77 Compare March 9, 2025 11:11
@ggiguash ggiguash marked this pull request as ready for review March 11, 2025 06:29
@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 11, 2025
@openshift-ci openshift-ci bot requested review from jerpeter1 and vanhalenar March 11, 2025 06:30
@ggiguash
Copy link
Contributor Author

PIP errors. Retrying verify test.
/test verify

@ggiguash ggiguash closed this Mar 12, 2025
@ggiguash ggiguash deleted the rpm-ostree-to-bootc-docs branch March 12, 2025 06:49
@ggiguash ggiguash restored the rpm-ostree-to-bootc-docs branch March 12, 2025 14:41
@ggiguash ggiguash reopened this Mar 12, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 12, 2025

@ggiguash: This pull request references USHIFT-3839 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.19.0" version, but no target version was set.

In response to this:

We expect RHEL documentation to cover this process in great detail.
The current PR attempts to provide a minimal MicroShift-specific context. The mentioned workaround is currently tested / used in MicroShift CI.

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.

@pmtk
Copy link
Member

pmtk commented Mar 12, 2025

/lgtm

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

openshift-ci bot commented Mar 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pmtk

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

The pull request process is described here

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

Copy link
Contributor

openshift-ci bot commented Mar 12, 2025

@ggiguash: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 955c545 into openshift:main Mar 12, 2025
5 checks passed
@ggiguash ggiguash deleted the rpm-ostree-to-bootc-docs branch March 13, 2025 16:18
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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants