Bug #7784
closedUser story #7698: Make the output of rudder agent readable by a human
Rudder agent new output does not give the same number of results success/error with nothing/-i/-r
Description
I have a case where some reports are not consistantly parsed depending of the verbosiby of the rudder agent run command:
Case 1 (rudder agent run):
root@server:/var/rudder/configuration-repository# rudder agent run Rudder agent 3.2.0~rc3~git201601150159-wheezy0 (CFEngine Core 3.7.1) Node uuid: root Start execution with config [-1059466650] Result Technique Component Key Message error Common Update Cannot update Rudder tools last updated file success Common Update Rudder ncf instance already up to date on this root server. No action required. success Common Security parameters The internal environment security is acceptable success Common Red Button Red Button is not in effect, continuing as normal... success Common Process checking There is an acceptable number of CFEngine processes running on the machine success Common Log system for reports Logging system for report centralization is already correctly configured success Common CRON Daemon Cron daemon status was correct success Common Binaries update The CFengine binaries in /var/rudder/cfengine-community/bin are up to date success DistributePolicy Configure ncf Configure ncf was correct success DistributePolicy Propagate promises All files have been propagated success DistributePolicy Send inventories to CMDB No inventory to send success Inventory inventory Next inventory scheduled between 00:00 and 06:00 success server-roles Check logrotate configur| The logrotate configuration is correct success server-roles Check LDAP in rudder-web| The Rudder Webapp configuration files are OK (checked LDAP password) success server-roles Check LDAP credentials The OpenLDAP configuration file is OK (checked rootdn password) success server-roles Check SQL in rudder-weba| The Rudder Webapp configuration files are OK (checked SQL password) success server-roles Check SQL credentials The Rudder PostgreSQL user account's password is correct and works success server-roles Check rudder-passwords.c| The Rudder passwords file is present and secure success server-roles Check allowed networks c| The Rudder allowed networks configuration is OK success server-roles Check WebDAV credentials The Rudder WebDAV user and password are OK success server-roles Check apache process The apache process is already running success server-roles Check apache boot script Check apache boot starting parameters was correct success server-roles Check jetty process The jetty process is already running success server-roles Check configuration-repo| The /var/rudder/configuration-repository directory is present success server-roles Check configuration-repo| The /var/rudder/configuration-repository GIT lock file is not present or not older than 5 minutes success server-roles Check rudder status The http://localhost:8080/rudder/api/status web application is running success server-roles Check endpoint status The http://localhost:8080/endpoint/api/status web application is running success server-roles Check slapd process The slapd process is already running success server-roles Check PostgreSQL configu| Their is no need of specific postgresql configuration on this system success server-roles Check postgresql process The postgresql process is already running success server-roles Check postgresql boot sc| Check postgresql boot starting parameters was correct n/a server-roles Send metrics to rudder-p| Sending metrics to rudder-project is not enabled. Skipping. ## Summary ##################################################################### success: 30 error: 1 execution time: 1.68s ################################################################################
Case 2 (rudder agent run -i):
root@server:/var/rudder/configuration-repository# rudder agent run -i rudder info: Error reading assumed integer value '0.000000' => 'non-value', found remainder '000000' rudder info: Error reading assumed integer value '0.000000' => 'non-value', found remainder '000000' rudder info: Unable to lookup hostname 'rudder' or cfengine service. (getaddrinfo: Name or service not known) rudder info: Error reading assumed integer value '0.000000' => 'non-value', found remainder '000000' rudder info: Error reading assumed integer value '0.000000' => 'non-value', found remainder '000000' rudder info: Error reading assumed integer value '0.000000' => 'non-value', found remainder '000000' rudder info: Error reading assumed integer value '0.000000' => 'non-value', found remainder '000000' R: @@Common@@log_info@@hasPolicyServer-root@@common-root@@3@@common@@StartRun@@2016-01-15 13:38:28+00:00##root@#Start execution with config [-1059466650] rudder info: Automatically promoting context scope for 'heartbeat_sent' to namespace visibility, due to persistence R: @@Common@@result_error@@hasPolicyServer-root@@common-root@@3@@Update@@None@@2016-01-15 13:38:28+00:00##root@#Cannot update Rudder tools last updated file Result Technique Component Key Message success Common Update Rudder ncf instance already up to date on this root server. No action required. success Common Security parameters The internal environment security is acceptable success Common Red Button Red Button is not in effect, continuing as normal... success Common Process checking There is an acceptable number of CFEngine processes running on the machine info Common Log system for reports Detected running syslog as rsyslog success Common Log system for reports Logging system for report centralization is already correctly configured rudder info: Executing 'no timeout' ... '/var/rudder/tools/check-rsyslog-version' rudder info: Completed execution of '/var/rudder/tools/check-rsyslog-version' R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@3@@CRON Daemon@@None@@2016-01-15 13:38:28+00:00##root@#Cron daemon status was correct success Common Binaries update The CFengine binaries in /var/rudder/cfengine-community/bin are up to date success DistributePolicy Configure ncf Configure ncf was correct success DistributePolicy Propagate promises All files have been propagated success DistributePolicy Send inventories to CMDB No inventory to send rudder info: Executing 'no timeout' ... '/usr/bin/curl -L -k -1 -s -f --proxy '' -o "/var/rudder/cfengine-community/rudder-server-uuid.txt" https://127.0.0.1/uuid' rudder info: Completed execution of '/usr/bin/curl -L -k -1 -s -f --proxy '' -o "/var/rudder/cfengine-community/rudder-server-uuid.txt" https://127.0.0.1/uuid' R: @@Inventory@@log_info@@inventory-all@@inventory-all@@3@@inventory@@None@@2016-01-15 13:38:28+00:00##root@#An inventory was already sent less than 8 hours ago success Inventory inventory Next inventory scheduled between 00:00 and 06:00 success server-roles Check logrotate configur| The logrotate configuration is correct success server-roles Check LDAP in rudder-web| The Rudder Webapp configuration files are OK (checked LDAP password) success server-roles Check LDAP credentials The OpenLDAP configuration file is OK (checked rootdn password) success server-roles Check SQL in rudder-weba| The Rudder Webapp configuration files are OK (checked SQL password) success server-roles Check SQL credentials The Rudder PostgreSQL user account's password is correct and works success server-roles Check rudder-passwords.c| The Rudder passwords file is present and secure success server-roles Check allowed networks c| The Rudder allowed networks configuration is OK success server-roles Check WebDAV credentials The Rudder WebDAV user and password are OK R: [DEBUG] Promise kept, not doing anything: Check if the service apache2 is started using ps R: [DEBUG] Promise kept, not doing anything: Check if the service ${service_regex} is started R: [DEBUG] Promise kept, not doing anything: Ensure that service apache2 is running success server-roles Check apache process The apache process is already running R: [DEBUG] Promise kept, not doing anything: Check if service apache2 is defined at boot R: [DEBUG] Promise kept, not doing anything: Ensure service apache2 is set at boot success server-roles Check apache boot script Check apache boot starting parameters was correct R: [DEBUG] Promise kept, not doing anything: Check if the service .*java.*/opt/rudder/jetty7/start.jar is started using ps R: [DEBUG] Promise kept, not doing anything: Ensure that service rudder-jetty is running success server-roles Check jetty process The jetty process is already running success server-roles Check configuration-repo| The /var/rudder/configuration-repository directory is present success server-roles Check configuration-repo| The /var/rudder/configuration-repository GIT lock file is not present or not older than 5 minutes rudder info: Executing 'no timeout' ... '/usr/bin/curl -s http://localhost:8080/rudder/api/status |/bin/grep -q OK' rudder info: Automatically promoting context scope for 'site_ok' to namespace visibility, due to persistence rudder info: Completed execution of '/usr/bin/curl -s http://localhost:8080/rudder/api/status |/bin/grep -q OK' R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check rudder status@@None@@2016-01-15 13:38:28+00:00##root@#The http://localhost:8080/rudder/api/status web application is running rudder info: Executing 'no timeout' ... '/usr/bin/curl -s http://localhost:8080/endpoint/api/status |/bin/grep -q OK' rudder info: Automatically promoting context scope for 'site_ok' to namespace visibility, due to persistence rudder info: Completed execution of '/usr/bin/curl -s http://localhost:8080/endpoint/api/status |/bin/grep -q OK' R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check endpoint status@@None@@2016-01-15 13:38:28+00:00##root@#The http://localhost:8080/endpoint/api/status web application is running R: [DEBUG] Promise kept, not doing anything: Check if the service /opt/rudder/libexec/slapd is started using ps R: [DEBUG] Promise kept, not doing anything: Ensure that service rudder-slapd is running success server-roles Check slapd process The slapd process is already running success server-roles Check PostgreSQL configu| Their is no need of specific postgresql configuration on this system R: [DEBUG] Promise kept, not doing anything: Check if the service postgres: writer process is started using ps R: [DEBUG] Promise kept, not doing anything: Ensure that service postgresql is running success server-roles Check postgresql process The postgresql process is already running R: [DEBUG] Promise kept, not doing anything: Check if service postgresql is defined at boot R: [DEBUG] Promise kept, not doing anything: Ensure service postgresql is set at boot success server-roles Check postgresql boot sc| Check postgresql boot starting parameters was correct n/a server-roles Send metrics to rudder-p| Sending metrics to rudder-project is not enabled. Skipping. ## Summary ##################################################################### success: 27 execution time: 1.82s ################################################################################
Case 3 (rudder agent run -r)
root@server:/var/rudder/configuration-repository# rudder agent run -r R: @@Common@@log_info@@hasPolicyServer-root@@common-root@@3@@common@@StartRun@@2016-01-15 13:39:49+00:00##root@#Start execution with config [-1059466650] Rudder agent 3.2.0~rc3~git201601150159-wheezy0 (CFEngine Core 3.7.1) Node uuid: root Start execution with config [-1059466650] R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@3@@Update@@None@@2016-01-15 13:39:49+00:00##root@#Rudder ncf instance already up to date on this root server. No action required. R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@3@@Security parameters@@None@@2016-01-15 13:39:49+00:00##root@#The internal environment security is acceptable R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@3@@Red Button@@None@@2016-01-15 13:39:49+00:00##root@#Red Button is not in effect, continuing as normal... R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@3@@Process checking@@None@@2016-01-15 13:39:49+00:00##root@#There is an acceptable number of CFEngine processes running on the machine R: @@Common@@log_info@@hasPolicyServer-root@@common-root@@3@@Log system for reports@@None@@2016-01-15 13:39:49+00:00##root@#Detected running syslog as rsyslog R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@3@@Log system for reports@@None@@2016-01-15 13:39:49+00:00##root@#Logging system for report centralization is already correctly configured R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@3@@CRON Daemon@@None@@2016-01-15 13:39:49+00:00##root@#Cron daemon status was correct R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@3@@Binaries update@@None@@2016-01-15 13:39:49+00:00##root@#The CFengine binaries in /var/rudder/cfengine-community/bin are up to date R: @@DistributePolicy@@result_success@@root-DP@@root-distributePolicy@@3@@Configure ncf@@None@@2016-01-15 13:39:49+00:00##root@#Configure ncf was correct R: @@DistributePolicy@@result_success@@root-DP@@root-distributePolicy@@3@@Propagate promises@@None@@2016-01-15 13:39:49+00:00##root@#All files have been propagated R: @@DistributePolicy@@result_success@@root-DP@@root-distributePolicy@@3@@Send inventories to CMDB@@None@@2016-01-15 13:39:49+00:00##root@#No inventory to send R: @@Inventory@@log_info@@inventory-all@@inventory-all@@3@@inventory@@None@@2016-01-15 13:39:49+00:00##root@#An inventory was already sent less than 8 hours ago R: @@Inventory@@result_success@@inventory-all@@inventory-all@@3@@inventory@@None@@2016-01-15 13:39:49+00:00##root@#Next inventory scheduled between 00:00 and 06:00 R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check logrotate configuration@@None@@2016-01-15 13:39:49+00:00##root@#The logrotate configuration is correct R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check LDAP in rudder-webapp.properties@@None@@2016-01-15 13:39:49+00:00##root@#The Rudder Webapp configuration files are OK (checked LDAP password) R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check LDAP credentials@@None@@2016-01-15 13:39:49+00:00##root@#The OpenLDAP configuration file is OK (checked rootdn password) R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check SQL in rudder-webapp.properties@@None@@2016-01-15 13:39:49+00:00##root@#The Rudder Webapp configuration files are OK (checked SQL password) R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check SQL credentials@@None@@2016-01-15 13:39:49+00:00##root@#The Rudder PostgreSQL user account's password is correct and works R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check rudder-passwords.conf and pgpass files@@None@@2016-01-15 13:39:49+00:00##root@#The Rudder passwords file is present and secure R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check allowed networks configuration@@None@@2016-01-15 13:39:49+00:00##root@#The Rudder allowed networks configuration is OK R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check WebDAV credentials@@None@@2016-01-15 13:39:49+00:00##root@#The Rudder WebDAV user and password are OK R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check apache process@@None@@2016-01-15 13:39:49+00:00##root@#The apache process is already running R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check apache boot script@@None@@2016-01-15 13:39:49+00:00##root@#Check apache boot starting parameters was correct R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check jetty process@@None@@2016-01-15 13:39:49+00:00##root@#The jetty process is already running R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check configuration-repository folder@@None@@2016-01-15 13:39:49+00:00##root@#The /var/rudder/configuration-repository directory is present R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check configuration-repository GIT lock@@None@@2016-01-15 13:39:49+00:00##root@#The /var/rudder/configuration-repository GIT lock file is not present or not older than 5 minutes R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check rudder status@@None@@2016-01-15 13:39:49+00:00##root@#The http://localhost:8080/rudder/api/status web application is running R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check endpoint status@@None@@2016-01-15 13:39:49+00:00##root@#The http://localhost:8080/endpoint/api/status web application is running R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check slapd process@@None@@2016-01-15 13:39:49+00:00##root@#The slapd process is already running R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check PostgreSQL configuration@@None@@2016-01-15 13:39:49+00:00##root@#Their is no need of specific postgresql configuration on this system R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check postgresql process@@None@@2016-01-15 13:39:49+00:00##root@#The postgresql process is already running R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check postgresql boot script@@None@@2016-01-15 13:39:49+00:00##root@#Check postgresql boot starting parameters was correct R: @@server-roles@@result_na@@server-roles@@server-roles-directive@@3@@Send metrics to rudder-project@@None@@2016-01-15 13:39:49+00:00##root@#Sending metrics to rudder-project is not enabled. Skipping. R: @@Common@@log_info@@hasPolicyServer-root@@common-root@@3@@common@@EndRun@@2016-01-15 13:39:49+00:00##root@#End execution with config [-1059466650] ## Summary ##################################################################### success: 30 execution time: 1.71s ################################################################################
Case 4 (rudder agent run -R):
root@server:/var/rudder/configuration-repository# rudder agent run -R R: @@Common@@log_info@@hasPolicyServer-root@@common-root@@3@@common@@StartRun@@2016-01-15 13:39:59+00:00##root@#Start execution with config [-1059466650] R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@3@@Update@@None@@2016-01-15 13:39:59+00:00##root@#Rudder ncf instance already up to date on this root server. No action required. R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@3@@Security parameters@@None@@2016-01-15 13:39:59+00:00##root@#The internal environment security is acceptable R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@3@@Red Button@@None@@2016-01-15 13:39:59+00:00##root@#Red Button is not in effect, continuing as normal... R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@3@@Process checking@@None@@2016-01-15 13:39:59+00:00##root@#There is an acceptable number of CFEngine processes running on the machine R: @@Common@@log_info@@hasPolicyServer-root@@common-root@@3@@Log system for reports@@None@@2016-01-15 13:39:59+00:00##root@#Detected running syslog as rsyslog R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@3@@Log system for reports@@None@@2016-01-15 13:39:59+00:00##root@#Logging system for report centralization is already correctly configured R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@3@@CRON Daemon@@None@@2016-01-15 13:39:59+00:00##root@#Cron daemon status was correct R: @@Common@@result_success@@hasPolicyServer-root@@common-root@@3@@Binaries update@@None@@2016-01-15 13:39:59+00:00##root@#The CFengine binaries in /var/rudder/cfengine-community/bin are up to date R: @@DistributePolicy@@result_success@@root-DP@@root-distributePolicy@@3@@Configure ncf@@None@@2016-01-15 13:39:59+00:00##root@#Configure ncf was correct R: @@DistributePolicy@@result_success@@root-DP@@root-distributePolicy@@3@@Propagate promises@@None@@2016-01-15 13:39:59+00:00##root@#All files have been propagated R: @@DistributePolicy@@result_success@@root-DP@@root-distributePolicy@@3@@Send inventories to CMDB@@None@@2016-01-15 13:39:59+00:00##root@#No inventory to send R: @@Inventory@@log_info@@inventory-all@@inventory-all@@3@@inventory@@None@@2016-01-15 13:39:59+00:00##root@#An inventory was already sent less than 8 hours ago R: @@Inventory@@result_success@@inventory-all@@inventory-all@@3@@inventory@@None@@2016-01-15 13:39:59+00:00##root@#Next inventory scheduled between 00:00 and 06:00 R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check logrotate configuration@@None@@2016-01-15 13:39:59+00:00##root@#The logrotate configuration is correct R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check LDAP in rudder-webapp.properties@@None@@2016-01-15 13:39:59+00:00##root@#The Rudder Webapp configuration files are OK (checked LDAP password) R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check LDAP credentials@@None@@2016-01-15 13:39:59+00:00##root@#The OpenLDAP configuration file is OK (checked rootdn password) R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check SQL in rudder-webapp.properties@@None@@2016-01-15 13:39:59+00:00##root@#The Rudder Webapp configuration files are OK (checked SQL password) R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check SQL credentials@@None@@2016-01-15 13:39:59+00:00##root@#The Rudder PostgreSQL user account's password is correct and works R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check rudder-passwords.conf and pgpass files@@None@@2016-01-15 13:39:59+00:00##root@#The Rudder passwords file is present and secure R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check allowed networks configuration@@None@@2016-01-15 13:39:59+00:00##root@#The Rudder allowed networks configuration is OK R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check WebDAV credentials@@None@@2016-01-15 13:39:59+00:00##root@#The Rudder WebDAV user and password are OK R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check apache process@@None@@2016-01-15 13:39:59+00:00##root@#The apache process is already running R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check apache boot script@@None@@2016-01-15 13:39:59+00:00##root@#Check apache boot starting parameters was correct R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check jetty process@@None@@2016-01-15 13:39:59+00:00##root@#The jetty process is already running R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check configuration-repository folder@@None@@2016-01-15 13:39:59+00:00##root@#The /var/rudder/configuration-repository directory is present R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check configuration-repository GIT lock@@None@@2016-01-15 13:39:59+00:00##root@#The /var/rudder/configuration-repository GIT lock file is not present or not older than 5 minutes R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check rudder status@@None@@2016-01-15 13:39:59+00:00##root@#The http://localhost:8080/rudder/api/status web application is running R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check endpoint status@@None@@2016-01-15 13:39:59+00:00##root@#The http://localhost:8080/endpoint/api/status web application is running R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check slapd process@@None@@2016-01-15 13:39:59+00:00##root@#The slapd process is already running R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check PostgreSQL configuration@@None@@2016-01-15 13:39:59+00:00##root@#Their is no need of specific postgresql configuration on this system R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check postgresql process@@None@@2016-01-15 13:39:59+00:00##root@#The postgresql process is already running R: @@server-roles@@result_success@@server-roles@@server-roles-directive@@3@@Check postgresql boot script@@None@@2016-01-15 13:39:59+00:00##root@#Check postgresql boot starting parameters was correct R: @@server-roles@@result_na@@server-roles@@server-roles-directive@@3@@Send metrics to rudder-project@@None@@2016-01-15 13:39:59+00:00##root@#Sending metrics to rudder-project is not enabled. Skipping. R: @@Common@@log_info@@hasPolicyServer-root@@common-root@@3@@common@@EndRun@@2016-01-15 13:39:59+00:00##root@#End execution with config [-1059466650]
Updated by Alexis Mousset almost 9 years ago
- Status changed from New to In progress
The
error Common Update Cannot update Rudder tools last updated file success Common Update Rudder ncf instance already up to date on this root server. No action required.
looks like a bug in the technique, opening another ticket.
For the -i problem, it seems messages following "rudder info: " are not parsed, I'm investigating.
Updated by Alexis Mousset almost 9 years ago
- Target version changed from 3.0.13 to 3.2.0
The problem is linked to changes in log display in 3.7. The color reset happens after the line break, which breaks parsing of Rudder reports.
Updated by Alexis Mousset almost 9 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-agent/pull/44
Updated by Alexis Mousset almost 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-agent|ba1c4e8a8175eda80ac496b47b2fbde780ae6623.
Updated by Vincent MEMBRÉ almost 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.2.0 which were released today.