Project

General

Profile

Actions

Bug #12247

closed

rudder-init fails when rudder-server-roles.conf does not exist

Added by Janos Mattyasovszky about 6 years ago. Updated almost 6 years ago.

Status:
Released
Priority:
N/A
Category:
Packaging
Target version:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
User visibility:
First impressions of Rudder
Effort required:
Priority:
77
Name check:
Fix check:
Regression:

Description

With rudder-webapp-4.3.0.rc1-1.SLES.12.noarch after a vanilla installation on SLES12 SP3:

# /opt/rudder/bin/rudder-init

Welcome to the Rudder initialization utility

This utility configures a Rudder root server, and may be
called again if reconfiguration is required.

Enter network allowed to access server (i.e 192.168.0.0/24): 10.0.0.0/16
10.0.0.0/16
Network(s) added:
10.0.0.0/16
Add more networks? (yes/no) no
no

SUMMARY OF OPTIONS:

Allowed networks: 10.0.0.0/16

Hit any key to continue....
Configuring and installing initial Rudder policies...mv: cannot stat '/var/rudder/cfengine-community/inputs/rudder-server-roles.conf': No such file or directory
mv: cannot stat '/tmp/tmp.W9oWqfEYEo/rudder-server-roles.conf': No such file or directory
 Done.
Initializing LDAP database... done.

Updating Rudder password file with random passwords...  done.
Cleaning up temporary directories... done.
Restarting services...
[...]
Actions

Also available in: Atom PDF