[Bug 2142650] [NEW] autopkgtests in noble are flaky causing reoccurring pain for many uploads

[Christian Ehrhardt]

Public bug reported:

Hi,
the package and tests of ceilometer in noble are not reliable.
=> https://autopkgtest.ubuntu.com/packages/ceilometer

You see that on most releases this is mostly fine, but on noble it isn't
if you go into noble I see a  following pattern (for example -
https://autopkgtest.ubuntu.com/packages/c/ceilometer/noble/amd64).

1. The tests are flaky, but known broken and not expected to pass
2. something passes the test, by random chance it seems
3. from then on all things are blocked as they run into the same issue
4. people run many retries to overcome it
5. as some point someone explodes, runs migration-reference/0 and it is again expecting not to pass
*. loop by jumping to 2.

Since it seems fixed in later releases, could I ask you to have a look
what makes this so flaky and maybe resolve that?

And if the conclusion to to not resolve it for $goodreason then please
add an unversioned test hint for noble that it should stay bad and not
randomly work to be resetting the expectation.

** Affects: ceilometer (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: ceilometer (Ubuntu Noble)
     Importance: Undecided
         Status: New

** Also affects: ceilometer (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Changed in: ceilometer (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to ceilometer in Ubuntu.
https://bugs.launchpad.net/bugs/2142650

Title:
  autopkgtests in noble are flaky causing reoccurring pain for many
  uploads

Status in ceilometer package in Ubuntu:
  Invalid
Status in ceilometer source package in Noble:
  New

Bug description:
  Hi,
  the package and tests of ceilometer in noble are not reliable.
  => https://autopkgtest.ubuntu.com/packages/ceilometer

  You see that on most releases this is mostly fine, but on noble it
  isn't if you go into noble I see a  following pattern (for example -
  https://autopkgtest.ubuntu.com/packages/c/ceilometer/noble/amd64).

  1. The tests are flaky, but known broken and not expected to pass
  2. something passes the test, by random chance it seems
  3. from then on all things are blocked as they run into the same issue
  4. people run many retries to overcome it
  5. as some point someone explodes, runs migration-reference/0 and it is again expecting not to pass
  *. loop by jumping to 2.

  Since it seems fixed in later releases, could I ask you to have a look
  what makes this so flaky and maybe resolve that?

  And if the conclusion to to not resolve it for $goodreason then please
  add an unversioned test hint for noble that it should stay bad and not
  randomly work to be resetting the expectation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/2142650/+subscriptions