Project

General

Profile

Actions
Copy link

Bug #7110

closed

If I have a Rudder server in 3.1, but the relay in 3.0, all nodes behind the relay can't fetch the uuid of the relay

Added by Nicolas CHARLES over 8 years ago. Updated about 8 years ago.

Status:
Rejected
Priority:
1
Assignee:
-
Category:
Server components
Target version:
3.1.1
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I upgraded my rudder serve to 3.1.1, but forgot to upgrade my relay
The nodes now fetch the uuid of the policy server on https, but the conf of the relay havent apperently been upgraded:

netstat -laputen
tcp        0      0 :::22                       :::*                        LISTEN      0          11086      1120/sshd           
tcp        0      0 ::1:25                      :::*                        LISTEN      0          11296      1198/master         
tcp        0      0 :::514                      :::*                        LISTEN      0          10507      951/rsyslogd        
tcp        0      0 :::37934                    :::*                        LISTEN      29         10714      998/rpc.statd       
tcp        0      0 :::111                      :::*                        LISTEN      0          10605      978/rpcbind         
tcp        0      0 :::80                       :::*                        LISTEN      0          11433      1209/httpd

On the node

/usr/bin/curl -k -1 -s -f --proxy '' -o "/var/rudder/cfengine-community/rudder-server-uuid.txt" https://relay1.rudder.local/uuid
echo $?
7

Is it mandatory to upgrade the relay ??

Actions
Copy link

Also available in: Atom PDF