User story #3924
closedAdd node with same IP of another node: error message should explain that we have to remove it from authorized network
Description
All my nodes have two network cards: "Eth0" and a "tun".
To join the root server, it's on the network of the tun card.
All the nodes have a different ip on the tun card,
but on the eth card, sometimes there are the same IP.
So when I try to accept a node, I have this error : Error when trying to execute pre-accepting for phase accept_new_server:check_hostname_unicity. Stop. <- There is already a node with IP '192.168.1.100' in database. You can not add it again.
It's on the 2.6.5
What do you think?
Updated by François ARMAND about 11 years ago
Hello,
That seems to be the same kind of bug as in http://www.rudder-project.org/redmine/issues/3625
The reason why we don't accept node with the same IP on authorized networks is that CFengine need to have uniqu IP to be able to talk with nodes.
So, given your configuration, I suspect that you use IP from "tun" interfaces to communicate between nodes and Rudder? If so, could you remove the 192.169.* network from authorized network (in the admin tab) ?
Thanks
Updated by Clément Defourneaux about 11 years ago
Hi, Thanks for your answer.
My problems look like in deed of [[http://www.rudder-project.org/redmine/issues/3625]] .
So I have tried to remove the 192.168.1.0/24 but when I submit, I have an error on the others networks " Bad format for given network".
I tried your solution :
I have a very hacky solution: with the LDAP browser, go to "Pending Inventories -> Nodes", and for each node, remove the faulty "ipHostNumber" value (the local one). That will allows to accept the nodes. Then, on the next inventories, the IP will be restaured (but as the nodes are already accepted, that won't matter).
It's not working but I think I don't modify the good file
Thanks for your help
Updated by François ARMAND about 11 years ago
- Status changed from New to Discussion
What are the other networks leading to "bad format"?
They should not lead to "bad net format", and perhaps there is an other bug here.
Updated by Clément Defourneaux about 11 years ago
Currently, I have 3 allowed network :
192.168.1.0/24
10.31.0.0/24
10.31.1.0/24
All my nodes are on the 10.31.0.0/24 and 10.31.1.0/24 with unique IP for each node.(On the network 10.31.1.0 or on the 10.31.0.0)
I can't modify the allowed network...
Do you have any idea ?
Updated by François ARMAND about 11 years ago
There is no reason these network should not be accepted (and testing on our labs server does not lead to error).
Oh, it seems that the test for validating network is space-sensisitive, so for example " 192.168.0.0 / 24 " will lead to bad format, and "192.168.0.0/24" is OK.
Else, could you try to see in the webapp log if there is some error message when you try to save the allowed networks?
Updated by Clément Defourneaux about 11 years ago
It's works !
The problem is on the adminsitration page, I didn't notice that in the texte area where there are the allowed network, there is a space at the first position.
It was " 10.31.1.0/24" and " 10.31.0.0/24" but the first text area was ok : "192.168.1.0/24"
After, correction on the text area, it's ok !
So I can delete the first network and accept my nodes !
Thank a lot for your help! Rudder is great !
Very good program!
Thanks !
Updated by François ARMAND about 11 years ago
Cool, so I will rename that ticket in "better error message for node acceptation when ip duplication", and open an other to make IP checking space-insensitive.
Updated by François ARMAND about 11 years ago
- Subject changed from Add node with same IP of another node to Add node with same IP of another node: error message should explain that we have to remove it from authorized network
Updated by Jonathan CLARKE about 11 years ago
- Category set to Web - Nodes & inventories
Updated by Benoît PECCATTE over 7 years ago
- Tracker changed from Bug to User story
- Status changed from Discussion to New
Updated by Benoît PECCATTE almost 7 years ago
- Target version set to Ideas (not version specific)
Updated by François ARMAND 7 months ago
- Status changed from New to Resolved
- Regression set to No
This was changed and rewroten since that time. Closing, but please open a new ticket if needed.