[Bug 2066983] Re: Bug in /etc/update-motd.d/50-landscape-sysinfo script - incorrect variable used for load threshold calculation

[Spencer Runde]

Hi Simon,

It doesn't look like the relevant change is present in ubuntu/devel:
https://git.launchpad.net/ubuntu/+source/landscape-
client/tree/debian/landscape-sysinfo.wrapper

I'm not sure why that MP got marked as 'superseded'.  We will want this
fix in Oracular as well.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2066983

Title:
  Bug in /etc/update-motd.d/50-landscape-sysinfo script - incorrect
  variable used for load threshold calculation

Status in landscape-client package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

   * The CPU load is incorrectly calculated, and users won't get system info in
  the message-of-the-day (motd).

   * The `cores` variable was misnamed; it should be `CORES` since bash
  variables are case-sensitive

  * Affects landscape-client on noble, mantic, jammy, and focal.

  [ Test Plan ]

  Steps to Reproduce:

      1. Open the /etc/update-motd.d/50-landscape-sysinfo script.
      2. Notice the line where THRESHOLD is set: THRESHOLD="${cores:-1}.0".
      3. The correct variable should be CORES instead of cores.

  To trigger MOTD and view incorrect calculation:

  sudo run-parts /etc/update-motd.d/
  Notice message: " System information disabled due to load higher than 1.0" even on systems with multiple cores.

  [ Where problems could occur ]

   * This fix will necessarily run the system process info on more
  systems during MOTD.  If the CPU load threshold was poorly chosen,
  then overly-loaded systems might be slow during MOTD while landscape-
  sysinfo runs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/2066983/+subscriptions