hpe-storage / python-hpedockerplugin

HPE Native Docker Plugin
Apache License 2.0
36 stars 64 forks source link

DECO: docker volume ls not working. #700

Open sandesh-desai opened 5 years ago

sandesh-desai commented 5 years ago

Steps to re-produce:

1) docker volume create -d hpe --name Merlin_Volume14 -o backend=Merlin 2) docker volume inspect Merlin_Volume14 3) docker volume ls

Expected result:It should show volume name as Merlin_Volume14 Actual result: It shows blank.

Below hpe.conf details:

[root@cssosbe01-b13-196117 ~]# cat /etc/hpedockerplugin/hpe.conf [DEFAULT] ssh_hosts_key_file = /root/.ssh/known_hosts logging = DEBUG hpe3par_debug = False suppress_requests_ssl_warnings = False host_etcd_ip_address = 15.212.196.117 host_etcd_port_number = 2379

hpedockerplugin_driver = hpedockerplugin.hpe.hpe_3par_iscsi.HPE3PARISCSIDriver

hpedockerplugin_driver = hpedockerplugin.hpe.hpe_3par_fc.HPE3PARFCDriver hpe3par_api_url = https://15.213.71.140:443/api/v1 hpe3par_username = 3paradm hpe3par_password = 3pardata san_ip = 15.213.71.140 san_login = 3paradm san_password = 3pardata hpe3par_cpg = arshad_ssd hpe3par_snapcpg = arshad_ssd

hpe3par_iscsi_chap_enabled = True

use_multipath = True

enforce_multipath = True

mount_conflict_delay = 30

[Merlin] ssh_hosts_key_file = /root/.ssh/known_hosts host_etcd_ip_address = 15.212.196.117 host_etcd_port_number = 2379 logging = DEBUG hpedockerplugin_driver = hpedockerplugin.hpe.hpe_3par_fc.HPE3PARFCDriver hpe3par_api_url = https://15.213.71.140:443/api/v1 hpe3par_username = 3paradm hpe3par_password = 3pardata san_ip = 15.213.71.140 san_login = 3paradm san_password = 3pardata hpe3par_cpg = bh_cpg hpe3par_snapcpg = bh_cpg

imran-ansari commented 5 years ago

This was due to the failure in initializing the default backend. And the failure was due to incorrect password provided for the array. Please always check the default backend status when you don't get anything displayed in the ls command after creating volume(s). Once the backend is initialized properly, ls should work.

I'm marking this as a documentation issue unless proper backend initialization doesn't resolve it.

sneharai4 commented 4 years ago

@sandesh-desai Please close this defect if no more actions pending.