<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="DE" link="#0563C1" vlink="#954F72"> <div class="WordSection1"> Just further information….what I just yet notices is….why does SW 2.7 try to sync *all* erratas new?<o:p></o:p> <o:p> </o:p> Last Wednesday (and before upgrade to 2.7), sync of SLES11-SP4-Updates worked and hat 609 errata<o:p></o:p> <o:p> </o:p> Linking packages to channel.<o:p></o:p> Repo https://user:pass@nu.novell.com/repo/$RCE/SLES11-SP4-Updates/sle-11-x86_64/ has 609 errata.<o:p></o:p> Sync completed.<o:p></o:p> Total time: 0:06:37<o:p></o:p> <o:p> </o:p> Then on Monday, I upgraded SW to 2.7. Now the sync of SLES11-SP4 looks like this<o:p></o:p> <o:p> </o:p> 2017/10/09 15:59:09 +02:00 Command: ['/usr/bin/spacewalk-repo-sync', '--channel', 'sles11-sp4-updates-x86_64', '--type', 'yum']<o:p></o:p> 2017/10/09 15:59:09 +02:00 Sync of channel started.<o:p></o:p> 2017/10/09 15:59:09 +02:00 Repo URL: https://user:pass@nu.novell.com/repo/$RCE/SLES11-SP4-Updates/sle-11-x86_64/<o:p></o:p> 2017/10/09 15:59:14 +02:00 Packages in repo: 3655<o:p></o:p> 2017/10/09 16:02:49 +02:00 Packages already synced: 2846<o:p></o:p> 2017/10/09 16:02:49 +02:00 Packages to sync: 5<o:p></o:p> 2017/10/09 16:02:49 +02:00 New packages to download: 5<o:p></o:p> 2017/10/09 16:02:50 +02:00 1/5 : libvirt-1.2.5-23.3.1.x86_64.rpm<o:p></o:p> 2017/10/09 16:02:51 +02:00 2/5 : libvirt-lock-sanlock-1.2.5-23.3.1.x86_64.rpm<o:p></o:p> 2017/10/09 16:02:51 +02:00 3/5 : libvirt-client-32bit-1.2.5-23.3.1.x86_64.rpm<o:p></o:p> 2017/10/09 16:02:51 +02:00 4/5 : libvirt-doc-1.2.5-23.3.1.x86_64.rpm<o:p></o:p> 2017/10/09 16:02:51 +02:00 5/5 : libvirt-client-1.2.5-23.3.1.x86_64.rpm<o:p></o:p> 2017/10/09 16:02:51 +02:00 Importing packages started.<o:p></o:p> 2017/10/09 16:03:01 +02:00 Importing packages finished.<o:p></o:p> 2017/10/09 16:03:01 +02:00 Linking packages to channel.<o:p></o:p> 2017/10/09 16:03:03 +02:00 Repo https://user:pass@nu.novell.com/repo/$RCE/SLES11-SP4-Updates/sle-11-x86_64/ has 610 errata.<o:p></o:p> -->2017/10/09 16:03:17 +02:00 Syncing 610 new errata to channel.<o:p></o:p> 2017/10/09 16:03:50 +02:00 ERROR: FEHLER: doppelter Schlüsselwert verletzt Unique-Constraint »rhn_errata_adv_org_uq«<o:p></o:p> <o:p> </o:p> 2017/10/09 16:03:50 +02:00 ERROR: FEHLER: doppelter Schlüsselwert verletzt Unique-Constraint »rhn_errata_adv_org_uq«<o:p></o:p> <o:p> </o:p> 2017/10/09 16:03:50 +02:00 Sync of channel completed in 0:04:41.<o:p></o:p> <o:p> </o:p> Why is it trying to create 610 *new* errata? It should only create *one*<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm"> Von: spacewalk-list-bounces@redhat.com [mailto:spacewalk-list-bounces@redhat.com] Im Auftrag von Paschedag, Robert Gesendet: Mittwoch, 11. Oktober 2017 08:44 An: spacewalk-list@redhat.com Betreff: [Spacewalk-list] Anybody syncing SLES repositories with SW 2.7?<o:p></o:p> </div> </div> <o:p> </o:p> Hi all,<o:p></o:p> <o:p> </o:p> is anybody here that is also syncing SLES repositories and has updated to SW 2.7?<o:p></o:p> <o:p> </o:p> 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.<o:p></o:p> <o:p> </o:p> Now, when I try to sync a SLES respository, on older repos (< SLES12), I get the following error<o:p></o:p> <o:p> </o:p> 2017/10/11 06:00:00 +02:00 Command: ['/usr/bin/spacewalk-repo-sync', '--channel', 'sle11-sdk-sp3-updates-x86_64', '--type', 'yum']<o:p></o:p> 2017/10/11 06:00:00 +02:00 Sync of channel started.<o:p></o:p> 2017/10/11 06:00:00 +02:00 Repo URL: <a href="https://user:pass@nu.novell.com/repo/$RCE/SLE11-SDK-SP3-Updates/sle-11-x86_64/">https://user:pass@nu.novell.com/repo/$RCE/SLE11-SDK-SP3-Updates/sle-11-x86_64/</a><o:p></o:p> 2017/10/11 06:00:10 +02:00 Packages in repo: 2404<o:p></o:p> 2017/10/11 06:02:17 +02:00 No new packages to sync.<o:p></o:p> 2017/10/11 06:02:17 +02:00 Repo <a href="https://user:pass@nu.novell.com/repo/$RCE/SLE11-SDK-SP3-Updates/sle-11-x86_64/">https://user:pass@nu.novell.com/repo/$RCE/SLE11-SDK-SP3-Updates/sle-11-x86_64/</a> has 559 errata.<o:p></o:p> 2017/10/11 06:02:23 +02:00 Syncing 559 new errata to channel.<o:p></o:p> 2017/10/11 06:02:34 +02:00 ERROR: 'list' object has no attribute 'keys'<o:p></o:p> 2017/10/11 06:02:34 +02:00 ERROR: 'list' object has no attribute 'keys'<o:p></o:p> 2017/10/11 06:02:34 +02:00 Sync of channel completed in 0:02:33.<o:p></o:p> <o:p> </o:p> This on repos which seem to be “smaller” than SLES11-SP4. I therefore created PR<o:p></o:p> <o:p> </o:p> <a href="https://github.com/spacewalkproject/spacewalk/pull/581">https://github.com/spacewalkproject/spacewalk/pull/581</a><o:p></o:p> <o:p> </o:p> which should fix the<o:p></o:p> <o:p> </o:p> “ERROR: ‘list’ object has no attribute ‘keys’”<o:p></o:p> <o:p> </o:p> 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,<o:p></o:p> (where the above mentioned error is *not* hit), I get the following db “constraint” error<o:p></o:p> <o:p> </o:p> 2017/10/11 08:32:23 +02:00 Repo URL: <a href="https://user:pass@nu.novell.com/repo/$RCE/SLES11-SP4-Updates/sle-11-x86_64/">https://user:pass@nu.novell.com/repo/$RCE/SLES11-SP4-Updates/sle-11-x86_64/</a><o:p></o:p> 2017/10/11 08:32:27 +02:00 Packages in repo: 3661<o:p></o:p> 2017/10/11 08:33:23 +02:00 Packages already synced: 2852<o:p></o:p> 2017/10/11 08:33:23 +02:00 Packages to sync: 2<o:p></o:p> 2017/10/11 08:33:23 +02:00 New packages to download: 2<o:p></o:p> 2017/10/11 08:33:24 +02:00 1/2 : tcpdump-3.9.8-1.30.5.1.x86_64.rpm<o:p></o:p> 2017/10/11 08:33:25 +02:00 2/2 : xinetd-2.3.14-130.133.7.1.x86_64.rpm<o:p></o:p> 2017/10/11 08:33:25 +02:00 Importing packages started.<o:p></o:p> 2017/10/11 08:33:27 +02:00 Importing packages finished.<o:p></o:p> 2017/10/11 08:33:27 +02:00 Linking packages to channel.<o:p></o:p> 2017/10/11 08:33:29 +02:00 Repo <a href="https://user:pass@nu.novell.com/repo/$RCE/SLES11-SP4-Updates/sle-11-x86_64/">https://user:pass@nu.novell.com/repo/$RCE/SLES11-SP4-Updates/sle-11-x86_64/</a> has 613 errata.<o:p></o:p> 2017/10/11 08:33:48 +02:00 Syncing 613 new errata to channel.<o:p></o:p> 2017/10/11 08:33:59 +02:00 ERROR: FEHLER: doppelter Schlüsselwert verletzt Unique-Constraint »rhn_errata_adv_org_uq«<o:p></o:p> <o:p> </o:p> 2017/10/11 08:33:59 +02:00 ERROR: FEHLER: doppelter Schlüsselwert verletzt Unique-Constraint »rhn_errata_adv_org_uq«<o:p></o:p> <o:p> </o:p> 2017/10/11 08:33:59 +02:00 Sync of channel completed in 0:01:36.<o:p></o:p> <o:p> </o:p> 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.<o:p></o:p> <o:p> </o:p> 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.<o:p></o:p> <o:p> </o:p> Thanks.<o:p></o:p> Robert<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> Mit freundlichen Grüßen<o:p></o:p> <o:p> </o:p> Robert Paschedag<o:p></o:p> Netlution GmbH<o:p></o:p> Landteilstr. 33<o:p></o:p> 68163 Mannheim<o:p></o:p> <o:p> </o:p> im Auftrag des<o:p></o:p> SWR<o:p></o:p> Südwestrundfunk<o:p></o:p> HA IT, Medientechnik und Programmverbreitung<o:p></o:p> Neckarstraße 230<o:p></o:p> 70190 Stuttgart<o:p></o:p> </div> </body> </html>