Actions
Bug #11996
closedBroken reporting on Rudder 4.3
Status:
Rejected
Priority:
N/A
Assignee:
Category:
System techniques
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
68
Name check:
Fix check:
Regression:
Description
E| error ${t_name} ${c_name} ${c_key} Presence of package curl in any version could not be repaired E| error Inventory inventory Installing 'curl' failed. Inventory registration will fail if curl is unavailable E| compliant Inventory inventory Next inventory scheduled between 00:00 and 06:00 E| compliant server-roles Check logrotate configur| The logrotate configuration is correct E| compliant server-roles Check LDAP in rudder-web| Web interface configuration files are correct (checked LDAP password) E| compliant server-roles Check LDAP credentials OpenLDAP configuration file is correct (checked rootdn password) E| compliant server-roles Check rudder-passwords.c| Rudder passwords file is present and secure E| compliant server-roles Check SQL in rudder-weba| Web interface configuration files are OK (checked SQL password) E| compliant server-roles Check SQL credentials PostgreSQL user account's password is correct and works E| compliant server-roles Check allowed networks c| Allowed networks configuration is correct E| compliant server-roles Check WebDAV credentials Apache WebDAV user and password are OK E| compliant ${t_name} ${c_name} ${c_key} Check if the service apache2 is started using ps was correct E| compliant ${t_name} ${c_name} ${c_key} Ensure that service apache2 is running was correct E| compliant server-roles Check apache process Check apache process running was correct E| compliant ${t_name} ${c_name} ${c_key} Check if service apache2 is started at boot was correct E| compliant ${t_name} ${c_name} ${c_key} Ensure service apache2 is started at boot was correct E| compliant server-roles Check apache boot script Check apache boot starting parameters was correct E| error ${t_name} ${c_name} ${c_key} Check if the service .*java.*/opt/rudder/jetty7/start.jar is started using ps could not be repaired E| repaired ${t_name} ${c_name} ${c_key} Run action start on service rudder-jetty was repaired E| repaired ${t_name} ${c_name} ${c_key} Start service rudder-jetty was repaired E| repaired ${t_name} ${c_name} ${c_key} Ensure that service rudder-jetty is running was repaired E| repaired server-roles Check jetty process Check jetty process running was repaired E| compliant server-roles Check configuration-repo| The /var/rudder/configuration-repository directory is present E| compliant server-roles Check configuration-repo| The /var/rudder/configuration-repository git lock file is not present or not older than 5 minutes E| compliant server-roles Check rudder status The http://localhost:8080/rudder/api/status web interface is running E| compliant server-roles Check endpoint status The http://localhost:8080/endpoint/api/status web interface is running E| compliant ${t_name} ${c_name} ${c_key} Check if the service /opt/rudder/libexec/slapd is started using ps was correct E| compliant ${t_name} ${c_name} ${c_key} Ensure that service rudder-slapd is running was correct E| compliant server-roles Check slapd process Check slapd process running was correct E| compliant server-roles Check PostgreSQL configu| There is no need of specific PostgreSQL configuration on this system E| compliant ${t_name} ${c_name} ${c_key} Check if the service postgres:.* writer process is started using ps was correct E| compliant ${t_name} ${c_name} ${c_key} Ensure that service postgresql is running was correct E| compliant server-roles Check postgresql process Check postgresql process running was correct E| compliant ${t_name} ${c_name} ${c_key} Check if service postgresql is started at boot was correct E| compliant ${t_name} ${c_name} ${c_key} Ensure service postgresql is started at boot was correct
Actions