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
When following the guide on the migration of kubeflow 1.7 to 1.8, the migration is finalized but there is an issue with the argo-operator charm with the message on kubectl logs: time="2024-03-13T09:05:43.392Z" level=fatal msg="Failed to register watch for controller config map: Unauthorized"
This issue lasted for about one hour and then fixed itself, so this might cause maybe some confusion to what is upgrading and perhaps we can improve the recovery of this specific charm?
To Reproduce
Follow the guide on a microk8s deployment and run a migration from juju 2.9 to 3.4.
Environment
Juju/Kubeflow on microk8s.
Relevant Log Output
`time="2024-03-13T09:05:43.392Z" level=fatal msg="Failed to register watch for controller config map: Unauthorized"`
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Bug Description
When following the guide on the migration of kubeflow 1.7 to 1.8, the migration is finalized but there is an issue with the argo-operator charm with the message on kubectl logs:
time="2024-03-13T09:05:43.392Z" level=fatal msg="Failed to register watch for controller config map: Unauthorized"
This issue lasted for about one hour and then fixed itself, so this might cause maybe some confusion to what is upgrading and perhaps we can improve the recovery of this specific charm?
To Reproduce
Follow the guide on a microk8s deployment and run a migration from juju 2.9 to 3.4.
Environment
Juju/Kubeflow on microk8s.
Relevant Log Output
`time="2024-03-13T09:05:43.392Z" level=fatal msg="Failed to register watch for controller config map: Unauthorized" `
Additional Context
No response
The text was updated successfully, but these errors were encountered: