[Linux] Fix cloud-init GOSC failure on Ubuntu and Photon OS #479
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When enabling and starting cloud-init services on Ubuntu with latest cloud-init version, it will cause network interface down. By consulting with GOSC team, it is suggested to only enable but no start cloud-init services when enabling cloud-init GOSC.
On Photon OS OVA deployment, installing latest chrony will also lead to cloud-init service failure. As chrony won't affect Photon OS testing, so this fix removed it from Photon OS OVA's user data.
Besides, to gain more information to debug GOSC failures, this fix adjusted GOSC testing workflow, which will always collect tools deploypkg log for both perl GOSC and cloud-init, cloud-init config and logs for cloud-init GOSC.
And some ansible-lint errors were also fixed.