Freshly created 'Start/Stop VM' runbook is nowhere to be found

Question

Freshly created 'Start/Stop VM' runbook is nowhere to be found

Andrej Zupan 101

Hi, noob here.

I've created 'Start/Stop VM' runbook here:

https://portal.azure.com/#create/Microsoft.StartStopVMSolution

Now, it's not shown among other resources, but it must be somewhere, because when I try to create it again, I get the following error:

{
  "telemetryId": "dc6443a6-bc42-4b1f-9ad8-4ebd3646835c",
  "bladeInstanceId": "Blade_f40e63de401c422599e6b7b857dce7f7_2_0",
  "galleryItemId": "Microsoft.StartStopVMSolution",
  "createBlade": "NewGallerySolutionV3Blade",
  "code": "InvalidResourceLocation",
  "message": "The resource 'ScheduledStartStop_Parent' already exists in location 'eastus' in resource group 'Securities-Grid-Resources'. A resource with the same name cannot be created in location 'westeurope'. Please select a new resource name."
}

BhargaviAnnadevara-MSFT 5,341 Reputation points

2020-12-21T15:10:52.97+00:00

@Andrej Zupan As per the error message, it seems like the solution was attempted to deploy to the Securities-Grid-Resources resource group in the West Europe location. If that deployment was indeed successful, you should find all the related components in the same resource group by browsing to Azure portal > Resource groups > Securities-Grid-Resources similar to the screenshot below:

An overview of this solution can be found here: Start/Stop VMs during off-hours overview.

Please check and let me know what you see.
Andrej Zupan 101 Reputation points

2020-12-22T07:20:39.673+00:00

The problem is I can't see it, yet, Azure behaves as if it's there.

Problems started after I've deleted a "Start/Stop VMs during off-hours" some weeks ago,
BhargaviAnnadevara-MSFT 5,341 Reputation points

2020-12-22T07:28:33.47+00:00

@Andrej Zupan Ah ok. Could you confirm if you had deleted the feature along with all of its related resources? Can you see the Securities-Grid-Resources resource group on the Azure portal?

Deleting the feature only removes the associated runbooks. It doesn't delete the schedules or variables that were created when the feature was added. If you don't want to keep the Azure Automation account feature components like Runbooks/Variables/Schedules, you can manually delete each.
Andrej Zupan 101 Reputation points

2020-12-22T07:45:15.107+00:00

I've deleted Azure Automation Account together with all its resources. Now I can't see any.

I had trouble creating Log Analytics workspace. Azure kept rejecting any reasonable name I could possibly come up with. At the end, I had to resort to "Workspace666". Anything else just didn't work.

Looks like my Azure subscription is cursed or something.
BhargaviAnnadevara-MSFT 5,341 Reputation points

2020-12-22T10:16:28.53+00:00

@Andrej Zupan Thank you for the additional details.

Although it might seem like the resource group is empty, note that some resource types like microsoft.insights/scheduledqueryrules and microsoft.insights/actiongroups would be hidden from the default view unless "Show hidden types" checkbox is selected. This highlighted resource below is most likely the one that caused the resource already exists error that you initially encountered.
BhargaviAnnadevara-MSFT 5,341 Reputation points

2020-12-22T10:25:00.257+00:00

@Andrej Zupan Secondly, the name you choose for your workspace must be globally unique across all Azure Monitor subscriptions.

When you delete a LA workspace, the service places it in a soft-delete state making it inaccessible to any operation. The name of the deleted workspace is preserved during the soft-delete period and can't be used for creating a new workspace. After the soft-delete period, the workspace is non-recoverable, it is scheduled for permanent deletion and its name it released and can be used for creating a new workspace.

You can permanently delete your workspace and override the soft-delete period. The permanent workspace delete operation releases the workspace name and you can create a new workspace using the same name.

BhargaviAnnadevara-MSFT 5,341 Reputation points

2020-12-21T15:10:52.97+00:00

@Andrej Zupan As per the error message, it seems like the solution was attempted to deploy to the Securities-Grid-Resources resource group in the West Europe location. If that deployment was indeed successful, you should find all the related components in the same resource group by browsing to Azure portal > Resource groups > Securities-Grid-Resources similar to the screenshot below:

