← Back to team overview

openstack team mailing list archive

Re: nova cloud controller and compute issues Diablo v3

 

Any reason for trying out over RHEL having so many good distros out there ?
:P

Injection issues are pretty common under RH, but first off all, you have
metadata fetching issues, AND do you have a VT capable processor on the
compute node ?, first you need to check that, and enable on the advanced
options of the BIOS, then you have to

In the COMPUTEs node you need to add this RULE :

iptables -t nat -A PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80
-j DNAT --to-destination YOURCONTROLLERIP:8773

You dont need to add a rule on the controller node . To change the br100 you
have to change it on the database

Regards

:



On Thu, Aug 18, 2011 at 8:32 PM, Steve Eastham <steve.eastham@xxxxxxxxx>wrote:

> I  recently deployed a couple of test servers for Nova; I'm using Diablo
> v3  (http://wiki.openstack.org/NovaInstall/RHEL6Notes-Diablo-3) on RHEL
> v6; here are my current issues:
>
> On the Cloud Controller node I can launch instances and I'm able to ping
> them but they don't come up cleanly because they're unable to connect to the
> 169.254.169.254 host via HTTP for metadata
>
> cloud-setup: checking
> http://169.254.169.254/2009-04-04/meta-data/instance-id
> wget: can't connect to remote host (169.254.169.254): Connection timed out
> cloud-setup: failed 1/30: up 1.38. request failed
>
> I've tried various IPTables settings but still no go.
>
> On the compute only node (1st one of hopefully many); I have larger issues:
>
> I haven't figured out how to successfully change the bridge interface for
> br100; my network uses eth0 for the monitoring/admin NW and I can't change
> that. I was able to change it OK for the cloud controller via the settings
> for the network.
> Also, when instances try to run on the compute node I receive the errors
> below; also I see that the kernel files out in the instances sub-directories
> are 0 byte files:
>
> ./instance-0000000b:
> total 4124
> -rw-r--r-- 1 root root         0 Aug 17 23:28 ramdisk
> -rw-r--r-- 1 nova nobody    1704 Aug 17 23:28 libvirt.xml
> -rw-r--r-- 1 root root         0 Aug 17 23:28 kernel
> -rw-r--r-- 1 root root   6291456 Aug 17 23:28 disk
> drwxr-xr-x 2 nova nobody    4096 Aug 17 23:28 .
> -rw-r----- 1 root root         0 Aug 17 23:29 console.logdrwxr-xr-x 7 nova
> nobody    4096 Aug 18 18:12 ..
>
> 2011-08-18 18:10:46,058 nova: called setup_basic_filtering in nwfilter
> 2011-08-18 18:10:46,059 nova: ensuring static filters
> 2011-08-18 18:10:46,194 nova.virt.libvirt_conn: instance instance-0000001c:
> Creating image
> 2011-08-18 18:10:46,292 nova.virt.libvirt_conn: instance instance-0000001c:
> injecting key into image 3
> 2011-08-18 18:11:00,652 nova.compute.disk: list index out of range
> (nova.compute.disk): TRACE: Traceback (most recent call last):
> (nova.compute.disk): TRACE:   File
> "/usr/lib/python2.6/site-packages/nova/virt/disk.py", line 82, in
> inject_data
> (nova.compute.disk): TRACE:     device = devices[0]
> (nova.compute.disk): TRACE: IndexError: list index out of range
> (nova.compute.disk): TRACE:
> 2011-08-18 18:11:00,750 nova.virt.libvirt_conn: instance instance-0000001c:
> ignoring error injecting data into image 3 (list index out of range)
> 2011-08-18 18:11:01,541 nova.exception: Uncaught exception
> (nova.exception): TRACE: Traceback (most recent call last):
> (nova.exception): TRACE:   File
> "/usr/lib/python2.6/site-packages/nova/exception.py", line 97, in wrapped
> (nova.exception): TRACE:     return f(*args, **kw)
> (nova.exception): TRACE:   File
> "/usr/lib/python2.6/site-packages/nova/virt/libvirt/connection.py", line
> 582, in spawn
> (nova.exception): TRACE:     domain = self._create_new_domain(xml)
> (nova.exception): TRACE:   File
> "/usr/lib/python2.6/site-packages/nova/virt/libvirt/connection.py", line
> 1048, in _create_new_domain
> (nova.exception): TRACE:     domain.createWithFlags(launch_flags)
> (nova.exception): TRACE:   File
> "/usr/lib64/python2.6/site-packages/libvirt.py", line 337, in
> createWithFlags
> (nova.exception): TRACE:     if ret == -1: raise libvirtError
> ('virDomainCreateWithFlags() failed', dom=self)
> (nova.exception): TRACE: libvirtError: internal error Process exited while
> reading console log output: char device redirected to /dev/pts/0
> (nova.exception): TRACE: qemu: could not load kernel
> '/var/lib/nova/instances/instance-0000001c/kernel': Inappropriate ioctl for
> device
> (nova.exception): TRACE:
> (nova.exception): TRACE:
> 2011-08-18 18:11:01,542 nova.compute.manager: Instance '28' failed to
> spawn. Is virtualization enabled in the BIOS? Details: internal error
> Process exited while reading console log output: char device redirected to
> /dev/pts/0
> qemu: could not load kernel
> '/var/lib/nova/instances/instance-0000001c/kernel': Inappropriate ioctl for
> device
> (nova.compute.manager): TRACE: Traceback (most recent call last):
> (nova.compute.manager): TRACE:   File
> "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 355, in
> _run_instance
> (nova.compute.manager): TRACE:     self.driver.spawn(instance,
> network_info, bd_mapping)
> (nova.compute.manager): TRACE:   File
> "/usr/lib/python2.6/site-packages/nova/exception.py", line 124, in wrapped
> (nova.compute.manager): TRACE:     raise Error(str(e))
> (nova.compute.manager): TRACE: Error: internal error Process exited while
> reading console log output: char device redirected to /dev/pts/0
> (nova.compute.manager): TRACE: qemu: could not load kernel
> '/var/lib/nova/instances/instance-0000001c/kernel': Inappropriate ioctl for
> device
> (nova.compute.manager): TRACE:
> (nova.compute.manager): TRACE:
>
> Any help would be greatly appreciated; next step is digging into the source
> but I want to make sure I'm setting the environment up correctly 1st.
>
> -Steve
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>

References