[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
With the changed focus from xenial to bionic - the xenial entry is now set to Won't Fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
** Changed in: ubuntu-z-systems Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1~18.04.1 --- makedumpfile (1:1.6.5-1ubuntu1~18.04.1) bionic; urgency=low * Backport back to bionic. (LP: #1655280) (LP: #1790788) makedumpfile (1:1.6.5-1ubuntu1) disco; urgency=low [ Ubuntu Merge-o-Matic ] * Merge from Debian unstable. Remaining changes: - Bump amd64 crashkernel from 384M-:128M to 512M-:192M. [ Thadeu Lima de Souza Cascardo ] * Use a different service for vmcore dump. (LP: #1811692) makedumpfile (1:1.6.5-1) unstable; urgency=medium * Update to new upstream version 1.6.5. * debian: remove debian/source/local-options * [i18n] Move PT debconf translation (Closes: #910465) makedumpfile (1:1.6.4-3) unstable; urgency=medium * Reload kdump after memory/CPU hotplug. (LP: #1655280) * Fix adding crashkernel to zipl.conf when no quotation mark is used. (LP: #1790788) -- Thadeu Lima de Souza Cascardo Thu, 07 Feb 2019 09:22:23 -0200 ** Changed in: makedumpfile (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1~18.10.1 --- makedumpfile (1:1.6.5-1ubuntu1~18.10.1) cosmic; urgency=low * Backport back to cosmic. (LP: #1655280) (LP: #1790788) makedumpfile (1:1.6.5-1ubuntu1) disco; urgency=low [ Ubuntu Merge-o-Matic ] * Merge from Debian unstable. Remaining changes: - Bump amd64 crashkernel from 384M-:128M to 512M-:192M. [ Thadeu Lima de Souza Cascardo ] * Use a different service for vmcore dump. (LP: #1811692) makedumpfile (1:1.6.5-1) unstable; urgency=medium * Update to new upstream version 1.6.5. * debian: remove debian/source/local-options * [i18n] Move PT debconf translation (Closes: #910465) makedumpfile (1:1.6.4-3) unstable; urgency=medium * Reload kdump after memory/CPU hotplug. (LP: #1655280) * Fix adding crashkernel to zipl.conf when no quotation mark is used. (LP: #1790788) -- Thadeu Lima de Souza Cascardo Thu, 07 Feb 2019 09:22:23 -0200 ** Changed in: makedumpfile (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
Adjusting the bionic-verification tag, since I was able to successfully verify the package from bionic-proposed, too. ** Attachment added: "verification-bionic.txt" https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+attachment/5260250/+files/verification-bionic.txt ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
Adjusting the cosmic-verification tag, since I was able to successfully verify the package from cosmic-proposed. ** Attachment added: "verification-cosmic.txt" https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+attachment/5260249/+files/verification-cosmic.txt ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
Hello Frank, or anyone else affected, Accepted makedumpfile into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: makedumpfile (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
Hello Frank, or anyone else affected, Accepted makedumpfile into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: makedumpfile (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
Our makedumpfile updates are waiting for us to get approval for micro release updates. I am working on the justification so we can get exceptions for this and future updates, as makedumpfile is closely tied to the kernel version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
** Changed in: makedumpfile (Ubuntu Bionic) Status: New => In Progress ** Changed in: makedumpfile (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: makedumpfile (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
** Description changed:
SRU Justification:
--
[Impact]
- * While installing makedumpfile the "crashkernel=" argument is not
+ * While installing makedumpfile the "crashkernel=" argument is not
properly set, hence dump is not triggered on reboot.
- * Means the triggering of dumpfiles is currently not possible using
+ * Means the triggering of dumpfiles is currently not possible using
makedumpfile.
- * Dumpfiles are obviously only needed in rare cases, but if they are
+ * Dumpfiles are obviously only needed in rare cases, but if they are
needed (e.g. in production environments) the situation is usually
critical.
- * Hence fixing this is needed to allow post-mortem analysis of a dumps.
+ * Hence fixing this is needed to allow post-mortem analysis of a dumps.
- * The provided shell code snippet provides a fixed sed statement that
+ * The provided shell code snippet provides a fixed sed statement that
makes sure that the kernel parameter is propoerly set.
[Test Case]
- * Create and boot a s390x (KVM virtual) machine
+ * Create and boot a s390x (KVM virtual) machine
- * Install kdump-tools and makedumpfile
-Select 'yes' on question 'Should kdump-tools be enabled by default?'
during installation
+ * Install kdump-tools and makedumpfile
+ Select 'yes' on question 'Should kdump-tools be enabled by default?'
during installation
- * [ Reboot system ]
+ * [ Reboot system ]
- * Look for crashkernel line in zipl boot-loader
-grep crashkernel /etc/zipl.conf
-crashkernel line is missing in case this bug still exists
-one or more lines like this should be given:
-parameters = root=UUID=5ed8f208-adce-4fad-b1a6-feb5e8732d89
crashkernel=196M
+ * Look for crashkernel line in zipl boot-loader
+ grep crashkernel /etc/zipl.conf
+ crashkernel line is missing in case this bug still exists
+ one or more lines like this should be given:
+ parameters = root=UUID=5ed8f208-adce-4fad-b1a6-feb5e8732d89
crashkernel=196M
- * One may further trigger a crash (for a full positiv test)
-sudo -s
-sysctl -w kernel.sysrq=1
-echo c > /proc/sysrq-trigger
-(in case this bug still exists the system will not come up again - check
console in parallel)
+ * One may further trigger a crash (for a full positiv test)
+ sudo -s
+ sysctl -w kernel.sysrq=1
+ echo c > /proc/sysrq-trigger
+ (in case this bug still exists the system will not come up again - check
console in parallel)
+Finally dump files should be visible in /var/crash
[Regression Potential]
- * The regression potential is very low, since:
+ * The regression potential is very low, since:
- * it's limited to the zipl boot loader configuration file only
-and this means again it's on the s390x platform only (IBM Z)
+ * it's limited to the zipl boot loader configuration file only
+ and this means again it's on the s390x platform only (IBM Z)
- * kdump-tools and makedumpfile are not installed by default and only used in
debug situations
-hence only system where the package(s) got manually installed get updated
+ * kdump-tools and makedumpfile are not installed by default and only used in
debug situations
+ hence only system where the package(s) got manually installed get updated
- * The function is today broken anyway, hence it can actually only get
+ * The function is today broken anyway, hence it can actually only get
better
- * I successfully verified this in disco.
+ * I successfully verified this in disco.
_
Trying to use crashdump especially in a KVM machine.
Installation looks fine and the reboot is triggered.
But it does not work because the kernel does not have a 'crashkernel='
parameter.
Nothing in /proc/cmdline:
$ cat /proc/cmdline
root=LABEL=cloudimg-rootfs
Issue seems to be in adding the crashkernel line in this snippet:
# Customize crashkernel= value according to architecture
ARCH="$(arch)"
DEF_PRESET="384M-:128M"
case "$ARCH" in
s390x)
HAS_CRASHKERNEL="$(grep crashkernel /etc/zipl.conf)" || true
if test -z "$HAS_CRASHKERNEL"; then
sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}"
/etc/zipl.conf
zipl
fi
CIO_IGNORE="$(cio_ignore -u -k)"
sed -i "s/\#KDUMP_CMDLINE_APPEND/KDUMP_CMDLINE_APPEND/" $INITCONFFILE
sed -i "/KDUMP_CMDLINE_APPEND/{s|\"$| ${CIO_IGNORE}\"|}"
$INITCONFFILE
;;
esac
(especially 1st sed stmt)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790788
Title:
Customize 'crashkernel' parameter is not properly working
To manage notifications about this bug go to:
https://b
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
SRU justification added - see bug description
** Description changed:
+ SRU Justification:
+ --
+
+ [Impact]
+
+ * While installing makedumpfile the "crashkernel=" argument is not
+ properly set, hence dump is not triggered on reboot.
+
+ * Means the triggering of dumpfiles is currently not possible using
+ makedumpfile.
+
+ * Dumpfiles are obviously only needed in rare cases, but if they are
+ needed (e.g. in production environments) the situation is usually
+ critical.
+
+ * Hence fixing this is needed to allow post-mortem analysis of a dumps.
+
+ * The provided shell code snippet provides a fixed sed statement that
+ makes sure that the kernel parameter is propoerly set.
+
+ [Test Case]
+
+ * Create and boot a s390x (KVM virtual) machine
+
+ * Install kdump-tools and makedumpfile
+Select 'yes' on question 'Should kdump-tools be enabled by default?'
during installation
+
+ * [ Reboot system ]
+
+ * Look for crashkernel line in zipl boot-loader
+grep crashkernel /etc/zipl.conf
+crashkernel line is missing in case this bug still exists
+one or more lines like this should be given:
+parameters = root=UUID=5ed8f208-adce-4fad-b1a6-feb5e8732d89
crashkernel=196M
+
+ * One may further trigger a crash (for a full positiv test)
+sudo -s
+sysctl -w kernel.sysrq=1
+echo c > /proc/sysrq-trigger
+(in case this bug still exists the system will not come up again - check
console in parallel)
+
+ [Regression Potential]
+
+ * The regression potential is very low, since:
+
+ * it's limited to the zipl boot loader configuration file only
+and this means again it's on the s390x platform only (IBM Z)
+
+ * kdump-tools and makedumpfile are not installed by default and only used in
debug situations
+hence only system where the package(s) got manually installed get updated
+
+ * The function is today broken anyway, hence it can actually only get
+ better
+
+ * I successfully verified this in disco.
+ _
+
Trying to use crashdump especially in a KVM machine.
Installation looks fine and the reboot is triggered.
But it does not work because the kernel does not have a 'crashkernel='
parameter.
Nothing in /proc/cmdline:
- $ cat /proc/cmdline
+ $ cat /proc/cmdline
root=LABEL=cloudimg-rootfs
Issue seems to be in adding the crashkernel line in this snippet:
# Customize crashkernel= value according to architecture
ARCH="$(arch)"
DEF_PRESET="384M-:128M"
case "$ARCH" in
-s390x)
- HAS_CRASHKERNEL="$(grep crashkernel /etc/zipl.conf)" || true
- if test -z "$HAS_CRASHKERNEL"; then
- sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}"
/etc/zipl.conf
- zipl
- fi
- CIO_IGNORE="$(cio_ignore -u -k)"
- sed -i "s/\#KDUMP_CMDLINE_APPEND/KDUMP_CMDLINE_APPEND/" $INITCONFFILE
- sed -i "/KDUMP_CMDLINE_APPEND/{s|\"$| ${CIO_IGNORE}\"|}"
$INITCONFFILE
- ;;
+ s390x)
+ HAS_CRASHKERNEL="$(grep crashkernel /etc/zipl.conf)" || true
+ if test -z "$HAS_CRASHKERNEL"; then
+ sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}"
/etc/zipl.conf
+ zipl
+ fi
+ CIO_IGNORE="$(cio_ignore -u -k)"
+ sed -i "s/\#KDUMP_CMDLINE_APPEND/KDUMP_CMDLINE_APPEND/" $INITCONFFILE
+ sed -i "/KDUMP_CMDLINE_APPEND/{s|\"$| ${CIO_IGNORE}\"|}"
$INITCONFFILE
+ ;;
esac
(especially 1st sed stmt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790788
Title:
Customize 'crashkernel' parameter is not properly working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
needs SRU template, test case etc ** Also affects: makedumpfile (Ubuntu Disco) Importance: High Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
This bug was fixed in the package makedumpfile - 1:1.6.5-1ubuntu1 --- makedumpfile (1:1.6.5-1ubuntu1) disco; urgency=low [ Ubuntu Merge-o-Matic ] * Merge from Debian unstable. Remaining changes: - Bump amd64 crashkernel from 384M-:128M to 512M-:192M. [ Thadeu Lima de Souza Cascardo ] * Use a different service for vmcore dump. (LP: #1811692) makedumpfile (1:1.6.5-1) unstable; urgency=medium * Update to new upstream version 1.6.5. * debian: remove debian/source/local-options * [i18n] Move PT debconf translation (Closes: #910465) makedumpfile (1:1.6.4-3) unstable; urgency=medium * Reload kdump after memory/CPU hotplug. (LP: #1655280) * Fix adding crashkernel to zipl.conf when no quotation mark is used. (LP: #1790788) -- Thadeu Lima de Souza Cascardo Mon, 14 Jan 2019 15:42:44 -0200 ** Changed in: makedumpfile (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
I am working on the merge of Debian and Ubuntu changes to Disco. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
This fix has been uploaded to Debian, and will be synced to 19.04 when it opens. After that, it will be backported to cosmic, bionic and xenial. Thanks. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
** Patch added: "makedumpfile_1.6.4-2ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+attachment/5195297/+files/makedumpfile_1.6.4-2ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
** Also affects: makedumpfile (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Cosmic) Importance: High Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: makedumpfile (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
Adding a sample zipl.conf of an LPAR installation - just for reference: $ cat /etc/zipl.conf [defaultboot] defaultmenu = menu :menu target = /boot 1 = ubuntu 2 = old default = 1 prompt = 1 timeout = 10 [ubuntu] target = /boot image = /boot/vmlinuz ramdisk = /boot/initrd.img parameters = root=UUID=83c2f8ac-7d56-4085-9d20-1e6e01175326 crashkernel=196M [old] target = /boot image = /boot/vmlinuz.old ramdisk = /boot/initrd.img.old parameters = root=UUID=83c2f8ac-7d56-4085-9d20-1e6e01175326 crashkernel=196M optional = 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
** Changed in: makedumpfile (Ubuntu) Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: makedumpfile (Ubuntu) Status: New => In Progress ** Changed in: makedumpfile (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
Note: this also affects the makedumpfile autopkgtest -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
Assigned the task on request by JFH ** Changed in: makedumpfile (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
Ack to the report.
While I had some systems (lpar) which worked I was trivially able to confirm
that it doesn't work on KVM guests based on cloud images.
I see this on install of kdump-tools (default answers to debconf)
Setting up kdump-tools (1:1.6.4-2) ...
Using config file '/etc/zipl.conf'
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Preparing boot device: vda ().
Done.
Creating config file /etc/default/kdump-tools with new version
But that leaves /etc/zipl.conf unmodified.
Frank already copied the snippet in the report.
This line isn't working:
$ sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}"
/etc/zipl.conf
At least in my guest and my LPARs the following seemed better, so for
your consideration:
$ sed -i "s/^parameters\s*=/& crashkernel=${DEF_PRESET} /"
/etc/zipl.conf
Note: at this point it already checked there is no crashkernel statement
yet, so we can unconditionally insert it here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790788
Title:
Customize 'crashkernel' parameter is not properly working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
This is also the reason for all the fails in [1] which actually flags a real issue as reported in this bug [1]: http://autopkgtest.ubuntu.com/packages/m/makedumpfile/cosmic/s390x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
For your testing here the default content of zipl.conf on a cloud-img KVM guest $ cat /etc/zipl.conf # This has been modified by the cloud image build process [defaultboot] default=ubuntu [ubuntu] target = /boot image = /boot/vmlinuz parameters = root=LABEL=cloudimg-rootfs ramdisk = /boot/initrd.img -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790788 Title: Customize 'crashkernel' parameter is not properly working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
