Merge ~yeazelm/cloud-init:ssh_authorizedkeys into cloud-init:master
| Status: | Needs review |
|---|---|
| Proposed branch: | ~yeazelm/cloud-init:ssh_authorizedkeys |
| Merge into: | cloud-init:master |
| Diff against target: |
99 lines (+49/-2) 3 files modified
cloudinit/sources/DataSourceAzure.py (+1/-1) cloudinit/ssh_util.py (+7/-0) tests/unittests/test_sshutil.py (+41/-1) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Server Team CI bot | continuous-integration | Needs Fixing on 2018-01-08 | |
| Scott Moser | 2017-10-05 | Needs Fixing on 2017-11-21 | |
|
Review via email:
|
|||
Description of the Change
Fix issue with multiple AuthorizedKeysFile entries
If a user puts two entries for AuthorizedKeysFile in an sshd_config,
then cloud-init would fail when trying to add keys.
The change is to pick the first entry.
LP: #1404060
FAILED: Continuous integration, rev:
https:/
Executed test runs:
SUCCESS: Checkout
FAILED: Unit & Style Tests
Click here to trigger a rebuild:
https:/
- 50ad259... by Matthew Yeazel on 2017-11-13
| Matthew Yeazel (yeazelm) wrote : | # |
Added an additional test and fixed the formatting (I think). Is there a way I can kick off the CI?
| Scott Moser (smoser) wrote : | # |
I started one. It should post shortly
On November 13, 2017 4:59:59 PM EST, Matthew Yeazel <email address hidden> wrote:
>Added an additional test and fixed the formatting (I think). Is there a
>way I can kick off the CI?
>--
>https:/
>You are reviewing the proposed merge of
>~yeazelm/
FAILED: Continuous integration, rev:
https:/
Executed test runs:
SUCCESS: Checkout
FAILED: Unit & Style Tests
Click here to trigger a rebuild:
https:/
- 4dd5d27... by Matthew Yeazel on 2017-11-14
| Matthew Yeazel (yeazelm) wrote : | # |
Ok, from what I can tell I fixed my tests, but it looks like pre-existing tests still fail.
FAILED: Continuous integration, rev:d5de4e2fdb7
https:/
Executed test runs:
SUCCESS: Checkout
FAILED: Unit & Style Tests
Click here to trigger a rebuild:
https:/
- c02b357... by Matthew Yeazel on 2017-11-16
FAILED: Continuous integration, rev:ed2496354f0
https:/
Executed test runs:
SUCCESS: Checkout
FAILED: Unit & Style Tests
Click here to trigger a rebuild:
https:/
- 1de7f2e... by Matthew Yeazel on 2017-11-16
FAILED: Continuous integration, rev:3f65e992d94
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
FAILED: Ubuntu LTS: Integration
Click here to trigger a rebuild:
https:/
FAILED: Continuous integration, rev:3f65e992d94
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
FAILED: Ubuntu LTS: Integration
Click here to trigger a rebuild:
https:/
| Scott Moser (smoser) wrote : | # |
Matthew,
Sorry for delay.
I took a look today, and had some more comments inline.
The mock.side_effect can definitely be confusing, but the way you did it does not get the change *undone*, so other tests will have your dummy_users_
http://
^ is a change that sums up what I tried to say in English.
| Matthew Yeazel (yeazelm) wrote : | # |
I agree with your comments, and your patch looks good. I'll push another commit with those changes.
- adab261... by Matthew Yeazel on 2017-11-21
FAILED: Continuous integration, rev:79b3c9e7b50
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
FAILED: Ubuntu LTS: Integration
Click here to trigger a rebuild:
https:/
| Scott Moser (smoser) wrote : | # |
OK.
Two things are causing your branch to fail integration test.
a.) your package is older than is in xenial. Thats not your fault
and I put a MP up to that at
https:/
b.) the integration tests will actually show a failure on this.
I'm pretty sure its not just noise.
Even though 'a' should make you not need to do it, you should rebase your
branch on master (git rebase master).
FAILED: Continuous integration, rev:764002694e6
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
FAILED: Ubuntu LTS: Integration
Click here to trigger a rebuild:
https:/
FAILED: Continuous integration, rev:c5781d2c148
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
FAILED: Ubuntu LTS: Integration
Click here to trigger a rebuild:
https:/
FAILED: Continuous integration, rev:adab2612b3b
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
FAILED: Ubuntu LTS: Integration
Click here to trigger a rebuild:
https:/
Unmerged commits
- adab261... by Matthew Yeazel on 2017-11-21
- 1de7f2e... by Matthew Yeazel on 2017-11-16
- c02b357... by Matthew Yeazel on 2017-11-16
- 4dd5d27... by Matthew Yeazel on 2017-11-14
- 50ad259... by Matthew Yeazel on 2017-11-13
- 895ba3c... by Matthew Yeazel on 2017-10-05


Hi, ssh_info.
A couple things
a.) run 'tox' on your branch . (I'll point the c-i at it and it will report here, but it will complain about long lines in your dummy_users_
b.) can you put a test for "expected" path ? just one where there
is only a single filename in Authorizedkeysfile.