CCE Agent Versions

Check Items

Check whether cce-agent on the current node is of the latest version.

Solution

Scenario 1: The error message "you cce-agent no update, please restart it" is displayed.
cce-agent does not need to be updated but is not restarted. In this case, log in to the node and manually restart cce-agent.

Solution: Log in to the node and run the following command:
```
systemctl restart cce-agent
```
Perform the pre-upgrade check again.
Scenario 2: The error message "your cce-agent is not the latest version" is displayed.
cce-agent is not of the latest version, and the automatic update failed. This issue is typically caused by an invalid OBS path or the component version is outdated.

Solution
1. Log in to the affected node and run the following command to obtain a valid OBS address:
```
cat /home/paas/upgrade/agentConfig | python -m json.tool
```
2. Log in to a where the check failed, obtain the OBS address again by referring to the previous step, and check whether the OBS addresses are the same. If they are different, change the OBS address of the abnormal node to the correct address.
3. Run the following commands to download the latest binary file:
  - x86
```
curl -k "https://{OBS address you have obtained}/cluster-versions/base/cce-agent" > /tmp/cce-agent
```
  - Arm
```
curl -k "https://{OBS address you have obtained}/cluster-versions/base/cce-agent-arm" > /tmp/cce-agent-arm
```
4. Replace the original cce-agent binary file.
  - x86
```
mv -f /tmp/cce-agent /usr/local/bin/cce-agent
chmod 750 /usr/local/bin/cce-agent
chown root:root /usr/local/bin/cce-agent
```
  - Arm
```
mv -f /tmp/cce-agent-arm /usr/local/bin/cce-agent-arm
chmod 750 /usr/local/bin/cce-agent-arm
chown root:root /usr/local/bin/cce-agent-arm
```
5. Restart cce-agent.
```
systemctl restart cce-agent
```
  If you have any questions about the preceding operations, contact technical support.