Comment 1 for bug 1982902

Thanks for filing a bug and helping make cloud-init better.

I'm having a hard time with these logs deterimining what may be contributing to the configdrive device busy. I suppose we could add a bit of retry logic on device busy errors here, but I'm not sure whether this is due to the underlying system being under high load or some other symptom that leads to this.

Would it be possible to run `cloud-init collect-logs` and attach the resulting tarfile of logs/system configuration to this bug to help us triage.
Note if providing
collect-logs --include-userdata that you may want to inspect the userdata included to make sure no secrets or passwords are included in the tarfile.

Much thanks.