Adding ubuntu core fails on first boot with rtc is present

[bugraaydogar]

Hi @rahul-tt,

There was a similar discussion last year that can be seen in the thread below.

Custom UC20 Image for RPi4 fails

Hi all, I was experimenting with the custom UC20 image creation process for my RPi4. After creating and flashing the image, I have an expired public key error which makes the system unbootable. It is quite strange that the mentioned keys are just registered and everything seems fine. In addition to that, I did not really understand how the system checks if these public keys are valid or not without internet access. Here is the logs; Here you can also see the model assertion file. A…

The initial problem was available in all of the systems that do not have a RTC. Basically, the initrd was stuck at Nov 2019, so if you created the key that you signed your model assertion with after that date, then the image was unable to boot. Then the engineering team improved the situation by introducing fetching the timestamp of the trusted assertions (e.g.model-assertion, system-user assertion) and move the system time forward accordingly. Therefore, the problem was solved.

Considering that, if I understand your situation correctly, although you have a RTC in your system, it is not actively used. So your situation is identical.

By looking at the error messages you have shared;

statenegine.go 149: state ensure error: devimgr: cannot seed: cannot accept some assertions: -assertion is signed with expired public key “” from “canonical”

• no matching public key “” for signature by canonical

Why is there an assertion in your system that is signed by “canonical” ? I would highly recommend double checking your model.json and assertion files in case you used an assertion coming from Canonical rather than you.