Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OSASINFRA-3368: Revendor CAPO #103

Merged
merged 2 commits into from Feb 13, 2024

Conversation

mandre
Copy link
Member

@mandre mandre commented Feb 8, 2024

Point to the main branch of downstream CAPO, that is tracking
upstream's release-0.9 branch.

Copy link
Contributor

openshift-ci bot commented Feb 8, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mandre

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 8, 2024
@mandre
Copy link
Member Author

mandre commented Feb 8, 2024

Hmm it didn't collect logs
/test e2e-openstack

Point to the main branch of downstream CAPO, that is tracking
upstream's `release-0.9` branch.
@mandre mandre changed the title DNM: testing CAPO 0.9 Revendor CAPO Feb 12, 2024
@mandre
Copy link
Member Author

mandre commented Feb 12, 2024

/retest

2 similar comments
@mandre
Copy link
Member Author

mandre commented Feb 12, 2024

/retest

@mandre
Copy link
Member Author

mandre commented Feb 13, 2024

/retest

@mandre mandre changed the title Revendor CAPO OSASINFRA-3368: Revendor CAPO Feb 13, 2024
@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 13, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 13, 2024

@mandre: This pull request references OSASINFRA-3368 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.0" version, but no target version was set.

In response to this:

Point to the main branch of downstream CAPO, that is tracking
upstream's release-0.9 branch.

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.

@mandre
Copy link
Member Author

mandre commented Feb 13, 2024

/retest

@mandre
Copy link
Member Author

mandre commented Feb 13, 2024

This has passed before with the same code.
/retest

@mandre
Copy link
Member Author

mandre commented Feb 13, 2024

/retest

Copy link
Contributor

openshift-ci bot commented Feb 13, 2024

@mandre: 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/test-infra repository. I understand the commands that are listed here.

@EmilienM
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 13, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 9de6d17 into openshift:master Feb 13, 2024
10 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-machine-api-provider-openstack-container-v4.16.0-202402131839.p0.g9de6d17.assembly.stream.el9 for distgit ose-machine-api-provider-openstack.
All builds following this will include this PR.

@mandre mandre deleted the revendor-capo-0.9 branch February 14, 2024 06:44
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.

None yet

4 participants