Skip to content

Conversation

msherman64
Copy link
Contributor

Workaround for nodes getting stuck in "bad" states until restart of ironic conductor, as well as recovery from network-related errors.

LP: https://bugs.launchpad.net/ironic/+bug/2054594 ironic uses a 32 character DB column for user_id, which is too short for the 64 character ids returned by keystone with federated login

the real fix is a db migration, but that is hugely painful to try and backport from 2024.1. Instead, just diable the node_history feature, which seems to be the only thing in ironic writing 64 character IDs.

Revert after upgrading to 2024.1.

Workaround for nodes getting stuck in "bad" states until restart of
ironic conductor, as well as recovery from network-related errors.

LP: https://bugs.launchpad.net/ironic/+bug/2054594
ironic uses a 32 character DB column for user_id, which is too short
for the 64 character ids returned by keystone with federated login

the real fix is a db migration, but that is hugely painful to try and
backport from 2024.1. Instead, just diable the node_history feature,
which seems to be the only thing in ironic writing 64 character IDs.

Revert after upgrading to 2024.1.
Copy link
Member

@codyhammock codyhammock left a comment

Choose a reason for hiding this comment

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

No notes

@msherman64 msherman64 merged commit cd1cc4a into stable/2023.1 Apr 29, 2025
1 check passed
@msherman64 msherman64 deleted the fix/ironic_node_history branch April 29, 2025 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants