Comment 5 for bug 2043997

Revision history for this message
Marian Gasparovic (marosg) wrote (last edit ):

I noticed there are many "[warn] Next IP address to allocate from 'oam (10.246.164.0/22)' has been observed previously:..." messages in maas.log during the problematic period (Nov 18, 19, 20)

grep "Next IP address to allocate" maas.log |sed "s/T.*//"|uniq -c
    352 2023-10-13
   2011 2023-10-14
   1908 2023-10-15
   1731 2023-10-16
   1571 2023-10-17
   1509 2023-10-18
   1453 2023-10-19
   1140 2023-10-20
    455 2023-10-21
    462 2023-10-22
    434 2023-10-23
    268 2023-10-24
    610 2023-10-25
    862 2023-10-26
   1018 2023-10-27
    793 2023-10-28
    731 2023-10-29
   1103 2023-10-30
   1017 2023-10-31
    982 2023-11-01
    778 2023-11-02
   1137 2023-11-03
   1127 2023-11-04
     98 2023-11-05
    695 2023-11-06
   1179 2023-11-07
   1360 2023-11-08
   1173 2023-11-09
   1263 2023-11-10
   1160 2023-11-11
   1378 2023-11-12
   1454 2023-11-13
    937 2023-11-14
    512 2023-11-15
   1128 2023-11-16
    995 2023-11-17
 504694 2023-11-18
1675764 2023-11-19
 891664 2023-11-20
    335 2023-11-21

And they started to be excessive after 15:00
     20 2023-11-18T00
     57 2023-11-18T01
     49 2023-11-18T02
      3 2023-11-18T03
     20 2023-11-18T04
    222 2023-11-18T05
     95 2023-11-18T06
    232 2023-11-18T10
    911 2023-11-18T11
    279 2023-11-18T12
    111 2023-11-18T13
    331 2023-11-18T14
  28568 2023-11-18T15
  42623 2023-11-18T16
  40828 2023-11-18T17
  45518 2023-11-18T18
  63902 2023-11-18T19
  69211 2023-11-18T20
  70637 2023-11-18T21
  71009 2023-11-18T22
  70068 2023-11-18T23