Updating trigger in template deletes dependencies on host triggers

XMLWordPrintable

    • Type: Incident report
    • Resolution: Fixed
    • Priority: Minor
    • 1.8.5
    • Affects Version/s: 1.6
    • Component/s: None
    • None
    • Environment:
      Linux (2.6 Kernel)

      Consider the following scenario:

      1. Create 2 hosts based on a template which contains a trigger called "trigger

      {hostname}"
      2. Create a dependency on the first host that points to the trigger on the second host.
      3. Rename the trigger in the template to read "renamed trigger {hostname}

      "

      All dependencies will be gone, which is a pain if you have a large number of hosts inheriting from that template.

      Was suggested in forums that this should be posted here.

      Kind Regards,
      -Mark

            Assignee:
            Unassigned
            Reporter:
            Mark Brochu
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: