Bug 1007931 - if a kernel is installed, write /etc/sysconfig/kernel with DEFAULTKERNEL set appropriately
if a kernel is installed, write /etc/sysconfig/kernel with DEFAULTKERNEL set ...
Product: Fedora
Classification: Fedora
Component: appliance-tools (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Dennis Gilmore
Fedora Extras Quality Assurance
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2013-09-13 11:02 EDT by Matthew Miller
Modified: 2015-06-29 20:42 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-06-29 20:42:17 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Matthew Miller 2013-09-13 11:02:24 EDT
appliance-creator currently does not create this file, but anaconda does. (It's in bootloader.py.) Currently, we're writing this in the cloud-kickstart file, but that is a) ugly and b) doesn't work if we want to use the same kickstart for archs which require different kernel package names (like kernel-PAE).
Comment 1 Dennis Gilmore 2013-09-13 11:33:49 EDT
this is not a bug at all, not being there doesn't cause any issues. in some appliance cases we install two or more kernels. which makes it impossible to say whats the right kernel
Comment 2 Matthew Miller 2013-09-13 11:39:22 EDT
(In reply to Dennis Gilmore from comment #1)
> this is not a bug at all, not being there doesn't cause any issues.

This is incorrect. Without this file, the default for new-kernel-pkg is to not make kernel upgrades the default. Since that's the normal behavior in Fedora and kind of surprising, I think it does indeed count as an issue.
Comment 3 Fedora Admin XMLRPC Client 2014-01-12 14:52:05 EST
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 4 Fedora End Of Life 2015-05-29 05:23:52 EDT
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 5 Fedora End Of Life 2015-06-29 20:42:17 EDT
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.