8000 Make `striker-check-power` and `striker-boot-machine` more resilient to bad `host_ipmi` data · Issue #874 · ClusterLabs/anvil · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Make striker-check-power and striker-boot-machine more resilient to bad host_ipmi data #874

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
digimer opened this issue Mar 20, 2025 · 0 comments
Open

Make striker-check-power and striker-boot-machine more resilient to bad host_ipmi data #874

digimer opened this issue Mar 20, 2025 · 0 comments
Assignees
@digimer
Labels
priority normal normal priority
Milestone
3.2 Beta

Comments

@digimer
Copy link
Member
digimer commented Mar 20, 2025

In some cases, the hosts -> host_ipmi can get cleared. When this happens, check the history schema for past known host_ipmi data and see if it works. If so, update the hosts table and proceed.
@digimer digimer added the priority normal normal priority label Mar 20, 2025
@digimer digimer self-assigned this Mar 20, 2025
digimer pushed a commit that referenced this issue Mar 20, 2025
@digimer-bot
Fixed issue #874; Check for old host_ipmi data
a7c85d9 
Signed-off-by: Madison Kelly <mkelly@alteeve.com>
@digimer digimer mentioned this issue Mar 20, 2025
Merged
digimer pushed a commit that referenced this issue Mar 20, 2025
@digimer-bot
Fixed issue #874; Check for old host_ipmi data
71fd003 
Signed-off-by: Madison Kelly <mkelly@alteeve.com>
@digimer digimer added this to the 3.2 Beta milestone May 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@digimer digimer

Labels
priority normal normal priority
Projects
None yet
Milestone
3.2 Beta
Development

No branches or pull requests
1 participant
@digimer
0