I'm going to update HDP-184.108.40.206 to HDP-220.127.116.11 using Ambari.
After I've registered HDP-18.104.22.168 version, it's not displayed on Versions tab in Ambari.
I'm using Ambari 2.2. What am I missing?
I had the same problem and I have tried this and it works!
1 - Access Ambari Database
2 - ambari=> select * from stack;
stack_id | stack_name | stack_version
1 | HDP | 2.3
2 | HDP | 2.1.GlusterFS
3 | HDP | 2.2
4 | HDP | 2.1
5 | HDP | 2.0
6 | HDP | 2.0.6
7 | HDP | 2.3.GlusterFS
8 | HDP | 2.0.6.GlusterFS
ambari=> select cluster_id, desired_stack_id from clusters;
cluster_id | desired_stack_id
4 | 3
Then update table "clusters" to set the correct stack_id (HDP 2.3)
ambari=> update clusters set desired_stack_id = 1 where cluster_id = 4;
Maybe the URLs you registered are not accessible. I had the same issue the other day and there was no error, only the version was not registered. Just retry to register the new version again, making sure the repo URLs are correct and accessible.
I've created a local copy of HDP-2.3.4 repo on my network and it's accesible by all nodes.
I did the same when updted 2.2.0 to 2.2.8 and 2.2.9 and it worked fine for me. The issue is only while trying to upgrade 2.2.* to 2.3.*
I understand what are you saying, but it's possible that your "Base URLs" don't map exactly your un-tarred directory layout. If you are using the latest HDP-UTILS the layout of directories after untar is a little bit different than before. So, can you please check that. Also check ambari-server log if the registration fails again. Finally, if you are most certain that your Base URLs are correct you can check "Skip repo base URL validation" flag at the bottom of the page, but it's not recommended.
By the way, to check your base URLs you can try this, from any node in the cluster:
wget <HDP-base-URL>/repodata/repomd.xml wget <HDP-UTILS-base-URL>/repodata/repomd.xml
Dear @Predrag Minovic,
Thank you for your answer.
I've made all of the suggested checks, but no result... The version HDP-22.214.171.124 is registered and listed on 'Manage Versions' page (pls, see the attached picture).
When I click on the 'Install on...' button for version HDP-126.96.36.199, I'm transferred back to 'Stack and Versions' page, and I don't see previously registered version HDP-188.8.131.52...
Btw, I've switched from local repositories to Hortonworks' ones listed here: http://docs.hortonworks.com/HDPDocuments/Ambari-184.108.40.206/bk_Installing_HDP_AMB/content/_hdp_stack_rep...:
Hi @Dennis Fridlyand, well at this point I don't have any other idea. Anything in your abmari-server.log? The other day I registered, installed and upgraded from 2.2.8 to 2.3.4, the only difference with your screenshot was that I didn't have 2.2.9 ready to perform upgrade. Though, that page implies that you can register and install multiple versions. Is an upgrade to 2.2.9 first and then to 2.3.4 an option? Re repos: public or local should not make any difference as far as the links are accessible and correct. I always use local because the install is much faster.
why don't upgrade to 220.127.116.11 first, the current 2.2.8 will be de-registered and try again then? Also consider trying Ambari 18.104.22.168 that was just released. I'm guessing but I think Ambari can only maintain 4 versions of HDP and you have all four, you might need to drop one before upgrading to 2.3.4. Wierder things have happened...