Merge ~rbalint/cloud-init:fix-1717477 into cloud-init:master
| Status: | Merged |
|---|---|
| Approved by: | Scott Moser on 2017-09-15 |
| Approved revision: | 523da2740785a8f2d8fb0dc7ecf9235675716687 |
| Merged at revision: | 523da2740785a8f2d8fb0dc7ecf9235675716687 |
| Proposed branch: | ~rbalint/cloud-init:fix-1717477 |
| Merge into: | cloud-init:master |
| Diff against target: |
47 lines (+0/-12) 3 files modified
dev/null (+0/-2) packages/redhat/cloud-init.spec.in (+0/-6) setup.py (+0/-4) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Scott Moser | 2017-09-15 | Approve on 2017-09-15 | |
|
Review via email:
|
|||
Commit Message
Do not provide systemd-fsck drop-in which could cause ordering cycles.
Revert "centos: do not package systemd-fsck drop-in."
Revert "systemd: make systemd-fsck run after cloud-init.service"
The systemd-fsck drop-in caused regressions by introducing ordering
The change reverts the original commit that added systemd-fsck drop-in
and another commit that had removed that from the centos packaging:
1f5489c258a
8a5296c41db
The result is to no longer provide the systemd-fsck drop-in.
LP: #1717477
- 523da27... by Balint Reczey on 2017-09-15
| Balint Reczey (rbalint) wrote : | # |
| Scott Moser (smoser) wrote : | # |
I built a package with this, and then installed it into an artful system.
the installation resulted in
/lib/systemd/
being removed, so that seems right to me.
I've re-written the commit message to a single commit that we can then
cherry pick for the SRU.


Needs testing