2:06 p.m.
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
2:26 a.m.
On 31/07/18 21:06, iain MacDonnell wrote:
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 package was a rebuild from Fedora, and it got fixed in a later commit.
I'll push a newer build today.
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
_______________________________________________
dev mailing list
dev(a)lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/dev
To unsubscribe: dev-unsubscribe(a)lists.rdoproject.org
8:28 a.m.
New subject: Getting [WARNING]: Unable to parse /home/boris/.quickstart/hosts as an inventory source [WARNING]: No inventory was parsed, only implicit localhost is available
Attempt of remote Tripleo Quickstart deployment seems to be disabled by default
Screen output
[boris@fedora27workstation tripleo-quickstart]$ bash quickstart.sh --no-clone \
--tags all --nodes config/nodes/1ctlr_1comp.yml -p quickstart.yml $VIRTHOST
. . . . . .
. . . . . .
+++ basename /home/boris/.quickstart
++ PS1='(.quickstart) '
++ export PS1
++ alias pydoc
++ '[' -n /usr/bin/bash ']'
++ hash -r
+ export ANSIBLE_CONFIG=/home/boris/tripleo-quickstart/ansible.cfg
+ ANSIBLE_CONFIG=/home/boris/tripleo-quickstart/ansible.cfg
+ export ANSIBLE_INVENTORY=/home/boris/.quickstart/hosts
+ ANSIBLE_INVENTORY=/home/boris/.quickstart/hosts
+ export ARA_DATABASE=sqlite:////home/boris/.quickstart/ara.sqlite
+ ARA_DATABASE=sqlite:////home/boris/.quickstart/ara.sqlite
+ source /home/boris/tripleo-quickstart/ansible_ssh_env.sh
++ export OPT_WORKDIR=/home/boris/.quickstart
++ OPT_WORKDIR=/home/boris/.quickstart
++ export SSH_CONFIG=/home/boris/.quickstart/ssh.config.ansible
++ SSH_CONFIG=/home/boris/.quickstart/ssh.config.ansible
++ touch /home/boris/.quickstart/ssh.config.ansible
++ export 'ANSIBLE_SSH_ARGS=-F /home/boris/.quickstart/ssh.config.ansible'
++ ANSIBLE_SSH_ARGS='-F /home/boris/.quickstart/ssh.config.ansible'
+ '[' 0 = 0 -a -z '' ']'
+ rm -f /home/boris/.quickstart/hosts
+ '[' '' = 1 ']'
+ VERBOSITY=vv
+ '[' '!' -f /home/boris/.quickstart/playbooks/quickstart.yml ']'
+ ansible-playbook -vv /home/boris/.quickstart/playbooks/quickstart.yml -e
@/home/boris/.quickstart/config/release/queens.yml -e @config/nodes/1ctlr_1comp.yml -e
@/home/boris/.quickstart/config/general_config/minimal.yml -e
@/home/boris/.quickstart/config/environments/default_libvirt.yml -e
local_working_dir=/home/boris/.quickstart -e virthost=192.168.0.74 -t all,teardown-nodes
ansible-playbook 2.5.5
config file = /home/boris/tripleo-quickstart/ansible.cfg
configured module search path =
[u'/usr/lib/python2.7/site-packages/tripleo-quickstart/library',
u'/home/boris/.quickstart/usr/local/share/tripleo-quickstart/library',
u'/home/boris/tripleo-quickstart/library']
ansible python module location =
/home/boris/.quickstart/lib/python2.7/site-packages/ansible
executable location = /home/boris/.quickstart/bin/ansible-playbook
python version = 2.7.15 (default, May 15 2018, 15:37:31) [GCC 7.3.1 20180303 (Red Hat
7.3.1-5)]
Using /home/boris/tripleo-quickstart/ansible.cfg as config file
[WARNING]: Unable to parse /home/boris/.quickstart/hosts as an inventory source
[WARNING]: No inventory was parsed, only implicit localhost is available
[WARNING]: provided hosts list is empty, only localhost is available. Note that the
implicit
localhost does not match 'all'
Deployment shortly crashes with highlighted localhost line in the header
Do I have any chance to deploy to remote VIRTHOST versus recent
blog of Carlo Camacho suggesting VIRTHOST=127.0.0.2 ?
via tuning configs in tripleo-quickstart folder either quickstart.sh command line.
https://blogs.rdoproject.org/2018/01/rdo-community-blogposts/
Thanks.
Boris.
[https://s0.wp.com/i/blank.jpg]<https://blogs.rdoproject.org/2018/01/rd...
RDO Community Blogposts -
blogs.rdoproject.org<https://blogs.rdoproject.org/2018/01/rdo-communit...
blogs.rdoproject.org
If you’ve missed out on some of the great RDO Community content over the past few weeks
while you were on holiday, not to worry. I’ve gathered the recent blogposts right here for
you.
________________________________
![https://s0.wp.com/i/blank.jpg]<https://blogs.rdoproject.org/2018/01/rd...](https://s0.wp.com/i/blank.jpg]%3Chttps://blogs.rdoproject.org/2018/01/rdo-community-blogposts/%3E){kind=link}
2310
days inactive
2311
days old
2 comments
3 participants
participants (3)
-
Boris Derzhavets -
Haïkel Guémar -
iain MacDonnell