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

Initialization error if hostname is not resolvable #540

Open
paulomach opened this issue Dec 12, 2024 · 2 comments
Open

Initialization error if hostname is not resolvable #540

paulomach opened this issue Dec 12, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@paulomach
Copy link
Contributor

Steps to reproduce

In a microk8s env, misconfigure coredns to a non reachable DNS, e.g.:

kubectl edit configmap/coredns -n kube-system

replace DNS . to some valid but non reachable ipv4 address.

Deploy mysql-k8s.

Expected behavior

Once DNS is edited back to valid value, mysql-k8s is able to proper initialize.

Actual behavior

Initialization procedure is not idempotent for this case, rendering the mysql data_dir dirty, which blocks the charm

@paulomach paulomach added the bug Something isn't working label Dec 12, 2024
Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-6212.

This message was autogenerated

Copy link

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/DPE-6213.

This message was autogenerated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant