ambari-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Sposetti <>
Subject Re: new error
Date Fri, 18 Jul 2014 19:20:50 GMT
There is work underway in trunk (to be delivered in Ambari 1.7.0) that will
migrate the "global" config-type to "" config-type for each service.

The idea is before 1.7.0 ships, Ambari maintains "global" for backwards
compat (that's not there yet, but the -env work has begun), and then
removes support for "global" completely in a future release.

On Fri, Jul 18, 2014 at 2:51 PM, Greg Hill <> wrote:

>  Oh, I see the key changed from 'global' to 'nagios-env'.  Were the docs
> just wrong and it was escaping detection previously or did this
> backwards-incompatible change get purposely made in a point release?
>  Greg
>   From: Greg <>
> Reply-To: "" <>
> Date: Friday, July 18, 2014 1:43 PM
> To: "" <>
> Subject: new error
>   I was revisiting my Ambari API testing with the most recent changes and
> the code that worked a few weeks ago no longer is.  Apparently the way that
> is shown in the docs to define the nagios_contact no longer works.
>  I sent this in my blueprint:
>  "configurations": [
>         {
>             "global" : {
>                 "nagios_contact" : ""
>             }
>         }
>     ],
>  But when I attempt to create that blueprint, I get a 400 error with the
> following message:
>  Required configurations are missing from the specified host groups:
> {gateway={nagios-env=[nagios_contact]}}
>  ('gateway' is the name of one of my host_groups).  This error did not
> occur as of the latest code 3-4 weeks ago.  What do I need to be doing
> differently?
>  Greg

NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

View raw message