Ubuntu Utopic has gone End of Life as of today. As such, this bug is
being marked Won't Fix against the Utopic package.
Refer to: https://lists.ubuntu.com/archives/ubuntu-
announce/2015-July/000198.html
** Changed in: nginx (Ubuntu Utopic)
Status: Confirmed = Won't Fix
--
You received
This seems specific to the init scripts packaged with the .deb for NginX
to me. Unless there is an automated system creating these init-scripts
and omitting the exit-codes on failure.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Please see the bug report for Ansible: https://github.com/ansible
/ansible-modules-core/issues/952
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1413555
Title:
init script fails
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nginx (Ubuntu Utopic)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
Also, this is not specific to Nginx.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
https://bugs.launchpad.net/bugs/1413555
Title:
init script fails with error code 0 when configuration test doesn't
pass
To
If this is not specific to NGINX there needs to be additonal bugs opened
against the other projects. This bug will only address NGINX.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
Hello Thomas and thanks for taking an interest
Personally, I experienced the bug using Ansible, which I would argue is
well known.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nginx in Ubuntu.
Confirmed in 1.4.6-1ubuntu3.2 from trusty-updates. Not tested with
later releases.
I'm marking this as Confirmed against Trusty, however it needs testing
in Utopic and Vivid to determine the full extent of what's affected.
** Changed in: nginx (Ubuntu)
Status: New = Confirmed
** Also
Also, please elaborate what you mean by 'certain configuration
management tools' - unless they're used regularly by a substantial
portion of existence (such as a well known configuration management
tool) then I'm not sure the actual impact.
Until that's clarified, I'm marking importance on this
Confirmed that Vivid is not affected. Log data:
teward@vivid-server-vm:~$ sudo service nginx restart; echo $?
Job for nginx.service failed. See systemctl status nginx.service and
journalctl -xe for details.
1
** Also affects: nginx (Ubuntu Vivid)
Importance: Low
Status: New
** Also
10 matches
Mail list logo
