canonical / canonical/cloud-init

[enhancement]: Integration tests: change the cloud-init source in the actual image (not post-boot deb package installation)

Open
#6,885 6 comments 0 reactions 0 assignees View on GitHub
enhancement incomplete
Dominant language
Python
Stars
3.8k
Forks
1.1k
Avg merge
2d 23h
Merged PRs (30d)
18

Description

# Enhancement

I know this is porbably an overkill (probably new security scan on the modified image per CI run) but it's worth reporting.

In https://github.com/canonical/cloud-init/pull/6860 , my new integration test was succeeding locally while failing in the CI. I am 99% sure because:
- the test involved changing the default user settings
- my local environment was lxd contianers so cloud-init source was used in place
- the github CI was using a debian package (so it is installed post-boot)

Even when I added a commit to cloud-init clean then reboot then do the test assertions, I got the same error

I guess this can be solved if we modify the cloud-init scripts in the image (there are tools to modify in-place files in static images) instead of building a deb package then installing it after the instance creation

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.