Open Stack

On Wed, Jun 25, 2014 at 01:36:02PM +0530, Kashyap Chamarthy wrote:
> On Tue, Jun 24, 2014 at 06:59:17PM -0400, Rob Crittenden wrote:
[. . .]

> Examining my install log[2], I only see 3 ERRORs that looked legitimate:
> 
> (1) A fatal error about 'yaml.h' header file not found:
> -------------------
> [. . .]
> 2014-06-25 06:22:38.963 |     gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python2.7 -c build/temp.linux-x86_64-2.7/check_libyaml.c -o build/temp.linux-x86_64-2.7/check_libyaml.o
> 2014-06-25 06:22:38.976 |     build/temp.linux-x86_64-2.7/check_libyaml.c:2:18: fatal error: yaml.h: No such file or directory
> 2014-06-25 06:22:38.977 |      #include <yaml.h>
> 2014-06-25 06:22:38.977 |                       ^
> 2014-06-25 06:22:38.978 |     compilation terminated.
> 2014-06-25 06:22:38.995 |     
> 2014-06-25 06:22:38.996 |     libyaml is not found or a compiler error: forcing --without-libyaml
> 2014-06-25 06:22:38.996 |     (if libyaml is installed correctly, you may need to
> 2014-06-25 06:22:38.997 |      specify the option --include-dirs or uncomment and
> 2014-06-25 06:22:38.997 |      modify the parameter include_dirs in setup.cfg)
> 2014-06-25 06:22:39.044 |    
> [. . .]
> -------------------

This was resolved after I manually installed PyYAML RPM package on my
F20 system. (Thanks Attila Fazekas for pointing that out.)

> (2) For some reason, it couldn't connect to Libvirt Hypervisor, as it
> couldn't find the Libvirt socket file.
> -------------------
> [. . .]
> 2014-06-25 06:32:08.942 | error: failed to connect to the hypervisor
> 2014-06-25 06:32:08.943 | error: no valid connection
> 2014-06-25 06:32:08.943 | error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory
> 2014-06-25 06:32:08.948 | + instances=
> [. . .]
> -------------------

This too has gone in my second DevStack run.

> 
> However, the file _does_ exist:
> 
>     $ file /var/run/libvirt/libvirt-sock
>     /var/run/libvirt/libvirt-sock: socket
> 
> 
> (3) A Neutron complaint that it couldn't find a certain qprobe network
>     namespace:
> -------------------
> [. . .]
> 2014-06-25 06:37:21.009 | + neutron-debug --os-tenant-name admin --os-username admin --os-password fedora probe-create --device-owner compute 7624586e-120d-45dd-a918-716b942407ff
> 2014-06-25 06:37:23.435 | 2014-06-25 02:37:23.434 9698 ERROR neutron.agent.linux.utils [-] 
> 2014-06-25 06:37:23.436 | Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec', 'qprobe-19193c58-a12d-4910-b38d-cd638714b1df', 'ip', '-o', 'link', 'show', 'tap19193c58-a1']
> 2014-06-25 06:37:23.436 | Exit code: 1
> 2014-06-25 06:37:23.437 | Stdout: ''
> 2014-06-25 06:37:23.437 | Stderr: 'Cannot open network namespace "qprobe-19193c58-a12d-4910-b38d-cd638714b1df": No such file or directory\n'
> [. . .]
> -------------------
> 
> Howver, running `ip netns` _does_ enumerate the above qprobe network
> namespace.

 This still persists.

 And, when I boot an instance, it's still at SCHEDULING stage with no
 useful debug messages. I'll try verbose/debug logging.

-- 
/kashyap