Merge ~powersj/cloud-init:fix-integration-snappy into cloud-init:master
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Approved by: | Scott Moser on 2017-05-23 | ||||
| Approved revision: | b6c5ed3b04a00bba7e49ebb58947926b4f121e88 | ||||
| Merged at revision: | 06a7f0afc4db3f8ba2a6b3b521274ee45a028ef2 | ||||
| Proposed branch: | ~powersj/cloud-init:fix-integration-snappy | ||||
| Merge into: | cloud-init:master | ||||
| Diff against target: |
32 lines (+4/-7) 2 files modified
tests/cloud_tests/configs/modules/snappy.yaml (+2/-2) tests/cloud_tests/testcases/modules/snappy.py (+2/-5) |
||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Scott Moser | 2017-05-22 | Approve on 2017-05-23 | |
| Server Team CI bot | continuous-integration | Approve on 2017-05-23 | |
|
Review via email:
|
|||
Commit Message
tests: Fix snapd test case for non-started service
Snapd does not start on artful or on the versions in proposed. This
changes the behavior of the test to confirm that snapd is installed, not
that it is started, while the snap team fixes the issue.
LP: #1690880
| Ryan Harper (raharper) wrote : | # |
| Joshua Powers (powersj) wrote : | # |
We could have a version-based check, however the version that breaks this, 2.26, is in proposed and about to migrate to all supported releases at any day. I certainly expect this to be fixed unless someone tells me that what we are doing (e.g. running snapd in a container) isn't allowed.
My original intent with the test was to confirm that "system_snappy: auto" works by setting up and install snapd on the target system and using 'snap --version' seemed like the best method to confirm that is installed. However, this bug has shown that the output of --version changes based on whether snapd is even running.
Thoughts?
PASSED: Continuous integration, rev:201e100de76
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild:
https:/
- b6c5ed3... by Joshua Powers on 2017-05-23
PASSED: Continuous integration, rev:b6c5ed3b04a
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
Click here to trigger a rebuild:
https:/
| Joshua Powers (powersj) wrote : | # |
Updated the test content to check that snapd is installed using dpkg output rather than relying on --version output.
| Scott Moser (smoser) wrote : | # |
I'll pull this for now with a slight modification of the commit message.


Hrm, do we have a release-based (or even version-based) check here?
Presumable older images with snapd working/starting would continue to work.
Can we instead examine the installed version (via os's package system) and
infer the behavior? Or split this into two tests. one (is it installed) and then if it's installed to also check versions (ie, do we expect this to get fixed or is it an expected change in behavior?)