Bug #3602
closed
With RPM, if we uninstall rudder-agent and reinstall it, the file /opt/rudder/etc/uuid.hive will be replaced by another one
Added by Nicolas PERRON over 11 years ago.
Updated over 9 years ago.
Description
On SLES, by uninstalling rudder-agent and reinstalling it, the file /opt/rudder/etc/uuid.hive is renamed /opt/rudder/etc/uuid.hive.save and a new /opt/rudder/etc/uuid.hive is generated.
It should not happen since this file is unique to the machine.
- Status changed from New to Discussion
- Assignee set to Jonathan CLARKE
I don't know how to deal with that. With #3634, it will be impossible to keep the previous UUID. What's your opinion Jon ?
- Assignee changed from Jonathan CLARKE to Nicolas PERRON
Actually, I'm not sure if I agree with the original bug report. Why should the UUID not be changed? If you remove the rudder-agent, it seems to me that you want to get rid of Rudder management there. So if you reinstall it, I think it's OK to consider this, by default, as a new machine.
We could add something to enable the user to manually restore the previous UUID, maybe.
What do you think? If you agree, please reject the bug.
- Status changed from Discussion to Rejected
Jonathan CLARKE wrote:
Actually, I'm not sure if I agree with the original bug report. Why should the UUID not be changed? If you remove the rudder-agent, it seems to me that you want to get rid of Rudder management there. So if you reinstall it, I think it's OK to consider this, by default, as a new machine.
We could add something to enable the user to manually restore the previous UUID, maybe.
What do you think? If you agree, please reject the bug.
The only reason I could see is that it could prevent from having duplicate node caused by the same node having different UUID.
In early versions of Rudder (2.3) the duplication of node could be made but since Rudder 2.4 this is no more possible. I reject this bug.
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF