August 2014 - Openstack-stable-maint

Stable check of openstack/horizon failed
by jenkins＠openstack.org 21 Aug '14

21 Aug '14

Build failed. - periodic-horizon-docs-havana http://logs.openstack.org/periodic-stable/periodic-horizon-docs-havana/c814… : SUCCESS in 6m 58s - periodic-horizon-python26-havana http://logs.openstack.org/periodic-stable/periodic-horizon-python26-havana/… : FAILURE in 4m 25s - periodic-horizon-python27-havana http://logs.openstack.org/periodic-stable/periodic-horizon-python27-havana/… : FAILURE in 5m 26s

1 0

Stable check of openstack/heat failed
by jenkins＠openstack.org 21 Aug '14

21 Aug '14

Build failed. - periodic-heat-docs-havana http://logs.openstack.org/periodic-stable/periodic-heat-docs-havana/df65e60 : SUCCESS in 4m 19s - periodic-heat-python26-havana http://logs.openstack.org/periodic-stable/periodic-heat-python26-havana/cb7… : FAILURE in 3m 34s - periodic-heat-python27-havana http://logs.openstack.org/periodic-stable/periodic-heat-python27-havana/cc2… : FAILURE in 4m 30s

1 0

Proposing Morgan Fainberg for stable maintenance
by Dolph Mathews 21 Aug '14

21 Aug '14

tl;dr I consider it an oversight that Morgan is not already on the stable maintenance team. Morgan has a demonstrated interest in (and ability to contribute towards) maintaining backwards compatibility, security and stability. I'd certainly trust his votes on stable/* branches. I don't think I need to say much more! stable/icehouse reviews: https://review.openstack.org/#/q/reviewer:%22Morgan+Fainberg+%253Cmorgan.fa… stable/havana reviews: https://review.openstack.org/#/q/reviewer:%22Morgan+Fainberg+%253Cmorgan.fa… stable/grizzly reviews: https://review.openstack.org/#/q/reviewer:%22Morgan+Fainberg+%253Cmorgan.fa… -Dolph

5 7

tox >= 1.7 breaking the world
by Ihar Hrachyshka 21 Aug '14

21 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all, fasten your seatbelts if not already. So today infra team updated tox on all the nodes to 1.7.0 which now does not enforce PYTHONSEED, breaking multiple branches around. Several projects still lack modifications for tox.ini to pass unit testing: - - heat (havana): https://review.openstack.org/109758 - - glance (havana): https://review.openstack.org/109749 - - horizon (icehouse): https://review.openstack.org/115932 - - horizon (havana): https://review.openstack.org/115926 - - keystone (icehouse): https://review.openstack.org/115941 - - keystone (havana): https://review.openstack.org/115947 It also seems that most (all?) checks for Havana and Icehouse are now broken due to tempest not being patched for the new tox version. I've cherry-picked the fix for tempest (Havana) as: https://review.openstack.org/115963 Hopefully, the latter patch will unblock gate once merged, and we'll be able to push the other patches above. Of course, some review love for the above mentioned backports is highly appreciated. ;) /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJT9el0AAoJEC5aWaUY1u57HJsH+wUQX5FfRRWiJHOSFNwFmT8M eTYHi1OyvrqrXSyOgvL6+C7djrixErDsAnVrD6k7OQC2iEPRGxIhOSMh9+ZfswfH 1tnHK//K5TKaYxigBxffW23uUNROa6w5o01CuqQaay+D4wEhxun3kzhoNTEWTdYS 9ki6Njnwy8gWsTYkhyrnnm8u6lDfTvDK0rOER4dgU5QQwggtMU6Hv2F74ip7o3PD qCdJ2yHHQqjyWIFLP2RQVbAZQGEa1AK5zCqQFoWk9yr3Y/xdya/F7LtKarOXZjPf auS/3GwC/kjzg69Oyzq2bwRyuCBMfGLpx52m8FO6VTMxR1wnwFPzT7NahqrrVvA= =cBHE -----END PGP SIGNATURE-----

2 2

Stable check of openstack/heat failed
by jenkins＠openstack.org 21 Aug '14

21 Aug '14

Build failed. - periodic-heat-docs-havana http://logs.openstack.org/periodic-stable/periodic-heat-docs-havana/0f75a1b : SUCCESS in 4m 33s - periodic-heat-python26-havana http://logs.openstack.org/periodic-stable/periodic-heat-python26-havana/826… : FAILURE in 3m 07s - periodic-heat-python27-havana http://logs.openstack.org/periodic-stable/periodic-heat-python27-havana/35a… : FAILURE in 4m 56s

