Activity log for bug #1452644

Date Who What changed Old value New value Message
2015-05-07 09:32:51 kex bug added bug
2015-05-07 16:36:05 Steve Langasek tags amd64 apport-bug vivid amd64 apport-bug systemd-boot vivid
2015-05-07 17:08:22 Steve Langasek nfs-utils (Ubuntu): importance Undecided High
2015-05-07 17:08:22 Steve Langasek nfs-utils (Ubuntu): status New Triaged
2015-05-07 17:15:01 Launchpad Janitor branch linked lp:ubuntu/nfs-utils
2015-05-07 17:17:53 Steve Langasek nominated for series Ubuntu Wily
2015-05-07 17:17:53 Steve Langasek bug task added nfs-utils (Ubuntu Wily)
2015-05-07 17:17:53 Steve Langasek nominated for series Ubuntu Vivid
2015-05-07 17:17:53 Steve Langasek bug task added nfs-utils (Ubuntu Vivid)
2015-05-07 17:18:09 Steve Langasek nfs-utils (Ubuntu Vivid): status New Triaged
2015-05-07 17:18:13 Steve Langasek nfs-utils (Ubuntu Vivid): importance Undecided High
2015-05-27 09:11:07 Martin Pitt affects nfs-utils (Ubuntu Wily) setserial (Ubuntu Wily)
2015-05-27 09:11:07 Martin Pitt setserial (Ubuntu Wily): status Triaged In Progress
2015-05-27 09:11:07 Martin Pitt setserial (Ubuntu Wily): assignee Martin Pitt (pitti)
2015-05-27 09:11:18 Martin Pitt summary vivid NFSd does not start due to systemd ordering cycle NFSd does not start due to systemd ordering cycle with setserial
2015-05-27 09:14:11 Martin Pitt description NFSd does not start due to systemd ordering cycle. Manually starting with "systemctl start nfs-kernel-server" after boot works fine. here systemd lines from dmesg: [ 2.559819] random: systemd-udevd urandom read with 8 bits of entropy available [ 43.181921] systemd[1]: Inserted module 'autofs4' [ 43.210140] systemd[1]: systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN) [ 43.234042] systemd[1]: Detected architecture x86-64. [ 43.328158] systemd[1]: Set hostname to <xpc>. [ 43.434248] systemd-sysv-generator[337]: Overwriting existing symlink /run/systemd/generator.late/mdadm-waitidle.service with real service [ 43.569341] systemd[1]: Cannot add dependency job for unit gssproxy.service, ignoring: Unit gssproxy.service failed to load: No such file or directory. [ 43.595080] systemd[1]: Found ordering cycle on nfs-server.service/start [ 43.620748] systemd[1]: Found dependency on network.target/start [ 43.646476] systemd[1]: Found dependency on NetworkManager.service/start [ 43.672292] systemd[1]: Found dependency on basic.target/start [ 43.697952] systemd[1]: Found dependency on sockets.target/start [ 43.723381] systemd[1]: Found dependency on cups.socket/start [ 43.748530] systemd[1]: Found dependency on sysinit.target/start [ 43.773533] systemd[1]: Found dependency on setserial.service/start [ 43.798185] systemd[1]: Found dependency on remote-fs.target/start [ 43.822739] systemd[1]: Found dependency on remote-fs-pre.target/start [ 43.871768] systemd[1]: Found dependency on nfs-server.service/start [ 43.896442] systemd[1]: Breaking ordering cycle by deleting job network.target/start [ 43.921641] systemd[1]: Job network.target/start deleted to break ordering cycle starting with nfs-server.service/start [ 44.109024] systemd[1]: Reached target Encrypted Volumes. [ 44.135558] systemd[1]: Starting Encrypted Volumes. [ 44.189110] systemd[1]: Created slice Root Slice. [ 44.215900] systemd[1]: Starting Root Slice. [ 44.269513] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [ 44.296806] systemd[1]: Starting /dev/initctl Compatibility Named Pipe. [ 44.351462] systemd[1]: Listening on LVM2 metadata daemon socket. [ 44.378792] systemd[1]: Starting LVM2 metadata daemon socket. [ 44.459356] systemd[1]: Dependency failed for pNFS block layout mapping daemon. [ 44.486177] systemd[1]: Job nfs-blkmap.service/start failed with result 'dependency'. [ 44.539816] systemd[1]: Listening on Delayed Shutdown Socket. [ 44.566481] systemd[1]: Starting Delayed Shutdown Socket. [ 44.619658] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 44.647063] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point. [ 44.702240] systemd[1]: Listening on Journal Socket (/dev/log). [ 44.730201] systemd[1]: Starting Journal Socket (/dev/log). [ 44.786161] systemd[1]: Listening on fsck to fsckd communication Socket. [ 44.814391] systemd[1]: Starting fsck to fsckd communication Socket. [ 44.870869] systemd[1]: Listening on udev Control Socket. [ 44.899276] systemd[1]: Starting udev Control Socket. [ 44.927774] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 44.956547] systemd[1]: Starting Forward Password Requests to Wall Directory Watch. [ 45.013546] systemd[1]: Created slice User and Session Slice. [ 45.040955] systemd[1]: Starting User and Session Slice. [ 45.097664] systemd[1]: Listening on Device-mapper event daemon FIFOs. [ 45.125626] systemd[1]: Starting Device-mapper event daemon FIFOs. [ 45.181619] systemd[1]: Listening on udev Kernel Socket. [ 45.209643] systemd[1]: Starting udev Kernel Socket. [ 45.263885] systemd[1]: Listening on Journal Socket. [ 45.290707] systemd[1]: Starting Journal Socket. [ 45.344645] systemd[1]: Listening on Journal Audit Socket. [ 45.371233] systemd[1]: Starting Journal Audit Socket. [ 45.423314] systemd[1]: Created slice System Slice. [ 45.449542] systemd[1]: Starting System Slice. [ 45.475703] systemd[1]: Started Kernel Module supporting RPCSEC_GSS. [ 45.502333] systemd[1]: Starting LSB: controls configuration of serial ports... [ 45.556425] systemd[1]: Mounting POSIX Message Queue File System... [ 45.639083] systemd[1]: Created slice system-getty.slice. [ 45.666695] systemd[1]: Starting system-getty.slice. [ 45.694307] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... [ 45.750548] systemd[1]: Mounting Debug File System... [ 45.808508] systemd[1]: Started Set Up Additional Binary Formats. [ 45.863949] systemd[1]: Started Braille Device Support. [ 45.891808] systemd[1]: Starting Braille Device Support... [ 45.974979] systemd[1]: Created slice system-systemd\x2dfsck.slice. [ 46.002893] systemd[1]: Starting system-systemd\x2dfsck.slice. [ 46.059331] systemd[1]: Started Read required files in advance. [ 46.087550] systemd[1]: Starting Read required files in advance... [ 46.144006] systemd[1]: Starting Create list of required static device nodes for the current kernel... [ 46.201523] systemd[1]: Starting Uncomplicated firewall... [ 46.259112] systemd[1]: Mounting RPC Pipe File System... [ 46.428035] systemd[1]: Starting Increase datagram queue length... [ 46.483060] systemd[1]: Starting Nameserver information manager... [ 46.563816] systemd[1]: Reached target Slices. [ 46.590512] systemd[1]: Starting Slices. [ 46.617266] systemd[1]: Starting Setup Virtual Console... [ 46.670131] systemd[1]: Mounting Huge Pages File System... [ 46.722848] systemd[1]: Starting udev Coldplug all Devices... [ 46.775948] systemd[1]: Starting LSB: init script for readahead-fedora... [ 46.974038] systemd[1]: Starting Load Kernel Modules... [ 47.027087] systemd[1]: Mounting NFSD configuration filesystem... [ 47.187150] systemd[1]: Mounted NFSD configuration filesystem. [ 47.240600] systemd[1]: Mounted RPC Pipe File System. [ 47.294380] systemd[1]: Mounted Huge Pages File System. [ 47.348380] systemd[1]: Mounted POSIX Message Queue File System. [ 47.402700] systemd[1]: Mounted Debug File System. [ 47.457618] systemd[1]: Started LSB: controls configuration of serial ports. [ 47.513419] systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. [ 47.570781] systemd[1]: Started Create list of required static device nodes for the current kernel. [ 47.628494] systemd[1]: Started Uncomplicated firewall. [ 47.686300] systemd[1]: Started Increase datagram queue length. [ 47.743392] systemd[1]: Started Setup Virtual Console. [ 47.800282] systemd[1]: Started LSB: init script for readahead-fedora. [ 47.856992] systemd[1]: Started Load Kernel Modules. [ 47.915150] systemd[1]: Started Nameserver information manager. [ 47.972378] systemd[1]: Started udev Coldplug all Devices. [ 48.017097] systemd[1]: Starting udev Wait for Complete Device Initialization... [ 48.074473] systemd[1]: Mounted Configuration File System. [ 48.103413] systemd[1]: Starting Apply Kernel Variables... [ 48.160434] systemd[1]: Mounting FUSE Control File System... [ 48.215712] systemd[1]: Listening on Syslog Socket. [ 48.215721] systemd[1]: Starting Syslog Socket. [ 48.215980] systemd[1]: Starting Journal Service... [ 48.243677] systemd[1]: Starting Create Static Device Nodes in /dev... [ 48.298683] systemd[1]: Mounted FUSE Control File System. [ 48.325717] systemd[1]: Started Journal Service. [ 50.615277] systemd-journald[419]: Received request to flush runtime journal from PID 1 apt-cache policy nfs-kernel-server nfs-kernel-server: Asennettu: 1:1.2.8-9ubuntu8.1 Ehdokas: 1:1.2.8-9ubuntu8.1 Versiotaulukko: *** 1:1.2.8-9ubuntu8.1 0 500 http://fi.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:1.2.8-9ubuntu8 0 500 http://fi.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nfs-kernel-server 1:1.2.8-9ubuntu8.1 Uname: Linux 4.1.0-040100rc1-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 12:26:09 2015 InstallationDate: Installed on 2012-12-22 (865 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: nfs-utils UpgradeStatus: Upgraded to vivid on 2015-04-23 (13 days ago) NFSd does not start due to systemd ordering cycle. Manually starting with "systemctl start nfs-kernel-server" after boot works fine. here systemd lines from dmesg: [ 43.569341] systemd[1]: Cannot add dependency job for unit gssproxy.service, ignoring: Unit gssproxy.service failed to load: No such file or directory. [ 43.595080] systemd[1]: Found ordering cycle on nfs-server.service/start [ 43.620748] systemd[1]: Found dependency on network.target/start [ 43.646476] systemd[1]: Found dependency on NetworkManager.service/start [ 43.672292] systemd[1]: Found dependency on basic.target/start [ 43.697952] systemd[1]: Found dependency on sockets.target/start [ 43.723381] systemd[1]: Found dependency on cups.socket/start [ 43.748530] systemd[1]: Found dependency on sysinit.target/start [ 43.773533] systemd[1]: Found dependency on setserial.service/start [ 43.798185] systemd[1]: Found dependency on remote-fs.target/start [ 43.822739] systemd[1]: Found dependency on remote-fs-pre.target/start [ 43.871768] systemd[1]: Found dependency on nfs-server.service/start [ 43.896442] systemd[1]: Breaking ordering cycle by deleting job network.target/start [ 43.921641] systemd[1]: Job network.target/start deleted to break ordering cycle starting with nfs-server.service/start SRU test case ============= - Install network-manager, nfs-kernel-server, and setserial into a clean vivid VM. - Reboot, and you'll find the above ordering cycle (check "sudo journalctl -p warning"). "systemctl status nfs-server.service" will be not running (it could also be that the cycle gets broken on a different point, but that's the most likely one). - With the fixed setserial package (upgrade, then reboot) there should be no cycle and all services start up normally. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nfs-kernel-server 1:1.2.8-9ubuntu8.1 Uname: Linux 4.1.0-040100rc1-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 12:26:09 2015 InstallationDate: Installed on 2012-12-22 (865 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: nfs-utils UpgradeStatus: Upgraded to vivid on 2015-04-23 (13 days ago)
2015-05-27 10:14:38 Martin Pitt setserial (Ubuntu Wily): status In Progress Fix Committed
2015-05-27 10:14:48 Martin Pitt setserial (Ubuntu Vivid): status Triaged In Progress
2015-05-27 10:17:11 Martin Pitt description NFSd does not start due to systemd ordering cycle. Manually starting with "systemctl start nfs-kernel-server" after boot works fine. here systemd lines from dmesg: [ 43.569341] systemd[1]: Cannot add dependency job for unit gssproxy.service, ignoring: Unit gssproxy.service failed to load: No such file or directory. [ 43.595080] systemd[1]: Found ordering cycle on nfs-server.service/start [ 43.620748] systemd[1]: Found dependency on network.target/start [ 43.646476] systemd[1]: Found dependency on NetworkManager.service/start [ 43.672292] systemd[1]: Found dependency on basic.target/start [ 43.697952] systemd[1]: Found dependency on sockets.target/start [ 43.723381] systemd[1]: Found dependency on cups.socket/start [ 43.748530] systemd[1]: Found dependency on sysinit.target/start [ 43.773533] systemd[1]: Found dependency on setserial.service/start [ 43.798185] systemd[1]: Found dependency on remote-fs.target/start [ 43.822739] systemd[1]: Found dependency on remote-fs-pre.target/start [ 43.871768] systemd[1]: Found dependency on nfs-server.service/start [ 43.896442] systemd[1]: Breaking ordering cycle by deleting job network.target/start [ 43.921641] systemd[1]: Job network.target/start deleted to break ordering cycle starting with nfs-server.service/start SRU test case ============= - Install network-manager, nfs-kernel-server, and setserial into a clean vivid VM. - Reboot, and you'll find the above ordering cycle (check "sudo journalctl -p warning"). "systemctl status nfs-server.service" will be not running (it could also be that the cycle gets broken on a different point, but that's the most likely one). - With the fixed setserial package (upgrade, then reboot) there should be no cycle and all services start up normally. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nfs-kernel-server 1:1.2.8-9ubuntu8.1 Uname: Linux 4.1.0-040100rc1-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 12:26:09 2015 InstallationDate: Installed on 2012-12-22 (865 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: nfs-utils UpgradeStatus: Upgraded to vivid on 2015-04-23 (13 days ago) NFSd does not start due to systemd ordering cycle. Manually starting with "systemctl start nfs-kernel-server" after boot works fine. here systemd lines from dmesg: [ 43.569341] systemd[1]: Cannot add dependency job for unit gssproxy.service, ignoring: Unit gssproxy.service failed to load: No such file or directory. [ 43.595080] systemd[1]: Found ordering cycle on nfs-server.service/start [ 43.620748] systemd[1]: Found dependency on network.target/start [ 43.646476] systemd[1]: Found dependency on NetworkManager.service/start [ 43.672292] systemd[1]: Found dependency on basic.target/start [ 43.697952] systemd[1]: Found dependency on sockets.target/start [ 43.723381] systemd[1]: Found dependency on cups.socket/start [ 43.748530] systemd[1]: Found dependency on sysinit.target/start [ 43.773533] systemd[1]: Found dependency on setserial.service/start [ 43.798185] systemd[1]: Found dependency on remote-fs.target/start [ 43.822739] systemd[1]: Found dependency on remote-fs-pre.target/start [ 43.871768] systemd[1]: Found dependency on nfs-server.service/start [ 43.896442] systemd[1]: Breaking ordering cycle by deleting job network.target/start [ 43.921641] systemd[1]: Job network.target/start deleted to break ordering cycle starting with nfs-server.service/start SRU test case =============  - Install network-manager, nfs-kernel-server, and setserial into a clean vivid VM.  - Reboot, and you'll find the above ordering cycle (check "sudo journalctl -p warning"). "systemctl status nfs-server.service" will be not running (it could also be that the cycle gets broken on a different point, but that's the most likely one).  - With the fixed setserial package (upgrade, then reboot) there should be no cycle and all services start up normally. - Double-check "systemctl status setserial" that the unit started and output from the init.d script looks reasonable. Regression potential: The new .service has less strict startup dependencies/ordering than the autogenerated LSB one, so I don't see a potential problem with introducing new cycles. The new unit could potentially fail to start if there's a bug in unit installation (this is covered by the test case). So all in all, very low. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nfs-kernel-server 1:1.2.8-9ubuntu8.1 Uname: Linux 4.1.0-040100rc1-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 12:26:09 2015 InstallationDate: Installed on 2012-12-22 (865 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: nfs-utils UpgradeStatus: Upgraded to vivid on 2015-04-23 (13 days ago)
2015-05-27 10:38:26 Martin Pitt bug watch added http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786976
2015-05-27 10:38:26 Martin Pitt bug task added setserial (Debian)
2015-05-27 10:38:46 Launchpad Janitor setserial (Ubuntu Wily): status Fix Committed Fix Released
2015-05-27 12:08:24 Bug Watch Updater setserial (Debian): status Unknown New
2015-05-28 06:06:17 Launchpad Janitor branch linked lp:ubuntu/setserial
2015-06-10 17:55:38 Chris J Arges setserial (Ubuntu Vivid): status In Progress Fix Committed
2015-06-10 17:55:41 Chris J Arges bug added subscriber Ubuntu Stable Release Updates Team
2015-06-10 17:55:43 Chris J Arges bug added subscriber SRU Verification
2015-06-10 17:55:46 Chris J Arges tags amd64 apport-bug systemd-boot vivid amd64 apport-bug systemd-boot verification-needed vivid
2015-06-10 19:42:40 kex tags amd64 apport-bug systemd-boot verification-needed vivid amd64 apport-bug systemd-boot verification-failed vivid
2015-06-10 20:49:03 Martin Pitt tags amd64 apport-bug systemd-boot verification-failed vivid amd64 apport-bug systemd-boot verification-needed vivid
2015-06-10 20:53:49 Martin Pitt tags amd64 apport-bug systemd-boot verification-needed vivid amd64 apport-bug systemd-boot verification-done vivid
2015-06-16 22:15:05 Bug Watch Updater setserial (Debian): status New Incomplete
2015-06-18 16:02:31 Launchpad Janitor setserial (Ubuntu Vivid): status Fix Committed Fix Released
2015-06-18 16:02:36 Brian Murray removed subscriber Ubuntu Stable Release Updates Team
2015-06-23 01:37:49 Launchpad Janitor branch linked lp:~ubuntu-branches/ubuntu/vivid/setserial/vivid-proposed
2015-07-18 14:53:52 Bug Watch Updater setserial (Debian): status Incomplete New
2015-08-15 18:39:02 John Center bug added subscriber John Center
2015-09-24 11:37:50 Bug Watch Updater setserial (Debian): status New Fix Released
2015-09-25 13:25:55 Launchpad Janitor branch linked lp:debian/setserial