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
According to this PR (#7316), you must stop/disable the systemd-resolved service to run CRC with OCP 4.15. The issue is that minikube cannot start after executing that command:
π minikube v1.32.0 on Fedora 39
β¨ Using the kvm2 driver based on existing profile
π Starting control plane node minikube in cluster minikube
π Restarting existing kvm2 VM for "minikube" ...
:face_palm: StartHost failed, but will try again: driver start: ensuring active networks: starting network default: virError(Code=1, Domain=0, Message='internal error: Network is already in use by interface virbr0')
π Restarting existing kvm2 VM for "minikube" ...
πΏ Failed to start kvm2 VM. Running "minikube delete" may fix it: driver start: ensuring active networks: starting network default: virError(Code=1, Domain=0, Message='internal error: Network is already in use by interface virbr0')
β Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: driver start: ensuring active networks: starting network default: virError(Code=1, Domain=0, Message='internal error: Network is already in use by interface virbr0')
If you enable the systemd-resolved again and reboot your machine, minikube is able to start without any issue
Expected Behavior
I think it is better to revert that PR partially and come back to OCP 4.14 until CRC fixes the systemd-resolved issue (crc-org/crc#4143)
What are the steps to reproduce this bug?
Stop/disable the systemd-resolved service
Start minikube cluster
The text was updated successfully, but these errors were encountered:
Describe the bug
According to this PR (#7316), you must stop/disable the systemd-resolved service to run CRC with OCP 4.15. The issue is that minikube cannot start after executing that command:
π minikube v1.32.0 on Fedora 39
β¨ Using the kvm2 driver based on existing profile
π Starting control plane node minikube in cluster minikube
π Restarting existing kvm2 VM for "minikube" ...
:face_palm: StartHost failed, but will try again: driver start: ensuring active networks: starting network default: virError(Code=1, Domain=0, Message='internal error: Network is already in use by interface virbr0')
π Restarting existing kvm2 VM for "minikube" ...
πΏ Failed to start kvm2 VM. Running "minikube delete" may fix it: driver start: ensuring active networks: starting network default: virError(Code=1, Domain=0, Message='internal error: Network is already in use by interface virbr0')
β Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: driver start: ensuring active networks: starting network default: virError(Code=1, Domain=0, Message='internal error: Network is already in use by interface virbr0')
If you enable the systemd-resolved again and reboot your machine, minikube is able to start without any issue
Expected Behavior
I think it is better to revert that PR partially and come back to OCP 4.14 until CRC fixes the systemd-resolved issue (crc-org/crc#4143)
What are the steps to reproduce this bug?
The text was updated successfully, but these errors were encountered: