Activity log for bug #1472683

Date Who What changed Old value New value Message
2015-07-08 16:00:02 Thomas Ward bug added bug
2015-07-08 16:00:13 Thomas Ward nominated for series Ubuntu Wily
2015-07-08 16:00:13 Thomas Ward bug task added nginx (Ubuntu Wily)
2015-07-08 16:00:13 Thomas Ward nominated for series Ubuntu Vivid
2015-07-08 16:00:13 Thomas Ward bug task added nginx (Ubuntu Vivid)
2015-07-08 16:00:20 Thomas Ward nginx (Ubuntu Vivid): status New In Progress
2015-07-08 16:00:22 Thomas Ward nginx (Ubuntu Vivid): importance Undecided Medium
2015-07-08 16:00:24 Thomas Ward nginx (Ubuntu Vivid): assignee Thomas Ward (teward)
2015-07-08 16:01:27 Thomas Ward nginx (Ubuntu Vivid): status In Progress Triaged
2015-07-08 16:01:29 Thomas Ward nginx (Ubuntu Wily): status In Progress Triaged
2015-07-08 18:19:08 Thomas Ward summary Nginx bug reports for 'package' problem type are not providing useful data Nginx bug reports for Vivid and later not really returning useful data
2015-07-08 18:20:31 Thomas Ward description This is against the 'nginx' package because apport hooks need added here for Vivid and Wily. Currently, systemd and stderr and Apport do not pull in enough information for bug triage and handling to be done. We have several Vivid bugs now which show this - they're all for the same version of the package, in Wily, but different binaries, all with the Package problem type, and a postinstallation script failure. But that's it, there's no information of the errors, or anything. To that end, we need to expand what Apport pulls in, to include output from `journalctl -xe --unit=nginx.service` and `systemctl -l status nginx.service`, and also the `/var/log/nginx/error.log` file (if it exists) in order to get useful information for Package class bugs. I have given this a Medium importance, as there's no useful information in bug reports of the Package class currently that could allude to why the postinst scripts failed. This is against the 'nginx' package because apport hooks need added here for Vivid and Wily. Currently, systemd and stderr and Apport do not pull in enough information for bug triage and handling to be done. We have several Vivid bugs now which show this - they're all for the same version of the package, in Wily, but different binaries, all with the Package problem type, and a postinstallation script failure. But that's it, there's no information of the errors, or anything. This also extends to other bug types. We need error logs, configuration files, and additional information to test and reproduce problems which are not Package related types. As the error.log, nginx.conf, and /etc/nginx/sites-enabled/*.conf files could be sensitive, any apport hooks need to prompt for whether to include these files or not. To that end, we need to expand what Apport pulls in, to include output from `journalctl -xe --unit=nginx.service` and `systemctl -l status nginx.service`, and also the `/var/log/nginx/error.log` file (if it exists) in order to get useful information for Package class bugs. I have given this a Medium importance, as there's no useful information in bug reports of the Package class currently that could allude to why the postinst scripts failed.
2015-07-09 14:32:41 Thomas Ward description This is against the 'nginx' package because apport hooks need added here for Vivid and Wily. Currently, systemd and stderr and Apport do not pull in enough information for bug triage and handling to be done. We have several Vivid bugs now which show this - they're all for the same version of the package, in Wily, but different binaries, all with the Package problem type, and a postinstallation script failure. But that's it, there's no information of the errors, or anything. This also extends to other bug types. We need error logs, configuration files, and additional information to test and reproduce problems which are not Package related types. As the error.log, nginx.conf, and /etc/nginx/sites-enabled/*.conf files could be sensitive, any apport hooks need to prompt for whether to include these files or not. To that end, we need to expand what Apport pulls in, to include output from `journalctl -xe --unit=nginx.service` and `systemctl -l status nginx.service`, and also the `/var/log/nginx/error.log` file (if it exists) in order to get useful information for Package class bugs. I have given this a Medium importance, as there's no useful information in bug reports of the Package class currently that could allude to why the postinst scripts failed. This is against the 'nginx' package because apport hooks need added here for Vivid and Wily. Currently, systemd and stderr and Apport do not pull in enough information for bug triage and handling to be done. We have several Vivid bugs now which show this - they're all for the same version of the package, in Wily, but different binaries, all with the Package problem type, and a postinstallation script failure. But that's it, there's no information of the errors, or anything. To that end, we need to expand what Apport pulls in, to include output from `journalctl -xe --unit=nginx.service` and `systemctl -l status nginx.service` in order to get useful information for Package class bugs. I have given this a Medium importance, as there's no useful information in bug reports of the Package class currently that could allude to why the postinst scripts failed.
2015-07-09 14:33:07 Thomas Ward summary Nginx bug reports for Vivid and later not really returning useful data Nginx bug reports for 'package' problem type are not providing useful data for Vivid and later
2015-07-09 14:34:45 Thomas Ward nginx (Ubuntu Wily): status Triaged In Progress
2015-07-09 18:20:08 Thomas Ward nginx (Ubuntu Wily): status In Progress Triaged
2015-07-10 20:34:37 Thomas Ward nginx (Ubuntu Wily): status Triaged In Progress
2015-07-10 20:39:26 Launchpad Janitor branch linked lp:ubuntu/wily-proposed/nginx
2015-07-10 20:45:18 Thomas Ward description This is against the 'nginx' package because apport hooks need added here for Vivid and Wily. Currently, systemd and stderr and Apport do not pull in enough information for bug triage and handling to be done. We have several Vivid bugs now which show this - they're all for the same version of the package, in Wily, but different binaries, all with the Package problem type, and a postinstallation script failure. But that's it, there's no information of the errors, or anything. To that end, we need to expand what Apport pulls in, to include output from `journalctl -xe --unit=nginx.service` and `systemctl -l status nginx.service` in order to get useful information for Package class bugs. I have given this a Medium importance, as there's no useful information in bug reports of the Package class currently that could allude to why the postinst scripts failed. [Impact] This issue makes it impossible to reliably determine the cause of a postinstallation failure bug during the installation or upgrade attempt of an nginx binary package. A large number of the bugs have tied back to "Postinstall exited with error code" issues, but that's all we have about it. Additional data needs to be collected, which apport hooks solve. [Test Case] This does not resolve the issue with an installation failure. It does increase the amount of information made available by the bug report. (1) Have Apache or some other thing binding to port 80 (2) Install nginx-common and one of the following: nginx-core nginx-light nginx-full nginx-extras (3) Run `apport-bug` on the crash report and review the data. The problem is reproduced if all we get from the dpkg logs is something about the job failing to start, with no additional information. Testing the fix, when you run the report, you will get "Journalctl_Nginx.txt" and "SystemctlStatusFull_Nginx.txt" files in the report data. These will contain the output of the two commands that the system says you should run to get more information about the failure, and includes it in the report. [Regression Potential] None. All this adds is an apport hook, which has been tested on both Wily and Vivid. [Other Info] I know for a fact that Seth Arnold and Robie Basak will praise these apport hooks, if only because we will actually be able to debug installation and upgrade failures in which nginx binaries are failing to install due to some issue with the job start process. [Original Description] This is against the 'nginx' package because apport hooks need added here for Vivid and Wily. Currently, systemd and stderr and Apport do not pull in enough information for bug triage and handling to be done. We have several Vivid bugs now which show this - they're all for the same version of the package, in Wily, but different binaries, all with the Package problem type, and a postinstallation script failure. But that's it, there's no information of the errors, or anything. To that end, we need to expand what Apport pulls in, to include output from `journalctl -xe --unit=nginx.service` and `systemctl -l status nginx.service` in order to get useful information for Package class bugs. I have given this a Medium importance, as there's no useful information in bug reports of the Package class currently that could allude to why the postinst scripts failed.
2015-07-10 20:45:20 Thomas Ward nginx (Ubuntu Vivid): status Triaged In Progress
2015-07-10 21:40:54 Launchpad Janitor nginx (Ubuntu Wily): status In Progress Fix Released
2015-07-10 22:18:12 Thomas Ward bug added subscriber Ubuntu Stable Release Updates Team
2015-07-10 22:18:28 Thomas Ward nginx (Ubuntu Vivid): assignee Thomas Ward (teward)
2015-07-13 12:23:12 Thomas Ward nginx (Ubuntu Vivid): assignee Thomas Ward (teward)
2015-07-13 13:57:55 Adam Conrad nginx (Ubuntu Vivid): status In Progress Fix Committed
2015-07-13 13:57:58 Adam Conrad bug added subscriber SRU Verification
2015-07-13 13:58:01 Adam Conrad tags vivid wily verification-needed vivid wily
2015-07-13 14:19:19 Launchpad Janitor branch linked lp:ubuntu/vivid-proposed/nginx
2015-07-13 15:39:44 Thomas Ward tags verification-needed vivid wily verification-done vivid wily
2015-07-20 20:22:23 Launchpad Janitor nginx (Ubuntu Vivid): status Fix Committed Fix Released
2015-07-20 20:22:28 Adam Conrad removed subscriber Ubuntu Stable Release Updates Team