Thanks Prasanna,
I've confirmed that the vmdata.py is on the router vm.
root@r-7-VM:~# find / -name vmdata.py
/opt/cloud/bin/vmdata.py
Maybe some other commit fixed the problem at the same time for me.
Tom.
On Fri, 2013-08-02 at 14:42 +0530, Prasanna Santhanam wrote:
> I made a mistake - the v
I made a mistake - the vmdata goes into the router deployed by
cloudstack but is called by the router_proxy.sh script within the
/usr/lib/xcp directory of the host over ssh.
root@r-5-VM:/# find . -name vmdata.py
./opt/cloud/bin/vmdata.py
The tests are passing now and VM deploy works fine:
nosete
Prasanna,
when I first ran deploysvr after a new database install, I had quite a
lot of starting and crashing of the system vms (which seems new to me)
but I waited and it settled down.
I was then able to launch an instance again after the usual other steps.
The instance now tells me the password
Ok. I've just copied it over. Its the only one that ends with .py and
I've chmod'd it to 755 also.
Will check it shortly. I'm building.
Tom.
root@devcloud:~# ls -l /usr/lib/xcp/plugins/
total 164
-rwxrwxrwx 1 root root 8304 Nov 5 2012 coalesce-leaf
-rwxrwxrwx 1 root root 301 Nov 27 2012 ec
Yeah this was a recent change that Marcus made to optimize the vmdata
passed to guests. I'll verify why the change is not working shortly.
Running some other tests at the moment on my setup.
Meanwhile, Could you manually copy that to where you see the s3xen
plugin and retry?
On Fri, Aug 02, 2013
Hi Prasanna,
I've just finished re-initializing a brand new devcloud and am about to
start things up again.
root@devcloud:~# find / -name vmdata.py
root@devcloud:~#
Maybe it was there before in my previous install. How would it be copied
to devcloud usually? For example for the s3xen plugin I n
On devcloud
$ cd /
$ find . -name vmdata.py
Do you see a file by that name anywhere in the XCP plugins? If not -
it failed to copy over into the devcloud plugins for some reason when
adding the host.
On Fri, Aug 02, 2013 at 03:22:20PM +0900, Thomas O'Dowd wrote:
> This was working yesterday but
This was working yesterday but the launching of instances for me on 4.2
is currently not working. I have twice now tried a clean build along
with deploydb and deploysvr in the usual manner but no luck.
On the UI I get:
Unable to create a deployment for VM[User|tom1]
On the management server
