[ https://issues.apache.org/jira/browse/CLOUDSTACK-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14215910#comment-14215910 ]
ASF subversion and git services commented on CLOUDSTACK-7752: ------------------------------------------------------------- Commit ae199b6ce7634ef702243c20800937c8a3ab4b14 in cloudstack's branch refs/heads/4.5 from [~anshulg] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ae199b6 ] CLOUDSTACK-7703, CLOUDSTACK-7752: Fixed deployment planner stuck in infinite loop. If we create VM with shared service offering and attach disk with local disk offering, and one of storage pool is full(cannot be allocated) and other is not full then we are not putting the cluster in avoid list which is causing this infinite loop. Fixed by putting the cluster in avoid list even if one of the storage pool is full(cannot be allocated) > Management Server goes in infinite loop while creating a vm with tagged local > data disk when the pool is not tagged > ------------------------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-7752 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7752 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Reporter: Anshul Gangwar > Assignee: Anshul Gangwar > Priority: Critical > > Steps to reproduce: > Setup must have a single cluster with both local and shared storage. > 1) Create a local disk offering and tag it T1 > 2) Deploy vm with shared root disk and local data disk > Management server goes in an infinite loop. The vm is never started/expunged. > Also this causes vmops.log size to go very high. -- This message was sent by Atlassian JIRA (v6.3.4#6332)