2 1

Stable check of openstack/tempest failed
by jenkins＠openstack.org 20 Aug '14

20 Aug '14

Build failed. - periodic-tempest-dsvm-full-havana http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-full-havana… : SUCCESS in 35m 04s - periodic-tempest-dsvm-neutron-havana http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-neutron-hav… : SUCCESS in 33m 03s - periodic-tempest-dsvm-postgres-full-havana http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-postgres-fu… : FAILURE in 27m 07s

1 0

Stable check of openstack/keystone failed
by jenkins＠openstack.org 20 Aug '14

20 Aug '14

Build failed. - periodic-keystone-docs-havana http://logs.openstack.org/periodic-stable/periodic-keystone-docs-havana/8cd… : SUCCESS in 3m 03s - periodic-keystone-python26-havana http://logs.openstack.org/periodic-stable/periodic-keystone-python26-havana… : FAILURE in 12m 40s - periodic-keystone-python27-havana http://logs.openstack.org/periodic-stable/periodic-keystone-python27-havana… : FAILURE in 14m 49s

1 0

Stable check of openstack/horizon failed
by jenkins＠openstack.org 20 Aug '14

20 Aug '14

Build failed. - periodic-horizon-docs-havana http://logs.openstack.org/periodic-stable/periodic-horizon-docs-havana/9527… : SUCCESS in 4m 30s - periodic-horizon-python26-havana http://logs.openstack.org/periodic-stable/periodic-horizon-python26-havana/… : FAILURE in 4m 56s - periodic-horizon-python27-havana http://logs.openstack.org/periodic-stable/periodic-horizon-python27-havana/… : SUCCESS in 4m 32s

1 0

Controversial backport
by Ihar Hrachyshka 19 Aug '14

19 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all, we have a Neutron backport proposed in stable/havana that is in grey area in terms of applicability for stable branches. Located at [1]. The controversy is that it changes the default value of a configuration setting, which is generally considered as a no-go for backports. That said, it has additional aspects that may trigger the exception. Basically, the default value of the setting breaks all L3 agents we have in our tree. The failure state is an unstoppable agent resync due to incorrect gateway outside of subnet. To avoid the failure for any L3 agent that we ship, users need to change the value of that setting from default one. It's also not clear what's the value of having a gateway outside the current subnet. As of Juno, this 'feature' is obsolete and marked to be removed in Kilo. There is a change though that there are some third-party agents in the wild that support that 'feature'; in that case, changing the default value will affect them. Though we don't know whether they really exist. All in all, the 'feature' won't be available for them since Kilo, and there is no sign that its removal is controversial, so probably no one is interested in it anyway. So we have a dilemma: we may break the official stable rule of 'not introducing inconmpatible configuration changes' and in that way fix major failure scenario in Neutron; or we may leave everything as-is (=our own agents broken) to stick to the rule. My common sense tells me that we should fix our agents first, and then think about potential third-party L3 agents that possibly rely on that 'feature' being enabled by default. Hence my +2 vote. But your common sense may vary, so I'd like to hear from others on the matter. [1]: https://review.openstack.org/#/c/113129/ /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJT8wzoAAoJEC5aWaUY1u578HAH/0DB3+IpYWjKbwo9th3Phaf/ EvQEON2tMA177ufdgzO3KsWdx8VJxNzFfHU6Jl8aY9GQ3NYsg+5QYOJPcX0hHg4t g3yfrcUybDZ9roqzHZNYOUddm10Te7a+Q4Ykj2X2QiqEZC/VpxudRYDGU5O5cDpg sNeFltCp/vb/oGfX/E5dxdF5hzGd1sJQvDs+0jXfLghaCmNITvLFELN56JsUFxvr ZuzNxCnyvL7iJSHA+vWiG36jZCF/dR4eYly2CpRaQJ2Fp6ObVvkWCv+U+wtv+5bm TYl8PHpDmmGOlJPaBQn7OXAGc5eQZnkBwXGDxhRl6Fi9JF2fRSV0blSZl4rwpEA= =lxWH -----END PGP SIGNATURE-----

6 10

The order of master patches and stable backports
by Ihar Hrachyshka 19 Aug '14

