Error deploying eflow through Azure Pipelines about iotedge-eflow HOT 4 CLOSED

@ericvruder,

Thank you for the detailed issue report. I do not believe this is a scenario that we have considered thus far. Perhaps the issue is that our script is making an assumption that it is running under an Admin account rather than a System account. Can you invoke the command from the pipeline as an Admin rather than System account?

I will file a bug on your behalf for this issue, but any additional information you can provide would be greatly appreciated.

Terry Warwick
Microsoft
#32231675

from iotedge-eflow.

@TerryWarwick, I am really sorry but that is not something I can easily do. I'll try to see if I can find time at a later time to install the agent to run with the administrator account, but unfortunately that is not something that is that straight forward in my current setup.

But thank you for filing the report!

from iotedge-eflow.

@TerryWarwick , sorry for taking this long to test it out.

But it seems to work though if using a admin account. Created a Azure VM, installed eflow on it and then installed the agent on it using the admin user.

I then got my agent to deploy to it. Or at least start the process, there where(are) some issues with vTpm and the VM. But this doesn't really matter - it started the process and got much further than previously.

Things to note:

• Verify-EflowVm fails if the VM has not yet been deployed previously. So, straight after installing eflow, before deploying, it will fail. Not sure if this is intended or not - I would expect it to return false.
• Admin user was called ericvruder. Pretty sure this doesn't matter, but the more info the better.

from iotedge-eflow.

Thanks @ericvruder for your notes. We will take that into account in our future updates.

from iotedge-eflow.