chroot support is not reliable
Bug #728531 reported by
James Hunt
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
Invalid
|
Low
|
Unassigned | ||
upstart (Ubuntu) |
Fix Released
|
Medium
|
James Hunt | ||
Natty |
Fix Released
|
Medium
|
James Hunt |
Bug Description
Current natty chroot support does not seem to work reliably. Logging into a natty schroot as root and running "initctl list" shows:
plymouth-
james stop/waiting
Logging out of the chroot and back in as root again, "initctl list" shows no output. There are 38 .conf files in my chroots /etc/init/ so we would always expect (atleast) 38 jobs being listed by "initctl list" (possibly more if user sessions enabled).
Related branches
lp:~jamesodhunt/ubuntu/natty/upstart/fix-chroot-sessions
- Clint Byrum (community): Approve
-
Diff: 4753 lines (+842/-700)38 files modifiedChangeLog (+62/-0)
NEWS (+21/-0)
configure.ac (+1/-1)
debian/changelog (+28/-0)
debian/upstart-job (+14/-4)
init/Makefile.am (+4/-2)
init/conf.c (+18/-12)
init/conf.h (+1/-1)
init/control.c (+5/-1)
init/job.c (+8/-2)
init/job_class.c (+34/-14)
init/job_process.c (+59/-0)
init/job_process.h (+3/-1)
init/main.c (+8/-0)
init/man/init.5 (+0/-38)
init/man/init.8 (+11/-7)
init/parse_job.c (+2/-2)
init/session.c (+21/-8)
init/session.h (+27/-2)
init/tests/test_blocked.c (+4/-6)
init/tests/test_conf.c (+15/-22)
init/tests/test_control.c (+11/-12)
init/tests/test_environ.c (+3/-0)
init/tests/test_event.c (+28/-40)
init/tests/test_event_operator.c (+3/-0)
init/tests/test_job.c (+70/-148)
init/tests/test_job_class.c (+54/-145)
init/tests/test_job_process.c (+34/-59)
init/tests/test_parse_conf.c (+3/-0)
init/tests/test_parse_job.c (+3/-0)
init/tests/test_process.c (+3/-0)
init/tests/test_system.c (+3/-0)
po/upstart.pot (+152/-136)
scripts/init-checkconf.sh (+34/-10)
scripts/man/init-checkconf.8 (+22/-10)
util/initctl.c (+16/-5)
util/man/initctl.8 (+3/-1)
util/tests/test_initctl.c (+54/-11)
affects: | ubuntu → upstart (Ubuntu) |
Changed in upstart: | |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in upstart (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → James Hunt (jamesodhunt) |
Changed in upstart (Ubuntu Natty): | |
milestone: | none → ubuntu-11.04 |
tags: | added: server-nro |
Changed in upstart (Ubuntu Natty): | |
status: | In Progress → Fix Committed |
tags: | added: crasher |
To post a comment you must log in.
I clearly didn't test this well enough ;-)
On Thu, Mar 3, 2011 at 8:22 AM, James Hunt <email address hidden> wrote: upstart- bridge stop/waiting /bugs.launchpad .net/bugs/ 728531 upstart- bridge stop/waiting
> Public bug reported:
>
> Current natty chroot support does not seem to work reliably. Logging
> into a natty schroot as root and running "initctl list" shows:
>
> plymouth-
> james stop/waiting
>
> Logging out of the chroot and back in as root again, "initctl list"
> shows no output. There are 38 .conf files in my chroots /etc/init/ so we
> would always expect (atleast) 38 jobs being listed by "initctl list"
> (possibly more if user sessions enabled).
>
> ** Affects: upstart
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of Upstart
> Developers, which is subscribed to upstart .
> https:/
>
> Title:
> chroot support is not reliable
>
> Status in Upstart:
> New
>
> Bug description:
> Current natty chroot support does not seem to work reliably. Logging
> into a natty schroot as root and running "initctl list" shows:
>
> plymouth-
> james stop/waiting
>
> Logging out of the chroot and back in as root again, "initctl list"
> shows no output. There are 38 .conf files in my chroots /etc/init/ so
> we would always expect (atleast) 38 jobs being listed by "initctl
> list" (possibly more if user sessions enabled).
>