Bug 38120 - Check if univention-kernel-image is installed
Check if univention-kernel-image is installed
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Update - Release updates
UCS 3.2
Other Linux
: P5 normal (vote)
: UCS 4.0-x
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-03-24 11:04 CET by Tim Petersen
Modified: 2018-04-14 13:51 CEST (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 Tim Petersen univentionstaff 2015-03-24 11:04:18 CET
We should check in pre-up if univention-meta-packages is installed. This check should be ignorable via UCR (update40/ignorekernelpackage=true?)

We saw several older systems (mostly migrated ase instances) where the meta package wasn't installed and which didn't boot the old 2.6.32er kernel with UCS 4.0 (userspace tools too new).
Comment 1 Tim Petersen univentionstaff 2015-03-24 11:08:29 CET
(In reply to Tim Petersen from comment #0)
> We should check in pre-up if univention-meta-packages is installed. This
> check should be ignorable via UCR (update40/ignorekernelpackage=true?)

odd typo ... univention-kernel-image, of course
Comment 2 Janis Meybohm univentionstaff 2015-03-24 14:57:19 CET
Occured at least on three systems (all of them OXASE upgrades)
2015031621000442
2015030421000483
Comment 3 Janis Meybohm univentionstaff 2015-03-24 14:59:30 CET
Reason for errata:
After upgrade to UCS 4.x the systems won't boot because the old kernel (2.6.32 in my cases) does not work well with userspace tools from UCS 4. LVM won't come up on boot etc.
As this is _not_ seen by users they end up with system in recovery shell after successfully upgrading to UCS 4.
Comment 4 Michael Grandjean univentionstaff 2015-07-12 14:03:33 CEST
Also http://forum.univention.de/viewtopic.php?f=48&t=4180
UCS 3.2-5 with kernel 2.6, formerly OXASE
Comment 5 Stefan Gohmann univentionstaff 2017-06-16 20:38:22 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 6 Stefan Gohmann univentionstaff 2017-08-08 07:11:31 CEST
This issue has been filed against UCS 3.2.

UCS 3.2 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.