Feature #16300
closedAdd vm.overcommit_memory check
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1369589
Description of problem:
There should be a check to ensure that the vm.overcommit_memory variable is set to 0 on Red Hat Satellite 6.X
We have two scripts to add this check into:
One is : https://access.redhat.com/solutions/1474003
The other is the pre-upgrade check preformed by the foreman-installer itself:
- foreman-rake katello:upgrade_check
Version-Release number of selected component (if applicable):
How reproducible:
Very
Steps to Reproduce:
1. Set teh vm.overcommit to 2 and the upgrade will fail every time.
2.
3.
Actual results:
Currently there is no check for this.
Expected results:
For either the healthcheck script or the preupgrade script to flag this as needing to be fixed.
Additional info:
This BZ is related to https://access.redhat.com/solutions/2548501
Updated by Chris Roberts over 8 years ago
- Subject changed from Add vm.overcommit_memory check to Add vm.overcommit_memory check
- Assignee set to Chris Roberts
- Target version set to 126
- Difficulty set to easy
Updated by The Foreman Bot over 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello-installer/pull/398 added
Updated by Chris Roberts over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello-installer|18ec940b7e9b9c541cb64e0a12b773034a41ba52.
Updated by Justin Sherrill over 8 years ago
- Translation missing: en.field_release set to 162