Katello nightly pipeline failed:
https://ci.theforeman.org/job/katello-3.17-rpm-pipeline/4/
foreman-pipeline-katello-3.17-centos7-install (passed)
foreman-pipeline-katello-3.17-centos7-upgrade (failed)
Seeing the following, @evgeni this mean I need to update some packages in 3.17?
fatal: [pipeline-up-katello-3.17-centos7]: FAILED! => changed=true
changes:
installed: []
updated:
- - foreman-cli
- 2.2.0-0.30.rc1.el7.noarch from foreman-koji
- - tfm-rubygem-hammer_cli_foreman
- 2.2.0-1.el7.noarch from foreman-koji
- - tfm-rubygem-rack
- 2.2.3-1.el7.noarch from foreman-koji
- - foreman
- 2.2.0-0.30.rc1.el7.noarch from foreman-koji
- - tfm-rubygem-hammer_cli_katello
- 0.23-0.1.pre.master.20200806175849git5ff20ad.el7.noarch from katello-koji
- - tfm-rubygem-apipie-bindings
- 0.4.0-1.el7.noarch from foreman-koji
- - tfm-rubygem-dynflow
- 1.4.6-1.fm2_2.el7.noarch from foreman-koji
- - python3-cffi
- 1.14.1-1.el7.x86_64 from pulpcore-repository
- - python3-urllib3
- 1.25.10-1.el7.noarch from pulpcore-repository
- - foreman-dynflow-sidekiq
- 2.2.0-0.30.rc1.el7.noarch from foreman-koji
- - tfm-rubygem-smart_proxy_pulp
- 2.1.0-3.fm2_2.el7.noarch from foreman-plugins-koji
- - python3-importlib-metadata
- 1.7.0-1.el7.noarch from pulpcore-repository
- - tfm-rubygem-hammer_cli_foreman_tasks
- 0.0.15-1.fm2_2.el7.noarch from foreman-plugins-koji
- - python3-typing
- 3.7.4.3-1.el7.noarch from pulpcore-repository
- - katello-certs-tools
- 2.7.1-2.el7.noarch from foreman-koji
- - tfm-rubygem-websocket-extensions
- 0.1.5-1.el7.noarch from foreman-koji
- - tfm-rubygem-sprockets
- 4.0.2-1.el7.noarch from foreman-koji
- - python3-dotenv
- 0.14.0-1.el7.noarch from pulpcore-repository
- - python3-django
- 2.2.15-1.el7.noarch from pulpcore-repository
- - python3-openpyxl
- 3.0.4-1.el7.noarch from pulpcore-repository
- - tfm-rubygem-multi_json
- 1.14.1-2.el7.noarch from foreman-koji
- - python3-idna
- 2.10-1.el7.noarch from pulpcore-repository
- - tfm-rubygem-katello
- 3.17.0-0.1.rc1.el7.noarch from katello-koji
- - tfm-rubygem-hammer_cli
- 2.2.0-1.el7.noarch from foreman-koji
- - tfm-rubygem-foreman-tasks
- 2.0.2-1.fm2_2.el7.noarch from foreman-plugins-koji
- - foreman-postgresql
- 2.2.0-0.30.rc1.el7.noarch from foreman-koji
- - foreman-debug
- 2.2.0-0.30.rc1.el7.noarch from foreman-koji
- - python3-semantic-version
- 2.8.5-1.el7.noarch from pulpcore-repository
- - python3-diff-match-patch
- 20200713-1.el7.noarch from pulpcore-repository
- - python3-requests
- 2.24.0-1.el7.noarch from pulpcore-repository
- - tfm-rubygem-gitlab-sidekiq-fetcher
- 0.6.0-1.el7.noarch from foreman-koji
- - katello-debug
- 3.17.0-0.1.rc1.el7.noarch from katello-koji
- - tfm-runtime
- 6.1-3.el7.x86_64 from foreman-koji
- - python3-subscription-manager-rhsm
- 1.27.5-2.el7.x86_64 from pulpcore-repository
- - python3-rq
- 1.4.3-1.el7.noarch from pulpcore-repository
- - foreman-proxy
- 2.2.0-0.4.rc1.el7.noarch from foreman-koji
- - python3-box
- 5.1.0-1.el7.noarch from pulpcore-repository
- - tfm-rubygem-apipie-dsl
- 2.2.9-1.el7.noarch from foreman-koji
- - python3-pycryptodomex
- 3.9.8-1.el7.x86_64 from pulpcore-repository
- - python3-yarl
- 1.5.1-1.el7.x86_64 from pulpcore-repository
- - foreman-selinux
- 2.2.0-0.2.rc1.el7.noarch from foreman-koji
- - foreman-service
- 2.2.0-0.30.rc1.el7.noarch from foreman-koji
- - tfm-rubygem-excon
- 0.76.0-1.el7.noarch from foreman-koji
msg: |2-
Transaction check error:
file /usr/lib/python3.6/site-packages/dateutil/__init__.py from install of python3-dateutil-2.8.1-1.el7.noarch conflicts with file from package python36-dateutil-1:2.4.2-5.el7.noarch
file /usr/lib/python3.6/site-packages/dateutil/zoneinfo/__init__.py from install of python3-dateutil-2.8.1-1.el7.noarch conflicts with file from package python36-dateutil-1:2.4.2-5.el7.noarch
file /usr/lib/python3.6/site-packages/dateutil/__pycache__/__init__.cpython-36.pyc from install of python3-dateutil-2.8.1-1.el7.noarch conflicts with file from package python36-dateutil-1:2.4.2-5.el7.noarch
file /usr/lib/python3.6/site-packages/dateutil/zoneinfo/__pycache__/__init__.cpython-36.pyc from install of python3-dateutil-2.8.1-1.el7.noarch conflicts with file from package python36-dateutil-1:2.4.2-5.el7.noarch
file /usr/lib/python3.6/site-packages/dateutil/__pycache__/easter.cpython-36.pyc from install of python3-dateutil-2.8.1-1.el7.noarch conflicts with file from package python36-dateutil-1:2.4.2-5.el7.noarch
file /usr/lib/python3.6/site-packages/dateutil/__pycache__/relativedelta.cpython-36.pyc from install of python3-dateutil-2.8.1-1.el7.noarch conflicts with file from package python36-dateutil-1:2.4.2-5.el7.noarch
file /usr/lib/python3.6/site-packages/dateutil/__pycache__/rrule.cpython-36.pyc from install of python3-dateutil-2.8.1-1.el7.noarch conflicts with file from package python36-dateutil-1:2.4.2-5.el7.noarch
file /usr/lib/python3.6/site-packages/dateutil/__pycache__/tzwin.cpython-36.pyc from install of python3-dateutil-2.8.1-1.el7.noarch conflicts with file from package python36-dateutil-1:2.4.2-5.el7.noarch
file /usr/lib/python3.6/site-packages/dateutil/easter.py from install of python3-dateutil-2.8.1-1.el7.noarch conflicts with file from package python36-dateutil-1:2.4.2-5.el7.noarch
file /usr/lib/python3.6/site-packages/dateutil/relativedelta.py from install of python3-dateutil-2.8.1-1.el7.noarch conflicts with file from package python36-dateutil-1:2.4.2-5.el7.noarch
file /usr/lib/python3.6/site-packages/dateutil/rrule.py from install of python3-dateutil-2.8.1-1.el7.noarch conflicts with file from package python36-dateutil-1:2.4.2-5.el7.noarch
file /usr/lib/python3.6/site-packages/dateutil/tzwin.py from install of python3-dateutil-2.8.1-1.el7.noarch conflicts with file from package python36-dateutil-1:2.4.2-5.el7.noarch
Nothing should depend on python36-dateutil from EPEL anymore: https://github.com/theforeman/foreman-packaging/pull/5586
Ooh, that’s an upgrade… And its was installed before.
But why weren’t the nighly upgrades not broken?
Anyways, this will need an Obsoletes in our dateutil.
Thanks! I opened (https://github.com/theforeman/foreman-packaging/pull/5698) to try and capture that change to allow pulling it back. We have actually been seeing this on Katello nightly upgrades as well.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.