Bug 29208 - Upgrade 3.0 → 3.1 bricht ab: linux-image-3.x → update-grub -> python-ucr
Upgrade 3.0 → 3.1 bricht ab: linux-image-3.x → update-grub -> python-ucr
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: Update - Release updates
UCS 3.0
Other Linux
: P5 normal (vote)
: UCS 3.1
Assigned To: Stefan Gohmann
Sönke Schwardt-Krummrich
: interim-3
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-12 17:04 CET by Philipp Hahn
Modified: 2012-12-12 21:08 CET (History)
1 user (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2012-11-12 17:04:38 CET
Das Upgrade von 3.0-2 auf 3.1 brach ab, weil beim Installieren von linux-image-3.2.0-ucs17-amd64 über /etc/kernel-img.conf /usr/sbin/update-grub aufgerufen wird.
Diess wiederum ruft /usr/sbin/univention-grub-generate-menu-lst auf, was UCR benutzt.
Da es keine direkte Abhängigkeit von linux-image* auf python-univention-config-registry gibt, entschließt sich dpkg die Pakete parallel auszupacken und in der Teihenfolge
  linux-image
  python-univention-config-registry
  univention-grub
zu konfigurieren, was dann dazu führt, daß das postinst von linux-image-3.2.0 mit einem Fehler abbbricht, daß UCR nicht vefügbar ist:

# less /var/log/univention/updater.log
Traceback (most recent call last):
  File "/usr/sbin/univention-grub-generate-menu-lst", line 36, in <module>
    import univention.config_registry as ucr
ImportError: No module named config_registry
User postinst hook script [/usr/sbin/update-grub] exited with value 1
dpkg: Fehler beim Bearbeiten von linux-image-3.2.0-ucs17-amd64 (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

# egrep 'linux-image-3.2|config-registry|univention-grub' /var/log/dpkg.log
 :32:15 install linux-image-3.2.0-ucs17-amd64 <keine> 3.2.30-1.17.201210041157
 :32:15 status half-installed linux-image-3.2.0-ucs17-amd64 3.2.30-1.17.201210041157
 :32:18 status unpacked linux-image-3.2.0-ucs17-amd64 3.2.30-1.17.201210041157
 :32:18 status unpacked linux-image-3.2.0-ucs17-amd64 3.2.30-1.17.201210041157
 :32:20 upgrade python-univention-config-registry 7.0.33-2.384.201207061001 8.0.4-9.412.201210231803
 :32:20 status half-configured python-univention-config-registry 7.0.33-2.384.201207061001
 :32:20 status unpacked python-univention-config-registry 7.0.33-2.384.201207061001
 :32:20 status half-installed python-univention-config-registry 7.0.33-2.384.201207061001
 :32:20 status half-installed python-univention-config-registry 7.0.33-2.384.201207061001
Ab hier ist das alte UCR nicht mehr nutzbar.
 :32:21 status unpacked python-univention-config-registry 8.0.4-9.412.201210231803
 :32:21 status unpacked python-univention-config-registry 8.0.4-9.412.201210231803
 :32:31 upgrade univention-config-registry 7.0.33-2.384.201207061001 8.0.4-9.412.201210231803
 :32:31 status half-configured univention-config-registry 7.0.33-2.384.201207061001
 :32:31 status unpacked univention-config-registry 7.0.33-2.384.201207061001
 :32:31 status half-installed univention-config-registry 7.0.33-2.384.201207061001
 :32:31 status half-installed univention-config-registry 7.0.33-2.384.201207061001
 :32:31 status unpacked univention-config-registry 8.0.4-9.412.201210231803
 :32:31 status unpacked univention-config-registry 8.0.4-9.412.201210231803
 :32:55 upgrade univention-grub 5.0.9-10.88.201203201446 6.0.1-3.94.201211091655
 :32:55 status half-configured univention-grub 5.0.9-10.88.201203201446
 :32:55 status unpacked univention-grub 5.0.9-10.88.201203201446
 :32:55 status half-installed univention-grub 5.0.9-10.88.201203201446
 :32:55 status half-installed univention-grub 5.0.9-10.88.201203201446
 :32:55 status unpacked univention-grub 6.0.1-3.94.201211091655
 :32:55 status unpacked univention-grub 6.0.1-3.94.201211091655
 :33:09 configure linux-image-3.2.0-ucs17-amd64 3.2.30-1.17.201210041157 3.2.30-1.17.201210041157
 :33:09 status unpacked linux-image-3.2.0-ucs17-amd64 3.2.30-1.17.201210041157
 :33:09 status half-configured linux-image-3.2.0-ucs17-amd64 3.2.30-1.17.201210041157
Hier ist das postinst fehlgeschlagen.
 :33:20 configure python-univention-config-registry 8.0.4-9.412.201210231803 8.0.4-9.412.201210231803
 :33:20 status unpacked python-univention-config-registry 8.0.4-9.412.201210231803
 :33:20 status half-configured python-univention-config-registry 8.0.4-9.412.201210231803
 :33:21 status installed python-univention-config-registry 8.0.4-9.412.201210231803
Ab hier ist das neue UCR wieder verfügbar.
 :33:29 configure univention-config-registry 8.0.4-9.412.201210231803 8.0.4-9.412.201210231803
 :33:29 status unpacked univention-config-registry 8.0.4-9.412.201210231803
 :33:29 status half-configured univention-config-registry 8.0.4-9.412.201210231803
 :33:29 status installed univention-config-registry 8.0.4-9.412.201210231803
 :34:16 configure univention-grub 6.0.1-3.94.201211091655 6.0.1-3.94.201211091655
 :34:16 status unpacked univention-grub 6.0.1-3.94.201211091655
 :34:16 status unpacked univention-grub 6.0.1-3.94.201211091655
 :34:16 status unpacked univention-grub 6.0.1-3.94.201211091655
 :34:16 status unpacked univention-grub 6.0.1-3.94.201211091655
 :34:16 status unpacked univention-grub 6.0.1-3.94.201211091655
 :34:16 status half-configured univention-grub 6.0.1-3.94.201211091655
 :34:24 status installed univention-grub 6.0.1-3.94.201211091655

Ggf. sollten wir ucr wieder aus dem preup.sh heraus aktualisieren.
Comment 1 Stefan Gohmann univentionstaff 2012-11-12 21:21:37 CET
(In reply to comment #0)
> Ggf. sollten wir ucr wieder aus dem preup.sh heraus aktualisieren.

Ja. Ist umgesetzt.
Comment 2 Sönke Schwardt-Krummrich univentionstaff 2012-11-20 13:13:29 CET
(In reply to comment #1)
> (In reply to comment #0)
> > Ggf. sollten wir ucr wieder aus dem preup.sh heraus aktualisieren.
> 
> Ja. Ist umgesetzt.

- Änderungswunsch ist plausibel
- Änderung im preup.sh ist ok
- Updatetest mit Master erfolgreich → kein Fehler aufgetreten
- Changelogeintrag vorhanden
→ VERIFIED
Comment 3 Stefan Gohmann univentionstaff 2012-12-12 21:08:18 CET
UCS 3.1-0 has been released: 
 http://forum.univention.de/viewtopic.php?f=54&t=2125

If this error occurs again, please use "Clone This Bug".