On Mon, 2014-06-30 at 15:35 -0600, John Griffith wrote:
On Mon, Jun 30, 2014 at 3:17 PM, Mark McLoughlin mar...@redhat.com
wrote:
On Mon, 2014-06-30 at 12:04 -0600, John Griffith wrote:
Hey Everyone,
So I sent a note out yesterday asking about config changes
brought in
to Icehouse due to the OSLO Messaging update that went out
over the
week-end here. My initial email prior to realizing the
update that
caused the problem was OSLO Messaging update here [1].
(Periodic reminder that Oslo is not an acronym)
In the meantime I tried updating the cinder.conf sample in
Cinder's
stable Icehouse branch, but noticed that py26 doesn't seem
to pick up
the changes when running the oslo conf generation tools
against
oslo.messaging. I haven't spent any time digging into this
yet, was
hoping that perhaps somebody from the OSLO team or somewhere
else
maybe had some insight as to what's going on here.
Here's the patch I submitted that shows the failure on py26
and
success on py27 [2]. I'll get around to this eventually if
nobody
else knows anything off the top of their head.
Thanks,
John
[1]:
http://lists.openstack.org/pipermail/openstack-dev/2014-June/038926.html
[2]: https://review.openstack.org/#/c/103426/
Ok, that new cinder.conf.sample is showing changes caused by
these
oslo.messaging changes:
https://review.openstack.org/101583
https://review.openstack.org/99291
Both of those changes were first released in 1.4.0.0a1 which
is an alpha
version targeting Juno and are not available in the 1.3.0
Icehouse
version - i.e. 1.4.0.0a1 should not be used with
stable/icehouse Cinder.
It seems 1.3.0 *is* being used:
http://logs.openstack.org/26/103426/1/check/gate-cinder-python26/5c6c1dd/console.html
2014-06-29 19:17:50.154 | oslo.messaging==1.3.0
and the output is just confusing:
2014-06-29 19:17:49.900 |
--- /tmp/cinder.UtGHjm/cinder.conf.sample 2014-06-29
19:17:50.270071741 +
2014-06-29 19:17:49.900 | +++ etc/cinder/cinder.conf.sample
2014-06-29 19:10:48.396072037 +
...
2014-06-29 19:17:49.903 | +[matchmaker_redis]
2014-06-29 19:17:49.903 | +
i.e. it's showing that the file you proposed was generated
with
1.4.0.0a1 and the file generated during the test job was
generated with
1.3.0. Which is what I'd expect - the update you proposed is
not
appropriate for stable/icehouse.
So why is the py27 job passing?
http://logs.openstack.org/26/103426/1/check/gate-cinder-python27/7844c61/console.html
2014-06-29 19:21:12.875 | oslo.messaging==1.4.0.0a2
That's the problem right there - 1.4.0.0a2 should not be
getting
installed on the stable/icehouse branch. I'm not sure why it
is. Someone
on #openstack-infra could probably help figure it out.
Thanks,
Mark.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Thanks Mark... so the problem is Oslo messaging in requirements is =
in stable/icehouse [1](please note I used Oslo not OSLO).
[1]:
https://github.com/openstack/requirements/blob/stable/icehouse/global-requirements.txt#L49
Thanks for pointing me in the right direction.
Ah, yes! This is the problem:
oslo.messaging=1.3.0a9
This essentially allows *any* alpha release of oslo.messaging to be
used. We should change stable/icehouse to simply be:
oslo.messaging=1.3.0
I'm happy to do that tomorrow, but I suspect you'll get there first
Thanks,
Mark.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
