nagios-charmers team mailing list archive

[Giuseppe Petralia <1816638@xxxxxxxxxxxxxxxxxx>]

** Description changed:

+ I am using nagios-charm version: cs:nagios-27 revision: 0.
+ 
  In a customer environment we have internet access only through a proxy.
  
  I want to avoid using the proxy for internal connections so I configured
  the following param in model config:
  
  juju model-config juju-http-proxy=http://PROXY
  
  juju model-config juju-https-proxy=http://PROXY
  
  juju model-config juju-no-proxy=127.0.0.1,localhost,::1,10.216.0.0/13
  
  Then I access nagios unit and try to get
  https://events.pagerduty.com/v2/enqueue with
  
  "curl https://events.pagerduty.com/v2/enqueue";
  
  Resulting in nagios unable to post to pagerduty.
  
  I then reset the juju-*proxy vars and I repeated the same steps using
  the old juju model-config variables like this:
  
  juju model-config http-proxy=http://PROXY
  
  juju model-config https-proxy=http://PROXY
  
  juju model-config no-
  proxy=127.0.0.1,localhost,::1,10.216.5.2,10.216.5.3,10.216.5.4,....
  
  In no-proxy I listed all the internal ips as cidr notation can't be used
  then I logged in into nagios and I am able to get
  https://events.pagerduty.com/v2/enqueue
+ 
+ 
+ curl https://events.pagerduty.com/v2/enqueue
+ {"status":"Invalid method","message":"Events must be submitted using HTTP POST"}
+ 
+ Invalid status because it needs a post but it is just an example.

-- 
You received this bug notification because you are a member of Nagios
Charm developers, which is subscribed to Nagios Charm.
https://bugs.launchpad.net/bugs/1816638

Title:
  Nagios charm is not using juju-*proxy vars

Status in Nagios Charm:
  New

Bug description:
  I am using nagios-charm version: cs:nagios-27 revision: 0.

  In a customer environment we have internet access only through a
  proxy.

  I want to avoid using the proxy for internal connections so I
  configured the following param in model config:

  juju model-config juju-http-proxy=http://PROXY

  juju model-config juju-https-proxy=http://PROXY

  juju model-config juju-no-proxy=127.0.0.1,localhost,::1,10.216.0.0/13

  Then I access nagios unit and try to get
  https://events.pagerduty.com/v2/enqueue with

  "curl https://events.pagerduty.com/v2/enqueue";

  Resulting in nagios unable to post to pagerduty.

  I then reset the juju-*proxy vars and I repeated the same steps using
  the old juju model-config variables like this:

  juju model-config http-proxy=http://PROXY

  juju model-config https-proxy=http://PROXY

  juju model-config no-
  proxy=127.0.0.1,localhost,::1,10.216.5.2,10.216.5.3,10.216.5.4,....

  In no-proxy I listed all the internal ips as cidr notation can't be
  used then I logged in into nagios and I am able to get
  https://events.pagerduty.com/v2/enqueue

  
  curl https://events.pagerduty.com/v2/enqueue
  {"status":"Invalid method","message":"Events must be submitted using HTTP POST"}

  Invalid status because it needs a post but it is just an example.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nagios-charm/+bug/1816638/+subscriptions