Summary

We installed the Rex Ray plugin for using Docker Volumes on our Isilon appliance. When we use a permissions label, the label is only applied to 5 of our 7 nodes. The configuration is below. What are we doing wrong?

docker plugin install store/rexray/isilon:0.8.2 --alias rexray/isilon ISILON_ENDPOINT=https://xxxxxx.com:8080ISILON_USERNAME=xxxxxxx ISILON_PASSWORD=xxxxxxx ISILON_VOLUMEPATH=/ifs/docker/ddc1np ISILON_DATASUBNET=10.32.45.134/28 ISILON_QUOTAS=false ISILON_NFSHOST=dockernp-az ISILON_INSECURE=true

Bug Reports

This section is for issues that relate to discovered problems or bugs.

Version

Rex Ray software version: 0.8.2

$ rexray version
REX-Ray
-------
Binary: /usr/bin/rexray
Flavor: client+agent+controller
SemVer: 0.7.0
OsArch: Linux-x86_64
Branch: v0.7.0
Commit: a20a838ca70838a914b632637398824fcb10d0db
Formed: Mon, 23 Jan 2017 10:14:32 EST

libStorage
----------
SemVer: 0.4.0
OsArch: Linux-x86_64
Branch: v0.7.0
Commit: a1103d3f215117f7b9f51dae2b24f852c9c54995
Formed: Mon, 23 Jan 2017 10:14:12 EST

Expected Behavior

Permissions get applied to all instances of the volume created

Actual Behavior

Permissions get applied to some instances of the volume created

Steps To Reproduce

Please list the steps to reproduce the issue in this section.

1. Setup Rex Ray plugin: docker plugin install store/rexray/isilon:0.8.2 --alias rexray/isilon ISILON_ENDPOINT=https://xxxxxxxxxxxx.com:8080 ISILON_USERNAME=xxxxxxx ISILON_PASSWORD=xxxxxxx ISILON_VOLUMEPATH=/ifs/docker/ddc1np ISILON_DATASUBNET=10.32.45.134/28 ISILON_QUOTAS=false ISILON_NFSHOST=dockernp-az ISILON_INSECURE=true

2. Create Docker volume: docker volume create --driver=rexray/isilon --label='com.docker.ucp.access.label=myLabel' testVolume

3. View Docker volume: Through the UCP GUI, we aren't seeing the permissions label applied to the volumes on the different nodes.

Configuration Files

Please paste any related configuration files, such as /etc/rexray/config.yml
in this section. Please use the appropriate formatting when pasting YAML.
content. For example:

rexray:
  logLevel:        debug
libstorage:
  logging:
    level:         debug
    httpRequests:  true
    httpResponses: true
  service:         ebs
ebs:
  accessKey:       123456
  secretKey:       abcdef

Proper formatting of pasted content is very important as structured data can
sometimes be accidentally recorded incorrectly, affecting the desired outcome.

Logs

The REX-Ray client will emit all of its logs to the console when operating with debug logging enabled. Simply copy the contents of the console and paste them into the same gist as above naming the file rexray-client.log.sh. The sh

extension will cause the contents to be formatted as if they were emitted

to the shell, which they were.

Service Log

Client Log

Nolan