Update dependency k-orc/openstack-resource-controller to v2.6.0 (main)

Sylva Renovate botrequested to merge
renovate/main-k-orc-openstack-resource-controller-2.x into main

This MR contains the following updates:

Package Update Change
k-orc/openstack-resource-controller minor v2.5.0 -> v2.6.0

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

k-orc/openstack-resource-controller (k-orc/openstack-resource-controller)

v2.6.0

Compare Source

What's Changed

New features
  • Flavor: Added id field for creation
Bug fixes
  • Tightened adoption filters across multiple controllers (AddressScope, FloatingIP, Group, Network, Port, Project, Router, SecurityGroup, ServerGroup, Subnet, Trunk, User) to prevent adopting resources that don't fully match the spec
  • Fixed terminal error classification: use IsRetryable instead of IsConflict so non-HTTP gophercloud errors (e.g., client-side validation failures) are no longer retried indefinitely (Fixes #​241)
  • Treated Neutron quota-exceeded 409 errors as retryable so controllers retry when quota becomes available (Fixes #​667)
  • Fixed port status not updating to ACTIVE after server interface attachment
  • Fixed volume status not updating to in-use after server attachment
Infrastructure improvements
  • Bumped Go to 1.25.11
  • Bumped kuttl to v0.26.0
  • Bumped golang.org/x/net to v0.53.0 and other dependency updates
  • Added CI verification for generate-bundle

New Contributors

Full Changelog: https://github.com/k-orc/openstack-resource-controller/compare/v2.5.0...v2.6.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

  • If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot Sylva instance.

CI configuration couldn't be handle by MR description. A dedicated comment has been posted to control it.

If no checkbox is checked, a default pipeline will be enabled (capm3, or capo if capo label is set)

Merge request reports