I’ve deployed the latest master code, re-deployed the DB and uploaded new
system templates with 4.3 version. After that, UserVm fails to start because
DHCP entry fails to apply on the VR.
Its a xen host deployment, and I’ve tested that ssh to the VR works just fine.
Sheng, can you please take a
I also face this issue. Here is the snippet of logs. Please let me know if
you need any other info.
2014-01-21 10:52:46,909 INFO [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-1:ctx-57a7ba8c ctx-933fbba1) Unable to contact resource.
com.cloud.exception.ResourceUnavailableException: Resource
The systemvm iso changed. You need to rebuild system iso, clean up the tags
on xen host(assume), then the new iso would be copied to Xen host after you
reboot the mgmt server.
Check /opt/xensource/packages/iso/systemvm.iso ensure it's updated.
--Sheng
On Tue, Jan 21, 2014 at 11:09 AM, Nitin
To fix it, you should cleanup the tags on your xen host, so the MS will
copy the newest ISO there.
Sheng, thank you for helping to debug it.
-Alena.
On 1/21/14, 11:09 AM, Nitin Mehta nitin.me...@citrix.com wrote:
I also face this issue. Here is the snippet of logs. Please let me know if
you
+users
When ever we see the error 'Unable to contact resource', I suggest to check the
host agent logs (for xen /var/log/SMlog).
It will give you idea of what is going wrong from the router. Most of times
there could be script execution failures.
Adding command to clean up tags on xenserver
xe