Project

General

Profile

Actions

Feature #16300

closed

Add vm.overcommit_memory check

Added by Stephen Benjamin over 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Installer
Target version:
Difficulty:
easy
Triaged:
Fixed in Releases:
Found in Releases:

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:

  1. 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

Actions #1

Updated by Chris Roberts over 7 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
Actions #2

Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello-installer/pull/398 added
Actions #3

Updated by Chris Roberts over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #4

Updated by Justin Sherrill over 7 years ago

  • translation missing: en.field_release set to 162
Actions

Also available in: Atom PDF