Project

General

Profile

Bug #11125

When we have a /var full, Rudder LDAP or Postgres can be corrupted

Added by Nicolas CHARLES over 1 year ago. Updated about 1 year ago.

Status:
Released
Priority:
N/A
Category:
System integration
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
71

Description

When there's no space left on /var, ldap and/or postgres are at risk of failing hard - and not restart
Process to repair and restore is quite hard, so we need to prevent this situation (could be stop component before its too late, or something else...)


Subtasks

User story #11731: Add a new reason why rudder might not be loadedReleasedAlexis MOUSSET
Bug #11739: When we have a /var full, Rudder LDAP or Postgres can be corruptedReleasedAlexis MOUSSET
Bug #11740: When we have a /var full, Rudder LDAP or Postgres can be corruptedReleasedAlexis MOUSSET
Bug #11747: When we have a /var full, Rudder LDAP or Postgres can be corruptedReleasedAlexis MOUSSET

Associated revisions

Revision 0b7d8165 (diff)
Added by Benoît PECCATTE about 1 year ago

Fixes #11125: When we have a /var full, Rudder LDAP or Postgres can be corrupted

History

#1 Updated by Nicolas CHARLES over 1 year ago

  • Subject changed from When we have a /var full, Rudder LDAP or Postgres can be corrupded to When we have a /var full, Rudder LDAP or Postgres can be corrupted
  • Description updated (diff)
  • Category set to System integration
  • Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security

#2 Updated by Benoît PECCATTE over 1 year ago

  • User visibility set to Operational - other Techniques | Technique editor | Rudder settings
  • Priority changed from 0 to 76

We can manage the simple case: if /var is almost full, stop rudder, slapd and postgresql

#3 Updated by Benoît PECCATTE over 1 year ago

  • Assignee set to Benoît PECCATTE

This could be added to rudder agent check.

#4 Updated by Benoît PECCATTE about 1 year ago

  • Target version set to 3.1.24
  • Priority changed from 76 to 73

#5 Updated by Benoît PECCATTE about 1 year ago

  • Status changed from New to In progress

#6 Updated by Benoît PECCATTE about 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/1391

#7 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.24 to 3.1.25

#8 Updated by Benoît PECCATTE about 1 year ago

  • Priority changed from 73 to 72

#9 Updated by Benoît PECCATTE about 1 year ago

  • Assignee changed from Alexis MOUSSET to Benoît PECCATTE

#10 Updated by Benoît PECCATTE about 1 year ago

  • Assignee changed from Benoît PECCATTE to Alexis MOUSSET

#11 Updated by Benoît PECCATTE about 1 year ago

  • Status changed from Pending technical review to Pending release

#12 Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from Pending release to Released
  • Priority changed from 72 to 71

This bug has been fixed in Rudder 3.1.25, 4.1.9 and 4.2.3 which were released today.

Also available in: Atom PDF