glusterd2
glusterd2 copied to clipboard
Volume creation failing with hostname (FQDN)
Observed behavior
glustercli volume create rep10 replica 3 dhcp35-219.lab.eng.blr.redhat.com:/bricks/brick0/rep10 dhcp35-33.lab.eng.blr.redhat.com:/bricks/brick0/rep10 dhcp35-194.lab.eng.blr.redhat.com:/bricks/brick0/rep10 --create-brick-dir
Error getting brick UUIDs
could not find UUIDs of bricks specified
Expected/desired behavior
Volume creation should be successful
Details on how to reproduce (minimal and precise)
-> Create a cluster using ip (glustercli peer add <IP>) -> Try to create a volume with brick path containing hostnames -> Volume creation failing with below errors
could not find UUIDs of bricks specified
Information about the environment:
- Glusterd2 version used (e.g. v4.1.0 or master):
- Operating system used:
- Glusterd2 compiled from sources, as a package (rpm/deb), or container:
- Using External ETCD: (yes/no, if yes ETCD version):
- If container, which container image:
- Using kubernetes, openshift, or direct install:
- If kubernetes/openshift, is gluster running inside kubernetes/openshift or outside:
Other useful information
- glusterd2 config files from all nodes (default /etc/glusterd2/glusterd2.toml)
- glusterd2 log files from all nodes (default /var/log/glusterd2/glusterd2.log)
- ETCD configuration
- Contents of
uuid.toml
from all nodes (default /var/lib/glusterd2/uuid.toml) - Output of
statedump
from any one of the node
Useful commands
- To get glusterd2 version
glusterd2 --version
- To get ETCD version
etcd --version
- To get output of statedump
curl http://glusterd2-IP:glusterd2-Port/statedump
@rmadaka need peer list
output
@aravindavk If we are to implement this, should we add probing peer using hostname as well since we are just considering addresses currently ?
This isn't a priority from GCS perspective at this moment. We do have multi hostnames support in GD1, so eventually we have to get there when it comes to achieving parity of GD1, but our immediate goal is to satisfy the GCS needs.