Bug #9222
closed
Wrong detection of rudder init parameters
Added by Alexis Mousset about 8 years ago.
Updated about 8 years ago.
Category:
System integration
Description
On CentOS 7, allowed networks after a rudder-setup install are:
192.168.0.42/24
no
yes
yes
192.168.0.42/24
Which breaks things.
Looks like an error in detection of argument number (old/new syntax).
- Subject changed from The script to autodetect networks does not work correctly to Wrong detection of rudder init parameters
- Description updated (diff)
- Translation missing: en.field_tag_list set to Blocking 4.0
It looks like someone called the script with the old parameters, since we removed the old call convention in 4.0
Do you think it's too fast to change it in 4.0 ?
We should at least check that we only add valid IPs so that we don't break anything.
Well it was rudder-setup called by rtf that still uses the old paramaters ;) I don't think it is a problem to change this in 4.0 as installation procedure needs to be reviewed/changed anyway.
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-packages/pull/1097
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Target version changed from 4.0.0~rc2 to 318
- Target version changed from 318 to 4.0.0~rc2
- Target version changed from 4.0.0~rc2 to 4.0.0~rc1
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.0 which was released the 10th November 2016.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by