19 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all, I'm concerned that in some cases [1] we merge patches in stable branches before they reach master. My understanding is that in general such approach may lead to multiple kinds of issues: 1. if a master patch is not merged in the end due to negative review feedback, we will need to cope with a stable-only patch. 2. if a master patch is modified later before its merge, we need to cope with the need to apply last minute modifications to stable branches. In the worst cases, the difference won't even be noticed, and we'll result in unneeded differences between master and stable code. 3. also, if a patch is merged into e.g. havana and not icehouse, and then a user upgrades to icehouse, he will see a regression due to the missing patch that was once fixed in a prev-stable release. We could say that there are some cases where the strict ordering of backports is not applicable, like in [1]. Quoting Thierry, " @Ihar: stable branch changes come in two categories. There are project bugfixes (which are straight backports of stuff that has to land in master to ensure we have no regression) and infrastructure patches (to keep the test infrastructure working on stable branches). The latter do NOT have to land in master: in most cases, they are not even applicable there. This is basically a branch-specific infrastructure patch to keep the stable branch running. The fact that it has a master "equivalent" is more of a coincidence. Not having that patch in master wouldn't be a regression. To answer your question, if the patch has to be reworked, that would result in subsequent patchsets. " So some cases are not affected by problem (3), but still, (1) and (2) apply. I understand that in some cases we should not wait for long, like security fixes or infrastructure being broken right now. Though the case in question is not the latter (the infrastructure will become broken only if infra team enables latest tox without making sure all the branches are properly patched). So I think the following quote by Sean is not correct: "stable/* is going to be horribly broken if this doesn't land. We could let all the stable branches die, but I don't think that's sane." ...and hence, the rush with which we're pushing those patches into stable branches is not justified. I would like to hear from all of you on the matter, and I'm going to update our stable workflow rules based on your feedback. Comments? [1]: https://review.openstack.org/#/c/109750/ /Ihar -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJT5H1TAAoJEC5aWaUY1u57pOAH/2xFM3aC6J2juFGth4Z6bPsV le0gjz7bWl1KyTgyBBkD0LsZbkOg1UdKL5Vrg5Ua4iT0j2NP+Q6QCy/AuR94cGko v5n1AuQm8YQxB1wQAmuG8xG2YAHtiX7gx/5Kw/kIZgkVdd8UHQXp28dBwu9td1+k TLo7MfJ7jde/BAlB6OLCrPC7yctog4xANrZOYw3u2tzVqh4YK7o67QceAVKcNIW6 EgVTSF+f6SyzJYMHKB58kusLFMmmNQDCdL0/gqoJ3qgPMA5ASh6ZjXzFfVggR5pT UnqEJ+0yN47RzRWaH6KlAhhVDW7EwKJwgvlggr8dwnA7ei/TYDWqunsEQ4Wcbmk= =JXuG -----END PGP SIGNATURE-----

2 3

Re: [Openstack-stable-maint] [openstack-dev] stable/havana jobs failing due to keystone bug 1357652
by Alan Pevec 17 Aug '14

17 Aug '14

2014-08-17 18:30 GMT+02:00 Nathan Kinder <nkinder(a)redhat.com>: > This requirement change was backported for stable/icehouse: > https://review.openstack.org/#/c/112337/ > It seems like the right thing to do is to propose a similar change for > stable/havana instead of reverting the keystoneclient change. We had similar issue last month, it's due to fact we test master clients against stable releases of services. Change is appropriate for stable because it changes test requirements, not runtime deps for the project itself: https://review.openstack.org/106974 Cheers, Alan

2 4

Re: [Openstack-stable-maint] [openstack-dev] stable/havana jobs failing due to keystone bug 1357652
by Matt Riedemann 17 Aug '14

17 Aug '14

On 8/17/2014 11:30 AM, Nathan Kinder wrote: > > > On 08/17/2014 09:18 AM, Nathan Kinder wrote: >> >> >> On 08/17/2014 09:08 AM, Matt Riedemann wrote: >>> I'm seeing some nova stable/havana patches failing consistently on >>> keystone bug 1357652 [1], keystone won't start due to an import error. >>> >>> I'm not seeing any recent changes for keystone in stable/havana so not >>> sure if this is an infra issue or something else. >> >> I saw this too on Friday. I believe that it's related to a new >> keystoneclient requirement for oslo.utils, which isn't in >> requirements.txt for keystone. The change either needs to be reverted, >> or a requirement needs to be added to satisfy the dependency (which may >> not be appropriate for stable releases). > > This requirement change was backported for stable/icehouse: > > https://review.openstack.org/#/c/112337/ > > It seems like the right thing to do is to propose a similar change for > stable/havana instead of reverting the keystoneclient change. > >> >> -NGK >> >>> >>> I'm also not seeing the hits in logstash for some reason, which is odd. >>> >>> [1] https://bugs.launchpad.net/keystone/+bug/1357652 >>> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev(a)lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > I've got a series of backports to global-requirements for stable/havana here [1]. [1] https://review.openstack.org/#/q/status:open+project:openstack/requirements… -- Thanks, Matt Riedemann

1 0

stable/havana jobs failing due to keystone bug 1357652
by Matt Riedemann 17 Aug '14

17 Aug '14

I'm seeing some nova stable/havana patches failing consistently on keystone bug 1357652 [1], keystone won't start due to an import error. I'm not seeing any recent changes for keystone in stable/havana so not sure if this is an infra issue or something else. I'm also not seeing the hits in logstash for some reason, which is odd. [1] https://bugs.launchpad.net/keystone/+bug/1357652 -- Thanks, Matt Riedemann

1 1

Stable check of openstack/tempest failed
by jenkins＠openstack.org 17 Aug '14

17 Aug '14

Build failed. - periodic-tempest-dsvm-full-havana http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-full-havana… : FAILURE in 9m 06s - periodic-tempest-dsvm-neutron-havana http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-neutron-hav… : FAILURE in 9m 42s - periodic-tempest-dsvm-postgres-full-havana http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-postgres-fu… : FAILURE in 8m 58s

2 1

Stable check of openstack/keystone failed
by jenkins＠openstack.org 16 Aug '14

16 Aug '14

Build failed. - periodic-keystone-docs-havana http://logs.openstack.org/periodic-stable/periodic-keystone-docs-havana/40a… : SUCCESS in 3m 43s - periodic-keystone-python26-havana http://logs.openstack.org/periodic-stable/periodic-keystone-python26-havana… : FAILURE in 10m 59s - periodic-keystone-python27-havana http://logs.openstack.org/periodic-stable/periodic-keystone-python27-havana… : FAILURE in 14m 25s

1 0

Stable check of openstack/tempest failed
by jenkins＠openstack.org 16 Aug '14

16 Aug '14

Build failed. - periodic-tempest-dsvm-full-havana http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-full-havana… : FAILURE in 10m 14s - periodic-tempest-dsvm-neutron-havana http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-neutron-hav… : FAILURE in 9m 37s - periodic-tempest-dsvm-postgres-full-havana http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-postgres-fu… : FAILURE in 8m 55s

1 0

Stable check of openstack/keystone failed
by jenkins＠openstack.org 15 Aug '14

15 Aug '14

Build failed. - periodic-keystone-docs-havana http://logs.openstack.org/periodic-stable/periodic-keystone-docs-havana/f8f… : SUCCESS in 2m 17s - periodic-keystone-python26-havana http://logs.openstack.org/periodic-stable/periodic-keystone-python26-havana… : FAILURE in 15m 27s - periodic-keystone-python27-havana http://logs.openstack.org/periodic-stable/periodic-keystone-python27-havana… : FAILURE in 14m 15s

1 0

Review request for nova backport
by Yaguang Tang 15 Aug '14

15 Aug '14

Hi all, Please help review this nova backport patch https://review.openstack.org/#/c/100632/ which fixes a bug cause live migration fails. There has been more than two weeks since last core reviewer's review. -- Tang Yaguang Canonical Ltd. | www.ubuntu.com | www.canonical.com Mobile: +86 152 1094 6968 gpg key: 0x187F664F

1 0

Stable check of openstack/tempest failed
by jenkins＠openstack.org 14 Aug '14

14 Aug '14

Build failed. - periodic-tempest-dsvm-full-havana http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-full-havana… : FAILURE in 33m 37s - periodic-tempest-dsvm-neutron-havana http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-neutron-hav… : SUCCESS in 35m 11s - periodic-tempest-dsvm-postgres-full-havana http://logs.openstack.org/periodic-stable/periodic-tempest-dsvm-postgres-fu… : FAILURE in 35m 25s

2 1

Stable check of openstack/keystone failed
by jenkins＠openstack.org 13 Aug '14

13 Aug '14

Build failed. - periodic-keystone-docs-havana http://logs.openstack.org/periodic-stable/periodic-keystone-docs-havana/b23… : SUCCESS in 2m 25s - periodic-keystone-python26-havana http://logs.openstack.org/periodic-stable/periodic-keystone-python26-havana… : FAILURE in 13m 28s - periodic-keystone-python27-havana http://logs.openstack.org/periodic-stable/periodic-keystone-python27-havana… : SUCCESS in 11m 51s

1 0

[infra] periodic python2.6 checks for havana failing
by Ihar Hrachyshka 13 Aug '14

13 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all, several periodic checks for havana are failing due to missing libffi-devel or missing rpm/yum tools on bare-centos (sic!) node. For example, see [1] (rpm/yum missing) and [2] (compile failure due to missing libffi-devel). AFAIK there is a hack to overcome some issues in gate in infra config [3], though it looks it's not enough, or the hack is wrong. I'm not involved in infra, so I lack knowledge to fix it on my own, hence I ask community for help. Ideas/fixes? /Ihar === [1]: - http://logs.openstack.org/periodic-stable/periodic-cinder-python26-havana/0… [2]: - http://logs.openstack.org/periodic-stable/periodic-glance-python26-havana/9… [3]: https://github.com/openstack-infra/config/blob/master/modules/openstack_pro… -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEcBAEBCgAGBQJT60tWAAoJEC5aWaUY1u57QdEH/0zsNqGekvNR7py/TUpTjtc3 qIE5lf0uzdrn5sr5rlOGdbJGzi1fkeHvuftMrXJnFcN5jkWnRtb979xGYR01gvmK 7IQajjwCjp4ClO2eRGFrKqc0tFPx/j0Lo7yrrLc1jZDt6LTcdrPdkZxob8QvKCfo 5RRa95XSv0fRCp8whyEGZTYlNab/DLWjvrL1COsEjZfO9KU2gT6B9KrRNpejn0yu A9dJyEFkYVVDvfbXvlY2PFdE8bilHJEkGSOp27//d7c8Oo+x9ZtNZjTZs1kqwv+4 IyMawKG+KY9WQm8BBvPRcVCSP4Z3tX9zqLjiUvQoz8ex7iK3pNqh6SCSsbb7lqI= =4MIb -----END PGP SIGNATURE-----

1 0

Stable check of openstack/ceilometer failed
by jenkins＠openstack.org 12 Aug '14

12 Aug '14

Build failed. - periodic-ceilometer-docs-havana http://logs.openstack.org/periodic-stable/periodic-ceilometer-docs-havana/0… : SUCCESS in 9m 28s - periodic-ceilometer-python26-havana http://logs.openstack.org/periodic-stable/periodic-ceilometer-python26-hava… : FAILURE in 5m 36s - periodic-ceilometer-python27-havana http://logs.openstack.org/periodic-stable/periodic-ceilometer-python27-hava… : SUCCESS in 9m 41s

1 0

Stable check of openstack/cinder failed
by jenkins＠openstack.org 12 Aug '14

12 Aug '14

Build failed. - periodic-cinder-docs-havana http://logs.openstack.org/periodic-stable/periodic-cinder-docs-havana/e7d2e… : SUCCESS in 4m 30s - periodic-cinder-python26-havana http://logs.openstack.org/periodic-stable/periodic-cinder-python26-havana/0… : FAILURE in 2s - periodic-cinder-python27-havana http://logs.openstack.org/periodic-stable/periodic-cinder-python27-havana/a… : SUCCESS in 7m 20s

1 0

Stable check of openstack/ceilometer failed
by jenkins＠openstack.org 11 Aug '14

11 Aug '14

Build failed. - periodic-ceilometer-docs-havana http://logs.openstack.org/periodic-stable/periodic-ceilometer-docs-havana/4… : SUCCESS in 8m 53s - periodic-ceilometer-python26-havana http://logs.openstack.org/periodic-stable/periodic-ceilometer-python26-hava… : FAILURE in 5m 26s - periodic-ceilometer-python27-havana http://logs.openstack.org/periodic-stable/periodic-ceilometer-python27-hava… : SUCCESS in 9m 54s

1 0

Keystone 2014.1.2
by Chuck Short 11 Aug '14

11 Aug '14

An issue was discovered with Keystone 2014.1.2 stable release tarball shortly after it was uploaded on the release page at: https://launchpad.net/keystone/icehouse/2014.1.2 A new tarball corresponding to 2014.1.2 code was generated and uploaded: md5sum: c8a85fc2ac76679eb1b674e0c2c65e36 keystone-2014.1.2.tar.gz sha1sum: c1d481d8b330e50da5ace19c23e5909c04fa1cba keystone-2014.1.2.tar.gz Please double-check that you got the right one. Regards chuck

4 6