The issue is a bit of different with the one reported at the beginning of this bug. Let me explain the details and provide a workaround for you.
The key is when dbus.service is running at booting.
With ova, cloud-init will be enabled and run, when it's running, it blocks dbus, see reason at comment #8. So dbus is running too late to make customization work even with the fix in 6.7U3.
In your case, I suggest you create a new template but turn ova into template directly.
Steps:
1. Power-on VM which deploy from ova.
2. Disable cloud-init by by running the command “sudo touch /etc/cloud/cloud-init.disabled”
3. Power-off VM and convert it to template.
@Florian
The issue is a bit of different with the one reported at the beginning of this bug. Let me explain the details and provide a workaround for you.
The key is when dbus.service is running at booting.
With ova, cloud-init will be enabled and run, when it's running, it blocks dbus, see reason at comment #8. So dbus is running too late to make customization work even with the fix in 6.7U3.
In your case, I suggest you create a new template but turn ova into template directly. cloud-init. disabled”
Steps:
1. Power-on VM which deploy from ova.
2. Disable cloud-init by by running the command “sudo touch /etc/cloud/
3. Power-off VM and convert it to template.