Open johanrobinson opened 8 years ago
lpabon
commented
8 years ago @johanrobinson Hi, this is interesting. Do you mind supplying the following?
Thanks.
johanrobinson
commented
8 years ago @lpabon Thanks,
I'm using the openshift vagrant demo deployment No files are adjusted.
//JR
lpabon
commented
8 years ago @johanrobinson The vagrant demo already sets everything up for you once the ansible commands are finished deploying. Are you trying to deploy before or after the ansible commands run (which are executed by the up.sh script)?
johanrobinson
commented
8 years ago @lpabon: Thanks for trying to help! :-) I ran everything according to the instructions in this project, deploying everything with vagrant on virtualbox on my MacBookPro. Seems like the vagrant stuff kicked off well and the ansible playbook ran through too without errors. I never ran the 'up.sh' script manually afterwards as I thought this was invoked by vagrant?
lpabon
commented
8 years ago @johanrobinson Cool, so is everything all set?
johanrobinson
commented
8 years ago @lpabon, no it's not all set. As I said vagrant and Ansible ran through without errors, but then when trying to run the topology load in the lab, it fails according to my first post.
raghavendra-talur
commented
8 years ago After looking at #23 and this one, I think the centos/atomic-host vagrant box that @johanrobinson has might be pretty old.
Updating the vagrant box by vagrant box update --box centos/atomic-host could fix both the issues.
[vagrant@client ~]$ heketi-cli -s http://deploy-heketi-aplo.cloudapps.example.com topology load --json=/home/vagrant/topology.json Found node 192.168.10.100 on cluster ea5233c7ce5dc284deaa6324ca83e823 Adding device /dev/vdb ... Unable to add device: Unable to execute command on glusterfs-dc-192.168.10.100-1-sghyu: WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it! Device /dev/vdb not found (or ignored by filtering).
Device /dev/vdc not found (or ignored by filtering).
Device /dev/vdd not found (or ignored by filtering).
Device /dev/vdb not found (or ignored by filtering).
Device /dev/vdc not found (or ignored by filtering).
Device /dev/vdd not found (or ignored by filtering).
Device /dev/vdb not found (or ignored by filtering).
Device /dev/vdc not found (or ignored by filtering).
Device /dev/vdd not found (or ignored by filtering).
The devices /dev/vdb, /dev/vdc, /dev/vdd - doesn't exist on atomic0, atomic1, atomic2 in my setup. Did I miss something in my setup? Using MBP with virtualbox...