Cloning VM requires restart of Bind on cloudmin master before you can edit the VM

Submitted by Franco Nogarin on Mon, 05/02/2016 - 16:50 Pro Licensee

when I clone a VM and it is assigned an IP, I cannot edit the VM as I get:
Failed to save system details : The new hostname lampd7-template.virtual cannot be resolved to an IP address

so I open webmin for the cloudmin master and open the bind module and click "Apply Configuration" and this fixes the issue.

Status: 
Active

Comments

Submitted by JamieCameron on Mon, 05/02/2016 - 20:56

That's odd, because the current code already restarts BIND as part of the cloning process.

If you create a new VM, do you need this same restart before you can edit it?

chadwick89's picture
Submitted by chadwick89 on Wed, 05/04/2016 - 15:24

Hi Jamie,

I created a fresh CentOS7 VM for this test, and it seems that even a new VM requires manual BIND9 intervention before it can be edited. Prior to touching BIND9 after VM creation, I tried editing the system and got:

Failed to save system details : The new hostname bindtest.virtual cannot be resolved to an IP address

I then went into Webmin > Servers > BIND DNS and clicked "Apply Configuration" which solved the issues.

Submitted by JamieCameron on Wed, 05/04/2016 - 19:28

Do any errors from bind or named get logged to /var/log/messages when you create or clone a VM?