Actions
Bug #23166
closedInstallation of Rudder 8.0-nightly fails on AlmaLinux 9
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
First impressions of Rudder
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
during install, I have in stdout the following errors
oracle9_server: Installing : postgresql-13.11-1.el9_2.x86_64 17/80 oracle9_server: Running scriptlet: httpd-filesystem-2.4.53-11.el9_2.5.noarch 18/80 oracle9_server: useradd warning: apache's uid 48 outside of the SYS_UID_MIN 201 and SYS_UID_MAX 999 range. oracle9_server: oracle9_server: Installing : httpd-filesystem-2.4.53-11.el9_2.5.noarch 18/80 oracle9_server: Installing : python3-libsemanage-3.5-1.el9.x86_64 19/80 oracle9_server: Installing : python3-distro-1.5.0-7.el9.noarch 20/80 oracle9_server: Installing : python3-setools-4.4.1-1.el9.x86_64 21/80
oracle9_server: Installing : policycoreutils-python-utils-3.5-1.el9.noarch 64/80 oracle9_server: Installing : alsa-lib-1.2.8-3.el9.x86_64 65/80 oracle9_server: uavc: op=load_policy lsm=selinux seqno=5 res=1uavc: op=load_policy lsm=selinux seqno=6 res=1Error in POSTTRANS scriptlet in rpm package rudder-server oracle9_server: Installing : java-17-openjdk-headless-1:17.0.8.0.7-2.el9.x86_64 66/80 oracle9_server: Running scriptlet: java-17-openjdk-headless-1:17.0.8.0.7-2.el9.x86_64 66/80 oracle9_server: Installing : almalinux-logos-httpd-90.5.1-1.1.el9.noarch 67/80 oracle9_server: Installing : httpd-2.4.53-11.el9_2.5.x86_64 68/80 oracle9_server: Running scriptlet: httpd-2.4.53-11.el9_2.5.x86_64 68/80 oracle9_server: Installing : rudder-relay-8.0.0.alpha2.git202307300211-1.EL.9.x 69/80 oracle9_server: Running scriptlet: rudder-relay-8.0.0.alpha2.git202307300211-1.EL.9.x 69/80 oracle9_server: Running scriptlet: rudder-server-8.0.0.alpha2.git202307300211-1.EL.9. 70/80 oracle9_server: Installing : rudder-server-8.0.0.alpha2.git202307300211-1.EL.9. 70/80 oracle9_server: Running scriptlet: rudder-server-8.0.0.alpha2.git202307300211-1.EL.9. 70/80 oracle9_server: Job for rudder-slapd.service failed because the control process exited with error code. oracle9_server: See "systemctl status rudder-slapd.service" and "journalctl -xeu rudder-slapd.service" for details. oracle9_server: Already on 'master' oracle9_server: A dependency job for rudder-jetty.service failed. See 'journalctl -xe' for details. oracle9_server: oracle9_server: Upgrading : audit-3.0.7-103.el9.x86_64 71/80
oracle9_server: Running scriptlet: copy-jdk-configs-4.0-3.el9.noarch 80/80 oracle9_server: Running scriptlet: nss-3.79.0-18.el9_1.x86_64 80/80 oracle9_server: Running scriptlet: java-17-openjdk-headless-1:17.0.8.0.7-2.el9.x86_64 80/80 oracle9_server: Running scriptlet: httpd-2.4.53-11.el9_2.5.x86_64 80/80 oracle9_server: Running scriptlet: rudder-server-8.0.0.alpha2.git202307300211-1.EL.9. 80/80 oracle9_server: Job for rudder-slapd.service failed because the control process exited with error code. oracle9_server: See "systemctl status rudder-slapd.service" and "journalctl -xeu rudder-slapd.service" for details. oracle9_server: warning: %posttrans(rudder-server-0:8.0.0.alpha2.git202307300211-1.EL.9.x86_64) scriptlet failed, exit status 1 oracle9_server: oracle9_server: Running scriptlet: lua-libs-5.4.2-4.el9.x86_64 80/80 oracle9_server: Verifying : almalinux-logos-httpd-90.5.1-1.1.el9.noarch 1/80 oracle9_server: Verifying : alsa-lib-1.2.8-3.el9.x86_64 2/80 oracle9_server: Verifying : apr-1.7.0-11.el9.x86_64 3/80 oracle9_server: Verifying : apr-util-1.6.1-20.el9_2.1.x86_64 4/80
oracle9_server: lua-posix-35.0-8.el9.x86_64 oracle9_server: mailcap-2.1.49-5.el9.noarch oracle9_server: mod_http2-1.15.19-4.el9_2.4.x86_64 oracle9_server: A dependency job for rudder-jetty.service failed. See 'journalctl -xe' for details. oracle9_server: mod_lua-2.4.53-11.el9_2.5.x86_64 oracle9_server: mod_ssl-1:2.4.53-11.el9_2.5.x86_64 oracle9_server: net-tools-2.0-0.62.20160912git.el9.x86_64
Install logs say
Mon Jul 31 09:33:58 UTC 2023 - Starting rudder-server post installation script Mon Jul 31 09:33:58 UTC 2023 - Starting rudder-reports post installation step Found postgres service name: postgresql Initializing postgresql db (initdb) WARNING: using obsoleted argument syntax, try --help WARNING: arguments transformed to: postgresql-setup --initdb --unit postgresql * Initializing database in '/var/lib/pgsql/data' * Initialized, logs are in /var/lib/pgsql/initdb_postgresql.log Created symlink /etc/systemd/system/multi-user.target.wants/postgresql.service → /usr/lib/systemd/system/postgresql.service. Mon Jul 31 09:34:02 UTC 2023 - Ending rudder-reports post installation step Mon Jul 31 09:34:02 UTC 2023 - Starting rudder-webapp post installation step Creating rudder users Stopping apache before running upgrade scripts Managing services Created symlink /etc/systemd/system/multi-user.target.wants/rudder-jetty.service → /usr/lib/systemd/system/rudder-jetty.service. Created symlink /etc/systemd/system/rudder-server.service.requires/rudder-jetty.service → /usr/lib/systemd/system/rudder-jetty.service. Created symlink /etc/systemd/system/multi-user.target.wants/rudder-slapd.service → /usr/lib/systemd/system/rudder-slapd.service. Created symlink /etc/systemd/system/rudder-server.service.requires/rudder-slapd.service → /usr/lib/systemd/system/rudder-slapd.service. Created symlink /etc/systemd/system/multi-user.target.wants/rudder-server.service → /usr/lib/systemd/system/rudder-server.service. Initializing filesystem Initializing git Initialized empty shared Git repository in /var/rudder/configuration-repository/.git/ Upgrading techniques Correctly set option autoupdate-technique-library to value true Configuring LDAP SUMMARY OF OPTIONS: Allowed networks: 192.168.48.0/24 10.0.2.15/32 192.168.48.2/32 Force LDAP reset: no Initializing LDAP database...ERROR: Execution failed! Aborting. An error occurred. Please check /var/log/rudder/install/rudder-init-20230731093407.log for details. Running upgrade script INFO: Checking if rudder-web.properties database access credentials are all right... LDAP OK, SQL Credentials updated Overriding existing techniques INFO: Correcting permissions on /var/rudder/configuration-repository... Done On branch master nothing to commit, working tree clean Techniques have been updated, and update branch set to current state of the Techniques INFO: Upgrading PostgreSQL DB... OK INFO: Upgrading LDAP DB............ FAILED LDAP service verification failed after 10 tries. ERROR Plugins were not updated, because connection test is failing, please upgrade your plugins manually ERROR: The migration has failed in some steps. Check previous error messages. Please restart the failed service(s), and start the migration script again. (try service rudder-server restart) Once it is working, run: # /opt/rudder/bin/rudder-upgrade INFO: Correcting permissions on /var/rudder/configuration-repository... Done Running plugins upgrade scripts Restoring file ACLs INFO: Policies absent, restoring initial version, and updating ... error: Can't stat file '/var/rudder/configuration-repository/ncf' on 'localhost' in files.copy_from promise, it may be missing or access may not be authorized error: Errors encountered when actuating files promise '/var/rudder/ncf/local' error: Rudder agent policies could not be updated. ok: Rudder agent state has been reset. Done INFO: No disable file detected and no agent executor process either. Restarting agent service... Done INFO: Inventory older than 3 days, resending ...Rudder agent 8.0.0~alpha2~git202307300211 Node uuid: root error: Finished command related to promiser '/opt/rudder/bin/rudder-client -e /uuid -- --output "/var/rudder/cfengine-community/rudder-server-uuid.txt"' -- an error occurred, returned 7 M| State Technique Component Key Message E| error Inventory Inventory Could not retrieve the UUID of the policy server. Please check that the defined Policy Server exists, and that this Node IP address is in the Allowed Networks of its policy server. info Rudder agent was run on a subset of policies - not all policies were checked warning 1 reports were not parsable. Run with -i to see log messages. ## Summary ##################################################################### 1 components verified in 3 directives => 1 components in Enforce mode -> 1 error Execution time: 6.18s ################################################################################ Done FINISH: Rudder agent check ran properly, please look at messages above to see if there has been any error. Mon Jul 31 09:34:43 UTC 2023 - Ending rudder-webapp post installation step Mon Jul 31 09:34:43 UTC 2023 - Ending rudder-server post installation script
rudder-init log says
ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
Updated by Nicolas CHARLES over 1 year ago
- Target version changed from 8.0.0~beta1 to 7.2.10
Updated by Nicolas CHARLES over 1 year ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES over 1 year ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2792
Updated by Nicolas CHARLES over 1 year ago
- Target version changed from 7.2.10 to 8.0.0~beta1
Updated by Nicolas CHARLES over 1 year ago
- Status changed from Pending technical review to New
- Assignee deleted (
Alexis Mousset)
Updated by Nicolas CHARLES over 1 year ago
- Pull Request deleted (
https://github.com/Normation/rudder-packages/pull/2792)
Updated by Alexis Mousset over 1 year ago
- Status changed from New to Pending release
Updated by Vincent MEMBRÉ over 1 year ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.0.0~beta1 which was released today.
Actions