Ubuntu
ufw package

ufw needs systemd unit or init.d script

Bug #1341083 reported by dino99 on 2014-07-12

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	ufw (Ubuntu)	Fix Released	Medium	Martin Pitt

Bug Description

Always get an 'inactive' status when the system is booted, even if the setting is set to be 'active' into the 'system settings'

oem@dev32:~$ sudo ufw status
[sudo] password for oem:
Status: inactive

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ufw 0.34~rc-0ubuntu3
ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4
Uname: Linux 3.16.0-3-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.4-0ubuntu2
Architecture: i386
CurrentDesktop: GNOME
Date: Sat Jul 12 11:07:30 2014
PackageArchitecture: all
SourcePackage: ufw
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Related branches

lp:ubuntu/utopic-proposed/ufw

lp:ubuntu/wily-proposed/ufw

Revision history for this message

dino99 (9d9) wrote on 2014-07-12:

Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (381 bytes, text/plain; charset="utf-8")

tags:

added: systemd-boot

Martin Pitt (pitti) on 2014-07-22

summary:	- [systemd-boot] [utopic] ufw status 'inactive' at cold boot + ufw needs systemd unit or init.d script
Changed in ufw (Ubuntu):
status:	New → Triaged
importance:	Undecided → Medium

Martin Pitt (pitti) on 2014-07-30

Changed in ufw (Ubuntu):
status:	Triaged → In Progress
assignee:	nobody → Martin Pitt (pitti)

Revision history for this message

Martin Pitt (pitti) wrote on 2014-07-30:

debdiff Edit (11.7 KiB, text/plain)

This debdiff does both: It consistently installs sysvinit/upstart scripts on Debian and Ubuntu, and also adds a simple systemd service file which is equivalent to the upstart job. Tested under both upstart and systemd (I didn't test the sysvinit script).

Ubuntu Foundations Team Bug Bot (crichton) on 2014-07-30

tags:

added: patch

Revision history for this message

Dimitri John Ledkov (xnox) wrote on 2014-08-07:

lgtm +1

Revision history for this message

Jamie Strandboge (jdstrand) wrote on 2014-08-07:

This looks great. I tested it in a VM, on my local machine, mako and on the emulator (the emulator suffers from bug #1320329 still). Upstart does not regress as seen on my system, mako and the VM. In a VM, systemd job correctly starts when booting with "init=/lib/systmed/systemd" as seen from both "sudo ufw status" and "systemctl status ufw". "sudo systemctl stop ufw" and "sudo systemctl start ufw" operate correctly. Image tests pass on mako (and mostly on goldfish, see above).

I will sponsor the debdiff once we leave TRAINCON-0. Thanks!

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-08-11:

This bug was fixed in the package ufw - 0.34~rc-0ubuntu4

---------------
ufw (0.34~rc-0ubuntu4) utopic; urgency=medium

  * Install the SysV init and upstart script for both Debian and Ubuntu.
    Debian has upstart too, and in Ubuntu we need the init script for LSB
    dependencies and for systemd. (LP: #1341083)
    - Rename debian/ufw.init.debian to debian/ufw.init
    - Rename debian/ufw.upstart.ubuntu to debian/ufw.upstart
    - Remove all the distro specific code from debian/rules and just call
      dh_installinit.
  * Drop the distro specific logrotate configs, and use the ubuntu one with
    "rotate" instead of "reload" everywhere, as Debian's rsyslog init also
    supports "rotate".
  * Add a systemd unit:
    - Add debian/ufw.service
    - Add dh-systemd build dep.
    - debian/rulles: Call dh_systemd_{enable,start}.
-- Martin Pitt <email address hidden> Wed, 30 Jul 2014 15:06:25 +0200