Skip to content
This repository has been archived by the owner on Jul 7, 2020. It is now read-only.

Deamonset label to deploy gluster pods are not able to be accessed from heketi pod #59

Closed
MohamedAshiqrh opened this issue Dec 8, 2016 · 1 comment
Closed

Deamonset label to deploy gluster pods are not able to be accessed from heketi pod #59

MohamedAshiqrh opened this issue Dec 8, 2016 · 1 comment

Comments

@MohamedAshiqrh
Copy link
Member

MohamedAshiqrh commented Dec 8, 2016 •
edited

currently heketi searches for this label.
@MohamedAshiqrh MohamedAshiqrh changed the title Deamonset label is wrong and gluster pods are not able to be accessed from heketi pod Deamonset label to deploy gluster pods are not able to be accessed from heketi pod Dec 8, 2016
@MohamedAshiqrh
Copy link
Member Author

Creating cluster ... ID: 08247f43c94b81b28a8a140567c1a924
Creating node 192.168.50.2 ... ID: a86f3758ff72b4beb5f79f3e34b5af70
Adding device /dev/vde ... Unable to add device: Failed to get list of pods
Adding device /dev/vdc ... Unable to add device: Failed to get list of pods
Adding device /dev/vdd ... Unable to add device: Failed to get list of pods
Creating node 192.168.50.3 ... Unable to create node: Failed to get list of pods
Creating node 192.168.50.4 ... Unable to create node: Failed to get list of pods
Error: Error calling v.allocBricksInCluster: Id not found
error: the path "heketi-storage.json" does not exist

I saw this error. #57 fixes this. got confused the labels had to do something with this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MohamedAshiqrh