Unexpected hardware sync state change

[maasuser1]

3.4.0-14321-g.1027c7664
The event log shows hardware sync state change even if nothing was changed, as shown in the figure. The machine was running Ubuntu 22.04 LTS.

[maasuser1 (maasuser1)]

This issue has also been observed on Ubuntu 20.04 LTS.

[Björn Tillenius (bjornt)]

Do you see these message all the time, or are you referring to that some of the messages with the same timestamp were duplicated?

If the former, can you provide the event log from the API, so we can see how often they repeat?

[maasuser1 (maasuser1)]

Hi Björn,

I saw these messages all the time. They repeat every 15 minutes.

[Alexsander de Souza (alexsander-souza)]

Hi, can you provide the output of the following commands:

- maas $PROFILE node-script-result download $SYSTEM_ID current-commissioning

- maas $PROFILE node-devices read $SYSTEM_ID

This will help us to understand the initial state and why MAAS thinks the current state needs updating

[Björn Tillenius (bjornt)]

I can confirm this. All you have to do is to deploy a machine with hardware sync enabled. Then you will see log messages about hardware sync changes.

It seems like we don't actually check that something changed.

Also, at least for CPU, we log that a CPU is added every time a CPU wasn't created in the database.

See also bug 2062141.

[maasuser1 (maasuser1)]

Still observed on 3.4.2/stable with Ubuntu 18.04 LTS.