havengit opened a new issue #5527:
URL: https://github.com/apache/cloudstack/issues/5527


   <!--
   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.
   -->
   ~~~
   affinity Groups
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   
   ~~~
   CloudStack 4.15.0.0
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   CloudStack 4.15.0.0
   host  OS version: Ubuntu 20.04
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   
   Start virtual machines in batches, anti affinity Groups not work sometimes
   
   ##### 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.
   -->
   It doesn't happen every time
   
   1.Two host in one cluster
   2.add three VM to a anti-affinity group
   3.VM in stopped state
   4.start vm with WEB UI, Check three VM to start
   5.Three VMs will start successful 
   
   logs :
             vm id : 158 159 160 
             host id:  3 9
   job-5595: 
   2021-09-29 09:35:14,379 DEBUG [o.a.c.a.HostAntiAffinityProcessor] 
(API-Job-Executor-31:ctx-ff549a9e job-5595 ctx-e1872415) (logid:ec8a48c2) 
Processing affinity group gumd-test for VM Id: 158
   2021-09-29 09:35:14,382 DEBUG [o.a.c.a.HostAntiAffinityProcessor] 
(API-Job-Executor-31:ctx-ff549a9e job-5595 ctx-e1872415) (logid:ec8a48c2) Added 
host 3 to avoid set, since VM 159 is present on the host, in Stopped state but 
has reserved capacity
   2021-09-29 09:35:14,383 DEBUG [o.a.c.a.HostAntiAffinityProcessor] 
(API-Job-Executor-31:ctx-ff549a9e job-5595 ctx-e1872415) (logid:ec8a48c2) Added 
host 9 to avoid set, since VM 160 is present on the host, in Stopped state but 
has reserved capacity
   
   job-5598
   2021-09-29 09:35:14,594 DEBUG [o.a.c.a.HostAntiAffinityProcessor] 
(API-Job-Executor-32:ctx-acdc74f8 job-5598 ctx-3ce8dd3b) (logid:1d2445d0) 
Processing affinity group gumd-test for VM Id: 159
   2021-09-29 09:35:14,597 DEBUG [o.a.c.a.HostAntiAffinityProcessor] 
(API-Job-Executor-32:ctx-acdc74f8 job-5598 ctx-3ce8dd3b) (logid:1d2445d0) Added 
host 9 to avoid set, since VM 158 is present on the host, in Stopped state but 
has reserved capacity
   2021-09-29 09:35:14,600 DEBUG [o.a.c.a.HostAntiAffinityProcessor] 
(API-Job-Executor-32:ctx-acdc74f8 job-5598 ctx-3ce8dd3b) (logid:1d2445d0) Added 
host 9 to avoid set, since VM 160 is present on the host, in Stopped state but 
has reserved capacity
   
   job-5592
   2021-09-29 09:35:14,498 DEBUG [o.a.c.a.HostAntiAffinityProcessor] 
(API-Job-Executor-30:ctx-307add2b job-5592 ctx-0802d14f) (logid:c430fdd5) 
Processing affinity group gumd-test for VM Id: 160
   2021-09-29 09:35:14,500 DEBUG [o.a.c.a.HostAntiAffinityProcessor] 
(API-Job-Executor-30:ctx-307add2b job-5592 ctx-0802d14f) (logid:c430fdd5) Added 
host 9 to avoid set, since VM 158 is present on the host, in Stopped state but 
has reserved capacity
   2021-09-29 09:35:14,502 DEBUG [o.a.c.a.HostAntiAffinityProcessor] 
(API-Job-Executor-30:ctx-307add2b job-5592 ctx-0802d14f) (logid:c430fdd5) Added 
host 3 to avoid set, since VM 159 is present on the host, in Stopped state but 
has reserved capacity
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   Two VMs start success , one VM start failed
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   Three VMs start success 
   ~~~
   


-- 
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: [email protected]

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


Reply via email to