Hi all, is anybody here that is also syncing SLES repositories and has updated to SW 2.7?
While I was testing 2.7 (also nightly) on my test system, I was so focused primary on "deployment" of SLES and Debian systems, that I did not have an eye on the repo synchronization. Now, when I try to sync a SLES respository, on older repos (< SLES12), I get the following error 2017/10/11 06:00:00 +02:00 Command: ['/usr/bin/spacewalk-repo-sync', '--channel', 'sle11-sdk-sp3-updates-x86_64', '--type', 'yum'] 2017/10/11 06:00:00 +02:00 Sync of channel started. 2017/10/11 06:00:00 +02:00 Repo URL: https://user:[email protected]/repo/$RCE/SLE11-SDK-SP3-Updates/sle-11-x86_64/ 2017/10/11 06:00:10 +02:00 Packages in repo: 2404 2017/10/11 06:02:17 +02:00 No new packages to sync. 2017/10/11 06:02:17 +02:00 Repo https://user:[email protected]/repo/$RCE/SLE11-SDK-SP3-Updates/sle-11-x86_64/ has 559 errata. 2017/10/11 06:02:23 +02:00 Syncing 559 new errata to channel. 2017/10/11 06:02:34 +02:00 ERROR: 'list' object has no attribute 'keys' 2017/10/11 06:02:34 +02:00 ERROR: 'list' object has no attribute 'keys' 2017/10/11 06:02:34 +02:00 Sync of channel completed in 0:02:33. This on repos which seem to be "smaller" than SLES11-SP4. I therefore created PR https://github.com/spacewalkproject/spacewalk/pull/581 which should fix the "ERROR: 'list' object has no attribute 'keys'" But even if this patch is not yet put in place (here on my production server) and trying to sync a SLES11-SP4 (or SLES12-SP1) or newr repo, (where the above mentioned error is *not* hit), I get the following db "constraint" error 2017/10/11 08:32:23 +02:00 Repo URL: https://user:[email protected]/repo/$RCE/SLES11-SP4-Updates/sle-11-x86_64/ 2017/10/11 08:32:27 +02:00 Packages in repo: 3661 2017/10/11 08:33:23 +02:00 Packages already synced: 2852 2017/10/11 08:33:23 +02:00 Packages to sync: 2 2017/10/11 08:33:23 +02:00 New packages to download: 2 2017/10/11 08:33:24 +02:00 1/2 : tcpdump-3.9.8-1.30.5.1.x86_64.rpm 2017/10/11 08:33:25 +02:00 2/2 : xinetd-2.3.14-130.133.7.1.x86_64.rpm 2017/10/11 08:33:25 +02:00 Importing packages started. 2017/10/11 08:33:27 +02:00 Importing packages finished. 2017/10/11 08:33:27 +02:00 Linking packages to channel. 2017/10/11 08:33:29 +02:00 Repo https://user:[email protected]/repo/$RCE/SLES11-SP4-Updates/sle-11-x86_64/ has 613 errata. 2017/10/11 08:33:48 +02:00 Syncing 613 new errata to channel. 2017/10/11 08:33:59 +02:00 ERROR: FEHLER: doppelter Schlüsselwert verletzt Unique-Constraint »rhn_errata_adv_org_uq« 2017/10/11 08:33:59 +02:00 ERROR: FEHLER: doppelter Schlüsselwert verletzt Unique-Constraint »rhn_errata_adv_org_uq« 2017/10/11 08:33:59 +02:00 Sync of channel completed in 0:01:36. I was able to successfully sync the EPEL 7 repository without any problems, so I think, this is caused by "not very unique" "update_id" s in SLES. So if anybody also syncs SLES and has updated to SW 2.7, please report, if you also see this error or if it works in your setup. Thanks. Robert Mit freundlichen Grüßen Robert Paschedag Netlution GmbH Landteilstr. 33 68163 Mannheim im Auftrag des SWR Südwestrundfunk HA IT, Medientechnik und Programmverbreitung Neckarstraße 230 70190 Stuttgart
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
