torusblk.flex doesn't say why it failed to attach volume

[nak3]

version

• Version: a9c6bc1

issue

• torusblk doesn't say why it failed to attach volume when it used as k8s volume plugin.

step to reproduce (just an example case)

1. Don't create any volume intentionally

$ ./bin/torusctl volume list
VOLUME NAME  SIZE  TYPE

2. Deploy pod and try to use torus volume

• (e.g.) deploy postgres-oneshot.yaml here

Actually result and issue

Of course, Pod doesn't start, but the issue is event log and kublet log don't say the reason.

• event log

  2016-11-18 11:23:53 +0000 UTC   2016-11-18 11:23:53 +0000 UTC   1         postgres-torus                    Deployment                                 Normal    ScalingReplicaSet   {deployment-controller }   Scaled up replica set postgres-torus-1616493773 to 1
  2016-11-18 11:23:53 +0000 UTC   2016-11-18 11:23:53 +0000 UTC   1         postgres-torus-1616493773         ReplicaSet                                 Normal    SuccessfulCreate    {replicaset-controller }   Created pod: postgres-torus-1616493773-g5ljh
  2016-11-18 11:23:53 +0000 UTC   2016-11-18 11:23:53 +0000 UTC   1         postgres-torus-1616493773-g5ljh   Pod                                        Normal    Scheduled           {default-scheduler }       Successfully assigned postgres-torus-1616493773-g5ljh to fed-node
  2016-11-18 11:29:33 +0000 UTC   2016-11-18 11:29:48 +0000 UTC   2         postgres-torus-1616493773-g5ljh   Pod                                        Warning   FailedSync          {kubelet fed-node}         Error syncing pod, skipping: mount command failed, status: Failure, reason: failed
  2016-11-18 11:29:33 +0000 UTC   2016-11-18 11:29:48 +0000 UTC   2         postgres-torus-1616493773-g5ljh   Pod                                        Warning   FailedMount         {kubelet fed-node}         Unable to mount volumes for pod "postgres-torus-1616493773-g5ljh_default(7cad9650-ad81-11e6-b6f9-5254007c7544)": mount command failed, status: Failure, reason: failed
  2016-11-18 11:23:54 +0000 UTC   2016-11-18 11:40:59 +0000 UTC   72        postgres-torus-1616493773-g5ljh   Pod                                        Warning   FailedSync          {kubelet fed-node}         Error syncing pod, skipping: attach command failed, status: Failure, reason: Couldn't attach
  2016-11-18 11:23:54 +0000 UTC   2016-11-18 11:40:59 +0000 UTC   72        postgres-torus-1616493773-g5ljh   Pod                                        Warning   FailedMount         {kubelet fed-node}         Unable to mount volumes for pod "postgres-torus-1616493773-g5ljh_default(7cad9650-ad81-11e6-b6f9-5254007c7544)": attach command failed, status: Failure, reason: Couldn't attach

It just says Couldn't attach implemented here.

[nak3]

Actually the logs are ouptut in journal log, since it calls systemd/dbus and executes flex volumes. However, I believe that it should be ouptut in user side.