Custom AMI doesn't run ignition when used

[ziyuanchen-db]

Bug

I built a custom AWS AMI by creating an EC2 instance using the stock AMI, then added some customizations to it. However when I tried to create new instances using this AMI with metadata, I didn't see any new logs from sudo journalctl --identifier=ignition --all meaning ignition was never rerun. It seems ignition thinks that it has already run because a snapshot was taken from a booted VM.

Operating System Version

Ignition Version

2.14.0

Environment

What hardware/cloud provider/hypervisor is being used to run Ignition?

Expected Behavior

The AMI should be in a clean state and should have ignition running in a VM when it first boots.

Actual Behavior

Ignition seems to think of an AMI as a rebooted machine and never runs.

Reproduction Steps

1. ...
2. ...

Other Information

[travier]

I built a custom AWS AMI by creating an EC2 instance using the stock AMI, then added some customizations to it.

How did you customize your AMI? If you booted it then Ignition has already run and will refuse to run anymore.