Plugin transport-email (v0.6.0) broken ?
-
Can you test on XOA
latest
then? This will help to see if it's only onmaster
-
@olivierlambert Could need some help on testing this, since I am not sure if that was the correct way.
First did a Xen Orchestra Appliance (XOA) quick deploy on my playlab master host and registered XOA. Only telemetry (v0.4.0) and xoa (v0.11.3) are available plugins after deployment, both active. Logged in via SSH and did a
sudo xoa-updater --upgrade
which updated XOA successully.Since the the transport-email plugin was not available/installed after the quick deploy, I installed it manually - is that the correct way do install a plugin on XOA ? npm complained but installed the plugin:
[17:35 05] xoa@xoa:~$ sudo npm install --global xo-server-transport-email npm WARN deprecated xo-server-transport-email@0.5.0: Dont install XO plugin from npm, please refer to documentation https://xen-orchestra.com/docs/from_the_sources.html + xo-server-transport-email@0.5.0 added 6 packages from 3 contributors in 1.136s
And after a
sudo systemctl restart xo-server.service
the plugin transport-email (v0.5.0) is now available in XOA under settings/plugins. The plugin can be configured (settings can be saved), activated and it tests successfully. So transport-email (v0.5.0) on XOA does work, while transport-email (v0.6.0) on XO from 3rd party script does not. -
No, it doesn't work like that. This plugin is only available in XOA Starter or more (so you need an XOA Trial enabled).
On XOA, you never install anything manually
edit: obviously, if you have no trial left, I'll be happy to add you one for free
-
@olivierlambert said in Plugin transport-email (v0.6.0) broken ?:
Can you test on XOA
latest
then? This will help to see if it's only onmaster
Never done that, can i switch back and forth between master and latest on the same install?
I will have to wait as i am currently running full backups after delta keeps failing on me again (f** that). -
There's no
master
on XOA, it's onlystable
andlatest
. They aren't Git branches but release channels with validate with QA specifically on our virtual appliance. -
@meth0d said in Plugin transport-email (v0.6.0) broken ?:
@olivierlambert said in Plugin transport-email (v0.6.0) broken ?:
Can you test on XOA
latest
then? This will help to see if it's only onmaster
Never done that, can i switch back and forth between master and latest on the same install?
I will have to wait as i am currently running full backups after delta keeps failing on me again (f** that).Just go through this to use XOA Trial https://xen-orchestra.com/blog/xen-orchestra-free-trial/
-
I have same problem on community edition updated to the latest release.
There is error from log file:{ "message": "strict mode: unknown keyword: \"enumNames\"", "name": "Error", "stack": "Error: strict mode: unknown keyword: \"enumNames\" at checkStrictMode (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/util.ts:211:28) at checkUnknownRules (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/util.ts:27:22) at Object.alwaysValidSchema (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/util.ts:17:3) at /opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/vocabularies/applicator/properties.ts:23:48 at Array.filter (<anonymous>) at Object.code (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/vocabularies/applicator/properties.ts:23:33) at keywordCode (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/validate/index.ts:519:9) at /opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/validate/index.ts:265:9 at CodeGen.code (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/codegen/index.ts:525:33) at CodeGen.block (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/codegen/index.ts:680:20) at iterateKeywords (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/validate/index.ts:262:7) at groupKeywords (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/validate/index.ts:241:7) at /opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/validate/index.ts:233:38 at CodeGen.code (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/codegen/index.ts:525:33) at CodeGen.block (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/codegen/index.ts:680:20) at schemaKeywords (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/validate/index.ts:232:7) at typeAndKeywords (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/validate/index.ts:162:3) at subSchemaObjCode (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/validate/index.ts:148:3) at subschemaCode (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/validate/index.ts:125:7) at KeywordCxt.subschema (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/compile/validate/index.ts:487:5) at applyPropertySchema (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/vocabularies/applicator/properties.ts:45:11) at Object.code (/opt/xen-orchestra/packages/xo-server/node_modules/ajv/lib/vocabularies/applicator/properties.ts:32:9)" }
-
Have you checked this @Alexander-0 ? https://xen-orchestra.com/docs/community.html
-
-
@olivierlambert I made this operations from list and have the same result.
-
@alexander-0 Thank for this report, taking a look ASAP.
-
@julien-f I found that there is no folder lib in /opt/xen-orchestra/packages/xo-server/node_modules/ajv/
May be this will help in resolving -
Thank you all for your reports, should be fixed
https://github.com/vatesfr/xen-orchestra/commit/3cc9fd2782de353dbd866471a793366748c0c098
-
@julien-f Plugin works! Thank you.
-
@julien-f yes, works well (even with the 3td party script ). Nice job and fast as usual . Thanks @Alexander-0 for helping to pin it down