Bug 475677
Summary: | [LTC 5.4 FEAT] Firstboot for System z [201092] | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | IBM Bug Proxy <bugproxy> |
Component: | firstboot | Assignee: | Chris Lumens <clumens> |
Status: | CLOSED NOTABUG | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.4 | CC: | andriusb, atodorov, bhinson, borgan, hpicht, jjarvis |
Target Milestone: | alpha | Keywords: | FutureFeature, OtherQA |
Target Release: | 5.4 | ||
Hardware: | s390x | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-09-29 14:12:44 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: | 445204, 483784 |
Description
IBM Bug Proxy
2008-12-09 23:50:32 UTC
*** Bug 36226 has been marked as a duplicate of this bug. *** This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?". ------- Comment From gmuelas.com 2009-03-30 06:02 EDT------- Hello Red Hat Product Management, what is the concrete reason to reject this feature for RHEL 5.4? what would be Red Hat's impact of accepting this feature for RHEL 5.4? Thank you! Gonzalo Muelas Serrano. ------- Comment From tpnoonan.com 2009-04-21 23:15 EDT------- Hi John, Would you please take a second look at the following three rejected System z features for RHEL5.4 based on the justifications provided. It looks like these are being rejected due to Red Hat resources???. All three look to improve the IBM/Red Hat System z customer experience. The justifications are also documented in the feature bugzillas. Many thanks. 1.) First boot on System z Red Hat Bugzilla 475677 LTC 50304 ??-?? [LTC 5.4 FEAT] Firstboot for System z [201092] Status and related bugzillas: Has been reported with LTC 36226 ??-?? RIT126279- firstboot needed on IBM System z distribution On Red Hat advice, a feature request was opened for RHEL 5.2 with LTC 37758 ??-?? RHBZ 217921: 201092: Firstboot for System z Finally implemented and tested on RHEL 5.3 alpha. First boot is still disabled, not visible to the customer because it is not automatically initialized. Red Hat reason for reject: This component is not scheduled to be updated in the current Red Hat Enterprise Linux release. Business justification: This feature is needed to have in System z a post-install configuration the same way the customers are used to in other platforms and/or operating systems: - After a new installation, during the first boot of the system, RHEL on System z should automatically ask/help the customer to configure security tasks like: Red Hat Network for security update Firewall SELinux Without this feature, the customer has to do everything manually, having a big security risk if the customer misses this step, and that is why in the other platforms and/or operating system this task is prompt automatically after the first boot on a newly installed system. ------- Comment From mgrf.com 2009-04-27 13:04 EDT------- Hello Red Hat, Hi John, What is the status regarding RHEL 5.4 acceptance for this feature? This feature is denied for RHEL 5.4 due to a lack of resources. ------- Comment From gmuelas.com 2009-04-28 08:03 EDT------- Hello Red Hat, - if IBM takes over the QA (Test) responsibility for this feature, would you still have not resources to implement it? - IBM believes that this it is a very interesting feature for the RHEL 5 System z customers, but since to implement this feature, RHEL would need changes in firstboot and we already in the 4th minor update, is Red Hat interested in this feature at all for future minor updates in RHEL 5, assuming you have the resources for future RHEL 5 minor updates? Thank you! Gonzalo Muelas Serrano. ------- Comment From mgrf.com 2009-08-03 05:41 EDT------- Red Hat is rejecting this feature since RHEL 5.2. IBM not pursue this anymore for RHEL 5.5. Closing feature request for RHEL 5 stream Closing per last comment. |