Re: [openstack-dev] [tripleo] CI promotion blockers

[Emilien Macchi]

Here's an update on what we did the last days after merging these
blockers mentioned in the previous email:

- Ignore a failing test in tempest (workaround)
https://review.rdoproject.org/r/#/c/8/ until
https://review.openstack.org/#/c/526647/ is merged. It allowed RDO
repos to be consistent again, so we could have the latest patches in
TripleO, tested by Promotion jobs.
- scenario001 is timeouting a lot, we moved tacker/congress to
scenario007, and also removed MongoDB that was running for nothing.
- tripleo-ci-centos-7-containers-multinode was timeouting a lot, we
removed cinder and some other services already covered by scenarios,
so tripleo-ci-centos-7-containers-multinode is like ovb, testing the
minimum set of services (which is why we created this job).
- fixing an ipv6 issue in puppet-tripleo:
https://review.openstack.org/#/c/530219/

All of the above is merged.
Now the remaining blocker is to update the RDO CI layout for promotion jobs:
See https://review.rdoproject.org/r/#/c/9/ and
https://review.rdoproject.org/r/#/c/11120/
Once it merges and job runs, we should get a promotion.

Let me know any question,

On Wed, Dec 27, 2017 at 8:48 AM, Emilien Macchi  wrote:
> Just a heads-up about what we've done the last days to make progress
> and hopefully get a promotion this week:
>
> - Disabling voting on scenario001, 002 and 003. They timeout too much,
> we haven't figured out why yet but we'll look at it this week and next
> week. Hopefully we can re-enable voting today or so.
> - Kolla added Sensu support and it broke our container builds. It
> should be fixed by https://review.openstack.org/#/c/529890/ and
> https://review.openstack.org/530232
> - Keystone removed _member_ role management, so we stopped using it
> (only Member is enough): https://review.openstack.org/#/c/529849/
> - Fixup MTU configuration for CI envs: https://review.openstack.org/#/c/527249
> - Reduce memory for undercloud image convert:
> https://review.openstack.org/#/c/530137/
> - Remove policy.json default rules from Heat in THT:
> https://review.openstack.org/#/c/530225
>
> That's pretty all. Due to the lack of reviewers during the Christmas
> time, we had to land some patches ourselves. If there is any problem
> with one of them, please let us know. We're trying to maintain CI is
> good shape this week and it's a bit of a challenge ;-)
> --
> Emilien Macchi



-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] odl deployment failed due to opendaylight websocket config in haproxy

[Moshe Levi]

Hi,

So I did some investigation and it seem that the problem is with 
puppet-opendaylight.
The was a change to allow configure the ip address for the web sockets which 
uses 
restconf.cfg
 config file see [1].
This change was backport to nitrogen as well.
The carbon change for allowing configure websocket ip address is different [2] 
and uses 
10-rest-connector.xml.

In the puppet opendaylight the change that was introduce is according to carbon 
to create 
10-rest-connector.xml.
I create a patch that configure the 
restconf.cfg
 [4]. I tested and it solve  my issue. It should be backport to nitrogen as 
well.


[1] - https://git.opendaylight.org/gerrit/#/c/64242
[2] - https://git.opendaylight.org/gerrit/#/c/64602/
[3] - https://git.opendaylight.org/gerrit/#/c/64775/
[4] - https://git.opendaylight.org/gerrit/#/c/66777/




From: Janki Chhatbar [mailto:jankih...@gmail.com]
Sent: Wednesday, December 27, 2017 6:33 AM
To: OpenStack Development Mailing List (not for usage questions) 
; Moshe Levi 
Subject: Re: [openstack-dev] [tripleo] odl deployment failed due to 
opendaylight websocket config in haproxy

Hi Moshe

There is a corresponding ODL patch [1]. To verify if the rpm you are using has 
it, see if 
10-rest-connector.xml
 has a line ""



[1]. 
https://git.opendaylight.org/gerrit/#/c/64602/

On Tue, Dec 26, 2017 at 4:29 PM, Moshe Levi 
> wrote:
Hi all,

When I try to deploy tripleo with opendaylight oxygen release (we did a private 
build for master) it failed with haproxy failing
that it can't bind the opendaylight_ws: cannot bind socket see [1]. This is 
failing all the deployment as the haproxy is down.

The opendaylight_ws was introduced in this commit 
https://github.com/openstack/puppet-tripleo/commit/bc3feec75f8dc1bac6691ce8cd05a37c27aa5e42
If I will try to deploy with puppet-tripleo before that commit everything is 
passing and working.

Any Idea how to fix this? Maybe we should revert 
https://github.com/openstack/puppet-tripleo/commit/bc3feec75f8dc1bac6691ce8cd05a37c27aa5e42
 ?

Deployment works fine with this patch.

[1] -
Dec 26 10:32:56 localhost systemd: Starting HAProxy Load Balancer...
Dec 26 10:32:57 localhost haproxy-systemd-wrapper: [WARNING] 359/103257 (20629) 
: parsing [/etc/haproxy/haproxy.cfg:141] : 'option httplog' not usable with 
proxy 'nova_metadata' (needs 'mode http'). Falling back to 'option tcplog'.
Dec 26 10:32:57 localhost haproxy[20629]: Proxy cinder started.
Dec 26 10:32:57 localhost haproxy-systemd-wrapper: [WARNING] 359/103257 (20629) 
: Setting tune.ssl.default-dh-param to 1024 by default, if your workload 
permits it you should set it to at least 2048. Please set a value >= 1024 to 
make this warning disappear.
Dec 26 10:32:57 localhost haproxy-systemd-wrapper: [ALERT] 359/103257 (20629) : 
Starting proxy opendaylight_ws: cannot bind socket