Giters

Azure / iotedge

The IoT Edge OSS project

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

EFLOW VM stops working after some reboots. Most likely networking related issue

bhjertaas opened this issue · comments

commented

Expected Behavior

EFLOW with Edge running should start when Windows starts, and run smoothly in a stable manner, also when the PC changes between different networks.

Current Behavior

Sometimes, when a few of many PCs reboot (and it is thought also it happens when the PC changes between Wi-fi networks), EFLOW becomes unresponsive. hcsdiag list returns empty list and it is not possible to Connect-EflowVm.
More details in my post here Azure/iotedge-eflow#279

Steps to Reproduce

We've been unable to reproduce the issue in a reliable manner. The devices where we observe problems are not physically in our premises, and not always powered on.

Context (Environment)

Output of iotedge check

Click here 

We're not able to run iotedge check since we're unable to connect to the eflow vm. I really don't think the problem has anything to do with the internals of Edge or eflow, but the Hyper-V default switch - VM relationship.

Device Information

  • Host OS [e.g. Ubuntu 22.04, Windows Server IoT 2019]:
  • Architecture [e.g. amd64, arm32, arm64]:
  • Container OS [e.g. Linux containers, Windows containers]:

Runtime Versions

  • aziot-edged [run iotedge version]: 1.4.20
  • Edge Agent [image tag (e.g. 1.0.0)]: 1.4.10.25103
  • Edge Hub [image tag (e.g. 1.0.0)]:
  • Docker/Moby [run docker version]: 20.10.25

Logs

See my other issue which I linked to above

Additional Information

Support 2311150050002686 told me to post here

commented

Hi @bhjertaas, from above and linked EFLOW issue this appears to be EFLOW specific? Or are there additional problems you are seeing with iotedge?

commented

Thanks for a reply. Yes, I agree that it appears to be EFLOW related rather than Edge related. That is the reason I posted the issue at iotedge-eflow forum first, but Microsoft Azure support told me to raise an issue here instead.

commented

@bhjertaas since this is believed to be an EFLOW issue at the moment I am closing this issue, if it turns out there is an issue with iotedge please feel free to reopen :)