Open Stack

On 11/26/2015 10:52 AM, Paul Carlton wrote:
> Matt
> 
> Been working on getting devstack running in wheezy.
> 
> Hit one issue with a recent change to devstack....
> 
> 202279c4e5a222018e40883ee6500f9d26690b48 202279c
> jenkins at review.openstack.org Fri, 20 Nov 2015 22:02:18 +0000 Merge "Add
> liberasurecode-dev as a swift dependency"
> 2960bfa7f63c26d94c8aed2c3e1a6ff039b530f0 2960bfa tushar.gohad at intel.com
> Tue, 17 Nov 2015 14:06:28 -0700 Add liberasurecode-dev as a swift
> dependency
> 
> liberasurecode-dev is not available on wheezy. Since we are meant to
> support wheezy (clearly we don't
> have a CI job to test with it) I will raise a bug for this but for now I
> just checked out a version of devstack
> prior to this change.

Wheezy support is best effort.

liberasurecode-dev is really about to be a hard dependency for Swift, we
need it in our development toolchain. Someone (upstream) needs to
provide that as a backport to wheezy if running swift on wheezy is still
a thing people care about.

> tgt version on wheezy was DOA so I installed a latter version from the
> backports repo.
> Added 'deb http://ftp.de.debian.org/debian wheezy-backports main' to my
> sources.list
> 
> sudo apt-get install tgt=1:1.0.51-1~bpo70+1
> ...
> The following packages have unmet dependencies:
>  tgt : Depends: librdmacm1 (>= 1.0.16) but 1.0.15-1+deb7u1 is to be
> installed
> E: Unable to correct problems, you have held broken packages.
> pcarlton at debian7a:~$ sudo apt-cache policy librdmacm1
> librdmacm1:
>   Installed: (none)
>   Candidate: 1.0.15-1+deb7u1
>   Version table:
>      1.0.16-1~bpo70+1 0
>         100 http://ftp.de.debian.org/debian/ wheezy-backports/main amd64
> Packages
>      1.0.15-1+deb7u1 0
>         500 http://ukdebian.mirror.anlx.net/debian/ wheezy/main amd64
> Packages
> 
> sudo apt-get install librdmacm1=1.0.16-1~bpo70+1
> ...
> Setting up librdmacm1 (1.0.16-1~bpo70+1) ...
> 
> sudo apt-get install tgt=1:1.0.51-1~bpo70+1
> ...
> Setting up tgt (1:1.0.51-1~bpo70+1) ...
> [ ok ] Starting target framework daemon: tgtd.
> pcarlton at debian7a:~$ sudo apt-cache policy tgt
> tgt:
>   Installed: 1:1.0.51-1~bpo70+1
>   Candidate: 1:1.0.51-1~bpo70+1
>   Version table:
>  *** 1:1.0.51-1~bpo70+1 0
>         100 http://ftp.de.debian.org/debian/ wheezy-backports/main amd64
> Packages
>         100 /var/lib/dpkg/status
>      1:1.0.17-1 0
>         500 http://ukdebian.mirror.anlx.net/debian/ wheezy/main amd64
> Packages

The tgt packaging has always been really bad. How are things going with
Cinder making lio the default?

> 
> The final issue seems to be the version of ovs-vsctl.  Wheezy comes with
> 1.4.2.
> I first hit some issues with use of --may-exist option in devstack which
> 1.4.2 doesn't support.
> I tweak devstack code to get round that but it fails to start neutron
> agent with
> 
> 2015-11-26 15:01:07.155 92027 DEBUG neutron.agent.linux.utils [-]
> Running command (rootwrap daemon): ['ovs-vsctl', '--timeout=10',
> '--oneline', '--format=json', '--', 'set', 'Bridge', 'br-int',
> 'protocols=[OpenFlow10]'] execute_rootwrap_daemon
> /home/pcarlton/openstack/neutron/neutron/agent/linux/utils.py:100
> 2015-11-26 15:01:07.162 92027 ERROR neutron.agent.ovsdb.impl_vsctl [-]
> Unable to execute ['ovs-vsctl', '--timeout=10', '--oneline',
> '--format=json', '--', 'set', 'Bridge', 'br-int',
> 'protocols=[OpenFlow10]']. Exception: Exit code: 1; Stdin: ; Stdout: ;
> Stderr: ovs-vsctl: Bridge does not contain a column whose name matches
> "protocols"
> 
> 2015-11-26 15:01:07.163 92027 ERROR
> neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Exit
> code: 1; Stdin: ; Stdout: ; Stderr: ovs-vsctl: Bridge does not contain a
> column whose name matches "protocols"
>  Agent terminated!
> 
> I'll raise a bug for this too.
> 
> I couldn't see an obvious way to update ovs-vsctl on wheezy.
> 
> I'll ask the neutron team what the minimum version of ovs-ctl we are
> meant to support is.
> Given the US holiday we may not get answers till next week and I've
> spent long enough on this for now!

If this is really a min dep, it should be specified as such.

Wheezy is listed supported because it happened to work. There is no one
active on this front, so if no one steps up shortly I think it's
probably just better to remove it from the supported list in devstack,
so people don't expect it to work.

CI would be handy here. Without it this is going to keep happening.

	-Sean

-- 
Sean Dague
http://dague.net