Description of problem:
If a user removes a package (like hostname), but decides to recover the package before initiating a reboot, the MicroShift Greenboot logic does not take this into account. It sets the boot_counter, but it does not trigger the system to restore back to the previous known good image since the package was restored using rpm-ostree override reset. After a reboot, the boot_counter variable is still set. Please see attached log file
The workaround is to initiate a second reboot that will clear the counter.

Version-Release number of selected component (if applicable):

How reproducible:
100%

Steps to Reproduce:
1.Install MicroShift
2.rpm-ostree override remove hostname
3.rpm-ostree override reset hostname
4.Reboot
5. Observer output of journalctl -o cat -u greenboot-healthcheck.service, boot_counter=2 will still be set

Actual results:
boot_counter=2 is still set if rpm-ostree override reset hostname

Expected results:
boot_counter should not be visible if rpm-ostree override reset hostname is issued

Additional info: