[AMBARI-16134] Force running service checks for services before upgrade

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 2.4.0
• Component/s: ambari-server
• Assignee: Dmitry Lysnichenko
• Reporter: Dmitry Lysnichenko
• Created: 27/Apr/16 09:00
• Updated: 26/Sep/16 21:41
• Resolved: 28/Apr/16 17:03

Description

Just checking for service checks that were run within the last hour does not seem to be a warranty of anything. For example, user could install cluster, run service checks once, and then enable security/LDAP/change configuration as required by some pre-upgrade check/whatever, and still have Health Check passing.

So the current idea is to check configuration change history and compare config change timestamps with last time the service check for related service was run.

Also log to Ambari log timestamps of latest service checks for services, and timestamps of latest service config changes (INFO level)

Issue Links

• is related to: AMBARI-18470 RU/EU cannot start because ServiceCheckValidityCheck incorrectly calculates Service Checks that ran
• links to: review_request_