Bug 707034
| Summary: | [6.1 FEAT] Intuitive dump device configuration workflow and dialogue | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Cantrell <dcantrell> | ||||||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||
| Priority: | high | ||||||||||||||
| Version: | rawhide | CC: | anaconda-maint-list, bhinson, bugproxy, hamzy, jjarvis, jonathan, jstodola, mgrf, nobody+PNT0273897, vanmeeuwen+fedora | ||||||||||||
| Target Milestone: | --- | Keywords: | FutureFeature | ||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | s390x | ||||||||||||||
| OS: | All | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | 633398 | Environment: | |||||||||||||
| Last Closed: | 2012-06-27 13:50:21 UTC | Type: | --- | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Bug Depends On: | |||||||||||||||
| Bug Blocks: | 633398, 638197, 705163 | ||||||||||||||
| Attachments: |
|
||||||||||||||
Created attachment 521856 [details]
perl sample script for DASD
Created attachment 521857 [details]
perl sample script for SCSI
Hi Georg, On x86 the dump configuration (kdump) is done in firstboot, which happens after install and the first time the system comes up. Now that we have firstboot working on z, to be more consistent, we should add the z dump configuration in firstboot instead of anaconda. What do you think? -Brad Hi Brad, Yes first boot would also be ok instead of anaconda Just a simple to handle user interface for setting up the dump devices Site note: Good news -new to me- that first boot is functional again for System z Its been rejected for years throughout RHEL 5 ------- Comment From rsisk.com 2010-10-04 11:24 EDT------- Code Upstream Status: Pending ------- Comment From mgrf.com 2010-12-13 12:15 EDT------- Accept reject for R 6.1 - will request this for R 6.2 again ------- Comment From mgrf.com 2011-08-24 15:37 EDT------- Per discussion with John I assign this feature to the RHEL 6.3 tracking list This also get discussed in Fedora via ticket 707034 The process of mirroring from/to Fedora is actually in discussion 1) assign this feature BZ to the Fedora ticket when Fedora is resolved re-assign to R 6.3 2) create reverse mirror of the Fedora ticket and have parallel tracking Created attachment 531440 [details]
dump_install_dasd.pl
------- Comment on attachment From michael.holzheu.com 2011-09-13 08:48 EDT-------
Update for RHEL6
Created attachment 531441 [details]
dump_install_scsi.pl
------- Comment on attachment From michael.holzheu.com 2011-09-13 08:49 EDT-------
Update for RHEL6
As discussed I re-call + Yes setting up dump devices in first boot would also be ok + just a simple to handle user interface for setting up the dump devices -> Setting this up in first boot would avoid any changes in installer ? ------- Comment From mgrf.com 2012-06-07 06:48 EDT------- This feature got implemented into R 6.3 via 74353 - RH 745495 [6.3 FEAT] Two Stage Dumper framework - installer This feature is verified on R 6.3 snapshots -> set to verified on IBM site *** This bug has been marked as a duplicate of bug 745495 *** |
Created attachment 521855 [details] RHEL 6 dump install description