Hi,
thanks for your quick answer. I have upgraded from Katello 3.18. So many upgrade steps in between.
proxy.log (23.6 KB)
messages.log (2.7 MB)
I uploaded the foreman-proxy log and /var/log/messages from one of the proxies.
Cheers,
Oliver
Jul 26 10:49:58 gedalvl01 pulpcore-worker-1: pulp [38a75413-a394-4045-bba4-b88cfbe2466c]: pulpcore.tasking.pulpcore_worker:INFO: Task 8af03043-05c8-478f-a440-ffa6328937d7 failed (null value in column "issued_date" violates not-null constraint
This seems to be causing the failure. Is this SUSE-SLE-Module-Legacy-15-SP1-2020-1059 an errata? Do you see an issued date for this on the foreman server?
I’m pretty sure it is errata. I can’t find it in Katello. There is plenty of other errata available for SLES.
Ok, just did a fresh install of Katello 4.4 + Proxy and the problem is the same:
[root@katellonew4pxy ~]# tail -f /var/log/messages | grep -i fail
Jul 29 10:48:19 katellonew4pxy pulpcore-worker-2: pulp [66ea67d5-ea3e-456b-9fc7-59fa8adcd0a9]: pulpcore.tasking.pulpcore_worker:INFO: Task 8a819802-c80d-444c-86e0-bb2efe304f43 failed (null value in column “issued_date” violates not-null constraint
Jul 29 10:48:19 katellonew4pxy pulpcore-worker-2: DETAIL: Failing row contains (92f54d25-6a97-46b0-8e7e-999b71a60306, SUSE-SLE-Module-Legacy-15-SP1-2020-774, null,
Jul 29 10:48:20 katellonew4pxy pulpcore-worker-1: pulp [66ea67d5-ea3e-456b-9fc7-59fa8adcd0a9]: pulpcore.tasking.pulpcore_worker:INFO: Task 143cf2a6-cdcb-458e-be91-dca7b4f3da2b failed (null value in column “issued_date” violates not-null constraint
Jul 29 10:48:20 katellonew4pxy pulpcore-worker-1: DETAIL: Failing row contains (dd31da0e-6dfd-42b0-b178-49e4fb1f2473, SUSE-SLE-Module-Legacy-15-SP1-2020-774, null,
Jul 29 10:51:00 katellonew4pxy pulpcore-worker-2: pulp [5a4009f4-073a-4fbb-b913-b1a3c53a5fd8]: pulpcore.tasking.pulpcore_worker:INFO: Task 4a3b1ed0-cd88-4154-a253-13e38ee5aefb failed (null value in column “issued_date” violates not-null constraint
Jul 29 10:51:00 katellonew4pxy pulpcore-worker-2: DETAIL: Failing row contains (f329ecd4-a810-4d5f-80aa-93ab9d70da57, SUSE-SLE-Module-Legacy-15-SP1-2020-774, null,
Jul 29 10:51:00 katellonew4pxy pulpcore-worker-1: pulp [5a4009f4-073a-4fbb-b913-b1a3c53a5fd8]: pulpcore.tasking.pulpcore_worker:INFO: Task adc24118-d9eb-4c62-b890-c110a0f75ca0 failed (null value in column “issued_date” violates not-null constraint
Jul 29 10:51:00 katellonew4pxy pulpcore-worker-1: DETAIL: Failing row contains (70220f32-85c2-4722-a42c-ea8b120bd465, SUSE-SLE-Module-Legacy-15-SP1-2020-774, null,
Any help would be highly appreciated. 
Also under Katello 4.5. The same problem. I raised an issue on the SCC github page.
I think this is caused by this pulp_rpm issue: https://github.com/pulp/pulp_rpm/issues/2528
Looks like this was fixed in pulp_rpm 3.17.7.
pulp_rpm 3.17 is available as far back as Katello 4.3, but only at version 3.17.5.
If this could be updated here to include the latest pulp_rpm bugfix release, then this issue should go away after the next yum update.
Not 100% certain this is the same issue, but it does seem very similar.
Ok, so I noticed that there is now an updated version of the package available. So I updated the main Katello server and two proxies. All machines are now showing problems with the pulp core services:
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: Traceback (most recent call last):
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: File “/opt/theforeman/tfm-pulpcore/root/usr/bin/pulpcore-worker”, line 11, in
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: load_entry_point(‘pulpcore==3.18.5’, ‘console_scripts’, ‘pulpcore-worker’)()
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: File “/opt/theforeman/tfm-pulpcore/root/usr/lib/python3.8/site-packages/click/core.py”, line 1128, in call
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: return self.main(*args, **kwargs)
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: File “/opt/theforeman/tfm-pulpcore/root/usr/lib/python3.8/site-packages/click/core.py”, line 1053, in main
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: rv = self.invoke(ctx)
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: File “/opt/theforeman/tfm-pulpcore/root/usr/lib/python3.8/site-packages/click/core.py”, line 1395, in invoke
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: return ctx.invoke(self.callback, **ctx.params)
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: File “/opt/theforeman/tfm-pulpcore/root/usr/lib/python3.8/site-packages/click/core.py”, line 754, in invoke
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: return __callback(*args, **kwargs)
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: File “/opt/theforeman/tfm-pulpcore/root/usr/lib/python3.8/site-packages/pulpcore/tasking/entrypoint.py”, line 28, in worker
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: NewPulpWorker().run_forever()
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: File “/opt/theforeman/tfm-pulpcore/root/usr/lib/python3.8/site-packages/pulpcore/tasking/pulpcore_worker.py”, line 368, in run_forever
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: self.sleep()
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: File “/opt/theforeman/tfm-pulpcore/root/usr/lib/python3.8/site-packages/pulpcore/tasking/pulpcore_worker.py”, line 282, in sleep
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: connection.connection.poll()
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: psycopg2.OperationalError: server closed the connection unexpectedly
Aug 05 12:54:27 gedadvl02.a.space.corp pulpcore-worker-1[913]: This probably means the server terminated abnormally
Is there anything known about this issue?
Did you update just the one package (from what version to what version) or all available updates? Have you rerun foreman-installer after running yum upgrade? Have you tried simply restarting the services (foreman-maintain service restart)?
Hi,
i did a complete yum update:
====================================================================================================================================================================================================================
Package Arch Version Repository SizeUpdating:
puppet-agent x86_64 6.28.0-1.el7 puppet6 26 M
puppetserver noarch 6.20.0-1.el7 puppet6 75 M
rh-postgresql12-postgresql x86_64 12.11-1.el7 centos-sclo-rh 1.5 M
rh-postgresql12-postgresql-libs x86_64 12.11-1.el7 centos-sclo-rh 310 k
rh-postgresql12-postgresql-server x86_64 12.11-1.el7 centos-sclo-rh 5.4 M
rh-postgresql12-postgresql-server-syspaths x86_64 12.11-1.el7 centos-sclo-rh 44 k
rh-postgresql12-postgresql-syspaths x86_64 12.11-1.el7 centos-sclo-rh 43 k
tfm-pulpcore-python3-django-readonly-field noarch 1.1.1-1.el7 pulpcore 14 k
tfm-pulpcore-python3-jsonschema noarch 4.6.0-1.el7 pulpcore 145 k
tfm-pulpcore-python3-pulp-rpm noarch 3.17.7-1.el7 pulpcore 391 k
tfm-rubygem-smart_proxy_remote_execution_ssh noarch 0.7.1-1.fm3_3.el7 foreman-plugins 42 kTransaction Summary
Upgrade 11 Packages
Total download size: 109 M
Is this ok [y/d/N]:
Right after the update I ran a health check:
[root@gedapvl05 ~]# foreman-maintain health check
Running ForemanMaintain::Scenario::FilteredScenarioCheck to verify no empty CA cert requests exist: [OK]
Check whether all services are running: [FAIL]
Following services are not running: pulpcore-worker@1.service, pulpcore-worker@2.service, pulpcore-worker@3.service, pulpcore-worker@4.serviceContinue with step [Restart applicable services]?, [y(yes), n(no)] n
Check whether all services are running using the ping call: [OK]Scenario [ForemanMaintain::Scenario::FilteredScenario] failed.
The following steps ended up in failing state:
[services-up]
Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist=“services-up”
And I did run foreman-installer afterwards, this failed with an error:
[root@gedapvl05 ~]# foreman-installer
2022-08-08 07:24:20 [NOTICE] [root] Loading installer configuration. This will take some time.
2022-08-08 07:24:25 [NOTICE] [root] Running installer with log based terminal output at level NOTICE.
2022-08-08 07:24:25 [NOTICE] [root] Use -l to set the terminal output log level to ERROR, WARN, NOTICE, INFO, or DEBUG. See --full-help for definitions.
2022-08-08 07:24:38 [NOTICE] [configure] Starting system configuration.
2022-08-08 07:24:48 [NOTICE] [configure] 250 configuration steps out of 1597 steps complete.
2022-08-08 07:24:56 [NOTICE] [configure] 500 configuration steps out of 1601 steps complete.
2022-08-08 07:24:59 [NOTICE] [configure] 750 configuration steps out of 1605 steps complete.
2022-08-08 07:24:59 [NOTICE] [configure] 1000 configuration steps out of 1607 steps complete.
2022-08-08 07:24:59 [NOTICE] [configure] 1250 configuration steps out of 1943 steps complete.
2022-08-08 07:25:00 [NOTICE] [configure] 1500 configuration steps out of 2322 steps complete.
2022-08-08 07:25:00 [NOTICE] [configure] 1750 configuration steps out of 2322 steps complete.
2022-08-08 07:25:01 [NOTICE] [configure] 2000 configuration steps out of 2626 steps complete.
2022-08-08 07:25:01 [NOTICE] [configure] 2250 configuration steps out of 2672 steps complete.
2022-08-08 07:25:18 [NOTICE] [configure] 2500 configuration steps out of 2672 steps complete.
2022-08-08 07:25:19 [ERROR ] [configure] 'pulpcore-manager migrate --noinput' returned 1 instead of one of [0]
2022-08-08 07:25:19 [ERROR ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[migrate --noinput]/Exec[pulpcore-manager migrate --noinput]/returns: change from 'notrun' to ['0'] failed: 'pulpcore-manager migrate --noinput' returned 1 instead of one of [0]
2022-08-08 07:25:24 [NOTICE] [configure] System configuration has finished.
There were errors detected during install.
Please address the errors and re-run the installer to ensure the system is properly configured.
Failing to do so is likely to result in broken functionality.
The full log is at /var/log/foreman-installer/foreman-proxy-content.log
ERRORs of the /var/log/foreman-installer/foreman-proxy-content.logLog file:
[root@gedapvl05 ~]# grep ERROR /var/log/foreman-installer/foreman-proxy-content.log
2022-08-08 07:24:25 [NOTICE] [root] Use -l to set the terminal output log level to ERROR, WARN, NOTICE, INFO, or DEBUG. See --full-help for definitions.
2022-08-08 07:24:42 [DEBUG ] [configure] -D DEFAULT_ERRORLOG="logs/error_log"
2022-08-08 07:25:19 [ERROR ] [configure] 'pulpcore-manager migrate --noinput' returned 1 instead of one of [0]
2022-08-08 07:25:19 [ERROR ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[migrate --noinput]/Exec[pulpcore-manager migrate --noinput]/returns: change from 'notrun' to ['0'] failed: 'pulpcore-manager migrate --noinput' returned 1 instead of one of [0]
Running pulpcore-manager migrate --noinput manually throws an error:
[root@gedapvl05 ~]# pulpcore-manager migrate --noinput
Traceback (most recent call last):
File "/opt/rh/rh-python38/root/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 583, in _build_master
ws.require(__requires__)
File "/opt/rh/rh-python38/root/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 900, in require
needed = self.resolve(parse_requirements(requirements))
File "/opt/rh/rh-python38/root/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 791, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (importlib-resources 0.0.0 (/opt/theforeman/tfm-pulpcore/root/usr/lib/python3.8/site-packages), Requirement.parse('importlib_resources>=1.4.0'), {'jsonschema'})
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/theforeman/tfm-pulpcore/root/usr/bin/pulpcore-manager", line 6, in <module>
from pkg_resources import load_entry_point
File "/opt/rh/rh-python38/root/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3252, in <module>
def _initialize_master_working_set():
File "/opt/rh/rh-python38/root/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3235, in _call_aside
f(*args, **kwargs)
File "/opt/rh/rh-python38/root/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3264, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/opt/rh/rh-python38/root/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 585, in _build_master
return cls._build_from_requirements(__requires__)
File "/opt/rh/rh-python38/root/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 598, in _build_from_requirements
dists = ws.resolve(reqs, Environment())
File "/opt/rh/rh-python38/root/usr/lib/python3.8/site-packages/pkg_resources/__init__.py", line 786, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'importlib_resources>=1.4.0' distribution was not found and is required by jsonschema
Systemctl pulp services:
[root@gedapvl05 ~]# systemctl | grep -i pulp
var-lib-pulp.mount loaded active mounted /var/lib/pulp
pulp_celerybeat.service loaded active running Pulp's Celerybeat
pulp_resource_manager.service loaded active running Pulp Resource Manager
pulp_streamer.service loaded active running The Pulp lazy content loading streamer
pulp_worker-0.service loaded active running Pulp Worker #0
pulp_worker-1.service loaded active running Pulp Worker #1
pulp_worker-2.service loaded active running Pulp Worker #2
pulp_worker-3.service loaded active running Pulp Worker #3
pulp_workers.service loaded active exited Pulp Celery Workers
pulpcore-api.service loaded active running Pulp API Server
pulpcore-content.service loaded active running Pulp Content App
pulpcore-worker@1.service loaded activating auto-restart Pulp Worker
pulpcore-worker@2.service loaded activating auto-restart Pulp Worker
pulpcore-worker@3.service loaded activating auto-restart Pulp Worker
pulpcore-worker@4.service loaded activating auto-restart Pulp Worker
system-pulpcore\x2dworker.slice loaded active active system-pulpcore\x2dworker.slice
pulpcore-api.socket loaded active running Pulp API Server socket
pulpcore-content.socket loaded active running Pulp Content App socket
So it seems there is a missing dependeny?
pkg_resources.DistributionNotFound: The 'importlib_resources>=1.4.0' distribution was not found and is required by jsonschema
Cheers,
Oliver
I am pinging the @packaging team. Also @Odilhao should probably be added to the @packaging list.
This definitely looks like the pulpcore 3.16 repo is missing a dependency (and is by extension in an inconsistent state)!
This should be resolved by:
However, we’re suffering from an issue in our pipelines which blocks it from publishing.
Thanks. Then I just wait until this fix is published.
Hi, we have the package in our koji, if you want to install it manually, until our CI is working again.
Hi,
ok now I’m confused. On my system I have a newer package installed:
[root@gedapvl05 ~]# rpm -Uvh tfm-pulpcore-python3-importlib-resources-5.0.0-3.el7.noarch.rpm
Preparing... ################################# [100%]
package tfm-pulpcore-python3-importlib-resources-5.4.0-2.el7.noarch (which is newer than tfm-pulpcore-python3-importlib-resources-5.0.0-3.el7.noarch) is already installed
[root@gedapvl05 ~]# yum info tfm-pulpcore-python3-importlib-resources-5.4.0-2.el7.noarch
Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-manager
Loading mirror speeds from cached hostfile
* base: mirror.plusserver.com
* centos-sclo-rh: ftp.rezopole.net
* epel: it1.mirror.vhosting-it.com
* extras: ftp.rezopole.net
* updates: ftp.rezopole.net
Installed Packages
Name : tfm-pulpcore-python3-importlib-resources
Arch : noarch
Version : 5.4.0
Release : 2.el7
Size : 223 k
Repo : installed
From repo : pulpcore
Summary : Read resources from Python packages
URL : https://github.com/python/importlib_resources
License : Apache2
Description : Read resources from Python packages
Never mind. I force updated the package and now foreman-installer works just fine.
root@gedapvl05 ~]# rpm -Uvh tfm-pulpcore-python3-importlib-resources-5.0.0-3.el7.noarch.rpm --force
Preparing... ################################# [100%]
Updating / installing...
1:tfm-pulpcore-python3-importlib-re################################# [ 50%]
Cleaning up / removing...
2:tfm-pulpcore-python3-importlib-re################################# [100%]
(reverse-i-search)`install': yum ^Cstall http://koji.katello.org/releases/yum/pulpcore-3.16/el7/x86_64/tfm-pulpcore-python3-importlib-resources-5.0.0-3.el7.noarch.rpm
[root@gedapvl05 ~]# foreman-installer
2022-08-08 16:20:03 [NOTICE] [root] Loading installer configuration. This will take some time.
2022-08-08 16:20:08 [NOTICE] [root] Running installer with log based terminal output at level NOTICE.
2022-08-08 16:20:08 [NOTICE] [root] Use -l to set the terminal output log level to ERROR, WARN, NOTICE, INFO, or DEBUG. See --full-help for definitions.
2022-08-08 16:20:15 [NOTICE] [configure] Starting system configuration.
2022-08-08 16:20:25 [NOTICE] [configure] 250 configuration steps out of 1597 steps complete.
2022-08-08 16:20:34 [NOTICE] [configure] 500 configuration steps out of 1601 steps complete.
2022-08-08 16:20:36 [NOTICE] [configure] 750 configuration steps out of 1605 steps complete.
2022-08-08 16:20:36 [NOTICE] [configure] 1000 configuration steps out of 1607 steps complete.
2022-08-08 16:20:37 [NOTICE] [configure] 1250 configuration steps out of 1943 steps complete.
2022-08-08 16:20:37 [NOTICE] [configure] 1500 configuration steps out of 2322 steps complete.
2022-08-08 16:20:37 [NOTICE] [configure] 1750 configuration steps out of 2322 steps complete.
2022-08-08 16:20:38 [NOTICE] [configure] 2000 configuration steps out of 2626 steps complete.
2022-08-08 16:20:38 [NOTICE] [configure] 2250 configuration steps out of 2672 steps complete.
2022-08-08 16:20:38 [NOTICE] [configure] 2500 configuration steps out of 2672 steps complete.
2022-08-08 16:20:52 [NOTICE] [configure] System configuration has finished.
Success!
* Foreman Proxy is running at https://gedapvl05.a.space.corp:9090
The full log is at /var/log/foreman-installer/foreman-proxy-content.log
I checked and the newer version came from the pulpcore repo:
[root@gedapvl05 ~]# yum search tfm-pulpcore-python3-importlib-resources --show-duplicates
Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-manager
Loading mirror speeds from cached hostfile
* base: mirror.plusserver.com
* centos-sclo-rh: ftp.rezopole.net
* epel: it1.mirror.vhosting-it.com
* extras: ftp.rezopole.net
* updates: ftp.rezopole.net
========================================================================================================================================================================= N/S matched: tfm-pulpcore-python3-importlib-resources =========================================================================================================================================================================
tfm-pulpcore-python3-importlib-resources-5.0.0-3.el7.noarch : Read resources from Python packages
tfm-pulpcore-python3-importlib-resources-5.4.0-2.el7.noarch : Read resources from Python packages
Name and summary matches only, use "search all" for everything.
[root@gedapvl05 ~]# yum info tfm-pulpcore-python3-importlib-resources-5.4.0-2.el7.noarch
Loaded plugins: fastestmirror, product-id, search-disabled-repos, subscription-manager
Loading mirror speeds from cached hostfile
* base: mirror.plusserver.com
* centos-sclo-rh: ftp.rezopole.net
* epel: it1.mirror.vhosting-it.com
* extras: ftp.rezopole.net
* updates: ftp.rezopole.net
Available Packages
Name : tfm-pulpcore-python3-importlib-resources
Arch : noarch
Version : 5.4.0
Release : 2.el7
Size : 60 k
Repo : pulpcore/x86_64
Summary : Read resources from Python packages
URL : https://github.com/python/importlib_resources
License : Apache2
Description : Read resources from Python packages
Ok, but the initial problem with the SLES 15.x packages is not solved. 
null value in column "issued_date" violates not-null constraint
DETAIL: Failing row contains (c25662fc-ffa5-4e6d-b338-563c294d16dc, SUSE-SLE-Module-Legacy-15-SP1-2020-1059, null, This update for open-iscsi fixes the following issues:
- Avoid ..., null, maint-coord@suse.de, stable, Recommended update for open-iscsi, , 1, recommended, moderate, , SUSE Updates SLE-Module-Legacy 15-SP1 x86 64, , , 42e0608bd70f9fa94437d89c7f014f8bdee4ec1bb230e96b3750bf2172cdd70d, f).
Could not lookup a publication_href for repo 13565null value in column "issued_date" violates not-null constraint
DETAIL: Failing row contains (60d31311-8edb-4c63-a71d-f1d6e704fea4, SUSE-SLE-Module-Legacy-15-SP1-2020-1059, null, This update for open-iscsi fixes the following issues:
- Avoid ..., null, maint-coord@suse.de, stable, Recommended update for open-iscsi, , 1, recommended, moderate, , SUSE Updates SLE-Module-Legacy 15-SP1 x86 64, , , 42e0608bd70f9fa94437d89c7f014f8bdee4ec1bb230e96b3750bf2172cdd70d, f).
Could not lookup a publication_href for repo 13260null value in column "issued_date" violates not-null constraint
DETAIL: Failing row contains (1d45772e-d761-4a1a-9f80-8ca029f059b3, SUSE-SLE-Module-CAP-Tools-15-SP1-2019-1220, null, This update for cf-cli fixes the following issues:
cf-cli was u..., null, maint-coord@suse.de, stable, Security update for cf-cli, , 1, security, moderate, , SUSE Updates SLE-Module-CAP-Tools 15-SP1 x86 64, , , 1184cf6de95573276e30a2246b2d09c28e248167a4eec7222f2dd66a4919c7bb, f).
Could not lookup a publication_href for repo 12957null value in column "issued_date" violates not-null constraint
DETAIL: Failing row contains (e109ed5d-ec24-443c-905e-05ec87b7c3b5, SUSE-SLE-Module-Legacy-15-SP1-2020-1059, null, This update for open-iscsi fixes the following issues:
- Avoid ..., null, maint-coord@suse.de, stable, Recommended update for open-iscsi, , 1, recommended, moderate, , SUSE Updates SLE-Module-Legacy 15-SP1 x86 64, , , 42e0608bd70f9fa94437d89c7f014f8bdee4ec1bb230e96b3750bf2172cdd70d, f).
Could not lookup a publication_href for repo 14204null value in column "issued_date" violates not-null constraint
DETAIL: Failing row contains (de27365c-e922-46e6-a0ff-7e157aa7180f, SUSE-SLE-Module-Legacy-15-SP1-2020-1059, null, This update for open-iscsi fixes the following issues:
- Avoid ..., null, maint-coord@suse.de, stable, Recommended update for open-iscsi, , 1, recommended, moderate, , SUSE Updates SLE-Module-Legacy 15-SP1 x86 64, , , 42e0608bd70f9fa94437d89c7f014f8bdee4ec1bb230e96b3750bf2172cdd70d, f).
Could not lookup a publication_href for repo 13341null value in column "issued_date" violates not-null constraint
DETAIL: Failing row contains (b3c050d3-1d70-42fe-a54c-75759b8ee626, SUSE-SLE-Module-Legacy-15-SP1-2020-1059, null, This update for open-iscsi fixes the following issues:
- Avoid ..., null, maint-coord@suse.de, stable, Recommended update for open-iscsi, , 1, recommended, moderate, , SUSE Updates SLE-Module-Legacy 15-SP1 x86 64, , , 42e0608bd70f9fa94437d89c7f014f8bdee4ec1bb230e96b3750bf2172cdd70d, f).
Could not lookup a publication_href for repo 14071null value in column "issued_date" violates not-null constraint
DETAIL: Failing row contains (e049793e-3183-4c5e-945c-d83438758d42, SUSE-SLE-Module-Legacy-15-SP1-2020-1059, null, This update for open-iscsi fixes the following issues:
- Avoid ..., null, maint-coord@suse.de, stable, Recommended update for open-iscsi, , 1, recommended, moderate, , SUSE Updates SLE-Module-Legacy 15-SP1 x86 64, , , 42e0608bd70f9fa94437d89c7f014f8bdee4ec1bb230e96b3750bf2172cdd70d, f).
Could not lookup a publication_href for repo 13515null value in column "issued_date" violates not-null constraint
DETAIL: Failing row contains (395637ee-f58b-4623-9794-895957f7c454, SUSE-SLE-Module-Transactional-Server-15-SP1-2019-2765, null, This update for transactional-update contains the following fixe..., null, maint-coord@suse.de, stable, Recommended update for transactional-update, , 1, recommended, moderate, , SUSE Updates SLE-Module-Transactional-Server 15-SP1 x86 64, , , 824bb969888dcf7ce685750bdf6dcffd1137e92993b2e5d0dfefff9f952aebd8, f).
Could not lookup a publication_href for repo 12962null value in column "issued_date" violates not-null constraint
DETAIL: Failing row contains (dd74f257-a1e7-4a9e-906b-c1988cffd5a6, SUSE-SLE-Product-SLES-15-SP1-2020-2662, null, This update for release-notes-sles fixes the following issue
I have not yet tried to sync the repos and a content-view publish but will try this now…
I just checked again and my repo for pulpcore points to version 3.18 not 3.16. I also checked on a fresh install of Katello 4.5 and here it is also 3.18.
I’m running on CentOS 7 and Katello 4.5 / Foreman 3.3
Ok, so I synced the SLES 15.1 repos again, published a new content-view but the problem still remains:
Aug 9 07:13:39 gedapvl05 pulpcore-worker-3: DETAIL: Failing row contains (c141099e-a4f0-495f-b6c2-47a446ad492f, SUSE-SLE-Module-Legacy-15-SP1-2020-1059, null, This update for open-iscsi fixes the following issues:
Aug 9 07:13:40 gedapvl05 qdrouterd: SERVER (info) [C186395] Connection to katello.a.space.corp:5646 failed: proton:io Connection refused - disconnected katello.a.space.corp:5646
Aug 9 07:13:42 gedapvl05 pulpcore-worker-4: pulp [a62b85ab-a7ae-40ae-a7cb-00668392ec1c]: pulpcore.tasking.pulpcore_worker:INFO: Task cdd2e141-8592-4eef-834f-4dfc28e4016d failed (null value in column "issued_date" violates not-null constraint
Aug 9 07:13:42 gedapvl05 pulpcore-worker-4: DETAIL: Failing row contains (07cc1beb-f0bd-4c4b-a60f-be96fc4ac1ec, SUSE-SLE-Module-Python2-15-SP1-2020-1929, null, This update for python-numpy fixes the following issues:
What version of tfm-pulpcore-python3-pulp-rpm do you have installed? If it is at least 3.17.7, then that includes the fix I suspected would fix your problem. If you are still getting the error then, it is likely a new bug and we need to open a new pulp_rpm issue here: Issues · pulp/pulp_rpm · GitHub
Currently I have this version installed on the main katello server and one proxy.
This was to overcome the problem where foreman-installer would fail.