Review: Approve continuous-integration
PASSED: Continuous integration, rev:ac38c650c1b6cb9df4021786d772450470f17aff
https://jenkins.ubuntu.com/server/job/cloud-init-ci/1176/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu
Review: Approve continuous-integration
PASSED: Continuous integration, rev:485384fe14caf0a3da01dfd7d5c79027e2c00161
https://jenkins.ubuntu.com/server/job/cloud-init-ci/1141/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu
Maybe, but I don't think we really wanted to always append a header to the
file, and we certainly wanted to avoid writing the file if we didn't have a
config. Lastly the side-effect of modifying resolvconf without dns settings
disabled system auto-generation.
We do need to be careful w.r.t det
It can be argued that cloud-init *was* doing the right thing.
It was told that there were no dns servers and no dns 'search' (by lack of that
in network config).
dhcp muddies that argument for sure.
That said, based on the content in the description of the bug (the
previously-existing /etc/resol
Review: Approve continuous-integration
PASSED: Continuous integration, rev:cc70b43e9becd6a469ed17430c5907b85b5f2b2d
https://jenkins.ubuntu.com/server/job/cloud-init-ci/1139/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu
5 matches
Mail list logo