[jira] [Commented] (CLOUDSTACK-5853) cannot deploy vm with differing service storage tag and data disk storage tag
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14216919#comment-14216919 ] ASF subversion and git services commented on CLOUDSTACK-5853: - Commit 968ca060eea66ba7fe1853c6685069fe8b63b8f2 in cloudstack's branch refs/heads/4.5 from [~prachidamle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=968ca06 ] CLOUDSTACK-5853 cannot deploy vm with differing service storage tag and data disk storage tag Changes: - Reverting Marcus's fix since this issue has already fixed by https://issues.apache.org/jira/browse/CLOUDSTACK-5426 cannot deploy vm with differing service storage tag and data disk storage tag - Key: CLOUDSTACK-5853 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5853 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0, 4.3.0, 4.4.0 Reporter: Marcus Sorensen Assignee: Prachi Damle Priority: Critical Fix For: 4.4.0, 4.5.0 Create two storage pools, one with storage tag X, one with storage tag Y. Create a service offering with storage tag X. Create a disk offering with storage tag Y. Attempt to deploy a virtual machine with a datadisk, using given offerings, it fails. Deployment planner keeps a global object 'avoid'. It loops through each volume to be created, asking storage allocators for matching pools, passing this avoid object. First disk matches a pool or pools, adds ALL other pools to avoid object, then deployment planner attaches matching pools to a list for that disk. Second disk matches a pool, adds all other pools to avoid object, then deployment planner says wait, matching pool is in avoid, can't use it. Oops. In fact, at this point ALL pools are in avoid (unless there are other pools that have both tags). Need to remove matching pool from the avoid set during each select phase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-5853) cannot deploy vm with differing service storage tag and data disk storage tag
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14211512#comment-14211512 ] Prachi Damle commented on CLOUDSTACK-5853: -- The commit has not yet been reverted. I will be reverting this change for 4.5, since this has been fixed the correct way via this: https://issues.apache.org/jira/browse/CLOUDSTACK-5426 cannot deploy vm with differing service storage tag and data disk storage tag - Key: CLOUDSTACK-5853 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5853 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0, 4.3.0, 4.4.0 Reporter: Marcus Sorensen Assignee: Marcus Sorensen Priority: Critical Fix For: 4.4.0, 4.5.0 Create two storage pools, one with storage tag X, one with storage tag Y. Create a service offering with storage tag X. Create a disk offering with storage tag Y. Attempt to deploy a virtual machine with a datadisk, using given offerings, it fails. Deployment planner keeps a global object 'avoid'. It loops through each volume to be created, asking storage allocators for matching pools, passing this avoid object. First disk matches a pool or pools, adds ALL other pools to avoid object, then deployment planner attaches matching pools to a list for that disk. Second disk matches a pool, adds all other pools to avoid object, then deployment planner says wait, matching pool is in avoid, can't use it. Oops. In fact, at this point ALL pools are in avoid (unless there are other pools that have both tags). Need to remove matching pool from the avoid set during each select phase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-5853) cannot deploy vm with differing service storage tag and data disk storage tag
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048057#comment-14048057 ] sebastien goasguen commented on CLOUDSTACK-5853: Can someone update this and close the ticket or not ? [~prachidamle] ? thx cannot deploy vm with differing service storage tag and data disk storage tag - Key: CLOUDSTACK-5853 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5853 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0, 4.3.0, 4.4.0 Reporter: Marcus Sorensen Assignee: Marcus Sorensen Priority: Critical Fix For: 4.4.0 Create two storage pools, one with storage tag X, one with storage tag Y. Create a service offering with storage tag X. Create a disk offering with storage tag Y. Attempt to deploy a virtual machine with a datadisk, using given offerings, it fails. Deployment planner keeps a global object 'avoid'. It loops through each volume to be created, asking storage allocators for matching pools, passing this avoid object. First disk matches a pool or pools, adds ALL other pools to avoid object, then deployment planner attaches matching pools to a list for that disk. Second disk matches a pool, adds all other pools to avoid object, then deployment planner says wait, matching pool is in avoid, can't use it. Oops. In fact, at this point ALL pools are in avoid (unless there are other pools that have both tags). Need to remove matching pool from the avoid set during each select phase. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5853) cannot deploy vm with differing service storage tag and data disk storage tag
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868060#comment-13868060 ] ASF subversion and git services commented on CLOUDSTACK-5853: - Commit e5fc9fdef9d66172b870cfabecccf3ca38207ed0 in branch refs/heads/4.2 from [~mlsorensen] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e5fc9fd ] CLOUDSTACK-5853 Create two storage pools, one with storage tag X, one with storage tag Y. Create a service offering with storage tag X. Create a disk offering with storage tag Y. Attempt to deploy a virtual machine with a datadisk, using given offerings, it fails. Deployment planner keeps a global object 'avoid'. It loops through each volume to be created, asking storage allocators for matching pools, passing this avoid object. First disk matches a pool or pools, adds ALL other pools to avoid object, then deployment planner attaches matching pools to a list for that disk. Second disk matches a pool, adds all other pools to avoid object, then deployment planner says wait, matching pool is in avoid, can't use it. Oops. In fact, at this point ALL pools are in avoid (unless there are other pools that have both tags). Need to remove matching pool from the avoid set during each select phase. cannot deploy vm with differing service storage tag and data disk storage tag - Key: CLOUDSTACK-5853 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5853 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0, 4.3.0, 4.4.0 Reporter: Marcus Sorensen Assignee: Marcus Sorensen Create two storage pools, one with storage tag X, one with storage tag Y. Create a service offering with storage tag X. Create a disk offering with storage tag Y. Attempt to deploy a virtual machine with a datadisk, using given offerings, it fails. Deployment planner keeps a global object 'avoid'. It loops through each volume to be created, asking storage allocators for matching pools, passing this avoid object. First disk matches a pool or pools, adds ALL other pools to avoid object, then deployment planner attaches matching pools to a list for that disk. Second disk matches a pool, adds all other pools to avoid object, then deployment planner says wait, matching pool is in avoid, can't use it. Oops. In fact, at this point ALL pools are in avoid (unless there are other pools that have both tags). Need to remove matching pool from the avoid set during each select phase. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5853) cannot deploy vm with differing service storage tag and data disk storage tag
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868097#comment-13868097 ] ASF subversion and git services commented on CLOUDSTACK-5853: - Commit a80debbddf5b33921cfba38bb9f02f4bab11d2f5 in branch refs/heads/4.3 from [~mlsorensen] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a80debb ] CLOUDSTACK-5853 Create two storage pools, one with storage tag X, one with storage tag Y. Create a service offering with storage tag X. Create a disk offering with storage tag Y. Attempt to deploy a virtual machine with a datadisk, using given offerings, it fails. Deployment planner keeps a global object 'avoid'. It loops through each volume to be created, asking storage allocators for matching pools, passing this avoid object. First disk matches a pool or pools, adds ALL other pools to avoid object, then deployment planner attaches matching pools to a list for that disk. Second disk matches a pool, adds all other pools to avoid object, then deployment planner says wait, matching pool is in avoid, can't use it. Oops. In fact, at this point ALL pools are in avoid (unless there are other pools that have both tags). Need to remove matching pool from the avoid set during each select phase. cannot deploy vm with differing service storage tag and data disk storage tag - Key: CLOUDSTACK-5853 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5853 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0, 4.3.0, 4.4.0 Reporter: Marcus Sorensen Assignee: Marcus Sorensen Create two storage pools, one with storage tag X, one with storage tag Y. Create a service offering with storage tag X. Create a disk offering with storage tag Y. Attempt to deploy a virtual machine with a datadisk, using given offerings, it fails. Deployment planner keeps a global object 'avoid'. It loops through each volume to be created, asking storage allocators for matching pools, passing this avoid object. First disk matches a pool or pools, adds ALL other pools to avoid object, then deployment planner attaches matching pools to a list for that disk. Second disk matches a pool, adds all other pools to avoid object, then deployment planner says wait, matching pool is in avoid, can't use it. Oops. In fact, at this point ALL pools are in avoid (unless there are other pools that have both tags). Need to remove matching pool from the avoid set during each select phase. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5853) cannot deploy vm with differing service storage tag and data disk storage tag
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13868130#comment-13868130 ] ASF subversion and git services commented on CLOUDSTACK-5853: - Commit fc082832d3f9741cb06f09593e58db78e8c887d8 in branch refs/heads/master from [~mlsorensen] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fc08283 ] CLOUDSTACK-5853 Create two storage pools, one with storage tag X, one with storage tag Y. Create a service offering with storage tag X. Create a disk offering with storage tag Y. Attempt to deploy a virtual machine with a datadisk, using given offerings, it fails. Deployment planner keeps a global object 'avoid'. It loops through each volume to be created, asking storage allocators for matching pools, passing this avoid object. First disk matches a pool or pools, adds ALL other pools to avoid object, then deployment planner attaches matching pools to a list for that disk. Second disk matches a pool, adds all other pools to avoid object, then deployment planner says wait, matching pool is in avoid, can't use it. Oops. In fact, at this point ALL pools are in avoid (unless there are other pools that have both tags). Need to remove matching pool from the avoid set during each select phase. cannot deploy vm with differing service storage tag and data disk storage tag - Key: CLOUDSTACK-5853 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5853 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0, 4.3.0, 4.4.0 Reporter: Marcus Sorensen Assignee: Marcus Sorensen Create two storage pools, one with storage tag X, one with storage tag Y. Create a service offering with storage tag X. Create a disk offering with storage tag Y. Attempt to deploy a virtual machine with a datadisk, using given offerings, it fails. Deployment planner keeps a global object 'avoid'. It loops through each volume to be created, asking storage allocators for matching pools, passing this avoid object. First disk matches a pool or pools, adds ALL other pools to avoid object, then deployment planner attaches matching pools to a list for that disk. Second disk matches a pool, adds all other pools to avoid object, then deployment planner says wait, matching pool is in avoid, can't use it. Oops. In fact, at this point ALL pools are in avoid (unless there are other pools that have both tags). Need to remove matching pool from the avoid set during each select phase. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
