Update from Eflow version 1.1 to 1.4 fails - Need a password ?

Question

Windows Server 2019 
HyperV enabled (Passthrough)
	VM Options, enable VBS (Enable Virtualization based Security)
	Use External switch and turn on ‘Allow promiscuous mode’ 	
	EFLOW VM 1.1 in use 

Bug/Problem Description:

We are trying to update from Linux (Eflow version) 1.1 to 1.4  
However, the Linux VM is able to acquire the IP address and it begins an ssh connection but it asks me for a password which I do not have.  What is the password ?  Can it be reset to a default password ? 

Separately, when I try to use the newest version (1.4) the setup fails to acquire the IP and is unable to ssh into the machine. 

Answer 1

Hi @Michael Wilcox Greetings! I have tested the update of Azure IoT Edge from 1.1 to 1.4 on my local machine. I have used internal ***Default Switch ***instead of the External Switch and noticed that the Start-EflowMigration command executed as expected without any issues.

One observation I would like to note is that the update doesn't support migrations between the different release trains. If you want to move from the 1.1LTS or 1.4LTS version to the Continuous Release (CR) version or viceversa, you'll have to uninstall the current version and install the new desired version as mentioned in the documentation. If you were not on Azure IoT Edge 1.1LTS (1.1.2212.12122), I would recommend following the steps outlined in Update using Microsoft Update to get to the Azure IoT Edge LTS version of 1.1

Please refer the below screenshot showing the initial 1.1 version I have configured with, and the updates being installed for the Azure IoT Edge after enabling the above option and checked for updates.

Once you are the Azure IoT Edge 1.1LTS build, you can execute the Start-EflowMigration command to update the IoT Edge to 1.4 version. Please find the below screenshots from my testing

I then confirmed the Migration using Confirm-EflowMigration command. I could confirm that Edge version gets updated by connecting to the Eflow.

Separately, when I try to use the newest version (1.4) the setup fails to acquire the IP and is unable to ssh into the machine.

Please note that when deploying the Eflow using External switch, you would need to pass additional parameters to command Deploy-Eflow . Ensure to set the vswitchType and vswitchName parameters as needed referencing the Deploy-Eflow powershell functions. You can get more information about these commands and the default values they use by referencing the files under C:\Program Files\WindowsPowerShell\Modules\AzureEFLOW location.

I noticed that you have also created a GitHub tickect on this. Posting the link here https://github.com/Azure/iotedge-eflow/issues/239 I will check with the team and get back to you with more details on the reason why you see a password when using an external switch.

Please let us know if you have any questions or concerns in the comments below and we would be glad to help you.