-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add troubleshooting issue when VM does not show an IP #658
base: main
Are you sure you want to change the base?
Conversation
Related to: harvester/harvester#6644 Signed-off-by: Volker Theile <vtheile@suse.com>
|
LGTM,Thanks |
@votdev Just a thought, this applies only to linux based VMs and not windows VM as there is no cloud init/qemu-ga in windows VM.Do you think it is worth adding a a point on which VMs this is applicable ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review done
@@ -414,3 +414,37 @@ Node level operation, node by node: | |||
https://github.com/harvester/harvester/issues/5109 | |||
|
|||
https://github.com/longhorn/longhorn/issues/8009 | |||
|
|||
## VM does not show an IP address |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## VM does not show an IP address | |
## Virtual Machine IP Address Not Displayed |
|
||
### Issue Description | ||
|
||
The VM does not show an IP address on the **Virtual Machines** page on the Harvester UI. This issue might apply to newly created or imported VMs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The VM does not show an IP address on the **Virtual Machines** page on the Harvester UI. This issue might apply to newly created or imported VMs. | |
The **Virtual Machines** screen on the Harvester UI does not display the IP address of a newly created or imported virtual machine. |
If no IP address is displayed for a VM, this is usually because the **qemu-guest-agent** package is not installed in the VM. | ||
|
||
You can check this by looking at the status of the **VirtualMachineInstance** object. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If no IP address is displayed for a VM, this is usually because the **qemu-guest-agent** package is not installed in the VM. | |
You can check this by looking at the status of the **VirtualMachineInstance** object. | |
This issue usually occurs when the `qemu-guest-agent` package is not installed on the virtual machine. To determine if this is the root cause, check the status of the `VirtualMachineInstance` object. |
$ kubectl get vmi -n <NAMESPACE> <NAME> -ojsonpath='{.status.interfaces[0].infoSource}' | ||
``` | ||
|
||
If no **qemu-guest-agent** package is installed, then the output will not contain the string **guest-agent**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If no **qemu-guest-agent** package is installed, then the output will not contain the string **guest-agent**. | |
The output does not contain the string `guest-agent` when the `qemu-guest-agent` package is not installed. |
To solve the problem, you can select the **Install guest agent** checkbox in the VM settings under **Advanced Options**. | ||
|
||
The problem with this is that cloud-init is only executed once when the VM is started for the first time. To apply the settings specified under **Cloud Configuration** again when the VM is restarted the next time, the cloud-init directory in the VM must be deleted with the command |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To solve the problem, you can select the **Install guest agent** checkbox in the VM settings under **Advanced Options**. | |
The problem with this is that cloud-init is only executed once when the VM is started for the first time. To apply the settings specified under **Cloud Configuration** again when the VM is restarted the next time, the cloud-init directory in the VM must be deleted with the command | |
You can [install the QEMU guest agent](../vm/create-vm.md#installing-the-qemu-guest-agent) by editing the virtual machine configuration. | |
1. On the Harvester UI, go to **Virtual Machines**. | |
1. Locate the affected virtual machine, and then select **⋮ > Edit Config**. | |
1. On the **Advanced Options** tab, under **Cloud Config**, select **Install guest agent**. | |
1. Click **Save**. | |
However, cloud-init is run only once (when the virtual machine is started for the first time). To apply new **Cloud Config** settings, you must delete the cloud-init directory in the virtual machine. |
$ sudo rm -rf /var/lib/cloud/* | ||
``` | ||
|
||
The VM must then be restarted so that cloud-init is executed again and the **qemu-guest-agent** package is installed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The VM must then be restarted so that cloud-init is executed again and the **qemu-guest-agent** package is installed. | |
After deleting the directory, you must restart the virtual machine so that cloud-init is run again and the `qemu-guest-agent` package is installed. |
Related to: harvester/harvester#6644