Linux VM agent status in 'not ready' state

Question

I had a Linux VM that was agent stuck in a 'not ready' state. As a result, it caused my production eth1 to be stuck in a disconnected state. I tried restarting the machine and rolling back to last known state good configuration with no success. We were finally able to recover from this state by creating an ethernet config file. My question is, Do you know of any other suggestions to keep this from happening on my other machines, other than creating the ethernet config file??

Answer 1

@DG001 Sorry to hear your VM had an outage after being rebooted. It is not clear to me what exactly caused the outage. You are referencing that eth1 was showing as disconnected status and talk about the ethernet config file. Based on this it sounds like there might have been some misconfiguration that caused an impact after the VM was rebooted.

Please make sure that you are configuring your VM properly for multiple interfaces. This page walks you through all the necessary steps to configure this.

If you face this issue in the future you can attempt to Use Azure Linux Auto Repair to fix your VM. I also recommend opening a ticket with our support team so we can troubleshoot the issue directly to find the root cause.

Hope this helps. Let me know if you have any other questions.

Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Answer 2

This happened when we restarted the Linux VM. There were no upgrades or changes in progress when we did the reboot. The reboot was performed as the application was running on the RHEL VM and was having some issues with its services.