sts-sponsors team mailing list archive

[Jorge Merlino <1999816@xxxxxxxxxxxxxxxxxx>]

I've been investigating this issue but I could not find the exact difference between 3.8 and 3.9 that accounts for that change.
The output of the status command will indeed be different between 3.8 and 3.9 in this case as in one will say that the free space is unknown and in the other that the free space is undefined. I don't think that is important as long as the command works. It would be easy anyway to equalize that just changing the return value of the function to :unknown
I talked to upstream but they could not pinpoint the difference for me and they are not accepting patches for 3.8 either as there will be no new versions.
So, to move this forward I propose modifying that patch to change the origin from upstream to backport and leave the reference for the original patch. 
What do you think?

-- 
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1999816

Title:
  Failure to get free disk space breaks "rabbitmqctl status" command

Status in rabbitmq-server package in Ubuntu:
  Fix Released
Status in rabbitmq-server source package in Focal:
  Incomplete
Status in rabbitmq-server source package in Jammy:
  In Progress
Status in rabbitmq-server source package in Kinetic:
  In Progress

Bug description:
  [Impact]

  When for some reason the df command fails to get the disk free space
  (for example timeout on a heavily loaded system) the result is a
  harcoded value of "unknown". As this is not a valid number this
  generates arithmetic errors when the "rabbitmqctl status" command is
  run and tries to divide that value to convert it to another unit.

  This has been fixed upstream here:
  https://github.com/rabbitmq/rabbitmq-server/pull/4897

  [Test Plan]

  The df command can be linked to another file that just waits for a few
  minutes to force a timeout for example: [detailed steps in comment
  #5].

  #!/bin/bash
  sleep 5m

  After the timeout occurs the "rabbitmqctl status" returns an error
  with the unpatched version. After the patch it shows all the
  information and displays unknown in the free space line.

  [Where problems could occur]

  The patch just changes the display of information, it should not break
  anything in the core operations of the package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1999816/+subscriptions