I am seeing a similar problem pushing a configuration into Ambari through the REST API. I expect this is not an Ambari problem, but Ambari is tickling a data corruption problem in yum/rpm. Still, I think Ambari should provide a programmable method of recovering from such a failure
Is there such a method? Or do I really have to touch every node in the cluster manually and rebuild their rpm databases and then use the Ambari dashboard to manually complete the installations and start the services??
My environment is RedHat nodes in AWS EC2. Not enough characters in this box to provide the blueprint and host mapping json…