updating VM profile in OMS fails

[ilja_l]

Hi,

trying to update a profile of a running machine. Clicked edit icon, checked "start on boot" and clicked Update.

Effects:
1) Error message: "Server return: Disk size not correct" - disc sized was not modified.
2) "Update" label changed into "Creat..."
3) The autostart label was not set.

PS. Perhaps it would make sense to change "Abort" button to "Cancel"? Otherwise it feels like potentially killing a VM.

cheers,
I.

[frame]

Ok - probably disk size conversion is not right and thus minimum requirement applies blocking the edit update.
Added issue to our buglist and waiting now for a fix.
Added also renaming Abort to Cancel to our TODO list.
Target is alpha2 release.

[vmluva]

one more release and things should work a lot better

I cannot wait!
Virtual Lover

[vmluva]

Please help me with the following error.
This was done on 6/24/2011     (i thought something new was published.)
please help me get past this and at least info funcman where i can see my
virtual machines.

Am I doing something wrong? or shoudl we be patient with your development
department?

thank you

Copying OpenVZ template file system (this may take a while)
Generating OpenVZ CT configuration
Finalyzing OpenVZ template deployment
Traceback (most recent call last):
  File "/usr/bin/opennode", line 84, in ?
    opennode_utility.run(action)
  File "/usr/lib/python2.4/site-packages/opennode_lib/opennode.py", line 257, in       run
    self.runGUI()
  File "/usr/lib/python2.4/site-packages/opennode_lib/opennode.py", line 292, in       runGUI
    self.template_deploy_lib.run(True)
  File "/usr/lib/python2.4/site-packages/opennode_lib/template_deploy.py", line       117, in run
    deploy_converter.defineOpenvzCT()
  File "/usr/lib/python2.4/site-packages/opennode_lib/ovfopenvz.py", line 170, i      n defineOpenvzCT
    raise Exception, "Unable to define OpenVZ CT (CT starting failed)"
Exception: Unable to define OpenVZ CT (CT starting failed)
[root@Softvar-VM ~]#

[activesys]

This error usually means that there is something wrong with your newly created OpenVZ VM configuration - as it cannot start.

Could you please try to start this OpenVZ VM manually - eg with 'vzctl start VEID'
You can probably find VM ID (VEID) looking it up by 'vzlist -a' - as its shows also stopped VM-s.