[AMBARI-12101] Ambari : upgrading from 2.0.0 to 2.0.1 wipes out the added service folder on the stack.

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.1.0
• Component/s: ambari-server
• Assignee: Dmytro Sen
• Reporter: Dmytro Sen
• Created: 23/Jun/15 18:13
• Updated: 30/Jun/15 20:24
• Resolved: 30/Jun/15 17:02

Description

• Install Ambari 2.0 based cluster.
• Add a new service (custom) which is not part of the stack using "Add Service" wizard. This step requires the new custom service package needs to be copied to the /var/lib/ambari-server/resources/stacks/HDP/2.2/services folder.
• Deploy the new service and everything works fine.
• Now upgrade from Ambari 2.0 to Ambari 2.0.1

Problem: The /var/lib/ambari-server/resources/stacks/HDP/2.2/services/mycustomservice folder got wiped out. Restarting the ambari-server results in the following exception.

27 May 2015 10:53:55,441 ERROR [main] AmbariServer:667 - Failed to run the Ambari Server
org.apache.ambari.server.StackAccessException: Stack data, stackName=HDP, stackVersion=2.2, serviceName=HST
	at org.apache.ambari.server.api.services.AmbariMetaInfo.getService(AmbariMetaInfo.java:497)
	at org.apache.ambari.server.api.services.AmbariMetaInfo.getComponent(AmbariMetaInfo.java:265)
	at org.apache.ambari.server.controller.utilities.DatabaseChecker.checkDBConsistency(DatabaseChecker.java:96)
	at org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:217)
	at org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:665)

Expected: After upgrade the added service should be available and active. The custom service folder should not be wiped out from the stacks folder.

Issue Links

• links to: review request