search

openstack-k8s-operators / openstack-operator

Meta Operator for OpenStack
https://openstack-k8s-operators.github.io/openstack-operator/
Apache License 2.0
27 stars 76 forks source link

[WIP] Moving to 1.21 #886

Closed jpodivin closed 3 months ago

openshift-ci[bot] commented 3 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jpodivin

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: - ~~[OWNERS](https://github.com/openstack-k8s-operators/openstack-operator/blob/main/OWNERS)~~ [jpodivin] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
softwarefactory-project-zuul[bot] commented 3 months ago

Merge Failed.

This change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset.

stuggi commented 3 months ago

is this something we intend to do before GA? iirc last time we discussed that in the weekly sync call it was a post GA task, or has this changed?

softwarefactory-project-zuul[bot] commented 3 months ago

Build failed (check pipeline). Post recheck (without leading slash) to rerun all jobs. Make sure the failure cause has been resolved before you rerun jobs.

https://review.rdoproject.org/zuul/buildset/61293a5f89244a07a1b171f47b81ff19

:heavy_check_mark: openstack-k8s-operators-content-provider SUCCESS in 3h 13m 01s :heavy_check_mark: podified-multinode-edpm-deployment-crc SUCCESS in 1h 19m 55s :heavy_check_mark: cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 17m 08s :heavy_check_mark: cifmw-data-plane-adoption-osp-17-to-extracted-crc SUCCESS in 2h 39m 27s :x: openstack-operator-tempest-multinode POST_FAILURE in 1h 59m 10s

openshift-ci[bot] commented 3 months ago

@jpodivin: The following test 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/openstack-operator-build-deploy-kuttl d9fafc435891a99d3fbfc7eb5be4ecc6a550b094 link true /test openstack-operator-build-deploy-kuttl

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
softwarefactory-project-zuul[bot] commented 3 months ago

Build failed (check pipeline). Post recheck (without leading slash) to rerun all jobs. Make sure the failure cause has been resolved before you rerun jobs.

https://review.rdoproject.org/zuul/buildset/02fc45d80b6646b0b6b2e6bd4d70cc2a

:heavy_check_mark: openstack-k8s-operators-content-provider SUCCESS in 2h 22m 26s :heavy_check_mark: podified-multinode-edpm-deployment-crc SUCCESS in 1h 18m 36s :heavy_check_mark: cifmw-crc-podified-edpm-baremetal SUCCESS in 1h 13m 07s :x: cifmw-data-plane-adoption-osp-17-to-extracted-crc NODE_FAILURE Node request 099-0007393892 failed in 0s :heavy_check_mark: openstack-operator-tempest-multinode SUCCESS in 2h 04m 18s

bshephar commented 3 months ago

is this something we intend to do before GA? iirc last time we discussed that in the weekly sync call it was a post GA task, or has this changed?

I think we're still aiming for post GA. There's a bunch of supporting work that needs to be done, so there's probably value in capturing where CI fails with this and recording what needs to happen to get it all passing.

I see it's been opened with [WIP], probably for that very reason. We can probably just mark this as draft once we've captured the CI failures.

stuggi commented 3 months ago

is this something we intend to do before GA? iirc last time we discussed that in the weekly sync call it was a post GA task, or has this changed?

I think we're still aiming for post GA. There's a bunch of supporting work that needs to be done, so there's probably value in capturing where CI fails with this and recording what needs to happen to get it all passing.

I see it's been opened with [WIP], probably for that very reason. We can probably just mark this as draft once we've captured the CI failures.

when I looked/commented it did not have the [WIP], thanks for adding it!

jpodivin commented 3 months ago

is this something we intend to do before GA? iirc last time we discussed that in the weekly sync call it was a post GA task, or has this changed?

I think we're still aiming for post GA. There's a bunch of supporting work that needs to be done, so there's probably value in capturing where CI fails with this and recording what needs to happen to get it all passing. I see it's been opened with [WIP], probably for that very reason. We can probably just mark this as draft once we've captured the CI failures.

when I looked/commented it did not have the [WIP], thanks for adding it!

That's on me. I forgot to put it there when I opened it. Sorry.

bshephar commented 3 months ago

/recheck