Merge ~raharper/cloud-init:fix/cloud-test-apt-pipelining into cloud-init:master
Proposed by
Ryan Harper
Status: | Merged |
---|---|
Approved by: | Dan Watkins |
Approved revision: | 197bccde20622501c7c6e7e0e011c6414f98128b |
Merge reported by: | Server Team CI bot |
Merged at revision: | not available |
Proposed branch: | ~raharper/cloud-init:fix/cloud-test-apt-pipelining |
Merge into: | cloud-init:master |
Diff against target: |
54 lines (+8/-10) 3 files modified
tests/cloud_tests/testcases/modules/apt_pipelining_disable.yaml (+1/-2) tests/cloud_tests/testcases/modules/apt_pipelining_os.py (+3/-3) tests/cloud_tests/testcases/modules/apt_pipelining_os.yaml (+4/-5) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Server Team CI bot | continuous-integration | Approve | |
Dan Watkins | Approve | ||
Review via email: mp+365349@code.launchpad.net |
Commit message
cloud_tests: fix apt_pipelining test-cases
The apt_pipelining test-cases were broken but until cloud-init
changed it's default behavior to not disable, these silently passed
as both only ever checked if pipelinging was disabled.
First, the tests used the 'apt' namespace, which is not for
configuring pipelining, rather that requires 'apt_pipelining'
as the namespace.
Second, the 'os' variant needs to check that cloud-init does not
write a configuration file; it was a copy-and-paste error from the
disable test-case.
This branch fixes the config and collection to validate both
scenarios.
To post a comment you must log in.