----- Le 11 Déc 19, à 9:57, Daniel Berteaud [email protected] a écrit :
> ----- Le 11 Déc 19, à 9:51, mail [email protected] a écrit : > >> Hi Daniel, >> >> did you also upgrade the workflow for the report generation >> (workflow/def/report_full.yaml)? The method to load the values and >> labels for the report selection has changed so I guess this is the error >> you are seeing. > > Yes, I've updated the workflow to the 3.1.2 config release (I have very few > modifications, and none affects report_full.yaml) > >> >> Check for this part in the workflow def: >> >> report_config: >> name: report_config >> label: I18N_OPENXPKI_UI_REPORT_CONFIG_LABEL >> type: select >> option: >> item@: report >> mode: map >> required: 1 > > This section looks exactly like this : > > report_config: > name: report_config > label: I18N_OPENXPKI_UI_REPORT_CONFIG_LABEL > type: select > option: > item@: report > mode: map > required: 1 > > > I'll upgrade to 3.2 and see if it still happens. Same behavior and same error after upgrading OpenXPKI to 3.2.0 (and config to 3.2 too) The only modifications in the realm conf are in : - crypto.yaml - notification/smtp.yaml - publishing.yaml - profile/default.yaml - profile/signer.yaml - auth/stack.yaml - auth/handler.yaml - workflow/global/validator/password_quality.yaml - scep/scep-server.yaml So it doesn't look like any of my customizations could affect report_full. Everything else is the vanilla config we can find in realm.tpl of openxpki-config repo Regards, Daniel -- [ https://www.firewall-services.com/ ] Daniel Berteaud FIREWALL-SERVICES SAS, La sécurité des réseaux Société de Services en Logiciels Libres Tél : +33.5 56 64 15 32 Matrix: @dani:fws.fr [ https://www.firewall-services.com/ | https://www.firewall-services.com ] _______________________________________________ OpenXPKI-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-users
