Actions
Bug #16318
closedAt install agents are not printing anymore the mandatory configuration to do
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
Before 6.0 we had this which was printed when no policy_server was given:
echo "********************************************************************************" - echo "rudder-agent has been installed (not started). This host can be a Rudder node." - echo "To get started, configure your Rudder server's hostname and launch the agent:" - echo "# echo 'rudder.server' > ${CFE_DIR}/policy_server.dat" - echo "# rudder agent start" - echo "This node will then appear in the Rudder web interface under 'Accept new nodes'." + echo "rudder-agent has been updated, but was not started as it is disabled." + echo "To enable and start Rudder agent:" + echo "# rudder agent enable -s" echo "********************************************************************************"
Now, the first part should be done by rudder agent check. BUT, we are putting "rudder" as policy server earlier in the script. So when the rudder agent check is run,
there is ALWAYS a policy server define and the message is never prompted.
Updated by Félix DALLIDET almost 5 years ago
- Status changed from New to In progress
- Assignee set to Félix DALLIDET
Updated by Félix DALLIDET almost 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Félix DALLIDET to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2152
Updated by Félix DALLIDET almost 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|46d1e3f4f4898cb439a2d3b93f29b32b383aeca5.
Updated by Alexis Mousset almost 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.0 which was released today.
Actions