Bug #3747
closed
The script of initialization rudder-init.sh display an error message if called with arguments
Added by Nicolas PERRON almost 11 years ago.
Updated about 9 years ago.
Description
The rudder-init.sh script can be called with argument if, for example, we have to automate the installation of Rudder server. Nevertheless, an error message is displayed during its execution:
root@server:~# /tmp/rudder-init.sh server.rudder.local no yes yes 192.168.42.0/24
Hostname: server.rudder.local
Allowed networks: 192.168.42.0/24
Add sample data? no
Reinitialize LDAP database? yes
/tmp/rudder-init.sh: line 170: [: -ne: unary operator expected
Hit any key to continue....
- Status changed from New to Pending technical review
- Assignee changed from Nicolas PERRON to Jonathan CLARKE
- % Done changed from 0 to 100
- Status changed from Pending technical review to Pending release
Applied in changeset commit:e789ca02b2fd555cd9ce96e0cbcbe0abcb820a3f.
Applied in changeset commit:17f078b9b8f184271b2e4dbd758f6cc5a25cc9fb.
- Status changed from Pending release to Pending technical review
The PR was on master, and I merged it. We need to put this on 2.4 branch though.
- Status changed from Pending technical review to Pending release
Applied in changeset commit:bdf791cd577cb4df263f80f7d7afad678afce79b.
Applied in changeset commit:c817eb45443bd90c13bf52ed32deb435920790bf.
- Pull Request set to https://github.com/Normation/rudder-packages/pull/83
- Subject changed from the script of initialization rudder-init.sh display an error message if it is called with arguments to The script of initialization rudder-init.sh display an error message if called with arguments
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.4.7, which was released today.
Check out:
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF
Updated by Nicolas PERRON 
Updated by 
Updated by