cloud-final.service runs after cloud-config.service so either will work. I proposed cloud-final.service in my patch since prior to `debian/patches/0005-make-service-directive-explicit.patch` being added, that was the ordering constraint in place. The 0005 patch removes it due to redundancy, which has since clearly been changed but I thought it was cleaner to revert to the original ordering. Either ordering (cloud-config and cloud-final) appear to solve the issue in testing.
> Why the patch in https:/ /bugs.launchpad .net/ubuntu/ +source/ google- guest-agent/ +bug/2057965/ comments/ 5 and Impact description order gga after cloud-final.service but the merged (temporal) cpc_packaging.extra MRs order gga after cloud-config. service?
cloud-final.service runs after cloud-config. service so either will work. I proposed cloud-final.service in my patch since prior to `debian/ patches/ 0005-make- service- directive- explicit. patch` being added, that was the ordering constraint in place. The 0005 patch removes it due to redundancy, which has since clearly been changed but I thought it was cleaner to revert to the original ordering. Either ordering (cloud-config and cloud-final) appear to solve the issue in testing.