Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Ambari 2.0.0 #13

Closed
Joseph-R opened this issue Oct 29, 2015 · 0 comments
Closed

Support Ambari 2.0.0 #13

Joseph-R opened this issue Oct 29, 2015 · 0 comments

Comments

@Joseph-R
Copy link
Collaborator

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.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant