[jira] [Commented] (CLOUDSTACK-3400) Swift functionality broken after the object-storage branch merge into master
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702414#comment-13702414 ] ASF IRC Bot commented on CLOUDSTACK-3400: - Comment from chipc via IRC: Understanding the effort to correct this issue is the first question I'd ask, so that we can figure out how to proceed WRT the release impact. > Swift functionality broken after the object-storage branch merge into master > > > Key: CLOUDSTACK-3400 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3400 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller >Affects Versions: 4.2.0 >Reporter: Chip Childers >Priority: Blocker > Fix For: 4.2.0 > > > Per mailing list discussion: http://markmail.org/message/aitv5264swzwpedh > Swift support is broken in master. This is a release blocker ATM. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3054) modify cloud-set-guest-sshkey.in initscript to handle SELinux configuration
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686774#comment-13686774 ] ASF IRC Bot commented on CLOUDSTACK-3054: - Comment from chipc via IRC: code in https://reviews.apache.org/r/11934/ > modify cloud-set-guest-sshkey.in initscript to handle SELinux configuration > --- > > Key: CLOUDSTACK-3054 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3054 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Environment: CentOS 6.4 VM >Reporter: Ian Service >Priority: Minor > > https://reviews.apache.org/r/11934/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-3045) UI - Error "array2 is undefined" shown when try to add a host
[
https://issues.apache.org/jira/browse/CLOUDSTACK-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686770#comment-13686770
]
ASF IRC Bot commented on CLOUDSTACK-3045:
-
Comment from chipc via IRC:
code in https://reviews.apache.org/r/11934/
> UI - Error "array2 is undefined" shown when try to add a host
> --
>
> Key: CLOUDSTACK-3045
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3045
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
>Affects Versions: 4.2.0
>Reporter: Sheng Yang
>Priority: Critical
> Fix For: 4.2.0
>
>
> Tried to add a host, UI would show "array2 is undefined" for firebugs, and
> the screen won't be updated anyway.
> Firebugs said:
> TypeError: array2 is undefined
> [Break On This Error]
> ...eURL("dedicateHost&hostId=" +hostId +"&domainId=" +args.data.domainId +
> array2.j...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647509#comment-13647509 ] ASF IRC Bot commented on CLOUDSTACK-2207: - Comment from chipc via IRC: I need to confirm that the system VM template ends up being the correct version after using that process before documenting it > Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present > > > Key: CLOUDSTACK-2207 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2207 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault >Assignee: Chip Childers >Priority: Critical > Fix For: 4.1.0 > > > We're trying to upgrade from 2.2.14 to 4.1.0. > DatabaseUpgradeChecker failed : > 2013-04-26 12:11:45,205 ERROR [utils.component.ComponentContext] > (Timer-1:null) System integrity check failed. Refuse to startup > com.cloud.utils.exception.CloudRuntimeException: 3.0.0 VMware SystemVm > template not found. Cannot upgrade system Vms > at > com.cloud.upgrade.dao.Upgrade2214to30.updateSystemVms(Upgrade2214to30.java:713) > at > com.cloud.upgrade.dao.Upgrade2214to30.performDataMigration(Upgrade2214to30.java:82) > at > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:258) > at > com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:379) > at > com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:91) > at > com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > According to the documentation, there is no VMware SystemVm 3.0.0 to install. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644853#comment-13644853 ] ASF IRC Bot commented on CLOUDSTACK-2281: - Comment from chipc via IRC: And is this actually a blocker severity? Does it still occur after the expunge interval has cleaned out the datastore in question? > VM fails to deploy due to planner selecting deleted pool > > > Key: CLOUDSTACK-2281 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2281 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.1.0 >Reporter: Marcus Sorensen >Priority: Blocker > Fix For: 4.1.0 > > > Having trouble tracking this down. Here's what I did: > Created a 4.1 advanced zone > added primary storage A > deployed a template > deployed vms > added new primary storages > migrated VMs from primary storage A to others > removed initial primary storage A > try to deploy new vm from template, not working. It looks like the allocator > correctly finds and decides to use pool id 204, but somehow deployment is > actually attempted on deleted pool 202. See "Returning Deployment > Destination" and "DeploymentPlan is provided": > 2013-04-29 13:25:49,293 DEBUG [allocator.impl.FirstFitAllocator] > (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Found a suitable host, > adding to list: 19 > 2013-04-29 13:25:49,294 DEBUG [allocator.impl.FirstFitAllocator] > (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Host Allocator returning > 4 suitable hosts > 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) Checking suitable pools for volume (Id, Type): > (10663,ROOT) > 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) We need to allocate new storagepool for this volume > 2013-04-29 13:25:49,299 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) Calling StoragePoolAllocators to find suitable > pools > 2013-04-29 13:25:49,302 DEBUG > [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) > Looking for pools in dc: 1 pod:1 cluster:1 > 2013-04-29 13:25:49,304 DEBUG > [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) > FirstFitStoragePoolAllocator has 1 pools to check for allocation > 2013-04-29 13:25:49,304 DEBUG > [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) > Checking if storage pool is suitable, name: sansrv-row2-rack0 ,poolId: 204 > 2013-04-29 13:25:49,304 DEBUG > [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) > Is localStorageAllocationNeeded? false > 2013-04-29 13:25:49,305 DEBUG > [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) > Is storage pool shared? true > 2013-04-29 13:25:49,309 DEBUG [cloud.storage.StorageManagerImpl] > (Job-Executor-10:job-9908) Checking pool 204 for storage, totalSize: > 11984676742758, usedBytes: 879609302221, usedPct: 0.07339449541286318, > disable threshold: 0.85 > 2013-04-29 13:25:49,327 DEBUG [cloud.storage.StorageManagerImpl] > (Job-Executor-10:job-9908) Checking pool: 204 for volume allocation > [Vol[10663|vm=6189|ROOT]], maxSize : 11984676742758, totalAllocatedSize : > 588879744000, askingSize : 8589934592, allocated disable threshold: 0.85 > 2013-04-29 13:25:49,327 DEBUG > [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) > FirstFitStoragePoolAllocator returning 1 suitable storage pools > 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) Trying to find a potenial host and associated > storage pools from the suitable host/pool lists for this VM > 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) Checking if host: 17 can access any suitable > storage pool for volume: ROOT > 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) Host: 17 can access pool: 204 > 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) Found a potential host id: 17 name: ksrv2-000 and > associated storage pools for this VM > 2013-04-29 13:25:49,332 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) Returning Deployment Destination: > Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] > : > Dest[Zone(1)-Pod(1)-Cluster(1)-Host(17)-Storage(Volume(10663|ROOT-->Pool(204))] > 2013-04-29 13:25:49,370 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-10:job-9908) VM state transitted from :Stopped to Starting with > event: StartRequest
[jira] [Commented] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644848#comment-13644848 ] ASF IRC Bot commented on CLOUDSTACK-2281: - Comment from chipc via IRC: Marcus, is it possible that the specific deployment planner in question doesn't exclude the appropriate states from it's selction list? > VM fails to deploy due to planner selecting deleted pool > > > Key: CLOUDSTACK-2281 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2281 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.1.0 >Reporter: Marcus Sorensen >Priority: Blocker > Fix For: 4.1.0 > > > Having trouble tracking this down. Here's what I did: > Created a 4.1 advanced zone > added primary storage A > deployed a template > deployed vms > added new primary storages > migrated VMs from primary storage A to others > removed initial primary storage A > try to deploy new vm from template, not working. It looks like the allocator > correctly finds and decides to use pool id 204, but somehow deployment is > actually attempted on deleted pool 202. See "Returning Deployment > Destination" and "DeploymentPlan is provided": > 2013-04-29 13:25:49,293 DEBUG [allocator.impl.FirstFitAllocator] > (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Found a suitable host, > adding to list: 19 > 2013-04-29 13:25:49,294 DEBUG [allocator.impl.FirstFitAllocator] > (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Host Allocator returning > 4 suitable hosts > 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) Checking suitable pools for volume (Id, Type): > (10663,ROOT) > 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) We need to allocate new storagepool for this volume > 2013-04-29 13:25:49,299 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) Calling StoragePoolAllocators to find suitable > pools > 2013-04-29 13:25:49,302 DEBUG > [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) > Looking for pools in dc: 1 pod:1 cluster:1 > 2013-04-29 13:25:49,304 DEBUG > [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) > FirstFitStoragePoolAllocator has 1 pools to check for allocation > 2013-04-29 13:25:49,304 DEBUG > [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) > Checking if storage pool is suitable, name: sansrv-row2-rack0 ,poolId: 204 > 2013-04-29 13:25:49,304 DEBUG > [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) > Is localStorageAllocationNeeded? false > 2013-04-29 13:25:49,305 DEBUG > [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) > Is storage pool shared? true > 2013-04-29 13:25:49,309 DEBUG [cloud.storage.StorageManagerImpl] > (Job-Executor-10:job-9908) Checking pool 204 for storage, totalSize: > 11984676742758, usedBytes: 879609302221, usedPct: 0.07339449541286318, > disable threshold: 0.85 > 2013-04-29 13:25:49,327 DEBUG [cloud.storage.StorageManagerImpl] > (Job-Executor-10:job-9908) Checking pool: 204 for volume allocation > [Vol[10663|vm=6189|ROOT]], maxSize : 11984676742758, totalAllocatedSize : > 588879744000, askingSize : 8589934592, allocated disable threshold: 0.85 > 2013-04-29 13:25:49,327 DEBUG > [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) > FirstFitStoragePoolAllocator returning 1 suitable storage pools > 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) Trying to find a potenial host and associated > storage pools from the suitable host/pool lists for this VM > 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) Checking if host: 17 can access any suitable > storage pool for volume: ROOT > 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) Host: 17 can access pool: 204 > 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) Found a potential host id: 17 name: ksrv2-000 and > associated storage pools for this VM > 2013-04-29 13:25:49,332 DEBUG [cloud.deploy.FirstFitPlanner] > (Job-Executor-10:job-9908) Returning Deployment Destination: > Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))] > : > Dest[Zone(1)-Pod(1)-Cluster(1)-Host(17)-Storage(Volume(10663|ROOT-->Pool(204))] > 2013-04-29 13:25:49,370 DEBUG [cloud.capacity.CapacityManagerImpl] > (Job-Executor-10:job-9908) VM state transitted from :Stopped to Starting with > event: StartReq
[jira] [Commented] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644607#comment-13644607 ] ASF IRC Bot commented on CLOUDSTACK-2207: - Comment from chipc via IRC: We need to s/systemvm-*-4.1.0/systemvm-*-3.0.0/gc in the release notes. > Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present > > > Key: CLOUDSTACK-2207 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2207 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.1.0 >Reporter: Nicolas Lamirault > Fix For: 4.1.0 > > > We're trying to upgrade from 2.2.14 to 4.1.0. > DatabaseUpgradeChecker failed : > 2013-04-26 12:11:45,205 ERROR [utils.component.ComponentContext] > (Timer-1:null) System integrity check failed. Refuse to startup > com.cloud.utils.exception.CloudRuntimeException: 3.0.0 VMware SystemVm > template not found. Cannot upgrade system Vms > at > com.cloud.upgrade.dao.Upgrade2214to30.updateSystemVms(Upgrade2214to30.java:713) > at > com.cloud.upgrade.dao.Upgrade2214to30.performDataMigration(Upgrade2214to30.java:82) > at > com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:258) > at > com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:379) > at > com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:91) > at > com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > According to the documentation, there is no VMware SystemVm 3.0.0 to install. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2278) TEST Ticket - Please Ignore
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644493#comment-13644493 ] ASF IRC Bot commented on CLOUDSTACK-2278: - Comment from Humbedooh via IRC: testing 1 2 3 4 > TEST Ticket - Please Ignore > --- > > Key: CLOUDSTACK-2278 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2278 > Project: CloudStack > Issue Type: Wish > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Chip Childers >Priority: Trivial > > We are going to test adding comments from irc with this ticket. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2278) TEST Ticket - Please Ignore
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644494#comment-13644494 ] ASF IRC Bot commented on CLOUDSTACK-2278: - Comment from chipc via IRC: Thanks Humbedooh > TEST Ticket - Please Ignore > --- > > Key: CLOUDSTACK-2278 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2278 > Project: CloudStack > Issue Type: Wish > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Chip Childers >Priority: Trivial > > We are going to test adding comments from irc with this ticket. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
