|
[
Permalink
| « Hide
]
Valerie Kalusinski added a comment - 02/Jun/10 02:30 PM
added log traces.
It seems the behaviour has changed:
Now, when deploying and the NFS is not well mounted, is displayed in log: 6:00:40.797 ERROR c.a.virtualfactory.rimpstub.RimpStub - Exception executing the RIMP WS-MAM operation com.abiquo.virtualfactory.rimp.RimpCreate com.abiquo.virtualfactory.rimpstub.RimpException: Initialize error : nfs-testing:/opt/vm_repository : this remote repository is not mounted at com.abiquo.virtualfactory.rimpstub.RimpStub.checkRimpFault(RimpStub.java:353) [RimpStub.class:na] in notifications and events: Exception executing the RIMP WS-MAM operation com.abiquo.virtualfactory.rimp.RimpCreate should be indicated: Initialize error : nfs-testing:/opt/vm_repository : this remote repository is not mounted and in notifications: "The Virtual Appliances has not been deployed. Please, contact your System Administator." Now use the Appliance Manager *StaticRepositoryServlet* to check if the disk file is present on the datacenter repository file system.
trace the virtual appliance error as *Disk file not found on the datacenter repository: * 1/lala/fo.bar |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||