Skip to content

ci: add hibiscus release, drop epoxy - #1004

Merged
mandre merged 1 commit into
k-orc:mainfrom
shiftstack:remove-epoxy
Oct 22, 2026
Merged

mandre merged 1 commit into
k-orc:mainfrom
shiftstack:remove-epoxy

Conversation

@winiciusallan

Copy link
Copy Markdown
Member

The new OpenStack Hibiscus release has been launched and, with this, Epoxy is being moved to EOM[1].

[1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/YI657WSHMXS7XXVJLDF7JE4IIITVWBP7/

The new OpenStack Hibiscus release has been launched and, with this, Epoxy is being moved to EOM[1].

[1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/YI657WSHMXS7XXVJLDF7JE4IIITVWBP7/
@github-actions github-actions Bot added the semver:patch No API change label Oct 19, 2026
@winiciusallan

winiciusallan commented Oct 20, 2026 •

Copy link
Copy Markdown
Member Author

Hmm, interesting. Looks like we can't ensure that the masters list returned by the Designate API is the same as declared in the manifest.

             masters:
        +    - 192.0.2.2
             - 192.0.2.1
        -    - 192.0.2.2

    case.go:345: resource DNSZone:kuttl-settled-monkfish-zhcj/dnszone-create-full-secondary: .status.resource.masters: value mismatch, expected: 192.0.2.1 != actual: 192.0.2.2

And indeed, this function uses a generic _find that uses the created_at as the default sort_key. Rather than trying to control the output, I think we can change our tests to verify the status in a different manner -- the state is not differently, it's just the order.

edit: Actually, I think we could sort the status before writing it to have a deterministic behavior.

@mandre mandre left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Would you like to extract the second commit (bug fix) into a separate PR?

@winiciusallan

Copy link
Copy Markdown
Member Author

Would you like to extract the second commit (bug fix) into a separate PR?

Yup. Done in #1005

@mandre
mandre added this pull request to the merge queue Oct 22, 2026
Merged via the queue into k-orc:main with commit b7b7b1d Oct 22, 2026
22 of 23 checks passed
@mandre
mandre deleted the remove-epoxy branch October 22, 2026 07:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

semver:patch No API change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants