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
Hi,
I have been using Azure Migrate to move on-prem hyper-v VM's to Azure. These will sit in terraformed Vnets, subnets and resource groups. I'd like to bring these machines into the fold using aztfy.
Unfortunately I get an error:
"Error: /subscriptions/*****************/resourceGroups/rt-1-pr-euw-bfxapp-rsg-01/providers/Microsoft.Compute/virtualMachines/HYPAPPRT110: resolving "/subscriptions/****************/resourceGroups/rt-1-pr-euw-bfxapp-rsg-01/providers/Microsoft.Compute/virtualMachines/HYPAPPRT110": unexpected nil OS profile in response"
When I investigated there was indeed no OSProfile section in the Export Template for migrated VM's.
Our Azure VM's created with the old ARM templates or CLI'd have the OSProfile present and correct and can play nicely with aztfy.
Is there a workaround or are there plans to tackle this issue?
Thanks.
Paul.
EDIT: I found I could use terraform import to drag the VM into a state file then use tfadd to create the code. Looking in the state file I can find where the 'nil OS profile' is coming from:
"os_profile": [],
"os_profile_linux_config": [],
"os_profile_secrets": [],
"os_profile_windows_config": [],
"plan": [],
The text was updated successfully, but these errors were encountered:
Hi,
I have been using Azure Migrate to move on-prem hyper-v VM's to Azure. These will sit in terraformed Vnets, subnets and resource groups. I'd like to bring these machines into the fold using aztfy.
Unfortunately I get an error:
"Error: /subscriptions/*****************/resourceGroups/rt-1-pr-euw-bfxapp-rsg-01/providers/Microsoft.Compute/virtualMachines/HYPAPPRT110: resolving "/subscriptions/****************/resourceGroups/rt-1-pr-euw-bfxapp-rsg-01/providers/Microsoft.Compute/virtualMachines/HYPAPPRT110": unexpected nil OS profile in response"
When I investigated there was indeed no OSProfile section in the Export Template for migrated VM's.
Our Azure VM's created with the old ARM templates or CLI'd have the OSProfile present and correct and can play nicely with aztfy.
Is there a workaround or are there plans to tackle this issue?
Thanks.
Paul.
EDIT: I found I could use terraform import to drag the VM into a state file then use tfadd to create the code. Looking in the state file I can find where the 'nil OS profile' is coming from:
"os_profile": [],
"os_profile_linux_config": [],
"os_profile_secrets": [],
"os_profile_windows_config": [],
"plan": [],
The text was updated successfully, but these errors were encountered: