@Raja Sekhar Chintalapati The good news is that you can upgrade from 1.7 to 2.2 directly. "You mentioned this already" Issue is with the bug in the upgrade process. You followed the instructions in this link and hitting this error Error executing query: ALTER TABLE cluster_version ADD CONSTRAINT FK_cluster_version_cluster_id FOREIGN KEY (cluster_id) REFERENCES clusters (cluster_id) clusters table has one row and cluster_version table is empty. that was the reason it is not able to add FK ambari213=> select * from clusters; cluster_id | resource_id | cluster_info | cluster_name | provisioning_state | security_type | desired_cluster_state | desired_stack_id ------------+-------------+--------------+--------------+--------------------+---------------+-----------------------+------------------ 2 | 4 | | HDPTEST | INSTALLED | NONE | | 4 (1 row) ambari213=> select * from cluster_version; id | repo_version_id | cluster_id | state | start_time | end_time | user_name ----+-----------------+------------+---------+---------------+---------------+------------ 1 | 1 | 2 | CURRENT | 1447960627766 | 1447960627785 | _anonymous (1 row) ambari213=> Please see the above. We need to find the root cause on "0 rows in cluster_version" Can you paste the output of above queries? Also, Do you have access to support?
... View more
