Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
0.4.0
-
None
Description
This was noticed by elek while deploying Ozone on Kubernetes based environment.
When the datanode ip address change on restart, the Datanode details cease to be correct for the datanode. and this prevents the cluster from functioning after a restart.
Attachments
Issue Links
- is a child of
-
HDDS-6438 Support Ozone to run as a service within Kubernetes
- Open