An overview of this solution can be found here: Start/Stop VMs during off-hours overview.

Please check and let me know what you see.
Andrej Zupan 101 Reputation points

2020-12-22T07:20:39.673+00:00

The problem is I can't see it, yet, Azure behaves as if it's there.

Problems started after I've deleted a "Start/Stop VMs during off-hours" some weeks ago,
BhargaviAnnadevara-MSFT 5,341 Reputation points

2020-12-22T07:28:33.47+00:00

@Andrej Zupan Ah ok. Could you confirm if you had deleted the feature along with all of its related resources? Can you see the Securities-Grid-Resources resource group on the Azure portal?

Deleting the feature only removes the associated runbooks. It doesn't delete the schedules or variables that were created when the feature was added. If you don't want to keep the Azure Automation account feature components like Runbooks/Variables/Schedules, you can manually delete each.
Andrej Zupan 101 Reputation points

2020-12-22T07:45:15.107+00:00

I've deleted Azure Automation Account together with all its resources. Now I can't see any.

I had trouble creating Log Analytics workspace. Azure kept rejecting any reasonable name I could possibly come up with. At the end, I had to resort to "Workspace666". Anything else just didn't work.

Looks like my Azure subscription is cursed or something.
BhargaviAnnadevara-MSFT 5,341 Reputation points

2020-12-22T10:16:28.53+00:00

@Andrej Zupan Thank you for the additional details.

Although it might seem like the resource group is empty, note that some resource types like microsoft.insights/scheduledqueryrules and microsoft.insights/actiongroups would be hidden from the default view unless "Show hidden types" checkbox is selected. This highlighted resource below is most likely the one that caused the resource already exists error that you initially encountered.
BhargaviAnnadevara-MSFT 5,341 Reputation points

2020-12-22T10:25:00.257+00:00

@Andrej Zupan Secondly, the name you choose for your workspace must be globally unique across all Azure Monitor subscriptions.

When you delete a LA workspace, the service places it in a soft-delete state making it inaccessible to any operation. The name of the deleted workspace is preserved during the soft-delete period and can't be used for creating a new workspace. After the soft-delete period, the workspace is non-recoverable, it is scheduled for permanent deletion and its name it released and can be used for creating a new workspace.

You can permanently delete your workspace and override the soft-delete period. The permanent workspace delete operation releases the workspace name and you can create a new workspace using the same name.

Answer 1

Workspace recycle bin is empty, I'm afraid.

There is no "Show Hidden" button in Runbook list

When I tried to create Start/Stop VM again, things got even weirder. I've entered dates & times correctly, as far as I can tell, but I keep getting this error:

{"telemetryId":"96b823ff-7ef3-4d1a-ab07-c65b5549f6aa","bladeInstanceId":"Blade_2c78b14dbaba42e79a647db7cfcd9316_2_0","galleryItemId":"Microsoft.StartStopVMSolution","createBlade":"NewGallerySolutionV3Blade","code":"InvalidTemplate","message":"Deployment template validation failed: 'The value for the template parameter 'Daily Start Time' at line '1' and column '2352' is not provided. Please see https://aka.ms/resource-manager-parameter-files for usage details.'.","additionalInfo":[{"type":"TemplateViolation","info":{"lineNumber":1,"linePosition":2352,"path":"parameters['Daily Start Time']"}}]}

Answer 2

@Andrej Zupan Apologies if my previous comment did not convey the message clearly. The Show hidden types checkbox is available from within the Overview blade of the Resource Group view, as shown in the screenshot below:

Please wipe the resource group clean with this checkbox selected (unhide all resources in the resource group > Select all > Delete) before any attempt to recreate the solution in the same resource group.

I'm looking at the possible causes for the newer template deployment validation error that you shared.

On a side note, please note that for the Target ResourceGroup Names (string) parameter (in the Parameters blade), enter Resource Group names that contains VMs to be managed by this solution, and not the one where the solution is being deployed.

Andrej Zupan 101 Reputation points

2020-12-23T09:55:26.793+00:00

That solved the problem.

Thank you for your patience!

Freshly created 'Start/Stop VM' runbook is nowhere to be found

1 additional answer

Activity