Why Did the Component Controller Failed to Be Installed?

Possible Causes

The possible causes are as follows:

• The network between the ECS where you want to install component controller isap-agent and the OBS bucket storing the agent is disconnected.
• The disk space of the ECS server is insufficient.
• Failed to obtain the IAM token.
• Failed to verify the workspace ID.
• The component controller isap-agent has been installed. The system attempts to install it again.

Locating the Cause and Fixing the Failure

• The network between the ECS where you want to install component controller isap-agent and the OBS bucket storing the agent is disconnected.
  Figure 1 Disconnected network between the server and OBS
  

  Solution

  • (Optional) Method 1: Connect the ECS to OBS.
  • (Optional) Method 2: Manually download the installation script and installation package to the local PC, and upload the installation package to the /opt/cloud directory on the server.
    1. Log in to the OBS management console.
    2. In the navigation pane on the left, choose Buckets. On the displayed page, click the name of the target bucket.
    3. On the displayed details page, download the installation script and installation package.
    4. Use a remote management tool, such as SecureFX or WinSCP, to log in to the server.
    5. Upload the installation package to the /opt/cloud directory on the server.
• The disk space of the ECS is insufficient.
  Figure 2 Insufficient disk space
  

  Solution

  Clear the disk to reserve sufficient space.

• Failed to obtain the IAM token.
  • Symptoms

    If information shown in the following figure is displayed in the log, the call to obtain IAM token failed.

    Figure 3 IAM token failure
    
  • Troubleshooting and Solution
    1. Check whether the IAM account or username in the command is correct.
       Figure 4 Username and password of an IAM user
       
       • If any of them or both of them are incorrect, run the installation command with correct information again.
       • If they are correct, go to 2.
    2. Run the vim /etc/salt/iam_token.txt command to check whether the /etc/salt/iam_token.txt file exists.
       • If the information shown in the following figure is displayed, the directory exists. Go to 3.
         Figure 5 Checking files
         
       • If a message is displayed indicating that the file does not exist, contact technical support.
    3. Run the ping command to check whether the server is reachable. If it is unreachable, enable the communication.
       Figure 6 Checking the network
       
• Failed to verify workspace ID.
  • Symptoms
    If the information shown in the following figure is displayed, the Workspace ID verification fails.

    Figure 7 Workspace ID verification failure
    
  • Solution
    1. Log in to the SecMaster management console.
    2. In the navigation pane on the left, choose Workspaces. In the workspace list, click the name of the target workspace.
    3. In the navigation pane on the left, choose Settings > Components. On the displayed page, click the target node.
    4. Check workspace ID and project ID in the command output.
       Figure 8 Parameters on the console
       
    5. Check whether the workspace ID and project ID in the command are the same as those in the file in 4.
       Figure 9 Parameter information in the command
       
    6. Use the correct workspace ID and project ID to run the command again.
• The component controller isap-agent has been installed. The system attempts to install it again.
  • Symptoms
    If the information shown in the following figure is displayed, the Agent has been installed.

    Figure 10 Agent installed already
    
  • Solution
    1. (Optional) Method 1: Logging out the node on the management console.
       1. Log in to the SecMaster management console.
       2. In the navigation pane on the left, choose Workspaces. In the workspace list, click the name of the target workspace.
       3. In the navigation pane on the left, choose Settings > Components. On the displayed Nodes tab, locate the row that contains the target node and click Deregister in the Operation column.
       4. In the displayed dialog box, click OK.
    2. (Optional) Method 2: Run a script command to uninstall component controller isap-agent.
       1. Use a remote management tool, such as SecureFX or WinSCP, to log in to the server.
       2. Run the sh /opt/cloud/agent_controller_euler.sh uninstall command to uninstall the component controller.
    3. Check whether the uninstallation is complete.
       1. Use a remote management tool, such as SecureFX or WinSCP, to log in to the server.
       2. (Optional) Method 1: Run the ls -a /opt/cloud/ command to view the files in the /opt/cloud directory. If the information shown in the following figure is displayed (including only the script file), the uninstallation is complete.
          Figure 11 Script file
          
       3. (Optional) Method 2: Run the salt-minion --version command. If the following information is displayed, the uninstallation is complete.
          Figure 12 Checking isap-agent details
          
    

    It takes some time to deregister a node. Do not install the Agent until you confirm that the node has been deregistered.