-
Notifications
You must be signed in to change notification settings - Fork 15
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
tendrl-ansible playbook fails #62
Comments
Could you share the inventory file? You can anonymize hostnames, but I'm interested in number of machines in each group. I'm asking because 1) I want to understand your environment 2) at first sight, I see no way how could 2 node inventory be a valid setup for Tendrl.
What makes you think that this is a problem of tendrl-ansible? @r0h4n This error message |
@mbukatov
Regarding, centosmaster - it is a simple single node gluster server.
There seem to be many components in tendrl. I am not sure whether the issue is specific to tendrl-ansible except that I deployed it using tendrl-ansible. |
@SaravanaStorageNetwork your environment is not valid wrt both Gluster and Tendrl, you need at least 2 machines for gluster trusted storage pool to be created. With sheer single node, there is no cluster to be imported into Tendrl. Retry with at least 2 nodes to check if the problem was caused by this. USM QE team tests with 6 gluster servers, where we deploy either beta or gama volume from https://github.com/usmqe/usmqe-setup/tree/master/gdeploy_config |
You can create a gluster volume with single node.
But I cannot see the gluster volume. and few errors as mentioned above. Is there any limitation in tendrl supporting volume with minimum of 2 nodes ? Anyway, I will retry with two nodes and update. |
I have tried with two nodes. but it fails again with following messages.
|
@SaravanaStorageNetwork looking at the log, the root cause is fortunately stated there, package
Note: this error message is brought to you by @shtripat who fixed Tendrl/node-agent#627 for us. Let's thank him here again :-) Going back to your log output, based on this error, it seems you have some problem with gluster repositories. Have you enabled any additional repositories on your storage machines? What Anyway, the log you provided when trying with 2 machines also shows that the original error is no longer shown, which means that you should report he issue as I suggested in #62 (comment) |
This is news for me. Could you point me to upstream documentation for this single node gluster trusted storage pool feature? |
Please check this - one scenario where single node glusterfs is possible -
I am using Centos 7.4 and then trying out tendrl-ansible. Another error is, by default rubygem-json-2.0.2-2.el7.x86_64 gets installed and tendrl-ansible looks for rubygem-json-1.7.7-30.el7 and Fails. |
That message about one node cluster looks interesting, thank you for the pointer. I don't have enough time to check this now, but will look into this later. |
Transferring to Tendrl/gluster-integration#719 |
Hi,
Tried setting up tendrl-ansible with two nodes.
ansible-playbook of site.yml succeeded.
But, tendrl server accessed from browser, I can see the following errors after import.
Could you check?
The text was updated successfully, but these errors were encountered: