[chef] Re: Keeping DNS configuration eerrors from breaking working server with bind cookboks

["Julian C. Dunn" < >]

Can you just use "ignore_failure true" on the resources you don't care about?

- Julian

On Fri, Jun 20, 2014 at 6:35 PM, Kadel-Garcia, Nico
<
 >
 wrote:
> I’m looking at the bind and bind9 cookbooks, and realizing that they don’t
> check for certain types of invalid configurations that would cause the BIND
> daemon to fail to restart. In particular, for bind9, multiple data bags that
> have the same ‘domain’ setup are accepted without error, but break
> /etc/named.conf.local.
>
>
>
> The BIND published command ‘named-checkconf’ can be used check the
> configurations before the recipe comletes and prevent BIND from being
> restarted in a broken state. But I’ve been asked to let those BIND related
> cookbooks report errors, and not actually cause the rest of the chef run to
> fail.
>
>
>
> So I’ve tried various approaches, trying to tie “rescue” operations to the
> necessary shell command, simply wrapping the whole recipe in a “rescue”, and
> others. I seem unable to get the right balance of runingn the check,
> allowing the cookbook to succeed, and getting a visible error report.
>
>
>
> Has anyone in the community done this, or other “run this shell script, end
> this recipe, report the error, and allow other cookbooks to continue”
>
>
>
> --
> Nico Kadel-Garcia
> Senior Systems Consultant
> Email: 
> 
 
> Cell Phone: +1.339.368.2428
>
>



-- 
[ Julian C. Dunn 
<
 >
          * Sorry, I'm    ]
[ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ;]
[ gopher://sdf.org/1/users/keymaker/           * compliant!    ;]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]