Template Inheritance contact options

[lmiltchev]

Do you want me to make a bug report?

Yes. This way the issue won't "fall in the cracks".
http://tracker.nagios.com/

[WillemDH]

Bug report made: http://tracker.nagios.com/view.php?id=455

Just want to add that when any change is made to a service after it has been configured with the legacy config manager, the servicegroup option is reset to standard, which is pretty annoying..., as any changes I would make between now and a patch could be reset if any user makes any change to the service, even if I edit the servicegroup option with the legacy config manager.

[abrist]

Actually, yes please open up a bug report. I ran out of uninterrupted time today to hunt this issue down. Post a link to the bug report here in this thread.
http://tracker.nagios.com

[WillemDH]

Andy,

As you can see in my previous post, I already made a bug report..

Greetings.

[abrist]

Apologies - I do not think I refreshed the tab before I submitted the post. If I get time before the weekend, I will continue the bug hunt. The behavior is not consistent across all template types and I noticed that certain *groups were having similar issues. Changing CCM code should be done carefully - I will do what I can.

[WillemDH]

Ok, thanks for looking into this. It really prevents us from using templates in combinations with Nagios XI imo. Good luck with the bug hunt!

[sreinhardt]

That is a pretty fair point. I know abrist has been looking into it as time permits and testing some fixes on his own machine. Things are starting to get fixed for these couple issues!

[WillemDH]

Any news about this?

Willem

[abrist]

This ended up being a really complex issue - the devs are working on it.

[WillemDH]

I found a bug in the patch. it could also be caused by the bulk host import wizard. I changed the standard hostgroup, servicegroup contact and contactgroup options of a server to '+', and cloned this server to some other hostst. And today I check the yesterday created hosts and it seems the options are set to standard again. The source host is still ok, but the cloned hosts are not ok. can this please be fixed too? As when a host / service is cloned, we suspect the clone hosts / services to have the same options.... Same problem for cloned services.

Please let this know to he developer. This prevents me from resolving this issue for all hosts / services. I made bug report http://tracker.nagios.com/view.php?id=469

Willem