Closed verdurin closed 6 years ago
@verdurin Are you using ansible 2.6 ? We currently support only 2.4 and 2.5
@guits no, it's 2.4.2.0
.
please, share the full playbook run log in that case
@verdurin it'd be useful to see what facts Ansible is seeing too - using "ansible all -m setup -i inventory_file" or something similar. The error seems to suggest the network CIDR doesn't match the ip addresses on the interface - or something similar.
Thanks for looking. The context here is that I'd been trying to do this via TripleO
, and it was failing owing to device naming issues across the nodes, so I thought I'd just use plain ceph-ansible
.
That background meant an implicit assumption that it would setup interfaces for me, which is obviously nonsense.
Right. Today I was using ceph-deploy
, so I configured the interfaces on the nodes. Now ceph-ansible
is proceeding. I do wonder if the error shown here could be improved?
Do you still want to see that information?
@verdurin any chance you can provide the full log ?
@guits you mean of the last time it failed? (it worked with properly configured interfaces)
@verdurin If you have an actual issue, please, provide the log. Otherwise, I'll assume I can close this issue.
@guits It's working for me now, so I'll close it. Thanks.
I'm seeing this error when I try to create a
luminous
cluster:This is presumably because that interface has no IP address yet.
If I change the
monitor_interface
to refer to an interface that already has an IP, I see this error:Here are the values I've added to
group_vars/all.yml
:I've seen the same error or very similar errors with
stable-3.0
,stable-3.1
andmaster
.