mredaelli02 opened a new issue, #10070:
URL: https://github.com/apache/cloudstack/issues/10070

   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete 
the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   UI, HOST
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   
   ~~~
   4.19.1.3, 4.19.1.2
   ~~~
   Now I'm using 4.19.1.3 but I noticed the same problem on 4.19.1.2
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   advanced networking
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   ~~~
   Oracle Linux 8.8, Oracle Linux 8.10 on host set as ha_host
   ~~~
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   I have two different clusters:
   
   1.  In the first cluster, none of the hosts have tags configured, except for 
one host dedicated to HA with the `ha_host` tag. This host is completely unable 
to start or migrate VMs. 
   Example of nodes belonging to the first cluster (working one)
   ![Screenshot 2024-12-09 
152516](https://github.com/user-attachments/assets/95b8155a-25d1-4893-a51e-0c32d29eb93a)
   ![Screenshot 2024-12-09 
152449](https://github.com/user-attachments/assets/18e3abfe-8bad-4028-b5a0-5fa489b88c27)
   
   Retrieved information throgh cmk:
   ~~~
     "host": [
       {
         "hahost": true,
         "hostha": {
           "haenable": true,
           "haprovider": "kvmhaprovider",
           "hastate": "Ineligible"
         },
         "hosttags": "ha_host",
         "name": "cloud02"
       },
       {
         "hahost": false,
         "hostha": {
           "haenable": true,
           "haprovider": "kvmhaprovider",
           "hastate": "Ineligible"
         },
         "name": "cloud01"
       }
     ]
   ~~~
   
   2.  In the second cluster, all hosts have multiple tags configured. One of 
these hosts is dedicated to HA and like other host in the same cluster it has 
the same tags plus the `ha_host`, it should not be able to start or migrate 
VMs, but in this case i can work with this host like a normal one.
   Example of nodes belonging to the second cluster 
   ![Screenshot 2024-12-09 
151919](https://github.com/user-attachments/assets/a6a0dd17-a2f4-4ab9-aab9-87199d8cdd5a)
   ![Screenshot 2024-12-09 
151825](https://github.com/user-attachments/assets/6c15849f-96df-4a70-b2c4-18f1ff84b9ea)
   
   Retrieved information throgh cmk:
   ~~~
     "host": [
       {
         "hahost": false,
         "hostha": {
           "haenable": true,
           "haprovider": "kvmhaprovider",
           "hastate": "Ineligible"
         },
         "hosttags": "KVM,STORAGE1",
         "name": "cloud09"
       },
       {
         "hahost": true,
         "hostha": {
           "haenable": true,
           "haprovider": "kvmhaprovider",
           "hastate": "Ineligible"
         },
         "hosttags": "KVM,ha_host,STORAGE1",
         "name": "cloudha"
       }
     ]
   ~~~
   As you can see the host is correctly recognised as hahost.
   I noticed that the only difference is the multiple tag, this should be fixed 
by #4789. But apparently won't work for me.
   Any possible solution?
   
   ##### STEPS TO REPRODUCE
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal 
test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   Set Global Settings the host.ha=ha_host
   Restart cloudstack management service
   Set different tags to hosts
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   Example on first cluster
   ~~~
   <img width="448" alt="Screenshot 2024-12-09 152837" 
src="https://github.com/user-attachments/assets/c055cbbd-8942-4acd-80d7-6026bee526b8";>
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   Second Cluster
   ~~~
   Host running on ha_host, this shouldn't happen
   <img width="447" alt="Screenshot 2024-12-09 153223" 
src="https://github.com/user-attachments/assets/493bfcc7-710f-4cfa-959f-adc1fb2f66f2";>
   <img width="521" alt="Screenshot 2024-12-09 153553" 
src="https://github.com/user-attachments/assets/a9ed2cb1-8d68-4864-9029-e05d455ff1bc";>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@cloudstack.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to