cobbler does not start on transition from runlevel 1 to 2

Bug #820668 reported by Clint Byrum
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cobbler (Ubuntu)
Invalid
Medium
Unassigned
Oneiric
Won't Fix
Medium
Unassigned
Precise
Won't Fix
Medium
Unassigned

Bug Description

cobbler's upstart job is

stop on runlevel [016]

but the start on does not mention runlevel [2345] or [^016]. So cobbler will stop when a user switches to runlevel 1 but not start back up on the transition.

Tags: runlevel1

Related branches

Ursula Junque (ursinha)
Changed in cobbler (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Ben Howard (darkmuggle-deactivatedaccount) wrote :

Proposed branch for merging.

Changed in cobbler (Ubuntu):
assignee: nobody → Ben Howard (utlemming)
status: New → In Progress
status: In Progress → Triaged
Dave Walker (davewalker)
Changed in cobbler (Ubuntu Oneiric):
status: Triaged → Won't Fix
assignee: Ben Howard (utlemming) → nobody
James Page (james-page)
Changed in cobbler (Ubuntu Precise):
status: Triaged → Won't Fix
Changed in cobbler (Ubuntu):
assignee: Ben Howard (utlemming) → nobody
Changed in cobbler (Ubuntu Precise):
assignee: Ben Howard (utlemming) → nobody
Revision history for this message
Nish Aravamudan (nacc) wrote :

Given that we've moved to systemd and that 16.10's cobbler has:

# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6

I'm just going to close this crufty bug.

Changed in cobbler (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.