Bug #11630
closed
When installing a rudder root server (on debian), it asks to run rudder-node-to-relay
Added by Nicolas CHARLES about 7 years ago.
Updated almost 6 years ago.
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Description
When installing rudder-server-root-4.1.8.rc1.git201710190339-1.EL.7.noarch, I got the following output on centos
==> centos41_server: *****************************************************************************************
==> centos41_server: INFO: Now run on your root server:
==> centos41_server: INFO: '/opt/rudder/bin/rudder-node-to-relay c80e63e0-8808-4e52-b9f7-2a6ccc49b6aa
==> centos41_server: INFO: Please look at the documentation for details (Section 'Relay servers')
==> centos41_server: *******************************************************************i*********************
we should not ask user to run this command
Where did it get that UUID from ? :-)
- Target version changed from 4.1.8 to 4.1.9
- Severity changed from Trivial - no functional impact | cosmetic to Minor - inconvenience | misleading | easy workaround
- User visibility changed from First impressions of Rudder to Getting started - demo | first install | level 1 Techniques
- Priority changed from 77 to 50
- Target version changed from 4.1.9 to 4.1.10
- Target version changed from 4.1.10 to 4.1.11
- Priority changed from 50 to 48
- Target version changed from 4.1.11 to 4.1.12
- Priority changed from 48 to 47
- Target version changed from 4.1.12 to 4.1.13
- Priority changed from 47 to 46
- Target version changed from 4.1.13 to 411
- Target version changed from 411 to 4.1.13
- Target version changed from 4.1.13 to 4.1.14
- Priority changed from 46 to 44
- Target version changed from 4.1.14 to 4.1.15
- Effort required set to Medium
- Priority changed from 44 to 28
- Target version changed from 4.1.15 to 4.1.16
- Target version changed from 4.1.16 to 4.1.17
- Target version changed from 4.1.17 to 4.1.18
- Priority changed from 28 to 0
rudder-webapp depends on rudder-server-relay which depends on rudder-agent
Install are donr in reverse order :
- rudder-agent create an uuid since there is none
- rudder-relay runs and prints the message
- rudder-webapp set the uuid to root
So the solution is to create the uuid during preinst of rudder-webapp
- 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/1748
- Status changed from Pending technical review to Pending release
- Subject changed from When installing a rudder root server (on centos), it asks to run rudder-node-to-relay to When installing a rudder root server (on debian), it asks to run rudder-node-to-relay
- Status changed from Pending release to Released
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by