[AMBARI-19585] Client config tags may not be saved by agent

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5.0
• Fix Version/s: 3.0.0, 2.5.0
• Component/s: ambari-agent
• Assignee: Attila Doroszlai
• Reporter: Attila Doroszlai
• Created: 17/Jan/17 13:05
• Updated: 18/Jan/17 18:44
• Resolved: 18/Jan/17 16:15

Description

Ambari agent does not save the config tags (eg. "V1") during component installation if it cannot determine that the component is a client. For this decision it requests the list of services/components right after it receives the first status command, which might happen after some client components are already installed. If the initial tags are missing, no subsequent config changes trigger updates on the affected host (except forced update via "Service Actions > Refresh configs").

Issue Links

• links to: Review request