Comment 5 for bug 2016929

Hi Jane and thank you for your bug report.

It appears that the NZ archive mirror was syncing during the installation.
We worked this cycle on making subiquity proactively detect this kind of problem if possible, but sadly it is not a failproof solution.

From the syslog:

Apr 19 10:51:43 ubuntu subiquity_log.2982[6036]: File has unexpected size (14625628 != 14607080). Mirror sync in progress? [IP: 163.7.134.112 80]
Apr 19 10:51:43 ubuntu subiquity_log.2982[6036]: Hashes of expected file:
Apr 19 10:51:43 ubuntu subiquity_log.2982[6036]: - Filesize:14607080 [weak]
Apr 19 10:51:43 ubuntu subiquity_log.2982[6036]: - SHA256:00ab6434959abee6e7238bf896dcfca83e79646576ca867b504d5f91a7c1b21e
Apr 19 10:51:43 ubuntu subiquity_log.2982[6036]: - SHA1:a9c8f7cc42993e6dfe7cc433c5da601164231bd8 [weak]
Apr 19 10:51:43 ubuntu subiquity_log.2982[6036]: - MD5Sum:cf13aa77066561d70105743b839dba4c [weak]
Apr 19 10:51:43 ubuntu subiquity_log.2982[6036]: Release file created at: Tue, 18 Apr 2023 19:50:16 +0000
Apr 19 10:51:43 ubuntu subiquity_log.2982[6036]: Get:12 http://nz.archive.ubuntu.com/ubuntu lunar/universe amd64 DEP-11 Metadata [3,801 kB]
Apr 19 10:51:43 ubuntu subiquity_log.2982[6036]: Err:12 http://nz.archive.ubuntu.com/ubuntu lunar/universe amd64 DEP-11 Metadata
[...]

https://bugs.launchpad.net/subiquity/+bug/2012493 is another similar bug report.

> Does this actually need to be private? I'm using a VM for this and I can't think what information would be sensitive, but I'm willing to be corrected.

Yes, public reports are usually better for tracking :) Thanks for doing the update. Usually on VM, there isn't much sensitive data. as you said.

Thanks,
Olivier