staySober opened a new issue #5041:
URL: https://github.com/apache/cloudstack/issues/5041


   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and master 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 -->
    * Other
   
   ##### COMPONENT NAME
   ~~~
   UI
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on master 
branch.
   -->
   
   ~~~
   4.15.0
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   
   
   ##### OS / ENVIRONMENT
   <!--
   N/A
   -->
   
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   
   
   ##### STEPS TO REPRODUCE
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   I want to use Host HA, So I configure the tag `ha.tag=ha` and tagged the 
host Client1 with 'ha'. Then I restarted the cloudstack-management server. 
   But after I logged back in, I saw the client1 Host  label.hastate = 
'Ineligible' .
   and the Host HA is not working properly
   I am so confused that there is something wrong with my configuration, please 
help me
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   ```
   1. client1 Host Ha enable and label.hastate is displayed correctly 
   2.  Host HA can working correctly
   ```
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   
![image](https://user-images.githubusercontent.com/20500978/119757182-2997ea80-bed7-11eb-93da-2fbdf2b029e8.png)
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   
   ~~~
   


-- 
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to