You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is your environment(Kubernetes version, Fluid version, etc.) 36e9634
Describe the bug
DataLoad fails to launch after creating two types of Runtime CR sharing the same name. DataLoad's event shows that dataset-controller thinks the runtime is not ready.
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal RuntimeNotReady 7s (x12 over 3m47s) DataLoad Bounded accelerate runtime not ready
By checking logs of the dataset-controller, it is like:
It uses JindoRuntime's health checker to decide whether the runtime is ready, but I'm running a JuiceFSRuntime sharing the same name with a JindoRuntime deleted a few moments ago.
What you expect to happen:
DataLoad launches.
How to reproduce it
create a Dataset & JindoRuntime
create a DataLoad, and it will work well.
delete the Dataset & JindoRuntime
create a Dataset & JuiceFSRuntime with same name as the ones created before
create a DataLoad, DataLoad fails to launch
Additional Information
The text was updated successfully, but these errors were encountered:
What is your environment(Kubernetes version, Fluid version, etc.)
36e9634
Describe the bug
DataLoad fails to launch after creating two types of Runtime CR sharing the same name. DataLoad's event shows that dataset-controller thinks the runtime is not ready.
By checking logs of the dataset-controller, it is like:
It uses JindoRuntime's health checker to decide whether the runtime is ready, but I'm running a JuiceFSRuntime sharing the same name with a JindoRuntime deleted a few moments ago.
What you expect to happen:
DataLoad launches.
How to reproduce it
Additional Information
The text was updated successfully, but these errors were encountered: