Closed edgarhal closed 11 months ago
I`ve found a way to get it working. Instead leting AKSEdge create the aksedgesw-ext vSwitch on Hyper-V, do that yourself and rename the newly vSwitch created from vEthernet(aksedgesw-ext) to just aksedgesw-ext.
Create
Rename
And use the same name as Adapter Name:
Another step that Im doing is shutdown just the Windows node using Stop-AksEdgeNode -NodeType Windows before shutdown the computer or VM if nested VM, Im not sure if this is an essential step, but it`s working fine after all this.
Hi @patrickvargas,
Are you still seeing this issue?
Thanks, Francisco
@fcabrera23, I have to do a normal installation again to check if the issue is still there. Give me sometime and I`ll back to you if the answer. Thanks.
Hi @patrickvargas,
Closing this issue due to inactivity.
Thanks, Francisco
Describe the bug The Windows Node status stays as "NotReady" after restarting the Host machine when deploying a "SingleMachineCluster". Initially, the Windows Node works fine before restarting the Host machine, even after executing the below commands:
Once the Host machine gets rebooted, the Windows Node status stays as "NotReady".
To Reproduce Steps to reproduce the behavior:
Expected behavior The Windows Node should be in "Ready" state even after the Host Machine reboots.
Screenshots The below image shows how the Windows Node is registered but cannot reach the "Ready" state.
Environment:
Additional context None.