You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This meant any node provisioned with that code and added to an existing cluster would have an inconsistent version on the Ambari Server (2.0.0) and the newly-provisioned Ambari Agent (2.0.1) and fail to register.
INFO 2015-10-29 18:56:40,612 NetUtil.py:60 - Connecting to https://ip-10-0-1-168.ec2.internal:8440/connection_info
INFO 2015-10-29 18:56:40,724 security.py:93 - SSL Connect being called.. connecting to the server
INFO 2015-10-29 18:56:40,816 security.py:55 - SSL connection established. Two-way SSL authentication is turned off on the server.
ERROR 2015-10-29 18:56:40,860 Controller.py:143 - Cannot register host with non compatible agent version, hostname=ip-10-0-1-161.ec2.internal, agentVersion=2.0.1, serverVersion=2.0.0
INFO 2015-10-29 18:56:40,860 Controller.py:350 - Registration response from ip-10-0-1-168.ec2.internal was FAILED
Anyways, I ran into this today, saw the bug, and fixed it in 9876342.
The text was updated successfully, but these errors were encountered:
Ran into an issue today, using this cookbook to expand an old cluster that was provisioned with Ambari 2.0.0.
The repos under the case switch https://github.com/jp/ambari/blob/master/attributes/default.rb#L17 for Ambari 2.0.0 had been switched to the repos for 2.0.1 in #4ed33fb.
This meant any node provisioned with that code and added to an existing cluster would have an inconsistent version on the Ambari Server (2.0.0) and the newly-provisioned Ambari Agent (2.0.1) and fail to register.
Anyways, I ran into this today, saw the bug, and fixed it in 9876342.
The text was updated successfully, but these errors were encountered: