Merge ~smoser/cloud-init:cleanup/drop-ubuntu-init-switch into cloud-init:master
| Status: | Merged |
|---|---|
| Approved by: | Scott Moser on 2017-08-31 |
| Approved revision: | bc9d1b4806c8125ad2a4f954338955fa6f3e75aa |
| Merged at revision: | fa266bf8818a08e37cd32a603d076ba2db300124 |
| Proposed branch: | ~smoser/cloud-init:cleanup/drop-ubuntu-init-switch |
| Merge into: | cloud-init:master |
| Diff against target: |
254 lines (+4/-170) 8 files modified
config/cloud.cfg.tmpl (+0/-3) dev/null (+0/-160) doc/rtd/topics/modules.rst (+0/-1) packages/bddeb (+1/-2) packages/debian/dirs (+0/-1) packages/debian/rules.in (+1/-1) setup.py (+2/-0) tests/cloud_tests/configs/modules/TODO.md (+0/-2) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Server Team CI bot | continuous-integration | Approve on 2017-08-31 | |
| Chad Smith | 2017-08-30 | Approve on 2017-08-31 | |
|
Review via email:
|
|||
Commit Message
upstart: do not package upstart jobs, drop ubuntu-init-switch module.
The ubuntu-init-switch module allowed the use to launch an instance that
was booted with upstart and have it switch its init system to systemd and
then reboot itself. It was only useful for the time period when Ubuntu was
transitioning to systemd but only produced images using upstart.
Also, do not run setup with --init-
default, debian packages built with packages/bddeb will not have upstart
unit files included. No other removal is done here.
- 8555ddd... by Scott Moser on 2017-08-30
| Chad Smith (chad.smith) wrote : | # |
We need to drop the module from doc/rtd/
.. automodule:: cloudinit.
| Chad Smith (chad.smith) wrote : | # |
so that I understand intent here. We are leaving upstart logic in place so that tip could be used to still generate upstart-based packages if we wanted. We just don't want to package that init system by default anymore right?
| Scott Moser (smoser) wrote : | # |
> so that I understand intent here. We are leaving upstart logic in place so
> that tip could be used to still generate upstart-based packages if we wanted.
> We just don't want to package that init system by default anymore right?
correct.
we leave it all in place, but the upstream deb doesn't package it.
- 9167502... by Scott Moser on 2017-08-30
PASSED: Continuous integration, rev:8555dddadd5
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu LTS: Integration
SUCCESS: MAAS Compatability Testing
IN_PROGRESS: Declarative: Post Actions
Click here to trigger a rebuild:
https:/
PASSED: Continuous integration, rev:91675024ed0
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu LTS: Integration
SUCCESS: MAAS Compatability Testing
IN_PROGRESS: Declarative: Post Actions
Click here to trigger a rebuild:
https:/
| Chad Smith (chad.smith) wrote : | # |
Hrm, I'm still seeing upstart jobs included in /etc/init/*conf
dpkg -L cloud-init | grep etc/init
/etc/init
/etc/init/
/etc/init/
/etc/init/
/etc/init/
/etc/init/
/etc/init/
/etc/init/
/etc/init/
root@lxd-xenial:~# dpkg-query --show cloud-init
cloud-init 0.7.9-256-
| Scott Moser (smoser) wrote : | # |
I dont see the issues you're seeing . the etc/init/ files are not
present for me. See below. There was the empty etc/init/ directory
but I have a fix for that too i think.
$ git describe
0.7.9-257-g91675024
$ ./packages/bddeb -S -d
Creating a temporary tarball using the 'make-tarball' helper
Extracting temporary tarball 'cloud-
Creating a debian/ folder in '/tmp/tmpe5frrd
Running 'debuild -S -d -us -uc' in '/tmp/tmpe5frrd
Wrote 'cloud-
Wrote 'cloud-
Wrote 'cloud-
Wrote 'cloud-
Wrote 'cloud-
Wrote 'cloud-
Linked 'cloud-
$ sbuild --dist=artful --arch=amd64 --arch-all cloud-init_
$ pastebinit cloud-init_
http://
$ dpkg -c cloud-init_
drwxr-xr-x root/root 0 2011-12-16 11:50 ./etc/init/
$ dpkg -c cloud-init_
http://
- 8d180ec... by Scott Moser on 2017-08-31
| Scott Moser (smoser) wrote : | # |
$ dpkg -c /home/smoser-
nonoe there.
$ dpkg -c ../cloud-
http://
PASSED: Continuous integration, rev:8d180ecee1b
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu LTS: Integration
SUCCESS: MAAS Compatability Testing
IN_PROGRESS: Declarative: Post Actions
Click here to trigger a rebuild:
https:/
- bc9d1b4... by Scott Moser on 2017-08-31
| Chad Smith (chad.smith) wrote : | # |
+1 once unit tests complete here. Thanks for the fix. This is the issue I was seeing on my side
PASSED: Continuous integration, rev:bc9d1b4806c
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu LTS: Integration
SUCCESS: MAAS Compatability Testing
IN_PROGRESS: Declarative: Post Actions
Click here to trigger a rebuild:
https:/


PASSED: Continuous integration, rev:801c0cf7da2 05dc2bb0313eb99 a53df2b2b7c01b /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 230/
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu LTS: Integration
SUCCESS: MAAS Compatability Testing
IN_PROGRESS: Declarative: Post Actions
Click here to trigger a rebuild: /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 230/rebuild
https:/