It may take several hours of a cloned machine running before it is noticed by the backend.
Expected behavior
Clones should be counted right away after boot.
This may involve running ua-timer on boot (and bypassing the jobs-status.json timestamp check), or running a separate service that only does the activity-ping on boot.
Current behavior
The activity ping doesn't occur until ua-timer.service runs and enough time has passed since the timestamp in jobs-status.json.
To Reproduce
Please include details on how to reproduce the bug.
Launch a VM/Container
attach it
snapshot it
launch a clone
see that activityID has not changed (therefore it hasn't been counted)
Description of the bug
It may take several hours of a cloned machine running before it is noticed by the backend.
Expected behavior
Clones should be counted right away after boot.
This may involve running ua-timer on boot (and bypassing the
jobs-status.jsontimestamp check), or running a separate service that only does the activity-ping on boot.Current behavior
The activity ping doesn't occur until
ua-timer.serviceruns and enough time has passed since the timestamp injobs-status.json.To Reproduce
Please include details on how to reproduce the bug.
activityIDhas not changed (therefore it hasn't been counted)System information: