RDO Rocky M3 Test Days and Test Days Frequency
by Rain Leander
Hello all:
Over the past two RDO Community meetings [0], we've discussed the pros and
cons of having fewer official test days. Traditionally, we aim to conduct a
set of Test Days the Thursday / Friday after every official milestone based
on the upstream schedule [1] - thus M1, M2, M3, and GA. It was proposed and
accepted that we have fewer test days - M2 and GA - starting now, which
means this week's Test Days Rocky M3 is cancelled.
However, GA is 27-31 August which means that RDO's Rocky GA is normally the
following Thursday / Friday [2]. As this is the week before OpenStack PTG
[3], I propose we shift our Rocky GA Test Days to Wednesday / Thursday [4].
As always, I'm super keen for your input / opinions / questions regarding
this; please don't hesitate to reply to this thread and contribute to this
decision.
[0] https://etherpad.openstack.org/p/RDO-Meeting
[1] https://releases.openstack.org/rocky/schedule.html
[2] 6-7 September
[3] https://www.openstack.org/ptg/
[4] 5-6 September
Thanks so much,
--
K Rain Leander
OpenStack Community Liaison
Open Source and Standards Team
https://www.rdoproject.org/
http://community.redhat.com
5 years, 8 months
[Meeting] RDO meeting (2018-08-01) minutes
by Alfredo Moralejo Alonso
==============================
#rdo: RDO meeting - 2018-08-01
==============================
Meeting started by amoralej at 15:05:13 UTC. The full logs are
available athttp://eavesdrop.openstack.org/meetings/rdo_meeting___2018_08_01/2018/r...
.
Meeting summary
---------------
* roll call (amoralej, 15:05:21)
* propose we only have test days for m2 and ga for upcoming releases,
starting with rocky (not doing m3, but scheduling a ga test days)
(amoralej, 15:06:44)
* this week's test days is not happening (amoralej, 15:16:07)
* ACTION: leanderthal to research the possibility of test days 5-6
september (leanderthal, 15:17:00)
* ACTION: leanderthal email lists asking for input on m2 ga test days
only (leanderthal, 15:17:51)
* next week's chair (amoralej, 15:21:20)
* ACTION: jpena will chair the meeting on next week (amoralej,
15:22:12)
* open floor (amoralej, 15:22:25)
Meeting ended at 15:26:03 UTC.
Action items, by person
-----------------------
* jpena
* jpena will chair the meeting on next week
* leanderthal
* leanderthal to research the possibility of test days 5-6 september
* leanderthal email lists asking for input on m2 ga test days only
People present (lines said)
---------------------------
* leanderthal (36)
* amoralej (28)
* openstack (6)
* jpena (4)
* PagliaccisCloud (3)
* rbowen (2)
* radez (1)
* number80 (0)
5 years, 8 months
Rocky RPM dependency issue - pyparsing
by iain MacDonnell
Hi All,
Kicking the t[yi]res on Rocky a bit, and I've run into an(other) RPM
dependency issue. The symptom, when attempting to install
openstack-keystone, is:
Transaction check error:
file /usr/lib/python2.7/site-packages/pyparsing.py from install of
python2-pyparsing-2.1.10-3.el7.noarch conflicts with file from package
pyparsing-1.5.6-9.el7.noarch
...etc..
It appears that the RPM name changed from "pyparsing" to
"python2-pyparsing" somewhere along the way, and there's a kludgy
empty "pyparsing" RPM that "requires" "python2-pyparsing":
# rpm -qRlp /var/cache/yum/x86_64/7Server/centos7-master/packages/pyparsing-2.1.10-3.el7.noarch.rpm
python-pyparsing = 2.1.10-3.el7
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PayloadIsXz) <= 5.2-1
(contains no files)
#
This worked OK before because the "python-cmd2" RPM delivered in the
openstack-queens repo "requires" "pyparsing":
# rpm -qRp openstack-queens/python-cmd2-0.6.8-8.el7.noarch.rpm | grep parsing
pyparsing >= 2.0.1
#
but the version in centos7-master "requires" "python2-pyparsing":
# rpm -qRp /var/cache/yum/x86_64/7Server/centos7-master/packages/python2-cmd2-0.8.8-5.el7.noarch.rpm
| grep parsing
python2-pyparsing >= 2.0.1
#
and, unfortunately, that does not obsolete "pyparsing", so we end up
with the conflict.
Not sure why they didn't just have python2-pyparsing "provide" and
"obsolete" "pyparsing".
This would probably not be an issue if the OS had been installed with
centos7-master to begin with, but I don't think that that can be
assumed - 7.5 comes with pyparsing-1.5.6-9.el7.noarch.
Will openstack-rocky be delivered with a version of python2-cmd that
"requires" "pyparsing", or does this need to be fixed in
centos7-master, or ..... ? Seems it will need to provide something,
since the pyparsing in currently-shipping el7 is too old ....
~iain
5 years, 8 months