[AMBARI-24141] Rolling restarts not working when Kerberos Auto sign in is enabled for Ambari

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 2.7.0
• Component/s: ambari-server
• Labels: pull-request-available
• Assignee: Robert Levas
• Reporter: Robert Levas
• Due: 20/Jun/18
• Created: 19/Jun/18 03:00
• Updated: 20/Jun/18 19:53
• Resolved: 20/Jun/18 19:14

Description

Rolling restarts not working when Kerberos Auto sign in is enabled for Ambari. This is due to a missing user ID value in the requestschedule table, resulting in the Rolling Restart operation aborting with no deals in the ambari-server.log file.

schedule_id	cluster_id	authenticated_user_id	create_user	update_user	last_execution_status
2	2	-1	rlevas	rlevas	IN_PROGRESS

This occurs because the org.springframework.security.core.Authentication class stored in Ambari's SecurityContext for the authenticated user does not contain the authenticated user's ID data. Adjustments need to be made to the infrastructure to capture this data upon login and then retrieve it later, when needed.

Issue Links

• links to: GitHub Pull Request #1582