clusterName shows unnamedcluster in Resource properties of Linux® OS plug-in

Troubleshoot the issue that clusterName shows unnamedcluster in Resource properties of Linux® OS plug-in.

Problem

After you install Monitoring DataProvider Management, Linux® OS plug-in is automatically enabled. In the IBM Cloud Pak for Multicloud Management console, click Monitor health > Infrastructure monitoring, and then click Linux Systems. Click one worker node of your managed cluster. It is observed that clusterName shows unnamedcluster in Resource properties section.

Cause

The k8sdc dependent resource is created after the creation of UA daemonset.

Resolving the problem

1. On your managed cluster, do one of the following options.
   • Option 1: Manually delete UA pods one by one.
   • Option 2: Modify Linux® OS plug-in CR to make sure that daemonset restarts automatically.
     a. Run the following command to edit CR:

     kubectl edit ua ua-linuxos -n cp4mcm-cloud-native-monitoring
     

     b. Set enabled to false, and then save the CR.

     enabled: false
     

     c. Edit the CR again to set enabled to true, and then save it.

     enabled: true
     

2. You can see that ua-cloud-monitoring pods are restarted in cp4mcm-cloud-native-monitoring namespace on your managed cluster.

3. Verify that clusterName shows correct value in the console.