Error creating vm

Community Support
1

Dear Friends,

I am not able to create the VM. I selected the template, but VM creation getting Failed. Hosts and template are all working fine and UP. Log Files of VM Failure is below:

Sun Jan 29 04:31:15 2017 [Z0][DiM][I]: New VM state is ACTIVE.
Sun Jan 29 04:31:15 2017 [Z0][LCM][I]: New VM state is PROLOG.
Sun Jan 29 04:31:16 2017 [Z0][TM][I]: Command execution fail: /var/lib/one/remotes/tm/shared/clone ubuntu:/var/lib/one//datastores/1/2c439c89cd4e95977f1ecd79f5fc6291 192.168.17.130:/var/lib/one//datastores/0/2/disk.0 2 1
Sun Jan 29 04:31:16 2017 [Z0][TM][I]: clone: Cloning /var/lib/one/datastores/1/2c439c89cd4e95977f1ecd79f5fc6291 in 192.168.17.130:/var/lib/one//datastores/0/2/disk.0
Sun Jan 29 04:31:16 2017 [Z0][TM][E]: clone: Command “cd /var/lib/one/datastores/0/2; cp /var/lib/one/datastores/1/2c439c89cd4e95977f1ecd79f5fc6291 /var/lib/one/datastores/0/2/disk.0” failed: Warning: Permanently added ‘192.168.17.130’ (ECDSA) to the list of known hosts.
Sun Jan 29 04:31:16 2017 [Z0][TM][I]: cp: cannot stat ‘/var/lib/one/datastores/1/2c439c89cd4e95977f1ecd79f5fc6291’: No such file or directory
Sun Jan 29 04:31:16 2017 [Z0][TM][E]: Error copying ubuntu:/var/lib/one//datastores/1/2c439c89cd4e95977f1ecd79f5fc6291 to 192.168.17.130:/var/lib/one//datastores/0/2/disk.0
Sun Jan 29 04:31:16 2017 [Z0][TM][I]: ExitCode: 1
Sun Jan 29 04:31:16 2017 [Z0][TM][E]: Error executing image transfer script: Error copying ubuntu:/var/lib/one//datastores/1/2c439c89cd4e95977f1ecd79f5fc6291 to 192.168.17.130:/var/lib/one//datastores/0/2/disk.0
Sun Jan 29 04:31:16 2017 [Z0][DiM][I]: New VM state is FAILED

Please Suggest.

2

Hi Simar,

  1. I think you are using Ubuntu as OS.
  2. accordingly check the firewall status. Say you are using centos or any redhat flavor then check by command getenforce. the output of this command must be Disabled. If you get Enforcing or permissive, you need to change in /etc/sysconfig/selinux file.
    sudeep@syslap:~$ getenforce
    Disabled
  3. if output is Disabled, please check whether the network bond IP is pinging and the mount point /var/lib/one is mounted in worker node
  4. thereafter check whether the iptables is flushed in both the nodes. check by doing iptables -L if you find any rule, double-check whether you need that rule or may define later. to make iptables flush, do iptables -F
  5. I think, it is just a permission issue or firewall issue which is restricting the disk to get created(copied) i the DS.
3

Hi snbanerjee,

Yes I am using Ubuntu.
Thanks… It worked… It was the firewall issue.
Great…

4

thereafter check whether the iptables is flushed in both the nodes. check by doing iptables -L if you find any rule, double-check whether you need that rule or may define later. to make iptables flush, do iptables -F

What this iptables are? and what does these contains?

5

iptables are administration tool for IPv4/IPv6 packet filtering and NAT
use man iptables to know more
sudeep@syslap:~$ man iptables

6

Hi snbanerjee,

I was able to run opennebula, but after restart I am not able to run sunstone now. I am getting following page on http://frontend:9869. This seems to be some issues with ruby.

Untitled.jpg1093×633 101 KB

Please help.

7

Did you follow all the steps mentioned for ruby installation during install_gems??

yes, it seems like ruby error but something minor in /etc/sunstone.conf file

did you try to restart the daemons for opennebula and opennebula-sunstone? what is the outcome?

can you please post the history and content of sunstone.conf

8

I followed all the steps during the installation of install_gems. Some of them were getting failed due to Ruby>2.2.0. So i installed Ruby 2.3. Then again i installed and all the gems were successfully installed.

Now then I restart the system, then I am not able to open sunstone page i.e. http://frontend:9869. I am getting this error.

When I tried starting the services of opennebula and opennebula-sunstone, they are getting started fine. Screenshot below:

9

Thanks… It started working now.

10

tow thing

node and frontend talk together using hostname not IP addres
and i like to restart opennebula by …one (stop,start,restart)