Skip to content
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.

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

Improve dataflow when rendering config file. #178

Merged
merged 1 commit into from
Mar 1, 2024

Conversation

chanchiwai-ray
Copy link
Contributor

@chanchiwai-ray chanchiwai-ray commented Feb 29, 2024

Currently, service.ExporterTemplate.render_config determine REDFISH_ENABLE (jinja2) variable by get_hw_tool_white_list, but the same information is also retrieved in charm.HardwareObserverCharm._get_redfish_creds via bmc_hw_verifier. If the two does not match (e.g. bmc_hw_verifier determines it redfish is not available but get_hw_tool_white_list determines that redfish is available), it will cause issue mentioned in #130.

This PR tries to remove the possibility that the two information is inconsistent by relying on single source of truth. Note, it might not solve #130, since the root cause is not clear, and it's not reproducible from my environement.

Copy link
Contributor

@dashmage dashmage left a comment

Choose a reason for hiding this comment

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

LGTM 🚀 Good thing you added the warning log so we'll atleast be notified if there's some inconsistent behaviour while checking if redfish is available.

Copy link
Contributor

@rgildein rgildein left a comment

Choose a reason for hiding this comment

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

LGTM

src/service.py Show resolved Hide resolved
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.

Redfish credentials update failed
3 participants