** Description changed:

+ ## FFE ##
+ 
+ [Rationale]
+ 
+ * kdump-tools currently depends on initramfs-tools for generating the
+ kdump initrd used when taking the crashdump. We want to support dracut
+ so that initramfs-tools doesn't need to be installed.
+ 
+ [ Scope ]
+ 
+ * This change will add support for building the kdump initrd with dracut
+ so that initramfs-tools is no longer a direct dependency.
+ 
+ * This change is limited to the initrd generator functionality. There
+ are also new tests included to cover the initrd generator selection and
+ both the initramfs-tools and dracut initrd generation paths.
+ 
+ * In the case of both dracut and initramfs-tools being installed, the
+ dracut path is preferred.
+ 
+ * seeded-in-ubuntu output:
+ 
+ kdump-tools (from kdump-tools) is seeded in:
+   ubuntu-core-installer: daily-live
+ 
+ [ Regression Potential ]
+ 
+ * If there was a regression here, it would be evident in the process of
+ taking a crash dump. If the kdump initrd generation failed, then the
+ system would be unable to take a crash dump. This initrd is only used
+ for kdump, so any issues would be limited to the process of taking crash
+ dumps. The main system initrd is unaffected.
+ 
+ [ Testing ]
+ 
+ * Smoke test:
+   - PPA: 
https://launchpad.net/~kevinbecker/+archive/ubuntu/kdump-dracut-test-5
+   - Installation: <link to the installation test>
+   - Upgrade: <link to the upgrade test>
+   - Autopkgtest: <autopkgtest results>
+   - Does it break other packages: <link related bugs>
+ * Manual test plan
+   - Install kdump-tools update on stonking from PPA above
+   - Reboot
+   - Confirm kdump is configured with `kdump-config show`. If it isn't, do it 
manually ( https://ubuntu.com/server/docs/how-to/software/kernel-crash-dump/ )
+   - Take a dump manually ( # echo c > /proc/sysrq-trigger )
+   - The crash dump should be taken now and the system should reboot
+   - Confirm the dump exists in /var/crash
+   - Install the debug symbols for the kernel
+   - Use crash to inspect the crash dump
+ 
+ [ Other Info ]
+ 
+ * I plan to get these changes into Debian in the future, but didn't have
+ the time to get it there first before stonking.
+ 
+ [ Original Description ]
+ 
  supposedly ubuntu kdump & ubuntu dracut do not work together. like at
  all.

** Summary changed:

- kdump tools X dracut doesn't work
+ FFe: kdump tools X dracut doesn't work

** No longer affects: dracut (Ubuntu)

** Description changed:

  ## FFE ##
  
  [Rationale]
  
  * kdump-tools currently depends on initramfs-tools for generating the
  kdump initrd used when taking the crashdump. We want to support dracut
  so that initramfs-tools doesn't need to be installed.
  
  [ Scope ]
  
  * This change will add support for building the kdump initrd with dracut
  so that initramfs-tools is no longer a direct dependency.
  
  * This change is limited to the initrd generator functionality. There
  are also new tests included to cover the initrd generator selection and
  both the initramfs-tools and dracut initrd generation paths.
  
  * In the case of both dracut and initramfs-tools being installed, the
  dracut path is preferred.
  
+ * Merge request:
+ https://code.launchpad.net/~kevinbecker/ubuntu/+source/kdump-
+ tools/+git/kdump-tools/+merge/509792
+ 
  * seeded-in-ubuntu output:
  
  kdump-tools (from kdump-tools) is seeded in:
-   ubuntu-core-installer: daily-live
+   ubuntu-core-installer: daily-live
  
  [ Regression Potential ]
  
  * If there was a regression here, it would be evident in the process of
  taking a crash dump. If the kdump initrd generation failed, then the
- system would be unable to take a crash dump. This initrd is only used
- for kdump, so any issues would be limited to the process of taking crash
+ system may be unable to take a crash dump. This initrd is only used for
+ kdump, so any issues would be limited to the process of taking crash
  dumps. The main system initrd is unaffected.
  
  [ Testing ]
  
  * Smoke test:
-   - PPA: 
https://launchpad.net/~kevinbecker/+archive/ubuntu/kdump-dracut-test-5
-   - Installation: <link to the installation test>
-   - Upgrade: <link to the upgrade test>
-   - Autopkgtest: <autopkgtest results>
-   - Does it break other packages: <link related bugs>
+   - PPA: 
https://launchpad.net/~kevinbecker/+archive/ubuntu/kdump-dracut-test-5
+   - Installation: <link to the installation test>
+   - Upgrade: <link to the upgrade test>
+   - Autopkgtest: <autopkgtest results>
  * Manual test plan
-   - Install kdump-tools update on stonking from PPA above
-   - Reboot
-   - Confirm kdump is configured with `kdump-config show`. If it isn't, do it 
manually ( https://ubuntu.com/server/docs/how-to/software/kernel-crash-dump/ )
-   - Take a dump manually ( # echo c > /proc/sysrq-trigger )
-   - The crash dump should be taken now and the system should reboot
-   - Confirm the dump exists in /var/crash
-   - Install the debug symbols for the kernel
-   - Use crash to inspect the crash dump
+   - Install kdump-tools update on stonking from PPA above
+   - Reboot
+   - Confirm kdump is configured with `kdump-config show`. If it isn't, do it 
manually ( https://ubuntu.com/server/docs/how-to/software/kernel-crash-dump/ )
+   - Take a dump manually ( # echo c > /proc/sysrq-trigger )
+   - The crash dump should be taken now and the system should reboot
+   - Confirm the dump exists in /var/crash
+   - Install the debug symbols for the kernel
+   - Use crash to inspect the crash dump
  
  [ Other Info ]
  
  * I plan to get these changes into Debian in the future, but didn't have
  the time to get it there first before stonking.
  
  [ Original Description ]
  
  supposedly ubuntu kdump & ubuntu dracut do not work together. like at
  all.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2042955

Title:
  FFe: kdump tools X dracut doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2042955/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to