Azure VM agent status not ready.

Question

Azure VM agent status not ready.

All I can see is python2 is not installed under diagnostic settings.

it was working fine until yesterday morning before I added a data disk to VM.

Thanks.

Answer 1

Hello Abhishek Kumar Jha

Welcome to Microsoft Q&A Platform, thanks for posting your query here.

Adding a data disk to the VM should not affect the Azure VM agent status. It's possible that there might be a conflict or compatibility issue between the VM agent and the newly added data disk.

Try to detach the data disk, you can try detaching it temporarily and check if the VM agent status returns to "ready."

If detaching the data disk resolves the issue, it's likely that there is a configuration problem with the disk.

Review the VM's system and application logs to check for any disk-related errors or warnings.

Ensure that the VM agent on the virtual machine is up to date.

Also, if the Azure VM agent status is not ready and the only issue you can see is that python2 is not installed under diagnostic settings, the VM agent relies on Python 2 for certain functionalities. Ensure that Python 2 is installed on your virtual machine.
Double-check the diagnostic settings for your VM. Ensure that the correct versions of Python are specified in the diagnostic settings. Verify that the correct extension is installed and properly configured to use Python 2.

Restart the VM and see if that helps resolve the issue.

Hope this helps.

Answer 2

Hei @Abhishek Kumar Jha

Thank you for contacting Microsoft Q and A.

As I understand you have an Azure VM (presumably Windows) whose overview page shows 'status=running' but has a yellow warning bar just below the connect button that says 'Virtual machine status is not ready, troubleshoot the issue ->'

I am also assuming that you are not able to connect to the machine via RDP or SSH which is common in these situations.

You can try the following steps.

0. Take a snapshot of the OS disk and any other disk attached as a backup for precaution

1. Restart the computer and try to connect again. (I am sure you may have done it already but putting it in for the sake of completeness)
2. Check if you can 'run command' under the operations menu (any command, for example, pwd or dir).
3. Check if the serial port is available via 'serial console under the help menu.

If any of these interfaces work, then it may be possible to manually remove and install the VM agent again.

The following section shows how to remove and install the agent with these interfaces, link

In case, the interface is not working, try these suggestions.

4. Resize the VM, restart, and check.
5. Use REAPPLY and then use REDEPLOY from 'redeploy + reapply' under the help tab.

reapply: will reapply vm state and then redeploy will take it to a new host.

1. Use a repair VM to repair the VM boot disk, link

Please mark it as an answer if it helps you.