[Bug 1413555] Re: init script fails with error code 0 when configuration test doesn't pass

2015-04-23 Thread Stratos Moros
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.
https://bugs.launchpad.net/bugs/1413555

Title:
  init script fails with error code 0 when configuration test doesn't
  pass

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1413555/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1413555] [NEW] init script fails with error code 0 when configuration test doesn't pass

2015-01-22 Thread Stratos Moros
Public bug reported:

Ubuntu version: Ubuntu 14.04.1 LTS
Nginx version: 1.4.6-1ubuntu3.1

Steps to reproduce:

1. install nginx
2. add a configuration error to nginx's configuration (echo error  
/etc/nginx/nginx.conf)
3. reload nginx and check its exit code (/etc/init.d/nginx reload; echo $?)

What should happen:

Nginx should fail to reload with a non zero exit code.

What happens instead

Nginx does not reload, but the init script's exit code is 0. This
confuses certain configuration management tools that rely on init
scripts' exit codes to determine success.

** Affects: nginx (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1413555/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1412545] [NEW] proxy isn't used after a dropped connection

2015-01-19 Thread Stratos Moros
Public bug reported:

Ubuntu version: Ubuntu 14.04.1 LTS
python-urllib3 version: 1.7.1-1build1

Steps to reproduce:

1. set up an http proxy
2. configure a ProxyManager to use said http proxy
3. make successive GET requests to https://pypi.python.org/ 

example script: https://gist.github.com/stratoukos/7545c5c909fa9b5d1cfb

What happens:

urllib3 stops using the http proxy after the connection is dropped
(after 24 requests in my testing with pypi. other people have seen
different numbers)

What I expected to happen:

urllib3 should always use the proxy

Other Info:

This has been fixed in commit 1c30a1f3 of urllib3 and included in its
1.8.3 release. This bug also affects pip and requests as reported here:
https://github.com/pypa/pip/issues/1805

I really hope the bugfix will be backported, since pip is currently
unusable behind an outgoing firewall on 14.04

** Affects: python-urllib3 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-urllib3 in Ubuntu.
https://bugs.launchpad.net/bugs/1412545

Title:
  proxy isn't used after a dropped connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-urllib3/+bug/1412545/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs