[AMBARI-5589] Cannot start NodeManager after decommissioning, deleting, and then adding it back

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6.0
• Fix Version/s: 2.0.0
• Component/s: ambari-server
• Assignee: Dmitry Lysnichenko
• Reporter: Dmytro Shkvyra
• Created: 28/Apr/14 11:35
• Updated: 24/Nov/14 17:49
• Resolved: 24/Nov/14 17:49

Description

I decommissioned a NodeManager on a host, and then deleted it.
Then I added NodeManager back to the same host.
NodeManager will no longer start on this host, because from the ResourceManager's perspective, this host is still in the exclude list.

Issue Links

• Is contained by: AMBARI-5544 Deleted slave components stick around from the service's perspective
• links to: Review board