Hybrid Runbook Worker Status is Fail

三又アークウェイ 1

Hybrid Runbook Worker Status is Fail
Fail message is

’’Hybrid runbook worker is not running.
Update deployment is disabled in the current_mof file (/etc/opt/omi/conf/omsconfig/configuration/Current.mof).’’

I changed Update deployment from disabled to enabled in Current.mof.

ResourceSettings = "[{\"WorkspaceId\":\"******************\",\"AzureDnsAgentSvcZone\":\"agentsvc.azure-automation.net\",\"Solutions\":{\"Updates\":{\"Enabled\":false},\"AzureAutomation\":{\"Enabled\":true}}}]";

↓↓↓↓↓

After that Hybrid Runbook Worker Status was success and Update management schedule was done and success.
But at some point, Updates value of current.mod has changed to false , then Hybrid Runbook Worker Status was false again.
I use Azure Firewall and checked "Configure a private network"(https://learn.microsoft.com/ja-jp/azure/automation/automation-dsc-overview)
I add them to network rule.

Port: Only TCP 443 is required for outbound Internet access
Global URL: * .azure-automation.net
US Gov Virginia Global URL: * .azure automation.us
Agent Service: https://<workspaceId>.agentsvc.azure-automation.net

I dont know why updates value of current.mod has changed to false.
Please tell me how to deal with this.

olufemia-MSFT 2,861 Reputation points

2020-07-14T06:39:36.16+00:00

Do you know the last known update timestamp on the current.mof file? Is the rollback happening at a set cadence e.g. every 2-4 hours? Is it possible there are background security, network policies running in your environment that could be reverting this change?
三又アークウェイ 1 Reputation point

2020-07-15T04:56:26.387+00:00

thank you for your reply.

i checked update timestamp on file.it was 10th 20:00.
This event happens once a week. It is unknown if the times are the same.
we use backup , azure firewall and express route. but there are nothing that could be reverting this change.
olufemia-MSFT 2,861 Reputation points

2020-07-24T06:18:58.293+00:00

Sorry for the delay @三又アークウェイ , this is an interesting one. are you able to repo this on another Hybrid worker perhaps. I am unable to reproduce this behavior on my end. And from my convo with the feature engineers, this behavior is certainly not expected. If you run into this again, or on another worker machine, please send mail to Azcommunity@microsoft.com, (add "Attn:femi" to subject line) include you subscription ID, a link to this thread (for context) and we can connect you with the technical support channel for a deeper investigation.

Cheers,

Share via

Hybrid Runbook Worker Status is Fail