https://bugzilla.novell.com/show_bug.cgi?id=710876 https://bugzilla.novell.com/show_bug.cgi?id=710876#c0 Summary: zypper dist-upgrade upgrades very few packages Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jimc@math.ucla.edu QAContact: jsrain@novell.com Found By: Customer Blocker: --- I've upgraded 57 machines successfully so far from OpenSuSE 11.2 to 11.4, but two had a mysterious problem, in which zypper dist-upgrade thinks that installing about 17 packages is sufficient for the upgrade. The procedure goes like this. The architecture is the same for the master and target sites (separate masters for i586 and x86_64, already with v11.4). For production, this whole procedure is scripted; see "instsetup", attached. 1. Remove the target's v11.2 repos using zypper removerepo. 2. Emplace for v11.4 /etc/zypp/repos.d/(various).repo but don't refresh them yet. Although v11.2 seems to be able to refresh a v11.4 repo, v10.3 zypper choked on the v11.2 repo, so I avoid tempting fate. 3. Create a microcosm (directory), copy the v11.4 repo definitions into it, and install zypper (11.4) and its numerous dependencies into it (command line: zypper --root /tmp/microcosm install zypper) 4. Copy the microcosm from the v11.4 master site onto the v11.2 target. 5. On the target, boot the v11.4 installer. 6. Mount the target's root partition on the installer's /mnt. 7. Bind-mount the installer's /mnt onto /mnt/tmp/microcosm/mnt . This recursive mount actually works. 8. chroot /mnt/tmp/microcosm /usr/bin/zypper --root /mnt refresh 9. chroot /mnt/tmp/microcosm /usr/bin/zypper --root /mnt dist-upgrade At this point it usually does the whole dist-upgrade, but not on these two jinxed machines. Both are servers, but other servers (with identical or microscopically differing sets of packages) were upgraded successfully. The same failure occurs on every attempt despite forced repo rebuilds, etc. I succeeded in capturing it in the act without kicking off the users; the solver test case is attached. The procedure I used to generate it was this: Steps 1-4 and 7-9 from the above list, except in step 7 I'm bind-mounting the actual root (/) onto /tmp/microcosm/mnt, and the command line in step 9 is: 9. chroot /tmp/distro-upgrade/zypper.d /usr/bin/zypper --root /mnt dist-upgrade -l --debug-solver -D I've considered booting the installer and doing a normal upgrade with yast, but given that the installer and zypper use the same solver, I'm afraid that I'll get 17 packages installed (not including zypper and rpm from v11.4), and I'll end up with a broken system. Better to do a clean installation. Do you guys have any idea what's going on, and more important, how to get the upgrade on track? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.