Details
Description
It's called s3xen, not s3xenserver. While investigating, I found the same issue for swiftxen.
Regresion from a8212d9 where things were massively renamed, without proper verification.
Error seen:
2015-10-22 21:42:30,372 WARN [c.c.h.x.r.CitrixResourceBase] (DirectAgent-261:ctx-862ebceb) callHostPlugin failed for cmd: s3 with args maxErrorRetry: 10, secretKey: +XGy4yPPbAH9AijYxFTr1yVCCiVQuSfXWWj1Invs,
connectionTtl: null, iSCSIFlag: false, maxSingleUploadSizeInBytes: 5368709120, bucket: mccx-nl2, endPoint: s3.storage.acc.schubergphilis.com, filename: /var/run/sr-mount/9414f970-0afd-42db-972f-aa4743293430/2
cf0c24b-a596-4039-b50a-7ce87da4f273.vhd, accessKey: 16efbc4e870f24338141, socketTimeout: null, https: false, connectionTimeout: 300000, operation: put, key: snapshots/2/10/2cf0c24b-a596-4039-b50a-7ce87da4f273
.vhd, useTCPKeepAlive: null, due to Task failed! Task record: uuid: 4be8a515-1e2a-59de-6301-029fb0326651
nameLabel: Async.host.call_plugin
nameDescription:
allowedOperations: []
currentOperations: {}
created: Thu Oct 22 21:42:44 CEST 2015
finished: Thu Oct 22 21:42:44 CEST 2015
status: failure
residentOn: com.xensource.xenapi.Host@9c7aad90
progress: 1.0
type: <none/>
result:
errorInfo: [XENAPI_MISSING_PLUGIN, s3xenserver]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
Task failed! Task record: uuid: 4be8a515-1e2a-59de-6301-029fb0326651
nameLabel: Async.host.call_plugin
nameDescription:
allowedOperations: []
currentOperations: {}
created: Thu Oct 22 21:42:44 CEST 2015
finished: Thu Oct 22 21:42:44 CEST 2015
status: failure
residentOn: com.xensource.xenapi.Host@9c7aad90
progress: 1.0
type: <none/>
result:
errorInfo: [XENAPI_MISSING_PLUGIN, s3xenserver]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
Here we see the correct name:
scripts/vm/hypervisor/xenserver/s3xen:lib.setup_logging("/var/log/cloud/s3xen.log")
scripts/vm/hypervisor/xenserver/xenserver56/patch:s3xen=..,0755,/etc/xapi.d/plugins
scripts/vm/hypervisor/xenserver/xenserver56fp1/patch:s3xen=..,0755,/etc/xapi.d/plugins
scripts/vm/hypervisor/xenserver/xenserver60/patch:s3xen=..,0755,/etc/xapi.d/plugins
scripts/vm/hypervisor/xenserver/xenserver62/patch:s3xen=..,0755,/etc/xapi.d/plugins
scripts/vm/hypervisor/xenserver/xenserver65/patch:s3xen=..,0755,/etc/xapi.d/plugins
And:
scripts/vm/hypervisor/xenserver/xenserver56/patch:swiftxen=..,0755,/etc/xapi.d/plugins
scripts/vm/hypervisor/xenserver/xenserver56fp1/patch:swiftxen=..,0755,/etc/xapi.d/plugins
scripts/vm/hypervisor/xenserver/xenserver60/patch:swiftxen=..,0755,/etc/xapi.d/plugins
scripts/vm/hypervisor/xenserver/xenserver62/patch:swiftxen=..,0755,/etc/xapi.d/plugins
scripts/vm/hypervisor/xenserver/xenserver65/patch:swiftxen=..,0755,/etc/xapi.d/plugins
These plugins are pushed to the hypervisor.