You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Dmytro Grinenko (Jira)" <ji...@apache.org> on 2020/07/24 22:31:00 UTC

[jira] [Assigned] (AMBARI-25483) Web alert triggers a wrong critical alert in kerberized cluster.

     [ https://issues.apache.org/jira/browse/AMBARI-25483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmytro Grinenko reassigned AMBARI-25483:
----------------------------------------

    Assignee: Dmytro Grinenko

> Web alert triggers a wrong critical alert in kerberized cluster.
> ----------------------------------------------------------------
>
>                 Key: AMBARI-25483
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25483
>             Project: Ambari
>          Issue Type: Bug
>          Components: alerts, ambari-agent
>    Affects Versions: trunk
>         Environment: _Kerberized cluster._
>            Reporter: Frank
>            Assignee: Dmytro Grinenko
>            Priority: Minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> In a _Kerberized cluster,_ 
> When a "WEB" type alert checks its status with kinit for the very first time. It will create a cache file with command "kinit -c /path/to/tmp/cache -kt /path/to/keytab/file some-principal", next time the alert executes, it will check the cache file status first, which checks the difference between current timestamp and last kinit timestamp. But when compare these two timestamps, we should use "millisecond" unit, not "second". From the variable name of kinit_timer_ms we also could firgure is out. Otherwise, the "if" statement at line 128 will never return True after 14400000 seconds(166.66 days) later.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)