Skip to content

Conversation

@shiftstack-merge-bot
Copy link

No description provided.

EmilienM and others added 5 commits November 22, 2024 11:11
When a floating is created, we need to make sure that
`OpenStackCluster.Spec.DisableExternalNetwork` is not set to `True`.
Otherwise, we'll have a nil pointer error.

* Add a check in `reconcileBastion` to check that external network is
  not disabled before creating the floating IP for the bastion.
* Add a check in `reconcileControlPlaneEndpoint` and
  `reconcileAPIServerLoadBalancer` to check that external
  network is not disabled (alongside the DisableAPIServerFloatingIP
  check) before creating the floating IP for the API server endpoint.
* Add a safeguard in `GetOrCreateFloatingIP` to return a proper error
  (instead of a nil pointer error) when
  `openStackCluster.Status.ExternalNetwork` is nil.
* Add API CEL to check that when DisableExternalNetwork is set and true,
  the bastion (if defined) doesn't have a floating IP defined and also
  that disableAPIServerFloatingIP (when set) is not False.

(cherry picked from commit 5429b4b)
…-0.10-fip

[release-0.10] 🐛 Better checks before creating Floating IPs
If the bastion image is missing or ambiguous, we do not have a bastion.
In that case, we must continue with the deletion or be permanently
stuck.

Signed-off-by: Lennart Jern <[email protected]>
…ot/cherry-pick-2289-to-release-0.10

[release-0.10] 🌱 Automate the release process
@openshift-ci openshift-ci bot requested review from MaysaMacedo and mdbooth December 2, 2024 12:16
@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Dec 2, 2024
@openshift-ci
Copy link

openshift-ci bot commented Dec 2, 2024

Hi @shiftstack-merge-bot[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@EmilienM
Copy link
Member

EmilienM commented Dec 2, 2024

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 2, 2024
@EmilienM
Copy link
Member

EmilienM commented Dec 2, 2024

/lgtm
/approve

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Dec 2, 2024
…ion-deletion-release-0.10

🐛 Fix deletion of cluster when bastion image missing
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Dec 5, 2024
@EmilienM
Copy link
Member

EmilienM commented Dec 5, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 5, 2024
lentzi90 and others added 4 commits December 6, 2024 02:46
This makes it possible to set up a local devstack on libvirt. It is
probably not useful for running the full e2e suite (unless you have a
very beefy PC), but it is enough for development with Tilt.

Signed-off-by: Lennart Jern <[email protected]>
This is an attempt to make it more stable.

Signed-off-by: Lennart Jern <[email protected]>
(cherry picked from commit 5a86c5a)
While we investigate the issues with flatcar images further [1].

[1] https://bugs.launchpad.net/nova/+bug/2091114

Signed-off-by: Stephen Finucane <[email protected]>
(cherry picked from commit 0a28aae)
…ot/cherry-pick-2262-to-release-0.10

[release-0.10] 🌱 Add libvirt resource type for create_devstack.sh + Run devstack on ubuntu 24.04
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Dec 9, 2024
EmilienM and others added 2 commits December 9, 2024 17:51
Configuring the following in devstack:

```
ENABLE_SYSCTL_MEM_TUNING="True"
ENABLE_SYSCTL_NET_TUNING="True"
ENABLE_ZSWAP="True"
```

That tuning is what is done in the `devstack-platform-ubuntu-noble`
job.
Example:
https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_d17/936669/2/check/devstack-platform-ubuntu-noble/d178dad/controller/logs/local_conf.txt
…ot/cherry-pick-2307-to-release-0.10

[release-0.10] 🐛 ci/devstack: host tuning
…orts-tags-release-0.10

🐛 Ensure that existing ports also have correct tags and trunks
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 1, 2025
okozachenko1203 and others added 3 commits May 12, 2025 13:15
…ot/cherry-pick-2541-to-release-0.10

[release-0.10] 🐛 allow switching from filter.name to id of network and subnets in OSC spec
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 15, 2025
@mandre
Copy link
Member

mandre commented Jun 23, 2025

/retest

@mandre
Copy link
Member

mandre commented Jun 23, 2025

It's currently failing to build because this commit uses the slices package which was removed downstream in fe2962b665bc74d64710257a288d76bcfd95ff92 for go 1.21 compatibility.

It seems like the slices package in go 1.21 has the Equal and Sort functions so we should be able to resolve the build failure by re-adding the import slices to pkg/cloud/services/networking/port.go.

New commits were added that depend on slices functions available in go
1.21.
@mandre
Copy link
Member

mandre commented Jun 23, 2025

/lifecycle frozen

@openshift-ci
Copy link

openshift-ci bot commented Jun 23, 2025

@mandre: The lifecycle/frozen label cannot be applied to Pull Requests.

In response to this:

/lifecycle frozen

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.

@mandre
Copy link
Member

mandre commented Jun 23, 2025

/remove-lifecycle rotten

@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jun 23, 2025
Copy link
Member

@mandre mandre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve
/label backport-risk-assessed

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. lgtm Indicates that a PR is ready to be merged. labels Jun 23, 2025
@openshift-ci
Copy link

openshift-ci bot commented Jun 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: EmilienM, 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
Copy link

openshift-ci bot commented Jun 23, 2025

@shiftstack-merge-bot[bot]: 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 5593c5f into openshift:release-4.17 Jun 23, 2025
7 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the merge-bot-release-4.17 branch June 23, 2025 14:55
@openshift-ci-robot
Copy link

@shiftstack-merge-bot[bot]: Jira Issue OCPBUGS-44455: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-44455 has been moved to the MODIFIED state.

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.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: openstack-cluster-api-controllers
This PR has been included in build openstack-cluster-api-controllers-container-v4.17.0-202506231605.p0.g5593c5f.assembly.stream.el9.
All builds following this will include this PR.

@openshift-merge-robot
Copy link

Fix included in accepted release 4.17.0-0.nightly-2025-06-23-191650

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.