[Spacewalk-list] Syncing with SLES for SAP repos

Robert Paschedag robert.paschedag at web.de
Sat May 11 08:02:19 UTC 2019


Am 11. Mai 2019 01:30:07 MESZ schrieb Paul-Andre Panon <paul-andre.panon at avigilon.com>:
>On Tue, 16 Apr 2019 12:27:09 +0000, "Sadri, Wafa (BITBW)"
><Wafa.Sadri at bitbw.bwl.de> wrote;
>To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
>
>>Dear Paul-Andre,
>
>>coincidentally I'm having a very similar issue. We fixed this issue in
>2.7 and it's now back because SW has
>>fundamentally changed the way it syncs repos (either from 2.7 to 2.8
>or
>2.8 to 2.9 - not sure yet). Either way, the
>>problem - afaik - seems to be that the download.py file (in which we
>implemented the fix) doesn't get called until
>>later in the sync/download process. The error though occurs before
>this
>python script is called, resulting in the
>>problem you and I are having. So far I haven't yet figured out a way
>to
>fix this. At the moment I'm looking into the
>> reposync.py file as I'm suspecting the error to be caused here.
>
>>best regards,
>>Wafa
>
>Belated thanks.  I had some issues with licenses that appeared to have
>expired on the SUSE site (even though we had support), so I only got
>back
>to this recently when we found a solution to that issue. While I still
>need to set up SUSE 12 for some servers, I'm also needing to set up
>SUSE
>11 for SAP so I decided to look at the latter again. It looks like some
>of
>the problems I was having must have been due to mistyped URLs. I did
>manage to get working the two SLES 11 for SAP channels with which I was
>having problems, after re-creating the URLS - one with more success
>than
>another. In the case of the SLES 11 for SAP Base Pool channel, I got
>Spacewalk to talk to the repository, but it appears to be quite unhappy
>with the packages. It's choking when trying to import the packages, and
>the channel for that repo shows no packages.
>
>2019/05/08 18:16:03 -07:00 Command: ['/usr/bin/spacewalk-repo-sync',
>'--channel', 'sles11sp4-sap-base', '--type', 'yum']
>2019/05/08 18:16:03 -07:00 Sync of channel started.
>2019/05/08 18:16:03 -07:00
>2019/05/08 18:16:03 -07:00   Processing repository with URL:
>https://<NCCCredentials-user>:<NCCCredentials-password>@nu.novell.com/repo
>/$RCE/SLE11-SP4-SAP-Pool/sle-11-x86_64
>2019/05/08 18:16:05 -07:00     Packages in repo:              3094
>2019/05/08 18:16:14 -07:00     Packages already synced:          0
>2019/05/08 18:16:14 -07:00     Packages to sync:              3094
>2019/05/08 18:16:14 -07:00     New packages to download:        49
>2019/05/08 18:16:14 -07:00   Downloading packages:
>2019/05/08 18:16:14 -07:00     1/49 :
>ClusterTools2-2.5.3-14.1.noarch.rpm
>2019/05/08 18:16:14 -07:00     2/49 : SAPHanaSR-0.149-0.11.5.noarch.rpm
>2019/05/08 18:16:14 -07:00     3/49 :
>ClusterTools2-doc-2.5.3-14.1.noarch.rpm
>2019/05/08 18:16:14 -07:00     4/49 : HANA-Firewall-1.0-2.1.noarch.rpm
>2019/05/08 18:16:14 -07:00     5/49 :
>NetworkManager-openvpn-gnome-0.7.1-3.7.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     6/49 :
>SUSE_SLES_SAP-release-DVD-11.4-1.2.x86_64.rpm
>2019/05/08 18:16:15 -07:00     7/49 :
>SUSE_SLES_SAP-release-11.4-1.2.x86_64.rpm
>2019/05/08 18:16:15 -07:00     8/49 :
>HANA-Firewall-doc-1.0-2.1.noarch.rpm
>2019/05/08 18:16:15 -07:00     9/49 :
>check-create-certificate-0.5-0.2.3.noarch.rpm
>2019/05/08 18:16:15 -07:00     10/49 :
>SAPHanaSR-doc-0.149-0.11.5.noarch.rpm
>2019/05/08 18:16:15 -07:00     11/49 : collectd-4.9.4-0.13.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     12/49 : clamsap-0.9.8.0-0.5.5.x86_64.rpm
>2019/05/08 18:16:15 -07:00     13/49 :
>compat-32bit-2009.1.19-1.8.x86_64.rpm
>2019/05/08 18:16:15 -07:00     14/49 :
>compat-openssl097g-32bit-0.9.7g-146.22.29.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     15/49 :
>compat-openssl097g-0.9.7g-146.22.29.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     16/49 :
>libarchive2-2.5.5-5.19.x86_64.rpm
>2019/05/08 18:16:15 -07:00     17/49 : libunwind-0.98.6-26.6.x86_64.rpm
>2019/05/08 18:16:15 -07:00     18/49 :
>libcollectdclient-devel-4.9.4-0.13.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     19/49 :
>libcollectdclient0-4.9.4-0.13.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     20/49 :
>libstatgrab6-0.16-0.1.30.x86_64.rpm
>2019/05/08 18:16:15 -07:00     21/49 :
>lighttpd-mod_cml-1.4.20-2.54.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     22/49 :
>lighttpd-mod_magnet-1.4.20-2.54.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     23/49 :
>lighttpd-mod_mysql_vhost-1.4.20-2.54.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     24/49 :
>lighttpd-mod_rrdtool-1.4.20-2.54.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     25/49 :
>lighttpd-mod_trigger_b4_dl-1.4.20-2.54.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     26/49 :
>lighttpd-mod_webdav-1.4.20-2.54.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     27/49 :
>patterns-webyast-5-0.5.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     28/49 :
>openhpi-clients-2.12.0-1.31.x86_64.rpm
>2019/05/08 18:16:15 -07:00     29/49 :
>rubygem-locale-2.0.5-0.3.3.x86_64.rpm
>2019/05/08 18:16:15 -07:00     30/49 :
>rubygem-gettext-2.1.0-5.5.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     31/49 :
>ruby-devel-1.8.7.p357-0.9.17.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     32/49 :
>rubygem-haml-3.1.6-0.9.3.2.x86_64.rpm
>2019/05/08 18:16:15 -07:00     33/49 :
>rubygem-mime-types-1.18-0.7.3.2.x86_64.rpm
>2019/05/08 18:16:15 -07:00     34/49 :
>rubygem-json-1.6.1-0.11.10.2.x86_64.rpm
>2019/05/08 18:16:15 -07:00     35/49 :
>rubygem-rack-test-0_6-0.6.1-0.12.3.2.x86_64.rpm
>2019/05/08 18:16:15 -07:00     36/49 :
>rubygem-rake-compiler-0.7.0-0.2.26.x86_64.rpm
>2019/05/08 18:16:15 -07:00     37/49 :
>rubygem-sqlite3-1.3.6-0.10.1.x86_64.rpm
>2019/05/08 18:16:15 -07:00     38/49 :
>rubygem-rdoc-3.9.1-0.8.3.x86_64.rpm
>2019/05/08 18:16:16 -07:00     39/49 :
>rubygem-restility-0.0.1-0.1.32.x86_64.rpm
>2019/05/08 18:16:16 -07:00     40/49 :
>rubygem-test-unit-2.0.3-0.7.7.x86_64.rpm
>2019/05/08 18:16:16 -07:00     41/49 :
>sap-installation-wizard-2.29-0.75.1.noarch.rpm
>2019/05/08 18:16:16 -07:00     42/49 :
>rubygem-webyast-network-0.3.15-0.7.1.x86_64.rpm
>2019/05/08 18:16:16 -07:00     43/49 :
>rubygem-webyast-rake-tasks-0.1.8-0.3.2.x86_64.rpm
>2019/05/08 18:16:16 -07:00     44/49 :
>rubygem-webyast-status-0.3.16-0.7.1.x86_64.rpm
>2019/05/08 18:16:16 -07:00     45/49 :
>sap_suse_cluster_connector-1.1.0-1.18.noarch.rpm
>2019/05/08 18:16:16 -07:00     46/49 :
>spacewalksd-5.0.14.7-0.7.2.x86_64.rpm
>2019/05/08 18:16:16 -07:00     47/49 :
>talk-server-0.17-684.22.x86_64.rpm
>2019/05/08 18:16:16 -07:00     48/49 :
>yast2-trans-cy-2.17.1-1.15.noarch.rpm
>2019/05/08 18:16:16 -07:00     49/49 :
>unixODBC-gui-qt-2.2.12-198.21.x86_64.rpm
>2019/05/08 18:16:16 -07:00 Importing packages started.
>2019/05/08 18:16:16 -07:00
>2019/05/08 18:16:16 -07:00   Importing packages to DB:
>2019/05/08 18:16:18 -07:00 error reading package header
>2019/05/08 18:16:18 -07:00 error reading package header
>2019/05/08 18:16:20 -07:00 error reading package header
>2019/05/08 18:16:28 -07:00 error reading package header
>2019/05/08 18:16:28 -07:00 error reading package header
>2019/05/08 18:16:28 -07:00 error reading package header
>2019/05/08 18:16:28 -07:00 Importing packages finished.
>2019/05/08 18:16:28 -07:00
>2019/05/08 18:16:28 -07:00   Linking packages to the channel.
>2019/05/08 18:16:34 -07:00 ERROR: Could not find object
>[<spacewalk.server.importlib.importLib.IncompletePackage instance;
>attributes={'package_size': None, 'package_arch_id': 100, 'name':
>'sap-installation-wizard', 'checksum_list': None, 'md5sum': None,
>'org_id': 1, 'epoch': None, 'checksums': {'md5':
>'a832815f0af68f78621a0eebcdfb9a3f'}, 'channels': {166:
>'sles11sp4-sap-base'}, 'nevra_id': 272799, 'package_id': None,
>'last_modified': None, 'name_id': 100638, 'version': '2.29',
>'checksum':
>'a832815f0af68f78621a0eebcdfb9a3f', 'release': '0.75.1',
>'checksum_type':
>'md5', 'arch': 'noarch', 'evr_id': 53317, 'checksum_id': 6343100}] in
>table rhnPackage
>2019/05/08 18:16:34 -07:00 ERROR: Could not find object
>[<spacewalk.server.importlib.importLib.IncompletePackage instance;
>attributes={'package_size': None, 'package_arch_id': 100, 'name':
>'sap-installation-wizard', 'checksum_list': None, 'md5sum': None,
>'org_id': 1, 'epoch': None, 'checksums': {'md5':
>'a832815f0af68f78621a0eebcdfb9a3f'}, 'channels': {166:
>'sles11sp4-sap-base'}, 'nevra_id': 272799, 'package_id': None,
>'last_modified': None, 'name_id': 100638, 'version': '2.29',
>'checksum':
>'a832815f0af68f78621a0eebcdfb9a3f', 'release': '0.75.1',
>'checksum_type':
>'md5', 'arch': 'noarch', 'evr_id': 53317, 'checksum_id': 6343100}] in
>table rhnPackage
>2019/05/08 18:16:35 -07:00 Sync of channel completed in 0:00:31.
>2019/05/08 23:28:17 -07:00 Command: ['/usr/bin/spacewalk-repo-sync',
>'--channel', 'sles11sp4-sap-base', '--type', 'yum']
>2019/05/08 23:28:17 -07:00 Sync of channel started.
>2019/05/08 23:28:18 -07:00
>2019/05/08 23:28:18 -07:00   Processing repository with URL:
>https://<NCCCredentials-user>:<NCCCredentials-password>@nu.novell.com/repo
>/$RCE/SLE11-SP4-SAP-Pool/sle-11-x86_64
>2019/05/08 23:28:20 -07:00     Packages in repo:              3094
>2019/05/08 23:28:26 -07:00     Packages already synced:          0
>2019/05/08 23:28:26 -07:00     Packages to sync:              3094
>2019/05/08 23:28:26 -07:00     New packages to download:         9
>2019/05/08 23:28:26 -07:00   Downloading packages:
>2019/05/08 23:28:27 -07:00     1/9 : libarchive2-2.5.5-5.19.x86_64.rpm
>2019/05/08 23:28:27 -07:00     2/9 :
>sap-installation-wizard-2.29-0.75.1.noarch.rpm
>2019/05/08 23:28:27 -07:00     3/9 :
>spacewalksd-5.0.14.7-0.7.2.x86_64.rpm
>2019/05/08 23:28:27 -07:00     4/9 : libunwind-0.98.6-26.6.x86_64.rpm
>2019/05/08 23:28:27 -07:00     5/9 :
>sap_suse_cluster_connector-1.1.0-1.18.noarch.rpm
>2019/05/08 23:28:27 -07:00     6/9 :
>openhpi-clients-2.12.0-1.31.x86_64.rpm
>2019/05/08 23:28:27 -07:00     7/9 : talk-server-0.17-684.22.x86_64.rpm
>2019/05/08 23:28:27 -07:00     8/9 :
>yast2-trans-cy-2.17.1-1.15.noarch.rpm
>2019/05/08 23:28:27 -07:00     9/9 :
>unixODBC-gui-qt-2.2.12-198.21.x86_64.rpm
>2019/05/08 23:28:27 -07:00 Importing packages started.
>2019/05/08 23:28:27 -07:00
>2019/05/08 23:28:27 -07:00   Importing packages to DB:
>2019/05/08 23:28:27 -07:00 error reading package header
>2019/05/08 23:28:27 -07:00 error reading package header
>2019/05/08 23:28:27 -07:00 error reading package header
>2019/05/08 23:28:27 -07:00 error reading package header
>2019/05/08 23:28:27 -07:00 error reading package header
>2019/05/08 23:28:27 -07:00 error reading package header
>2019/05/08 23:28:27 -07:00 Importing packages finished.
>2019/05/08 23:28:27 -07:00
>2019/05/08 23:28:27 -07:00   Linking packages to the channel.
>2019/05/08 23:28:31 -07:00 ERROR: Could not find object
>[<spacewalk.server.importlib.importLib.IncompletePackage instance;
>attributes={'package_size': None, 'package_arch_id': 100, 'name':
>'sap-installation-wizard', 'checksum_list': None, 'md5sum': None,
>'org_id': 1, 'epoch': None, 'checksums': {'md5':
>'a832815f0af68f78621a0eebcdfb9a3f'}, 'channels': {166:
>'sles11sp4-sap-base'}, 'nevra_id': 272799, 'package_id': None,
>'last_modified': None, 'name_id': 100638, 'version': '2.29',
>'checksum':
>'a832815f0af68f78621a0eebcdfb9a3f', 'release': '0.75.1',
>'checksum_type':
>'md5', 'arch': 'noarch', 'evr_id': 53317, 'checksum_id': 6343100}] in
>table rhnPackage
>2019/05/08 23:28:31 -07:00 ERROR: Could not find object
>[<spacewalk.server.importlib.importLib.IncompletePackage instance;
>attributes={'package_size': None, 'package_arch_id': 100, 'name':
>'sap-installation-wizard', 'checksum_list': None, 'md5sum': None,
>'org_id': 1, 'epoch': None, 'checksums': {'md5':
>'a832815f0af68f78621a0eebcdfb9a3f'}, 'channels': {166:
>'sles11sp4-sap-base'}, 'nevra_id': 272799, 'package_id': None,
>'last_modified': None, 'name_id': 100638, 'version': '2.29',
>'checksum':
>'a832815f0af68f78621a0eebcdfb9a3f', 'release': '0.75.1',
>'checksum_type':
>'md5', 'arch': 'noarch', 'evr_id': 53317, 'checksum_id': 6343100}] in
>table rhnPackage
>2019/05/08 23:28:32 -07:00 Sync of channel completed in 0:00:14.
>
>
>Right now I've got that channel set up as a child of the standard SUSE
>11
>SP4 Base Pool channel, and that pool has 2905  packages and it shows
>similar errors. So I'm wondering if there's a way to find out which
>packages it's choking on. Since there appears to be a huge amount of
>duplication between the SLES 11 SP4 and SLES 11 SP4 for SAP
>repositories,
>I'm also starting to wonder if perhaps the latter should be a Parent
>channel.
>
>19/05/08 04:15:25 -07:00   Processing repository with URL:
>https://<NCCCredentials-user>:<NCCCredentials-password>@nu.novell.com/repo
>/$RCE/SLES11-SP4-Pool/sle-11-x86_64
>2019/05/08 04:15:27 -07:00     Packages in repo:              2913
>2019/05/08 04:15:34 -07:00     Packages already synced:       2905
>2019/05/08 04:15:34 -07:00     Packages to sync:                 8
>2019/05/08 04:15:34 -07:00     New packages to download:         8
>2019/05/08 04:15:34 -07:00   Downloading packages:
>2019/05/08 04:15:35 -07:00     1/8 : libunwind-0.98.6-26.6.x86_64.rpm
>2019/05/08 04:15:35 -07:00     2/8 : talk-server-0.17-684.22.x86_64.rpm
>2019/05/08 04:15:35 -07:00     3/8 :
>spacewalksd-5.0.14.7-0.7.2.x86_64.rpm
>2019/05/08 04:15:35 -07:00     4/8 :
>openhpi-clients-2.12.0-1.31.x86_64.rpm
>2019/05/08 04:15:35 -07:00     5/8 : libarchive2-2.5.5-5.19.x86_64.rpm
>2019/05/08 04:15:35 -07:00     6/8 :
>NetworkManager-openvpn-gnome-0.7.1-3.7.1.x86_64.rpm
>2019/05/08 04:15:35 -07:00     7/8 :
>yast2-trans-cy-2.17.1-1.15.noarch.rpm
>2019/05/08 04:15:35 -07:00     8/8 :
>unixODBC-gui-qt-2.2.12-198.21.x86_64.rpm
>2019/05/08 04:15:35 -07:00 Importing packages started.
>2019/05/08 04:15:35 -07:00
>2019/05/08 04:15:35 -07:00   Importing packages to DB:
>2019/05/08 04:15:35 -07:00 error reading package header
>2019/05/08 04:15:35 -07:00 error reading package header
>2019/05/08 04:15:35 -07:00 error reading package header
>2019/05/08 04:15:36 -07:00 error reading package header
>2019/05/08 04:15:36 -07:00 error reading package header
>2019/05/08 04:15:36 -07:00 error reading package header
>2019/05/08 04:15:36 -07:00 Importing packages finished.
>2019/05/08 04:15:36 -07:00
>2019/05/08 04:15:36 -07:00   Linking packages to the channel.
>2019/05/08 04:15:36 -07:00 ERROR: Could not find object
>[<spacewalk.server.importlib.importLib.IncompletePackage instance;
>attributes={'package_size': None, 'package_arch_id': 120, 'name':
>'NetworkManager-openvpn-gnome', 'checksum_list': None, 'md5sum': None,
>'org_id': 1, 'epoch': None, 'checksums': {'md5':
>'43005f4d3983035e0b77e396159c24bf'}, 'channels': {161:
>'sles-11-sp4-pool'}, 'nevra_id': 261186, 'package_id': None,
>'last_modified': None, 'name_id': 21373, 'version': '0.7.1',
>'checksum':
>'43005f4d3983035e0b77e396159c24bf', 'release': '3.7.1',
>'checksum_type':
>'md5', 'arch': 'x86_64', 'evr_id': 49701, 'checksum_id': 5910105}] in
>table rhnPackage
>2019/05/08 04:15:36 -07:00 ERROR: Could not find object
>[<spacewalk.server.importlib.importLib.IncompletePackage instance;
>attributes={'package_size': None, 'package_arch_id': 120, 'name':
>'NetworkManager-openvpn-gnome', 'checksum_list': None, 'md5sum': None,
>'org_id': 1, 'epoch': None, 'checksums': {'md5':
>'43005f4d3983035e0b77e396159c24bf'}, 'channels': {161:
>'sles-11-sp4-pool'}, 'nevra_id': 261186, 'package_id': None,
>'last_modified': None, 'name_id': 21373, 'version': '0.7.1',
>'checksum':
>'43005f4d3983035e0b77e396159c24bf', 'release': '3.7.1',
>'checksum_type':
>'md5', 'arch': 'x86_64', 'evr_id': 49701, 'checksum_id': 5910105}] in
>table rhnPackage
>2019/05/08 04:15:36 -07:00 Sync of channel completed in 0:00:11.
>
>Does anybody have any suggestions on how to clean up those errors, or
>at
>least how to find out which packages are causing them?
>
>Cheers,
>
>Paul-Andre
>
>_______________________________________________
>Spacewalk-list mailing list
>Spacewalk-list at redhat.com
>https://www.redhat.com/mailman/listinfo/spacewalk-list

Only thing you can do is find the place, where the error "reading package header"  is raised and modify this to also output the filename you're processing right now.

Also, the "sap-installtion-wizard" package seems to have a problem.

Maybe an error of the package itself (?!) but it could also be an error within the repo XML file.

I once traced that because I also had problems with some packages but have to look into the code on my computer. Should be somewhere in the "importLib.py" file (I think)

Robert

-- 
sent from my mobile device




More information about the Spacewalk-list mailing list