[jira] [Updated] (CLOUDSTACK-7399) broadcast_uri and possibly isolation_uri is not set correctly with Basic Network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-7399: - Fix Version/s: (was: 4.1.1) 4.4.1 broadcast_uri and possibly isolation_uri is not set correctly with Basic Network Key: CLOUDSTACK-7399 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7399 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: CentOS Linux 6.5 64Bit, KVM, Basic Network Reporter: Thomas Moroder Fix For: 4.4.1 Since updating to version 4.4.0 of Cloudstack I have noticed problems when starting new VMs and also System-VMs. After analyzing the database changes it seems that broadcast_uri and possibly isolation_uri do not get set and/or do not get set correctly for new VM instances in the nics table. E.g.: mysql select * from nics where instance_id=457; +-+--+-+---+--+---++-+---++--+---+--+---+--+---+-+---+-+-+-+-+-+-+--+--+-+ | id | uuid | instance_id | mac_address | ip4_address | netmask | gateway| ip_type | broadcast_uri | network_id | mode | state | strategy | reserver_name | reservation_id | device_id | update_time | isolation_uri | ip6_address | default_nic | vm_type | created | removed | ip6_gateway | ip6_cidr | secondary_ip | display_nic | +-+--+-+---+--+---++-+---++--+---+--+---+--+---+-+---+-+-+-+-+-+-+--+--+-+ | 668 | ec1d8296-1bb5-4844-8485-00ada7c7a8f9 | 457 | 06:97:ae:00:00:5c | 1.2.3.4 | 255.255.255.0 | 1.2.3.1 | Ip4 | NULL |212 | Dhcp | Allocated | Start| DirectPodBasedNetworkGuru | e7b3de50-8cf0-43db-a7b2-4cc44d2d13c5 | 0 | 2014-08-22 10:12:17 | NULL | NULL| 1 | User| 2014-08-22 08:12:09 | NULL | NULL| NULL |0 | 1 | +-+--+-+---+--+---++-+---++--+---+--+---+--+---+-+---+-+-+-+-+-+-+--+--+-+ With previous versions both broadcast_uri and isolation_uri where set in the Basic Network mode to vlan://untagged and ec2://untagged. This causes failures to start the VMs with the cloudstack-agent on the single hosts giving the following error message: 2014-08-22 02:43:08,457 WARN [cloud.agent.Agent] (agentRequest-Handler-5:null) Caught: java.lang.NullPointerException at com.cloud.network.Networks$BroadcastDomainType.getSchemeValue(Networks.java:160) at com.cloud.network.Networks$BroadcastDomainType.getValue(Networks.java:214) at com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:96) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:4010) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3795) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1333) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at
[jira] [Closed] (CLOUDSTACK-7238) [Automation] SQL exceptions seen in the runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-7238. [Automation] SQL exceptions seen in the runs Key: CLOUDSTACK-7238 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7238 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Reporter: Raja Pullela Assignee: Alena Prokharchyk Priority: Critical Attachments: simu_mgmt_log.txt Following SQL exceptions are seen the management server log: 2014-08-01 20:04:35,194 DEBUG [c.c.s.d.VMTemplateDaoImpl] (main:null) Found parameter routing unique name null 2014-08-01 20:04:35,194 DEBUG [c.c.s.d.VMTemplateDaoImpl] (main:null) Use console proxy template : routing 2014-08-01 20:04:35,229 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught exception when inserting system account: Duplicate entry '1' for key 'PRIMARY' 2014-08-01 20:04:35,231 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting system user: Duplicate entry '1' for key 'PRIMARY' 2014-08-01 20:04:35,231 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when creating admin account: Duplicate entry '2' for key 'PRIMARY' 2014-08-01 20:04:35,232 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught SQLException when inserting admin user: Duplicate entry '2' for key 'PRIMARY' 2014-08-01 20:04:35,233 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Caught (SQL?)Exception: no network_group Table 'cloud.network_group' doesn't exist 2014-08-01 20:04:35,238 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer is saving default values to the database. 2014-08-01 20:04:36,808 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer made secondary storage vm required. 2014-08-01 20:04:36,811 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer made secondary storage copy encrypt set to false. 2014-08-01 20:04:36,818 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer made secondary storage copy use realhostip. 2014-08-01 20:04:36,909 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer saved /mnt as mount.parent. 2014-08-01 20:04:36,915 DEBUG [c.c.u.s.Script] (main:null) Executing: /bin/bash -c /sbin/route | grep default 2014-08-01 20:04:36,955 DEBUG [c.c.u.s.Script] (main:null) Execution is successful. 2014-08-01 20:04:36,967 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) ConfigurationServer saved 172.16.88.23 as host. 2014-08-01 20:04:37,612 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) resource_count table has records missing for some domains...going to insert them 2014-08-01 20:04:37,624 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Inserting resource count of type user_vm for domain id=1 2014-08-01 20:04:37,626 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Inserting resource count of type public_ip for domain id=1 2014-08-01 20:04:37,627 DEBUG [c.c.s.ConfigurationServerImpl] (main:null) Inserting resource count of type -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7455) Unable to connect to management server ?since SAML2 merge?
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti closed CLOUDSTACK-7455.
this has been fixed in recent builds
Unable to connect to management server ?since SAML2 merge?
--
Key: CLOUDSTACK-7455
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7455
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.5.0
Reporter: Alex Brett
Priority: Blocker
Fix For: 4.5.0
Attachments: management-server.log
In builds that have the SAML2 merge in, while I can start the management
server, it appears not to fully startup, and doesn't give the UI or API.
management-server.log (attached) stops at:
{noformat}
2014-08-29 14:55:02,097 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle]
(main:null) Starting CloudStack Components
2014-08-29 14:55:02,098 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle]
(main:null) Done Starting CloudStack Components
2014-08-29 14:55:02,098 INFO [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) Starting module [core]
2014-08-29 14:55:02,098 INFO [o.a.c.s.l.CloudStackExtendedLifeCycle]
(main:null) Starting CloudStack Components
2014-08-29 14:55:02,106 INFO [c.c.h.h.m.HypervManagerImpl] (main:null)
Cleanup mounted mount points used in previous session
2014-08-29 14:55:02,141 INFO [c.c.u.DatabaseIntegrityChecker] (main:null)
Grabbing lock to check for database integrity.
2014-08-29 14:55:02,143 INFO [c.c.u.DatabaseIntegrityChecker] (main:null)
Performing database integrity check
2014-08-29 14:55:02,144 DEBUG [c.c.u.DatabaseIntegrityChecker] (main:null) No
duplicate hosts with the same local storage found in database
2014-08-29 14:55:02,146 DEBUG [c.c.u.d.VersionDaoImpl] (main:null) Checking
to see if the database is at a version before it was the version table is
created
2014-08-29 14:55:02,150 INFO [c.c.c.ClusterManagerImpl] (main:null) Starting
Cluster manager, msid : 99326614648649
2014-08-29 14:55:02,155 INFO [c.c.c.ClusterManagerImpl] (main:null)
Management server 99326614648649, runId 1409324073632 is being started
2014-08-29 14:55:02,156 INFO [c.c.c.ClusterManagerImpl] (main:null)
Management server (host id : 1) is being started at 127.0.0.1:9090
2014-08-29 14:55:02,162 INFO [c.c.c.ClusterManagerImpl] (main:null) Cluster
manager was started successfully
2014-08-29 14:55:02,167 DEBUG [c.c.u.s.Script] (main:null) Executing:
/bin/bash -c /sbin/route | grep default
2014-08-29 14:55:02,183 DEBUG [c.c.u.s.Script] (main:null) Execution is
successful.
2014-08-29 14:55:02,185 WARN [c.c.c.ConfigurationManagerImpl] (main:null)
Management network CIDR is not configured originally. Set it default to
10.220.128.0/19
2014-08-29 14:55:02,190 WARN [o.a.c.alerts] (main:null) alertType:: 14 //
dataCenterId:: 0 // podId:: 0 // clusterId:: null // message:: Management
network CIDR is not configured originally. Set it default to 10.220.128.0/19
2014-08-29 14:55:02,215 INFO [c.c.h.HighAvailabilityManagerImpl]
(HA-Worker-0:null) Starting work
2014-08-29 14:55:02,224 INFO [c.c.h.HighAvailabilityManagerImpl]
(HA-Worker-3:null) Starting work
2014-08-29 14:55:02,224 INFO [c.c.h.HighAvailabilityManagerImpl]
(HA-Worker-4:null) Starting work
2014-08-29 14:55:02,218 INFO [c.c.h.HighAvailabilityManagerImpl]
(HA-Worker-2:null) Starting work
2014-08-29 14:55:02,218 INFO [c.c.h.HighAvailabilityManagerImpl]
(HA-Worker-1:null) Starting work
2014-08-29 14:55:02,290 DEBUG [c.c.n.l.LBHealthCheckManagerImpl] (main:null)
LB HealthCheckmanager is getting Started
2014-08-29 14:55:02,307 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl]
(NetworkStatsUpdater-1:ctx-5b259b22) Successfully updated aggregate network
stats
2014-08-29 14:55:11,061 INFO [c.c.u.c.ComponentContext] (main:null)
Configuring
com.cloud.bridge.persist.dao.CloudStackAccountDaoImpl_EnhancerByCloudStack_156f5045
2014-08-29 14:55:11,066 INFO [c.c.u.c.ComponentContext] (main:null)
Configuring
com.cloud.bridge.persist.dao.OfferingDaoImpl_EnhancerByCloudStack_aa79bf9f
2014-08-29 14:55:11,066 INFO [c.c.u.c.ComponentContext] (main:null)
Configuring
com.cloud.bridge.persist.dao.SMetaDaoImpl_EnhancerByCloudStack_c720af97
2014-08-29 14:55:11,066 INFO [c.c.u.c.ComponentContext] (main:null)
Configuring
com.cloud.bridge.persist.dao.MultipartMetaDaoImpl_EnhancerByCloudStack_ae893256
2014-08-29 14:55:11,067 INFO [c.c.u.c.ComponentContext] (main:null)
Configuring
com.cloud.bridge.persist.dao.UserCredentialsDaoImpl_EnhancerByCloudStack_68227ab6
2014-08-29 14:55:11,067 INFO [c.c.u.c.ComponentContext] (main:null)
Configuring
[jira] [Commented] (CLOUDSTACK-7746) Baremetal related script erros seen on router console
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14217007#comment-14217007 ] Sudha Ponnaganti commented on CLOUDSTACK-7746: -- Can this be fixed? Baremetal related script erros seen on router console - Key: CLOUDSTACK-7746 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7746 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Environment: Build from master Reporter: Sangeetha Hariharan Assignee: frank zhang Priority: Critical Fix For: 4.5.0 Attachments: router.png Baremetal related script erros seen on router console. Advanced zone set up with 3 xenserver hosts in a cluster. When logging into the console view of router , following script errors are seen: /opt/cloud/bin/baremetal-vr.py:159: SyntaxWarning : name 'server' is assigned to before glocal declaration. .. Attached is the screen shot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7642) [Upgrade]java.lang.ClassNotFoundException after upgrading to 4.5 from 4.3.0.1 with Xenserver HV.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-7642: - Description: 1. Deployed 4.3.0 CS with 1zone,1 pod,1cluster,2 Xen 6.2 HVs using 4.3.0 build. 2. Registered the 4.5 template as systemvm-xenserver-4.5 3. Upgraded to 4.5 and started the MS. Observation: Observed the following exception in MS logs .Hosts went into disconnected stated. 2014-09-29 13:45:26,849 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] (ClusteredAgentManager Timer:ctx-7b268e53) Loading directly connected host 1(Rack1Pod1Host29) 2014-09-29 13:45:26,851 WARN [c.c.r.DiscovererBase] (ClusteredAgentManager Timer:ctx-7b268e53) Unable to find class com.cloud.hypervisor.xen.resource.XenServer620Resource java.lang.ClassNotFoundException: com.cloud.hypervisor.xen.resource.XenServer620Resource at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1484) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:186) at com.cloud.resource.DiscovererBase.getResource(DiscovererBase.java:89) at com.cloud.resource.DiscovererBase.reloadResource(DiscovererBase.java:150) at com.cloud.agent.manager.AgentManagerImpl.loadDirectlyConnectedHost(AgentManagerImpl.java:680) at com.cloud.agent.manager.ClusteredAgentManagerImpl.scanDirectAgentToLoad(ClusteredAgentManagerImpl.java:219) at com.cloud.agent.manager.ClusteredAgentManagerImpl.runDirectAgentScanTimerTask(ClusteredAgentManagerImpl.java:185) at com.cloud.agent.manager.ClusteredAgentManagerImpl.access$100(ClusteredAgentManagerImpl.java:99) at com.cloud.agent.manager.ClusteredAgentManagerImpl$DirectAgentScanTimerTask.runInContext(ClusteredAgentManagerImpl.java:235) at org.apache.cloudstack.managed.context.ManagedContextTimerTask$1.runInContext(ManagedContextTimerTask.java:30) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at org.apache.cloudstack.managed.context.ManagedContextTimerTask.run(ManagedContextTimerTask.java:27) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) 2014-09-29 13:45:26,852 WARN [c.c.a.m.AgentManagerImpl] (ClusteredAgentManager Timer:ctx-7b268e53) Unable to load the resource: 1 2014-09-29 13:45:26,853 DEBUG [c.c.h.Status] (ClusteredAgentManager Timer:ctx-7b268e53) Transition:[Resource state = Enabled, Agent event = AgentDisconnected, Host id = 1, name = Rack1Pod1Host29] Attaching the dumps and logs. was: 1. Deployed 4.3.0.1 CS with 1zone,1 pod,1cluster,2 Xen 6.2 HVs using 4.3.0.1 build. 2. Registered the 4.5 template as systemvm-xenserver-4.5 3. Upgraded to 4.5 and started the MS. Observation: Observed the following exception in MS logs .Hosts went into disconnected stated. 2014-09-29 13:45:26,849 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] (ClusteredAgentManager Timer:ctx-7b268e53) Loading directly connected host 1(Rack1Pod1Host29) 2014-09-29 13:45:26,851 WARN [c.c.r.DiscovererBase] (ClusteredAgentManager Timer:ctx-7b268e53) Unable to find class com.cloud.hypervisor.xen.resource.XenServer620Resource java.lang.ClassNotFoundException: com.cloud.hypervisor.xen.resource.XenServer620Resource at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1484) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:186) at com.cloud.resource.DiscovererBase.getResource(DiscovererBase.java:89) at com.cloud.resource.DiscovererBase.reloadResource(DiscovererBase.java:150) at com.cloud.agent.manager.AgentManagerImpl.loadDirectlyConnectedHost(AgentManagerImpl.java:680) at com.cloud.agent.manager.ClusteredAgentManagerImpl.scanDirectAgentToLoad(ClusteredAgentManagerImpl.java:219) at com.cloud.agent.manager.ClusteredAgentManagerImpl.runDirectAgentScanTimerTask(ClusteredAgentManagerImpl.java:185) at com.cloud.agent.manager.ClusteredAgentManagerImpl.access$100(ClusteredAgentManagerImpl.java:99) at
[jira] [Updated] (CLOUDSTACK-7642) [Upgrade]java.lang.ClassNotFoundException after upgrading to 4.5 from 4.3.0 with Xenserver HV.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-7642: - Summary: [Upgrade]java.lang.ClassNotFoundException after upgrading to 4.5 from 4.3.0 with Xenserver HV. (was: [Upgrade]java.lang.ClassNotFoundException after upgrading to 4.5 from 4.3.0.1 with Xenserver HV.) [Upgrade]java.lang.ClassNotFoundException after upgrading to 4.5 from 4.3.0 with Xenserver HV. -- Key: CLOUDSTACK-7642 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7642 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Upgrade Affects Versions: 4.5.0 Environment: upgrade from 4.3.0.1 to 4.5 using Xen server 6.2 Reporter: manasaveloori Priority: Blocker Fix For: 4.5.0 Attachments: management-server.rar, mysqldump4.5.rar, mysqldumpBeforeUp.rar 1. Deployed 4.3.0 CS with 1zone,1 pod,1cluster,2 Xen 6.2 HVs using 4.3.0 build. 2. Registered the 4.5 template as systemvm-xenserver-4.5 3. Upgraded to 4.5 and started the MS. Observation: Observed the following exception in MS logs .Hosts went into disconnected stated. 2014-09-29 13:45:26,849 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] (ClusteredAgentManager Timer:ctx-7b268e53) Loading directly connected host 1(Rack1Pod1Host29) 2014-09-29 13:45:26,851 WARN [c.c.r.DiscovererBase] (ClusteredAgentManager Timer:ctx-7b268e53) Unable to find class com.cloud.hypervisor.xen.resource.XenServer620Resource java.lang.ClassNotFoundException: com.cloud.hypervisor.xen.resource.XenServer620Resource at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1484) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:186) at com.cloud.resource.DiscovererBase.getResource(DiscovererBase.java:89) at com.cloud.resource.DiscovererBase.reloadResource(DiscovererBase.java:150) at com.cloud.agent.manager.AgentManagerImpl.loadDirectlyConnectedHost(AgentManagerImpl.java:680) at com.cloud.agent.manager.ClusteredAgentManagerImpl.scanDirectAgentToLoad(ClusteredAgentManagerImpl.java:219) at com.cloud.agent.manager.ClusteredAgentManagerImpl.runDirectAgentScanTimerTask(ClusteredAgentManagerImpl.java:185) at com.cloud.agent.manager.ClusteredAgentManagerImpl.access$100(ClusteredAgentManagerImpl.java:99) at com.cloud.agent.manager.ClusteredAgentManagerImpl$DirectAgentScanTimerTask.runInContext(ClusteredAgentManagerImpl.java:235) at org.apache.cloudstack.managed.context.ManagedContextTimerTask$1.runInContext(ManagedContextTimerTask.java:30) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at org.apache.cloudstack.managed.context.ManagedContextTimerTask.run(ManagedContextTimerTask.java:27) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) 2014-09-29 13:45:26,852 WARN [c.c.a.m.AgentManagerImpl] (ClusteredAgentManager Timer:ctx-7b268e53) Unable to load the resource: 1 2014-09-29 13:45:26,853 DEBUG [c.c.h.Status] (ClusteredAgentManager Timer:ctx-7b268e53) Transition:[Resource state = Enabled, Agent event = AgentDisconnected, Host id = 1, name = Rack1Pod1Host29] Attaching the dumps and logs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7642) [Upgrade]java.lang.ClassNotFoundException after upgrading to 4.5 from 4.3.0 with Xenserver HV.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-7642: - Environment: upgrade from 4.3.0 to 4.5 using Xen server 6.2 (was: upgrade from 4.3.0.1 to 4.5 using Xen server 6.2 ) [Upgrade]java.lang.ClassNotFoundException after upgrading to 4.5 from 4.3.0 with Xenserver HV. -- Key: CLOUDSTACK-7642 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7642 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Upgrade Affects Versions: 4.5.0 Environment: upgrade from 4.3.0 to 4.5 using Xen server 6.2 Reporter: manasaveloori Priority: Blocker Fix For: 4.5.0 Attachments: management-server.rar, mysqldump4.5.rar, mysqldumpBeforeUp.rar 1. Deployed 4.3.0 CS with 1zone,1 pod,1cluster,2 Xen 6.2 HVs using 4.3.0 build. 2. Registered the 4.5 template as systemvm-xenserver-4.5 3. Upgraded to 4.5 and started the MS. Observation: Observed the following exception in MS logs .Hosts went into disconnected stated. 2014-09-29 13:45:26,849 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] (ClusteredAgentManager Timer:ctx-7b268e53) Loading directly connected host 1(Rack1Pod1Host29) 2014-09-29 13:45:26,851 WARN [c.c.r.DiscovererBase] (ClusteredAgentManager Timer:ctx-7b268e53) Unable to find class com.cloud.hypervisor.xen.resource.XenServer620Resource java.lang.ClassNotFoundException: com.cloud.hypervisor.xen.resource.XenServer620Resource at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1484) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:186) at com.cloud.resource.DiscovererBase.getResource(DiscovererBase.java:89) at com.cloud.resource.DiscovererBase.reloadResource(DiscovererBase.java:150) at com.cloud.agent.manager.AgentManagerImpl.loadDirectlyConnectedHost(AgentManagerImpl.java:680) at com.cloud.agent.manager.ClusteredAgentManagerImpl.scanDirectAgentToLoad(ClusteredAgentManagerImpl.java:219) at com.cloud.agent.manager.ClusteredAgentManagerImpl.runDirectAgentScanTimerTask(ClusteredAgentManagerImpl.java:185) at com.cloud.agent.manager.ClusteredAgentManagerImpl.access$100(ClusteredAgentManagerImpl.java:99) at com.cloud.agent.manager.ClusteredAgentManagerImpl$DirectAgentScanTimerTask.runInContext(ClusteredAgentManagerImpl.java:235) at org.apache.cloudstack.managed.context.ManagedContextTimerTask$1.runInContext(ManagedContextTimerTask.java:30) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at org.apache.cloudstack.managed.context.ManagedContextTimerTask.run(ManagedContextTimerTask.java:27) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) 2014-09-29 13:45:26,852 WARN [c.c.a.m.AgentManagerImpl] (ClusteredAgentManager Timer:ctx-7b268e53) Unable to load the resource: 1 2014-09-29 13:45:26,853 DEBUG [c.c.h.Status] (ClusteredAgentManager Timer:ctx-7b268e53) Transition:[Resource state = Enabled, Agent event = AgentDisconnected, Host id = 1, name = Rack1Pod1Host29] Attaching the dumps and logs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6444) [Automation] test_01_primary_storage_iscsi failed on test_primary_storage.py - Wrong iscsi path format - it should be /targetIQN/LUN
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127418#comment-14127418
]
Sudha Ponnaganti commented on CLOUDSTACK-6444:
--
I am working out of cambridge office from 9/8 - 9/12. Will respond during UK
working hours
[Automation] test_01_primary_storage_iscsi failed on
test_primary_storage.py - Wrong iscsi path format - it should be
/targetIQN/LUN
Key: CLOUDSTACK-6444
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6444
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, XenServer
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Damodar Reddy T
Priority: Critical
Fix For: 4.4.0
Attachments: management-server.log.2014-04-16.gz
Error Message:
Execute cmd: createstoragepool failed, due to: errorCode: 530, errorText:None
begin captured logging
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
STARTED : TC: test_01_primary_storage_iscsi :::
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listZones {}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: zCinw6XM4JSpQF6uNjzREWyHshQ=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
HTTP/1.1 200 735
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
Response: { listzonesresponse : { count:2 ,zone : [
{id:4fbc4494-e655-49b6-bda1-7ad8eb641732,name:test0,dns1:10.223.240.232,dns2:10.223.240.234,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:f0aed2ee-a79d-3608-bae5-09972653a6cf,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]},
{id:55fe83ca-4160-40b2-89cb-63cadf8b90f9,name:test1,dns1:10.223.240.234,dns2:10.223.240.232,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:3973cd3a-d2ed-3242-8431-b40f919051f1,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listPods {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: Q5eN6r9ACb1qiPi7CI3wiB6wh0k=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
HTTP/1.1 200 314
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
Response: { listpodsresponse : { count:1 ,pod : [
{id:d99714b2-7164-4d85-b5a6-c0caf12eb57a,name:test0pod0,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,zonename:test0,gateway:10.223.251.1,netmask:255.255.255.192,startip:10.223.251.4,endip:10.223.251.14,allocationstate:Enabled}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listClusters {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: CGgAerZxK5EJBr34YnPiWBJHqWg=
requests.packages.urllib3.connectionpool:
[jira] [Updated] (CLOUDSTACK-7291) LXC: Mgmt server/agent keeps killing systemvms
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-7291: - Affects Version/s: 4.5.0 LXC: Mgmt server/agent keeps killing systemvms -- Key: CLOUDSTACK-7291 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7291 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0, 4.5.0, 4.3.1 Reporter: Rohit Yadav Priority: Blocker Fix For: 4.5.0, 4.3.1 Followed installation and setup docs of 4.3, was unable to get LXC to work on Ubuntu 14.04/trusty. The systemvms kept coming up and result from ssvm_check.sh was good and it was able to reach mgmt server /host, even then mgmt server complained that it was unable to contact agent on the systemvm (ping), while the agent would gracefully shutdown the systemvm (by killing them). Relevant log: 2014-08-07 19:52:26,294 INFO [c.c.u.e.CSExceptionErrorCode] (secstorage-1:ctx-fc57ef43) Could not find exception: com.cloud.exception.OperationTimedoutException in error code list for exceptions 2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl] (consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host Host[-1-Routing] 2014-08-07 19:52:26,295 DEBUG [c.c.a.m.AgentAttache] (consoleproxy-1:ctx-e123fa9c) Seq 1-51249205: Cancelling. 2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl] (consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host Host[-1-Routing] 2014-08-07 19:52:26,303 DEBUG [c.c.h.Status] (AgentTaskPool-13:ctx-0b35e679) Transition:[Resource state = Enabled, Agent event = ShutdownRequested, Host id = 1, name = bluebox1.bhaisaab.org] 2014-08-07 19:52:26,311 DEBUG [c.c.h.HighAvailabilityManagerImpl] (secstorage-1:ctx-fc57ef43) Scheduled HAWork[12-CheckStop-2-Starting-Scheduled] 2014-08-07 19:52:26,314 WARN [c.c.s.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-fc57ef43) Exception while trying to start secondary storage vm com.cloud.exception.AgentUnavailableException: Resource [Host:1] is unreachable: Host 1: Unable to start s-2-VM ---at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1051) ---at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761) ---at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:745) ---at com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:261) ---at com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:694) ---at com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1278) ---at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) ---at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) ---at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111) ... ... ... Caused by: com.cloud.exception.OperationTimedoutException: Commands 51249206 to Host 1 timed out after 3600 ---at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:439) ---at com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394) ---at com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920) ---at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:989) ---... 24 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7291) LXC: Mgmt server/agent keeps killing systemvms
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-7291: - Fix Version/s: 4.5.0 LXC: Mgmt server/agent keeps killing systemvms -- Key: CLOUDSTACK-7291 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7291 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0, 4.5.0, 4.3.1 Reporter: Rohit Yadav Priority: Blocker Fix For: 4.5.0, 4.3.1 Followed installation and setup docs of 4.3, was unable to get LXC to work on Ubuntu 14.04/trusty. The systemvms kept coming up and result from ssvm_check.sh was good and it was able to reach mgmt server /host, even then mgmt server complained that it was unable to contact agent on the systemvm (ping), while the agent would gracefully shutdown the systemvm (by killing them). Relevant log: 2014-08-07 19:52:26,294 INFO [c.c.u.e.CSExceptionErrorCode] (secstorage-1:ctx-fc57ef43) Could not find exception: com.cloud.exception.OperationTimedoutException in error code list for exceptions 2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl] (consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host Host[-1-Routing] 2014-08-07 19:52:26,295 DEBUG [c.c.a.m.AgentAttache] (consoleproxy-1:ctx-e123fa9c) Seq 1-51249205: Cancelling. 2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl] (consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host Host[-1-Routing] 2014-08-07 19:52:26,303 DEBUG [c.c.h.Status] (AgentTaskPool-13:ctx-0b35e679) Transition:[Resource state = Enabled, Agent event = ShutdownRequested, Host id = 1, name = bluebox1.bhaisaab.org] 2014-08-07 19:52:26,311 DEBUG [c.c.h.HighAvailabilityManagerImpl] (secstorage-1:ctx-fc57ef43) Scheduled HAWork[12-CheckStop-2-Starting-Scheduled] 2014-08-07 19:52:26,314 WARN [c.c.s.s.SecondaryStorageManagerImpl] (secstorage-1:ctx-fc57ef43) Exception while trying to start secondary storage vm com.cloud.exception.AgentUnavailableException: Resource [Host:1] is unreachable: Host 1: Unable to start s-2-VM ---at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1051) ---at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761) ---at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:745) ---at com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:261) ---at com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:694) ---at com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1278) ---at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123) ---at com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50) ---at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111) ... ... ... Caused by: com.cloud.exception.OperationTimedoutException: Commands 51249206 to Host 1 timed out after 3600 ---at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:439) ---at com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394) ---at com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920) ---at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:989) ---... 24 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CLOUDSTACK-7443) Cannot launch SSVMs when using Swift as Secondary Storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti reassigned CLOUDSTACK-7443: Assignee: Sudha Ponnaganti Cannot launch SSVMs when using Swift as Secondary Storage - Key: CLOUDSTACK-7443 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7443 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.4.1 Reporter: Francois Gaudreault Assignee: Sudha Ponnaganti Priority: Critical When using swift as secondary storage, the management server will download the system vm, push it to swift. But then when it's time to start the SSVMs, the template is not downloaded back to the NFS store, and the SSVM will fail to create. It looks like a path issue. If I strip one path level, say from template/1/1 to template/1, the template will be downloaded properly. However, SSVMs have a rough time to start. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-231) Tag creation using special characters
[ https://issues.apache.org/jira/browse/CLOUDSTACK-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-231. --- agree with saksham's assessment Tag creation using special characters -- Key: CLOUDSTACK-231 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-231 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: pre-4.0.0 Environment: MS(rhel6.3) Git Revision: 046e916fcf6d847e2cdf281233d2e68a8e6500f8 Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git Reporter: prashant kumar mishra Assignee: Saksham Srivastava Priority: Minor Fix For: 4.4.0 Tag creation - - steps to reproduce 1-create tag on any resource(vm/template/PF/FW) 2-provide detail key=value=some special character EXPECTED -- -- Tag creation shouldn't be happening with message special character's are not allowed ACTUAL --- -- Tag creation is happening properly using special characters -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6043) VMware detaching volume fails if volume has snapshots
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14102566#comment-14102566 ] Sudha Ponnaganti commented on CLOUDSTACK-6043: -- Chris, Do you agree with this assessment thanks /sudha VMware detaching volume fails if volume has snapshots - Key: CLOUDSTACK-6043 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6043 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware, Volumes Affects Versions: 4.3.0 Reporter: Chris Suich Assignee: Likitha Shetty Labels: vmware, volumes Fix For: 4.4.0 When detaching VMware volumes, a call is first made to the hypervisor to remove all snapshots for that volume. After this happens, the path for the volume potentially changes, but isn't updated in the ACS DB, which causes problems when the call is made to actually detach the volume. For example, if the volume has a single snapshot, then the current path would be something like VOLUME-1.vmdk which is a delta disk for VOLUME.vmdk. Once the snapshot is deleted, VOLUME-1.vmdk is coalesced into VOLUME.vmdk, which becomes the active path. However, ACS still believes the correct path is VOLUME-1.vmdk which causes the detach to fail. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4627) HA not working, User VM wasn't Migrated
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14102594#comment-14102594 ] Sudha Ponnaganti commented on CLOUDSTACK-4627: -- can you cofirm that this is actually working HA not working, User VM wasn't Migrated --- Key: CLOUDSTACK-4627 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4627 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, KVM, Management Server Affects Versions: 4.2.0 Environment: CentOS 6.3 64bit Reporter: Naoki Sakamoto Assignee: edison su Fix For: 4.2.1 Attachments: 20130906_HA_SystemVM_Migration_OK_But_UserVM_NG.zip, 20130909_HA_UserVM_Migration_NG.zip 1. We made one of KVM Host Power OFF by push power button of hardware for High Availability Test. 2. Vritual Router / Secodary Storage VM / Console Proxy VM is Migrated. But User VM wasn't Migrated. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-1389) Interactive Password Prompts during Management Server Startup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14090518#comment-14090518 ] Sudha Ponnaganti commented on CLOUDSTACK-1389: -- I am OOO from 8/6 through 8/22 Interactive Password Prompts during Management Server Startup - Key: CLOUDSTACK-1389 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1389 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, 4.2.0 Environment: devcloud Reporter: John Burwell Labels: security Fix For: 4.4.0 When starting the management with no SSL certificate present, the system attempts to run a shell script that requires interactive password entry. Executing the following steps with a user that is either non-sudoer or a sudoer that requires a password authentication to perform sudo actions (and who has not already authenticated to sudo), execute the following commands from root directory of a cloudstack/4.1 checkout: 1. mvn -P developer clean install 2. mvn -pl :cloud-client-ui jetty:run During the startup process, the management server will not find the cloud.keystore in the the client/target/cloud-client-ui-4.1-SNAPSHOT/WEB-INF/classes directory, and attempt to generate an SSL certificate using the following shell scripts: sudo keytool -genkey -keystore /Users/jburwell/Documents/projects/cloudstack/src/cloudstack-basho/client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/classes/cloud.keystore -store pass vmops.com -keypass vmops.com -keyalg RSA -validity 3650 -dname cn=Cloudstack User,ou=0.8.31,o=0.8.31,c=Unknown The following is a capture of the script timeout error from the vmops.log: 2013-02-27 09:52:17,157 INFO [cloud.server.ConfigurationServerImpl] (Timer-2:null) SSL keystore located at /Users/jburwell/Docum ents/projects/cloudstack/src/cloudstack-basho/client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/classes/cloud.keystore 2013-02-27 09:52:17,176 DEBUG [utils.script.Script] (Timer-2:null) Executing: sudo keytool -genkey -keystore /Users/jburwell/Docu ments/projects/cloudstack/src/cloudstack-basho/client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/classes/cloud.keystore -store pass vmops.com -keypass vmops.com -keyalg RSA -validity 3650 -dname cn=Cloudstack User,ou=0.8.31,o=0.8.31,c=Unknown 2013-02-27 09:52:22,188 WARN [utils.script.Script] (Script-1:null) Interrupting script. 2013-02-27 09:52:22,190 WARN [utils.script.Script] (Timer-2:null) Timed out: sudo keytool -genkey -keystore /Users/jburwell/Docu ments/projects/cloudstack/src/cloudstack-basho/client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/classes/cloud.keystore -store pass vmops.com -keypass vmops.com -keyalg RSA -validity 3650 -dname cn=Cloudstack User,ou=0.8.31,o=0.8.31,c=Unknown . Ou tput is: dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid 2013-02-27 09:52:22,191 WARN [cloud.server.ConfigurationServerImpl] (Timer-2:null) Would use fail-safe keystore to continue. java.io.IOException: Fail to generate certificate!: timeout at com.cloud.server.ConfigurationServerImpl.generateDefaultKeystore(ConfigurationServerImpl.java:490) at com.cloud.server.ConfigurationServerImpl.updateSSLKeystore(ConfigurationServerImpl.java:511) at com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:272) at com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:144) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:8 0) at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:37) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at
[jira] [Updated] (CLOUDSTACK-7247) marvin deployVirtualMachine calls default to hypervisor=XenServer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-7247: - Fix Version/s: 4.5.0 marvin deployVirtualMachine calls default to hypervisor=XenServer - Key: CLOUDSTACK-7247 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7247 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, marvin Affects Versions: 4.5.0 Reporter: John Dilley Assignee: John Dilley Priority: Blocker Fix For: 4.5.0 Lots of failures in marvin since the fix for CLOUDSTACK-7194 now validates that the template hypervisor type and the deployVirtualMachine hypervisor match, or only one specifies a hypervisor. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6862) [Automation] Test case TestDeployvGPUenabledVM.test_deploy_vgpu_enabled_vm faling during BVT
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-6862:
-
Assignee: Sanjay Tripathi
[Automation] Test case TestDeployvGPUenabledVM.test_deploy_vgpu_enabled_vm
faling during BVT
-
Key: CLOUDSTACK-6862
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6862
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.4.0
Reporter: Rayees Namathponnan
Assignee: Sanjay Tripathi
Priority: Blocker
Fix For: 4.4.0
Test case
integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM.test_deploy_vgpu_enabled_vm
failing in BVT
Error Message
Execute cmd: createserviceoffering failed, due to: errorCode: 401,
errorText:unable to verify user credentials and/or request signature
begin captured stdout -
=== TestName: test_deploy_vgpu_enabled_vm | Status : EXCEPTION ===
- end captured stdout --
begin captured logging
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
DEBUG: STARTED : TC: test_deploy_vgpu_enabled_vm :::
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
DEBUG: Payload: {'apiKey':
u'8wj_03oPp3z6PQXsldtXr3ChyTC4UsL9BOx9gRCT30xsgLqo3uQhklIturqaW5KgZPbpy_vkNUd0h8g_hTVs5A',
'command': 'listDomains', 'signature': '8Yh5KlFqCsxhD/NB2fOBHSPL1kI=',
'response': 'json'}
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
DEBUG: Sending GET Cmd : listDomains===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 172.16.88.21
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=8wj_03oPp3z6PQXsldtXr3ChyTC4UsL9BOx9gRCT30xsgLqo3uQhklIturqaW5KgZPbpy_vkNUd0h8g_hTVs5Acommand=listDomainsresponse=jsonsignature=8Yh5KlFqCsxhD%2FNB2fOBHSPL1kI%3D
HTTP/1.1 200 159
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
DEBUG: Response : [{path : u'ROOT', haschild : False, id :
u'6b3a436e-ef1f-11e3-a141-00163e189e44', name : u'ROOT', level : 0}]
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
DEBUG: Payload: {'apiKey':
u'8wj_03oPp3z6PQXsldtXr3ChyTC4UsL9BOx9gRCT30xsgLqo3uQhklIturqaW5KgZPbpy_vkNUd0h8g_hTVs5A',
'name': 'zone-xen', 'command': 'listZones', 'signature':
'Z7nIBao2vEVG1YiHM2kVrh6QcPY=', 'response': 'json'}
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
DEBUG: Sending GET Cmd : listZones===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 172.16.88.21
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?response=jsonapiKey=8wj_03oPp3z6PQXsldtXr3ChyTC4UsL9BOx9gRCT30xsgLqo3uQhklIturqaW5KgZPbpy_vkNUd0h8g_hTVs5Acommand=listZonesname=zone-xensignature=Z7nIBao2vEVG1YiHM2kVrh6QcPY%3D
HTTP/1.1 200 446
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
DEBUG: Response : [{localstorageenabled : False, name : u'zone-xen',
guestcidraddress : u'10.1.1.0/24', tags : [], zonetoken :
u'562e3c93-9149-38c6-8555-de48e3e6c847', dns2 : u'8.8.4.4', dns1 :
u'8.8.8.8', securitygroupsenabled : False, allocationstate : u'Enabled',
internaldns1 : u'172.16.88.7', dhcpprovider : u'VirtualRouter', networktype :
u'Advanced', id : u'ad43d834-dc57-4da5-b3ae-0ef3f106192b', internaldns2 :
u'172.16.88.8'}]
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
DEBUG: Payload: {'apiKey':
u'8wj_03oPp3z6PQXsldtXr3ChyTC4UsL9BOx9gRCT30xsgLqo3uQhklIturqaW5KgZPbpy_vkNUd0h8g_hTVs5A',
'templatefilter': 'featured', 'command': 'listTemplates', 'signature':
'KGHcOyWgw042qhRsMQWkZ7VdUIM=', 'zoneid':
u'ad43d834-dc57-4da5-b3ae-0ef3f106192b', 'response': 'json'}
test_deploy_vgpu_enabled_vm
(integration.smoke.test_deploy_vgpu_enabled_vm.TestDeployvGPUenabledVM):
DEBUG: Sending GET Cmd : listTemplates===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 172.16.88.21
requests.packages.urllib3.connectionpool: DEBUG: GET
[jira] [Commented] (CLOUDSTACK-7051) [Automation] Failed to create SSVM and CPVM in KVM,
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14058710#comment-14058710 ] Sudha Ponnaganti commented on CLOUDSTACK-7051: -- Any update n this ticket. [Automation] Failed to create SSVM and CPVM in KVM, Key: CLOUDSTACK-7051 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7051 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.5.0 Environment: RHEL : 6.3 build : 4.5 Reporter: Rayees Namathponnan Assignee: Kishan Kavala Priority: Blocker Fix For: 4.5.0 Attachments: agent.rar, management-server.rar SSVM and CPVM not creating with latest 4.5 build, copy command failing form agent observed below error in agent log, 2014-07-02 16:14:58,170 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) Execution is successful. 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) Formatting '/mnt/4f3ad80a-b7 96-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8', fmt=qcow2 size=262144 encryption=off clus ter_size=65536 preallocation='off' 2014-07-02 16:14:58,171 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) Executing: qemu-img info --o utput json /mnt/4f3ad80a-b796-3db3-b126-9c12b5b5eafc/48ef9a74-0244-11e4-b040-1a6f7bb0d0a8 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) Exit value is 1 2014-07-02 16:14:58,173 DEBUG [utils.script.Script] (agentRequest-Handler-1:null) info: invalid option -- '-'q emu-img version 0.12.1, Copyright (c) 2004-2008 Fabrice Bellardusage: qemu-img command [command options]QEMU d isk image utilityCommand syntax: check [-f fmt] filename create [-f fmt] [-o options] filename [size] commi t [-f fmt] [-t cache] filename convert [-c] [-p] [-f fmt] [-t cache] [-O output_fmt] [-o options] [-S sparse_ size] filename [filename2 [...]] output_filename info [-f fmt] filename snapshot [-l | -a snapshot | -c snap shot | -d snapshot] filename rebase [-f fmt] [-t cache] [-p] [-u] -b backing_file [-F backing_fmt] filename resize filename [+ | -]sizeCommand parameters: 'filename' is a disk image filename 'fmt' is the disk image f ormat. It is guessed automatically in most cases 'cache' is the cache mode used to write the output disk imag e, the validoptions are: 'none', 'writeback' (default), 'writethrough' and 'unsafe' 'size' is the disk im age size in bytes. Optional suffixes'k' or 'K' (kilobyte, 1024), 'M' (megabyte, 1024k), 'G' (gigabyte, 102 4M)and T (terabyte, 1024G) are supported. 'b' is ignored. 'output_filename' is the destination disk image filename 'output_fmt' is the destination format 'options' is a comma separated list of format specific opti ons in aname=value format. Use -o ? for an overview of the options supported by theused format '-c' i ndicates that target image must be compressed (qcow format only) '-u' enables unsafe rebasing. It is assumed that old and new backing file match exactly. The image doesn't need a working backing file before rebasing in this case (useful for renaming the backing file) '-h' with or without a command shows this help a nd lists the supported formats '-p' show progress of command (only certain commands) '-S' indicates the cons ecutive number of bytes that must contain only zeros for qemu-img to create a sparse image during conver sionParameters to snapshot subcommand: 'snapshot' is the name of the snapshot to create, apply or delete '-a ' applies a snapshot (revert disk to saved state) '-c' creates a snapshot '-d' deletes a snapshot '-l' lists all snapshots in the given imageSupported formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 qed parallels nbd blkdebug host_cdrom host_floppy host_device file -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6444) [Automation] test_01_primary_storage_iscsi failed on test_primary_storage.py - Wrong iscsi path format - it should be /targetIQN/LUN
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041676#comment-14041676
]
Sudha Ponnaganti commented on CLOUDSTACK-6444:
--
I am OOO from 6/23 through 6/27.
[Automation] test_01_primary_storage_iscsi failed on
test_primary_storage.py - Wrong iscsi path format - it should be
/targetIQN/LUN
Key: CLOUDSTACK-6444
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6444
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, XenServer
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Damodar Reddy T
Priority: Critical
Fix For: 4.4.0
Attachments: management-server.log.2014-04-16.gz
Error Message:
Execute cmd: createstoragepool failed, due to: errorCode: 530, errorText:None
begin captured logging
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
STARTED : TC: test_01_primary_storage_iscsi :::
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listZones {}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: zCinw6XM4JSpQF6uNjzREWyHshQ=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
HTTP/1.1 200 735
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
Response: { listzonesresponse : { count:2 ,zone : [
{id:4fbc4494-e655-49b6-bda1-7ad8eb641732,name:test0,dns1:10.223.240.232,dns2:10.223.240.234,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:f0aed2ee-a79d-3608-bae5-09972653a6cf,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]},
{id:55fe83ca-4160-40b2-89cb-63cadf8b90f9,name:test1,dns1:10.223.240.234,dns2:10.223.240.232,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:3973cd3a-d2ed-3242-8431-b40f919051f1,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listPods {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: Q5eN6r9ACb1qiPi7CI3wiB6wh0k=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
HTTP/1.1 200 314
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
Response: { listpodsresponse : { count:1 ,pod : [
{id:d99714b2-7164-4d85-b5a6-c0caf12eb57a,name:test0pod0,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,zonename:test0,gateway:10.223.251.1,netmask:255.255.255.192,startip:10.223.251.4,endip:10.223.251.14,allocationstate:Enabled}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listClusters {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: CGgAerZxK5EJBr34YnPiWBJHqWg=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
[jira] [Commented] (CLOUDSTACK-778) user provided hostname to be specified in vCenter instead of CloudStack generated name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14003488#comment-14003488 ] Sudha Ponnaganti commented on CLOUDSTACK-778: - Can someone respond to this after checking the code. Looks like this is supported only on VMWare. user provided hostname to be specified in vCenter instead of CloudStack generated name -- Key: CLOUDSTACK-778 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-778 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Reporter: haroon abdelrahman Assignee: Venkata Siva Vijayendra Bhamidipati Fix For: 4.2.0 Release Planning: Dev List discussion: unknown Functional Spec: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Allow+user+provided+hostname%2C+internal+VM+name+on+hypervisor+for+guest+VMs Feature Branch: unknown -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6644) Unable to attach Volume to a VM as a System User
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-6644:
-
Assignee: edison su
Unable to attach Volume to a VM as a System User
Key: CLOUDSTACK-6644
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6644
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: IAM
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: edison su
Priority: Blocker
Fix For: 4.4.0
As System User, tried to attach a Volume belonging to an account to a VM
belonging to the same account. Failed with the following error.
Acct[4f0e5b12-d6d8-11e3-952f-06098c000757-system] does not have permission
to perform this operation on these resources
mysql select account_id, uuid from vm_instance where uuid like '%56a4%';
++--+
| account_id | uuid |
++--+
| 3 | 56a488ce-9baf-4d99-8e25-002d565f6731 |
++--+
1 row in set (0.00 sec)
mysql select account_id, uuid from volumes where uuid like '%00585b50%';
++--+
| account_id | uuid |
++--+
| 3 | 00585b50-8c65-4e5b-95ee-853489e5499c |
++--+
1 row in set (0.00 sec)
2014-05-12 13:40:48,618 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-2:ctx-c551e67e ctx-2b2b4ddd ctx-4beab6a0) submit async
job-190, details: AsyncJobVO {id:190, userId: 1, accountId: 1, instanceType:
Volume, instanceId: 11, cmd:
org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
cmdInfo:
{virtualmachineid:56a488ce-9baf-4d99-8e25-002d565f6731,cmdEventType:VOLUME.ATTACH,ctxUserId:1,httpmethod:GET,deviceid:1,apikey:dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ,id:00585b50-8c65-4e5b-95ee-853489e5499c,response:json,ctxDetails:{\com.cloud.storage.Volume\:11,\Volume\:\00585b50-8c65-4e5b-95ee-853489e5499c\,\com.cloud.vm.VirtualMachine\:8},ctxAccountId:1,uuid:00585b50-8c65-4e5b-95ee-853489e5499c,ctxStartEventId:448,signature:euszCT397/kGpCM1fN+GQhTJCe8\u003d},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 6638073284439, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-12 13:40:48,619 DEBUG [c.c.a.ApiServlet]
(catalina-exec-2:ctx-c551e67e ctx-2b2b4ddd ctx-4beab6a0) ===END=== 127.0.0.1
-- GET
apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQcommand=attachVolumedeviceid=1id=00585b50-8c65-4e5b-95ee-853489e5499cresponse=jsonvirtualmachineid=56a488ce-9baf-4d99-8e25-002d565f6731apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQsignature=euszCT397%2FkGpCM1fN%2BGQhTJCe8%3D
2014-05-12 13:40:48,621 DEBUG [c.c.a.ApiServlet]
(catalina-exec-3:ctx-9e956cd7) ===START=== 127.0.0.1 -- GET
apikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQcommand=queryAsyncJobResultjobId=2ef19e77-29af-416f-bc16-f27df1b58e7fresponse=jsonapikey=dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQsignature=O1vnDPmstm6Xa2lEazduvETJkXk%3D
2014-05-12 13:40:48,627 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-45:job-190) Add job-190 into job monitoring
2014-05-12 13:40:48,627 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-45:job-190) Executing AsyncJobVO {id:190, userId: 1,
accountId: 1, instanceType: Volume, instanceId: 11, cmd:
org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin,
cmdInfo:
{virtualmachineid:56a488ce-9baf-4d99-8e25-002d565f6731,cmdEventType:VOLUME.ATTACH,ctxUserId:1,httpmethod:GET,deviceid:1,apikey:dXvODaGH1UvF0WKs63T_wCXsVEs5nFTJaNhBJCGF3sCYwgbuvUaelZf6V8tWjTsyB53LSIT9Wf4UUUQKSz8UXQ,id:00585b50-8c65-4e5b-95ee-853489e5499c,response:json,ctxDetails:{\com.cloud.storage.Volume\:11,\Volume\:\00585b50-8c65-4e5b-95ee-853489e5499c\,\com.cloud.vm.VirtualMachine\:8},ctxAccountId:1,uuid:00585b50-8c65-4e5b-95ee-853489e5499c,ctxStartEventId:448,signature:euszCT397/kGpCM1fN+GQhTJCe8\u003d},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 6638073284439, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-12 13:40:48,642 DEBUG [o.a.c.i.RoleBasedEntityAccessChecker]
(catalina-exec-3:ctx-9e956cd7 ctx-6c73263d
[jira] [Updated] (CLOUDSTACK-796) QA - User Provided hostname to be specified in vCenter instead of CS generated name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-796: Assignee: Kiran Koneti QA - User Provided hostname to be specified in vCenter instead of CS generated name Key: CLOUDSTACK-796 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-796 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Assignee: Kiran Koneti Fix For: 4.2.0 QA tasks to include - QA Test plan should be linked to 41 release - Upload Test results done on feature branch - Also make sure to do sanity testing and upload test results for it for ASF 41 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6679) [Automation] Vm deployment fails with error Could not find suitable Deployment Destination for this VM under any clusters
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-6679. -- Resolution: Not a Problem See comments from prachi [Automation] Vm deployment fails with error Could not find suitable Deployment Destination for this VM under any clusters --- Key: CLOUDSTACK-6679 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6679 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, Management Server Affects Versions: 4.4.0 Environment: vmware 5.0 4.4-forward Reporter: Rayees Namathponnan Assignee: Rayees Namathponnan Priority: Blocker Fix For: 4.4.0 This issue observed with test case integration.component.test_blocker_bugs.TestTemplate.test_01_create_template This test cases creating template from snapshot and deploying VM, Zone1 is vmware zone, and template created from snapshot of vmware vm, but in DB, its store with type: XenServer mysql select * from vm_template where uuid like 4dce%; +-+--+---+--++--+--+-+--+---++-+-++--++-+---+-+--+-+-+-+-++--+--++--+--+-+--+ | id | unique_name | name | uuid | public | featured | type | hvm | bits | url | format | created | removed | account_id | checksum | display_text | enable_password | enable_sshkey | guest_os_id | bootable | prepopulate | cross_zones | extractable | hypervisor_type | source_template_id | template_tag | sort_key | size | state| update_count | updated | dynamically_scalable | +-+--+---+--++--+--+-+--+---++-+-++--++-+---+-+--+-+-+-+-++--+--++--+--+-+--+ | 214 | 214-116-e52835bf-a537-3f13-aa38-164ba85f5801 | Template from snapshot-607C3Z | 4dcecb05-5930-469a-910c-691518bbafef | 1 |0 | USER | 1 | 64 | http://10.223.243.3/userdata/c583b4ad-81fe-4eab-a76d-74976f055e29.ova | OVA | 2014-05-14 01:31:57 | NULL|116 | 855be0d95c60e7abcd73e54a7ac38038 | Template from snapshot | 1 | 0 | 12 |1 | 0 | 0 | 1 | XenServer | NULL | NULL |0 | 2147483648 | Inactive |0 | NULL|0 | +-+--+---+--++--+--+-+--+---++-+-++--++-+---+-+--+-+-+-+-++--+--++--+--+-+--+ 1 row in set (0.00 sec) mysql select uuid,name,hypervisor_type from snapshots; +--++-+ | uuid | name | hypervisor_type | +--++-+ | cf01419c-7a57-42c9-a3b2-863f4f36c713 |
[jira] [Commented] (CLOUDSTACK-5632) [Automation] XenServer - Template deletion fails with error Please specify a template that is not currently being downloaded although the template is completely
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13989714#comment-13989714
]
Sudha Ponnaganti commented on CLOUDSTACK-5632:
--
provide the test script failing so dev can review it
[Automation] XenServer - Template deletion fails with error Please specify a
template that is not currently being downloaded although the template is
completely downloaded, installed and is in ready state
--
Key: CLOUDSTACK-5632
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5632
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.3.0
Environment: xenserver 62
advanced zone
Reporter: Srikanteswararao Talluri
Assignee: Min Chen
Fix For: 4.4.0
Creating this bug as a place holder for the following failures, needs further
analysis,
ContextSuite context=TestTemplateHierarchy:teardown FAILED Warning:
Exception during cleanup : Execute cmd: asyncquery failed, due to: {errorcode
: 530, errortext : u'Please specify a template that is not currently being
downloaded.'}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6498) [Automation] unable to start management server after restart
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-6498: - Assignee: Harikrishna Patnala [Automation] unable to start management server after restart Key: CLOUDSTACK-6498 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6498 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.5.0 Environment: advanced zone xenserer 6.2 Reporter: Srikanteswararao Talluri Assignee: Harikrishna Patnala Priority: Blocker Fix For: 4.5.0 Attachments: log.tar.gz on the daily automation environment, After the zone is deployed , system VMs came up fine. After setting few global settings, I tried to restart management server, it never came up again. I could see some db exceptions related to duplicate keys. I will attach management server logs to this bug for your reference. Caught SQLException when inserting system account com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '1' for key 'PRIMARY' at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) at com.mysql.jdbc.Util.getInstance(Util.java:386) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2415) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2333) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2318) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105) 14761,2-9 96% -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6481) Vhd-util is not copied to xenserver from MS...As a result system VMs fail to start in CS.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13978864#comment-13978864 ] Sudha Ponnaganti commented on CLOUDSTACK-6481: -- which template is being used?? Vhd-util is not copied to xenserver from MS...As a result system VMs fail to start in CS. - Key: CLOUDSTACK-6481 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6481 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup, XenServer Affects Versions: 4.4.0 Environment: Xenserver6.2 added to CS 4.4 Reporter: manasaveloori Priority: Blocker Fix For: 4.4.0 Attachments: management-server.log PXE booted the Xenserver. Added it to CS 4.4. observed that system vms fails to deploy with Exception: 2014-04-23 04:23:46,875 WARN [c.c.h.x.r.XenServerStorageProcessor] (DirectAgent-3:ctx-cf6a380b) Catch Exception com.cloud.utils.exception.CloudRuntimeException for template + due to com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 5cffabad-fb53-27ad-96eb-a1728623dd7c com.cloud.utils.exception.CloudRuntimeException: can not create vdi in sr 5cffabad-fb53-27ad-96eb-a1728623dd7c at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copy_vhd_from_secondarystorage(XenServerStorageProcessor.java:846) at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:962) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:77) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:52) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:542) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:60) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:92) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) 2014-04-23 04:23:46,883 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-3:ctx-cf6a380b) Seq 1-4533998924855246860: Response Received: Checked in xenserver the vhd-util file is missing under /opt/cloud/bin. As work around copied the vhd-util to /opt/cloud/bin. Attaching the log files -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6477) UI: Load Balancing - unable to add Load Balancing rule = error Unable to decode parameter vmidipmap[0].vmip[]; if specifying an object array, please use parameter[
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-6477:
-
Priority: Critical (was: Blocker)
UI: Load Balancing - unable to add Load Balancing rule = error Unable to
decode parameter vmidipmap[0].vmip[]; if specifying an object array, please
use parameter[index].field=XXX, ~
--
Key: CLOUDSTACK-6477
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6477
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.4.0
Reporter: Jessica Wang
Assignee: Jessica Wang
Priority: Critical
Fix For: 4.4.0
Attachments: add_LoadBalancingRule_error_1.PNG
http://10.215.3.26:8080/client/api?command=assignToLoadBalancerRuleresponse=jsonsessionkey=A13u47LsaXQAp3FIHH7NyuTJM8E%3Did=6417255f-50e7-45c3-9b49-f9c54bc34e50vmidipmap%5B0%5D.vmid=f1e1dc35-ef96-405c-af99-1aaf54d54094vmidipmap%5B0%5D.vmip%5B%5D=10.1.1.244_=1398211037075
{
assigntoloadbalancerruleresponse: {
uuidList: [],
errorcode: 430,
cserrorcode: ,
errortext: Unable to decode parameter vmidipmap[0].vmip[]; if
specifying an object array, please use parameter[index].field=XXX, e.g.
userGroupList[0].group=httpGroup
}
}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6475) [Automation] communication between cloudstack agent and MS disconnecting continuously
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13978875#comment-13978875 ] Sudha Ponnaganti commented on CLOUDSTACK-6475: -- Is there any issue with Network?? [Automation] communication between cloudstack agent and MS disconnecting continuously --- Key: CLOUDSTACK-6475 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6475 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.4.0 Environment: RHEL 6.3 Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.4.0 Attachments: Agent_log.rar, management-server.rar This issue is observed during automation, run. communication between cloudstack agent and ms getting disconnected continuously; observed below error in agent log 2014-04-22 04:08:47,867 INFO [cloud.agent.Agent] (AgentShutdownThread:null) Stopping the agent: Reason = sig.kill 2014-04-22 04:10:41,456 INFO [cloud.agent.AgentShell] (main:null) Agent started 2014-04-22 04:10:41,500 INFO [cloud.agent.AgentShell] (main:null) Implementation Version is 4.4.0-SNAPSHOT 2014-04-22 04:10:41,502 INFO [cloud.agent.AgentShell] (main:null) agent.properties found at /etc/cloudstack/agent/agent.properties 2014-04-22 04:10:41,551 INFO [cloud.agent.AgentShell] (main:null) Defaulting to using properties file for storage 2014-04-22 04:10:41,552 INFO [cloud.agent.AgentShell] (main:null) Defaulting to the constant time backoff algorithm 2014-04-22 04:10:41,572 INFO [cloud.utils.LogUtils] (main:null) log4j configuration found at /etc/cloudstack/agent/log4j-cloud.xml 2014-04-22 04:10:41,722 INFO [cloud.agent.Agent] (main:null) id is 0 2014-04-22 04:10:42,501 INFO [kvm.resource.LibvirtComputingResource] (main:null) No libvirt.vif.driver specified. Defaults to BridgeVifDriver. 2014-04-22 04:10:42,590 INFO [cloud.agent.Agent] (main:null) Agent [id = 0 : type = LibvirtComputingResource : zone = 1 : pod = 1 : workers = 5 : host = 10.223.49.195 : port = 8250 2014-04-22 04:10:42,664 INFO [utils.nio.NioClient] (Agent-Selector:null) Connecting to 10.223.49.195:8250 2014-04-22 04:10:42,920 INFO [utils.nio.NioClient] (Agent-Selector:null) SSL: Handshake done 2014-04-22 04:10:42,920 INFO [utils.nio.NioClient] (Agent-Selector:null) Connected to 10.223.49.195:8250 2014-04-22 04:10:42,941 WARN [kvm.resource.LibvirtComputingResource] (Agent-Handler-1:null) Could not read cpuinfo_max_freq 2014-04-22 04:10:43,158 INFO [cloud.serializer.GsonHelper] (Agent-Handler-1:null) Default Builder inited. 2014-04-22 04:10:43,227 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Proccess agent startup answer, agent id = 0 2014-04-22 04:10:43,227 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Set agent id 0 2014-04-22 04:10:43,233 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Startup Response Received: agent id = 0 2014-04-22 04:11:40,925 INFO [cloud.agent.Agent] (Agent-Handler-1:null) Lost connection to the server. Dealing with the remaining commands... 2014-04-22 04:11:42,352 WARN [kvm.resource.KVMHAMonitor] (Thread-4:null) write heartbeat failed: /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 131: echo: write error: Input/output error, retry: 0 2014-04-22 04:11:42,368 WARN [kvm.resource.KVMHAMonitor] (Thread-4:null) write heartbeat failed: /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 131: echo: write error: Input/output error, retry: 1 2014-04-22 04:11:42,383 WARN [kvm.resource.KVMHAMonitor] (Thread-4:null) write heartbeat failed: /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 131: echo: write error: Input/output error, retry: 2 2014-04-22 04:11:42,398 WARN [kvm.resource.KVMHAMonitor] (Thread-4:null) write heartbeat failed: /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 131: echo: write error: Input/output error, retry: 3 2014-04-22 04:11:42,413 WARN [kvm.resource.KVMHAMonitor] (Thread-4:null) write heartbeat failed: /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 131: echo: write error: Input/output error, retry: 4 2014-04-22 04:11:42,414 WARN [kvm.resource.KVMHAMonitor] (Thread-4:null) write heartbeat failed: /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/kvmheartbeat.sh: line 131: echo: write error: Input/output error; reboot the host 2014-04-22 04:11:42,472 WARN [kvm.resource.KVMHAMonitor] (Thread-4:null) write heartbeat failed:
[jira] [Commented] (CLOUDSTACK-6444) [Automation] Fix the script test_primary_storage.py - Wrong iscsi path format - it should be /targetIQN/LUN
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13978879#comment-13978879
]
Sudha Ponnaganti commented on CLOUDSTACK-6444:
--
Aren't these scripts passing before?? What changed now??
[Automation] Fix the script test_primary_storage.py - Wrong iscsi path
format - it should be /targetIQN/LUN
--
Key: CLOUDSTACK-6444
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6444
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Assignee: Srikanteswararao Talluri
Priority: Blocker
Fix For: 4.4.0
Attachments: management-server.log.2014-04-16.gz
Error Message:
Execute cmd: createstoragepool failed, due to: errorCode: 530, errorText:None
begin captured logging
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
STARTED : TC: test_01_primary_storage_iscsi :::
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listZones {}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: zCinw6XM4JSpQF6uNjzREWyHshQ=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
HTTP/1.1 200 735
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listZonessignature=zCinw6XM4JSpQF6uNjzREWyHshQ%3Dresponse=json
Response: { listzonesresponse : { count:2 ,zone : [
{id:4fbc4494-e655-49b6-bda1-7ad8eb641732,name:test0,dns1:10.223.240.232,dns2:10.223.240.234,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:f0aed2ee-a79d-3608-bae5-09972653a6cf,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]},
{id:55fe83ca-4160-40b2-89cb-63cadf8b90f9,name:test1,dns1:10.223.240.234,dns2:10.223.240.232,internaldns1:10.223.240.232,networktype:Basic,securitygroupsenabled:true,allocationstate:Enabled,zonetoken:3973cd3a-d2ed-3242-8431-b40f919051f1,dhcpprovider:VirtualRouter,localstorageenabled:false,tags:[]}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listPods {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: Q5eN6r9ACb1qiPi7CI3wiB6wh0k=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
HTTP/1.1 200 314
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qcommand=listPodssignature=Q5eN6r9ACb1qiPi7CI3wiB6wh0k%3Dzoneid=4fbc4494-e655-49b6-bda1-7ad8eb641732response=json
Response: { listpodsresponse : { count:1 ,pod : [
{id:d99714b2-7164-4d85-b5a6-c0caf12eb57a,name:test0pod0,zoneid:4fbc4494-e655-49b6-bda1-7ad8eb641732,zonename:test0,gateway:10.223.251.1,netmask:255.255.255.192,startip:10.223.251.4,endip:10.223.251.14,allocationstate:Enabled}
] } }
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
sending GET request: listClusters {'zoneid':
u'4fbc4494-e655-49b6-bda1-7ad8eb641732'}
test_01_primary_storage_iscsi
(integration.smoke.test_primary_storage.TestPrimaryStorageServices): DEBUG:
Computed Signature by Marvin: CGgAerZxK5EJBr34YnPiWBJHqWg=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
[jira] [Commented] (CLOUDSTACK-6439) [Automation] Assertion Error: Fix the script test_disk_offerings.py - provision type is not returned by listDiskOfferings response
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13978884#comment-13978884
]
Sudha Ponnaganti commented on CLOUDSTACK-6439:
--
why this test is failing now??it was passing before
[Automation] Assertion Error: Fix the script test_disk_offerings.py -
provision type is not returned by listDiskOfferings response
Key: CLOUDSTACK-6439
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6439
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation
Affects Versions: 4.4.0
Environment: Basic Zone
XenServer
Reporter: Chandan Purushothama
Assignee: Srikanteswararao Talluri
Priority: Blocker
Fix For: 4.4.0
Two Cases needs to be corrected:
1. test_02_create_sparse_type_disk_offering
2. test_04_create_fat_type_disk_offering
=
Assertion Errors:
=
*Assertion Error 1*
Check provisionig type in createServiceOffering
begin captured logging
test_02_create_sparse_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
STARTED : TC: test_02_create_sparse_type_disk_offering :::
test_02_create_sparse_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
sending GET request: createDiskOffering {'name': 'Sparse Type Disk offering',
'disksize': 1, 'displaytext': 'Sparse Type Disk offering'}
test_02_create_sparse_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
Computed Signature by Marvin: m0/TZdrSBwiGRHLEVS5pdjF/y0U=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qname=Sparse+Type+Disk+offeringcommand=createDiskOfferingdisksize=1signature=m0%2FTZdrSBwiGRHLEVS5pdjF%2Fy0U%3Ddisplaytext=Sparse+Type+Disk+offeringresponse=json
HTTP/1.1 200 297
test_02_create_sparse_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qname=Sparse+Type+Disk+offeringcommand=createDiskOfferingdisksize=1signature=m0%2FTZdrSBwiGRHLEVS5pdjF%2Fy0U%3Ddisplaytext=Sparse+Type+Disk+offeringresponse=json
Response: { creatediskofferingresponse : { diskoffering :
{id:ffece54d-6736-4d72-8426-6eeade833db8,name:Sparse Type Disk
offering,displaytext:Sparse Type Disk
offering,disksize:1,created:2014-04-16T15:52:37-0700,iscustomized:false,storagetype:shared,displayoffering:true}
} }
test_02_create_sparse_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
Created Disk offering with ID: ffece54d-6736-4d72-8426-6eeade833db8
test_02_create_sparse_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
sending GET request: listDiskOfferings {'id':
u'ffece54d-6736-4d72-8426-6eeade833db8'}
test_02_create_sparse_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
Computed Signature by Marvin: XtzgOFFqAn/1FdLA2F+/yDvHKbQ=
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.223.240.161
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qid=ffece54d-6736-4d72-8426-6eeade833db8command=listDiskOfferingssignature=XtzgOFFqAn%2F1FdLA2F%2B%2FyDvHKbQ%3Dresponse=json
HTTP/1.1 200 310
test_02_create_sparse_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): DEBUG:
Request:
http://10.223.240.161:8080/client/api?apiKey=MNQSBTYnkNvc4PCMgv7itBuPnuHpnUT_TEJRzzCOZXPL5bl9ihaz0P3TpkK3IW36icuUoFQkySLQkvQ9K6Dh0Qid=ffece54d-6736-4d72-8426-6eeade833db8command=listDiskOfferingssignature=XtzgOFFqAn%2F1FdLA2F%2B%2FyDvHKbQ%3Dresponse=json
Response: { listdiskofferingsresponse : { count:1 ,diskoffering : [
{id:ffece54d-6736-4d72-8426-6eeade833db8,name:Sparse Type Disk
offering,displaytext:Sparse Type Disk
offering,disksize:1,created:2014-04-16T15:52:37-0700,iscustomized:false,storagetype:shared,displayoffering:true}
] } }
test_02_create_sparse_type_disk_offering
(integration.smoke.test_disk_offerings.TestCreateDiskOffering): CRITICAL:
FAILED:
[jira] [Updated] (CLOUDSTACK-5212) Need Support for the LXC for the Report sockets CS-4908
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-5212: - Priority: Critical (was: Blocker) Need Support for the LXC for the Report sockets CS-4908 --- Key: CLOUDSTACK-5212 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5212 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Kiran Koneti Priority: Critical Fix For: 4.4.0 For the report sockets feature we need to provide support for the LXC hypervisor.The support is not yet added. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5212) Need Support for the LXC for the Report sockets CS-4908
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13978903#comment-13978903 ] Sudha Ponnaganti commented on CLOUDSTACK-5212: -- feature need to be enabled for LXC Need Support for the LXC for the Report sockets CS-4908 --- Key: CLOUDSTACK-5212 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5212 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Kiran Koneti Priority: Critical Fix For: 4.4.0 For the report sockets feature we need to provide support for the LXC hypervisor.The support is not yet added. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-3535) No HA actions are performed when a KVM host goes offline
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965421#comment-13965421 ] Sudha Ponnaganti commented on CLOUDSTACK-3535: -- Paul can you confirm that this is actually happening No HA actions are performed when a KVM host goes offline Key: CLOUDSTACK-3535 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, KVM, Management Server Affects Versions: 4.1.0, 4.1.1, 4.2.0 Environment: KVM (CentOS 6.3) with CloudStack 4.1 Reporter: Paul Angus Assignee: edison su Priority: Blocker Fix For: 4.2.0 Attachments: KVM-HA-4.1.1.2013-08-09-v1.patch, extract-management-server.log.2013-08-09, management-server.log.Agent If a KVM host 'goes down', CloudStack does not perform HA for instances which are marked as HA enabled on that host (including system VMs) CloudStack does not show the host as disconnected. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-3535) No HA actions are performed when a KVM host goes offline
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965421#comment-13965421 ] Sudha Ponnaganti edited comment on CLOUDSTACK-3535 at 4/10/14 3:04 PM: --- Paul can you confirm that this is actually working for you was (Author: sudhap): Paul can you confirm that this is actually happening for you No HA actions are performed when a KVM host goes offline Key: CLOUDSTACK-3535 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, KVM, Management Server Affects Versions: 4.1.0, 4.1.1, 4.2.0 Environment: KVM (CentOS 6.3) with CloudStack 4.1 Reporter: Paul Angus Assignee: edison su Priority: Blocker Fix For: 4.2.0 Attachments: KVM-HA-4.1.1.2013-08-09-v1.patch, extract-management-server.log.2013-08-09, management-server.log.Agent If a KVM host 'goes down', CloudStack does not perform HA for instances which are marked as HA enabled on that host (including system VMs) CloudStack does not show the host as disconnected. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-3535) No HA actions are performed when a KVM host goes offline
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965421#comment-13965421 ] Sudha Ponnaganti edited comment on CLOUDSTACK-3535 at 4/10/14 3:04 PM: --- Paul can you confirm that this is actually happening for you was (Author: sudhap): Paul can you confirm that this is actually happening No HA actions are performed when a KVM host goes offline Key: CLOUDSTACK-3535 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, KVM, Management Server Affects Versions: 4.1.0, 4.1.1, 4.2.0 Environment: KVM (CentOS 6.3) with CloudStack 4.1 Reporter: Paul Angus Assignee: edison su Priority: Blocker Fix For: 4.2.0 Attachments: KVM-HA-4.1.1.2013-08-09-v1.patch, extract-management-server.log.2013-08-09, management-server.log.Agent If a KVM host 'goes down', CloudStack does not perform HA for instances which are marked as HA enabled on that host (including system VMs) CloudStack does not show the host as disconnected. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6303) [Automation] [UI] Account creation hang in UI,
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-6303: - Summary: [Automation] [UI] Account creation hang in UI,(was: [UI] Account creation hang in UI, ) [Automation] [UI] Account creation hang in UI, Key: CLOUDSTACK-6303 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6303 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.4.0 Environment: 4.4 build Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.4.0 Steps to reproduce Step 1 : Create advanced zone Step 2 Create account Result Account create failing, observed below api not returning anything http://10.223.49.197:8080/client/api?command=createAccountusername=ryzemail=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0response=jsonsessionkey=on0txPc%2BWiHakJJs1p0AAEmEjW8%3D_=1396029526955 I tried to call below API 10.223.49.197:8096/?command=createAccountusername=ryz2email=r...@r.comfirstname=rlastname=rpassword=ryzdomainid=0ac38f1c-b68b-11e3-8418-52b2d980df8aaccount=ryzaccounttype=0 observed below error in MS log 2014-03-28 10:39:51,862 DEBUG [c.c.u.AccountManagerImpl] (ApiServer-7:ctx-de386625 ctx-316bc686) Creating user: ryz2, accountId: 54 timezon e:null -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-669) Better VM Sync
[ https://issues.apache.org/jira/browse/CLOUDSTACK-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-669. --- Already done in 4.3 Better VM Sync -- Key: CLOUDSTACK-669 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-669 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Reporter: Hari Kannan Assignee: Kelven Yang Fix For: 4.4.0 https://cwiki.apache.org/confluence/display/CLOUDSTACK/VMWare+Enhancements+-+Support+for+DRS+and+VM+HA -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-5535) Do not allow addNetwork to create NIC across VPC tiers and Isolated Networks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-5535. based on review closing Do not allow addNetwork to create NIC across VPC tiers and Isolated Networks - Key: CLOUDSTACK-5535 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5535 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Management Server Affects Versions: 4.3.0 Reporter: Saksham Srivastava Assignee: Saksham Srivastava Priority: Critical Fix For: 4.3.0 addNetworkToVM allows adding any network to VM. Ideally a VM running in isolated Guest Network should not be able to add a VPC tier. A VM running in VPC tier should not be allowed to add another tier A VM running in VPC tier should not be allowed to add another isolated guest network. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-4997) OVS integration is broken
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-4997. OVS integration is broken - Key: CLOUDSTACK-4997 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4997 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.0 Reporter: Murali Reddy Assignee: Murali Reddy Fix For: 4.3.0 OVS integration is broken as network orchestrator will not consult a network element unless its a service provider for a service in the network offering. Prior to 4.2, network orchestrator will blindly loop through all network elements so OVS functionality for GRE overlays used to work. this bug is to make OVS integration work by making it as service provider for 'Connectivity' service. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-3252) An instance deployed using explicit or implicit dedication doesn't generate a usage event
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-3252. -- Resolution: Fixed An instance deployed using explicit or implicit dedication doesn't generate a usage event - Key: CLOUDSTACK-3252 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3252 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 Reporter: Devdeep Singh Assignee: Saksham Srivastava Fix For: 4.3.0 If an instance is deployed using explicit or implicit dedication, or neither of them a usage event isn't generated. It'll be good to have a VM usage event generated so that someone looking at the usage logs can use this information. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-5295) [Automation] Router deployment failed with null pointer exception, while calling VirtualNetworkApplianceManagerImpl.getVpnCidr
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-5295. based on earlier comment and no action taken, closing it. Pl open if this happens again [Automation] Router deployment failed with null pointer exception, while calling VirtualNetworkApplianceManagerImpl.getVpnCidr --- Key: CLOUDSTACK-5295 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5295 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.3.0 Reporter: Rayees Namathponnan Assignee: Sheng Yang Priority: Blocker Fix For: 4.3.0 Attachments: agent1.rar, agent2.rar, management-server.log.2013-11-26.gz, management-server.rar This issue observed in autoamtion environment; many router deployment failed below error 2013-11-27 02:34:02,194 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-36:ctx-73116225 ctx-d59c6c54) Sending network shutdown to VirtualRouter 2013-11-27 02:34:02,196 DEBUG [c.c.n.r.VirtualNetworkApplianceManagerImpl] (Job-Executor-36:ctx-73116225 ctx-d59c6c54) Stopping router VM[DomainRouter|r-586-QA] 2013-11-27 02:34:02,198 DEBUG [c.c.v.VirtualMachineManagerImpl] (Job-Executor-36:ctx-73116225 ctx-d59c6c54) VM is already stopped: VM[DomainRouter|r-586-QA] 2013-11-27 02:34:02,200 DEBUG [c.c.a.ApiServlet] (catalina-exec-7:ctx-436ed958) ===START=== 10.223.240.194 -- GET signature=DFJW4CnPHf9BbR%2BTYevb%2FA8%2BZpM%3DapiKey=1fASWWJnTkiQdjWWd9ex6s pm2-D7xsAQvkXh8vBMHIay-aW6dYeUqWsBoAcK-jkfQKPvBaDJLQDEDra4cfGfaAcommand=queryAsyncJobResultresponse=jsonjobid=cb269b12-6c73-44dd-82aa-1303bf3d33fb 2013-11-27 02:34:02,204 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-36:ctx-73116225 ctx-d59c6c54) Network id=489 is shutdown successfully, cleaning up corresponding resources now. 2013-11-27 02:34:02,209 DEBUG [c.c.n.g.GuestNetworkGuru] (Job-Executor-36:ctx-73116225 ctx-d59c6c54) Releasing vnet for the network id=489 2013-11-27 02:34:02,221 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-36:ctx-73116225 ctx-d59c6c54) Lock is released for network Ntwk[489|Guest|8] as a part of network shutdown 2013-11-27 02:34:02,222 DEBUG [o.a.c.e.o.NetworkOrchestrator] (Job-Executor-36:ctx-73116225 ctx-d59c6c54) Lock is released for network id 489 as a part of network implement 2013-11-27 02:34:02,222 INFO [c.c.v.VirtualMachineManagerImpl] (Job-Executor-36:ctx-73116225 ctx-d59c6c54) Unable to contact resource. com.cloud.exception.AgentUnavailableException: Resource [Host:2] is unreachable: Host 2: Unable to start instance due to null at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1011) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:706) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.start(VirtualNetworkApplianceManagerImpl.java:2667) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startVirtualRouter(VirtualNetworkApplianceManagerImpl.java:1767) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.startRouters(VirtualNetworkApplianceManagerImpl.java:1867) at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.deployVirtualRouterInGuestNetwork(VirtualNetworkApplianceManagerImpl.java:1845) at sun.reflect.GeneratedMethodAccessor300.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.implementNetwork(NetworkOrchestrator.java:960) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.prepare(NetworkOrchestrator.java:1222) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:899) at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:706) at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:552) at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:227) at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209) at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3465) at
[jira] [Reopened] (CLOUDSTACK-3252) An instance deployed using explicit or implicit dedication doesn't generate a usage event
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti reopened CLOUDSTACK-3252: -- An instance deployed using explicit or implicit dedication doesn't generate a usage event - Key: CLOUDSTACK-3252 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3252 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 Reporter: Devdeep Singh Assignee: Saksham Srivastava Fix For: 4.3.0 If an instance is deployed using explicit or implicit dedication, or neither of them a usage event isn't generated. It'll be good to have a VM usage event generated so that someone looking at the usage logs can use this information. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-5343) Volume limit applied to project/account does not count root disks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-5343. Reopen if this happens again Volume limit applied to project/account does not count root disks - Key: CLOUDSTACK-5343 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5343 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.3.0 Reporter: Gaurav Aradhye Assignee: Prachi Damle Fix For: 4.3.0 1. Create any project or account. 2. Set the volume limit as 1. 3. Deploy an instance without data disk in project/account. 4. Now you can see the root disk in the volumes, but if you list the account/project, then the volume count still shows as 0. 5. Now add new data disk. 6. Check volume count, now it shows it as 1 (But it should have shown as 2, and it should have failed at this stage only saying limit exceeded.) 7. Add another data disk (Now it will fail) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-4676) [Baremetal] baremetal hostename should not be fixed in kickstart file
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-4676: - Fix Version/s: (was: 4.3.0) [Baremetal] baremetal hostename should not be fixed in kickstart file Key: CLOUDSTACK-4676 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4676 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 Reporter: angeline shen Assignee: frank zhang since baremetal hostname is fixed in kickstart file, if baremetal server choose same template, hostnames are all the same. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Reopened] (CLOUDSTACK-4676) [Baremetal] baremetal hostename should not be fixed in kickstart file
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti reopened CLOUDSTACK-4676: -- [Baremetal] baremetal hostename should not be fixed in kickstart file Key: CLOUDSTACK-4676 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4676 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 Reporter: angeline shen Assignee: frank zhang since baremetal hostname is fixed in kickstart file, if baremetal server choose same template, hostnames are all the same. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5883) unable to copy vmware routing template to primary storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13905936#comment-13905936 ] Sudha Ponnaganti commented on CLOUDSTACK-5883: -- Praveena, The template you are using is incorrect. You need to use the one from download.cloud.com thanks /sudha unable to copy vmware routing template to primary storage - Key: CLOUDSTACK-5883 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5883 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Environment: CloudStack branch 4.3, 9ed4ab731fc5d722e3e0b819958ec8a2f4beccdb vCenter vApp: vSphere 5.1 Hypervisor: VMware ESXi, 5.1.0, 799733 Reporter: Hugo Trippaers Assignee: Animesh Chaturvedi Priority: Blocker Fix For: 4.3.0 The following error is observed while doing a clean installation: 2014-01-16 10:22:00,521 ERROR [c.c.s.r.VmwareStorageProcessor] (DirectAgent-6:ctx-a6667180 10.200.23.49) Unable to copy templa te to primary storage due to exception:Exception: javax.xml.ws.soap.SOAPFaultException Message: Required parameter spec is missing while parsing call information for method ImportVApp at line 1, column 110 while parsing SOAP body at line 1, column 102 while parsing SOAP envelope at line 1, column 38 while parsing HTTP request for method importVApp on object of type vim.ResourcePool at line 1, column 0 javax.xml.ws.soap.SOAPFaultException: Required parameter spec is missing while parsing call information for method ImportVApp at line 1, column 110 while parsing SOAP body at line 1, column 102 while parsing SOAP envelope at line 1, column 38 while parsing HTTP request for method importVApp on object of type vim.ResourcePool at line 1, column 0 at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:119) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-1466) [Automation] Limit Resources on domains/accounts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-1466: - Priority: Critical (was: Major) [Automation] Limit Resources on domains/accounts - Key: CLOUDSTACK-1466 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1466 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.1.0 Reporter: Girish Shilamkar Priority: Critical Fix For: 4.3.0 Attachments: LimitResourcesTestPlan1.xlsx Automate attached test plan for feature - Limit resources on domain/accounts (cpu/memory/primary storage/secondary storage) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-1859) Automate test cases for IPV6 Support on Shared Network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-1859: - Affects Version/s: 4.2.0 Automate test cases for IPV6 Support on Shared Network -- Key: CLOUDSTACK-1859 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1859 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Sangeetha Hariharan Priority: Minor Fix For: Future Automate test cases for IPV6 Support on Shared Network. Test plan for this feature can be found in - https://cwiki.apache.org/confluence/display/CLOUDSTACK/Ipv6+Test+Cases -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-1859) Automate test cases for IPV6 Support on Shared Network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-1859: - Priority: Minor (was: Major) Automate test cases for IPV6 Support on Shared Network -- Key: CLOUDSTACK-1859 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1859 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: Sangeetha Hariharan Priority: Minor Fix For: Future Automate test cases for IPV6 Support on Shared Network. Test plan for this feature can be found in - https://cwiki.apache.org/confluence/display/CLOUDSTACK/Ipv6+Test+Cases -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-1833) Automation: Sanity Marvin tests are checked in by Nitin - Need to Extend it
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-1833: - Priority: Critical (was: Major) Automation: Sanity Marvin tests are checked in by Nitin - Need to Extend it --- Key: CLOUDSTACK-1833 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1833 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Assignee: Gaurav Aradhye Priority: Critical Fix For: 4.3.0 Test plan is posted on Wiki -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-2225) Automation - Add Automation for QuickView and Table widgent
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2225: - Priority: Trivial (was: Major) Automation - Add Automation for QuickView and Table widgent --- Key: CLOUDSTACK-2225 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2225 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Sudha Ponnaganti Priority: Trivial Fix For: 4.3.0 Add automation for this feature -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-2226) Automation: Add Automation for User and Domain admin can change his password
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2226: - Affects Version/s: 4.2.0 Automation: Add Automation for User and Domain admin can change his password Key: CLOUDSTACK-2226 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2226 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Priority: Critical Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-2226) Automation: Add Automation for User and Domain admin can change his password
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2226: - Priority: Critical (was: Major) Automation: Add Automation for User and Domain admin can change his password Key: CLOUDSTACK-2226 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2226 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Priority: Critical Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-2225) Automation - Add Automation for QuickView and Table widgent
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13887879#comment-13887879 ] Sudha Ponnaganti commented on CLOUDSTACK-2225: -- not sure if automation can be added to this Automation - Add Automation for QuickView and Table widgent --- Key: CLOUDSTACK-2225 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2225 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Sudha Ponnaganti Priority: Trivial Fix For: 4.3.0 Add automation for this feature -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-2228) Automation - Add automation for EC2 Query API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2228: - Priority: Critical (was: Major) Automation - Add automation for EC2 Query API - Key: CLOUDSTACK-2228 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2228 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: AWSAPI Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Priority: Critical Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-2228) Automation - Add automation for EC2 Query API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2228: - Affects Version/s: 4.2.0 Automation - Add automation for EC2 Query API - Key: CLOUDSTACK-2228 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2228 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: AWSAPI Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Priority: Critical Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-2227) [Automation] Add Automation for Egress firewall rules for guest network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2227: - Affects Version/s: 4.2.0 [Automation] Add Automation for Egress firewall rules for guest network --- Key: CLOUDSTACK-2227 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2227 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Network Devices Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Priority: Critical Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-2227) [Automation] Add Automation for Egress firewall rules for guest network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2227: - Priority: Critical (was: Major) [Automation] Add Automation for Egress firewall rules for guest network --- Key: CLOUDSTACK-2227 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2227 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Network Devices Affects Versions: 4.2.0 Reporter: Sudha Ponnaganti Priority: Critical Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-2229) Automation: Add Automation for resize volume feature
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2229: - Priority: Critical (was: Major) Automation: Add Automation for resize volume feature Key: CLOUDSTACK-2229 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2229 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Reporter: Sudha Ponnaganti Assignee: Srikanteswararao Talluri Priority: Critical Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-2248) Automation: Add automation for Better VM Sync
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2248: - Priority: Critical (was: Major) Automation: Add automation for Better VM Sync - Key: CLOUDSTACK-2248 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2248 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Reporter: Sudha Ponnaganti Priority: Critical Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CLOUDSTACK-4875) VMWARE: vCenter 5.5 - SYSTEM VM: Unable to create deployment for VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti closed CLOUDSTACK-4875.
VMWARE: vCenter 5.5 - SYSTEM VM: Unable to create deployment for VM
---
Key: CLOUDSTACK-4875
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4875
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: SystemVM, VMware
Affects Versions: 4.2.1
Environment: Master with vCenter 5.5 / ESXi 5.5
Reporter: Parth Jagirdar
Assignee: Likitha Shetty
Priority: Blocker
Fix For: 4.3.0
Attachments: VC5.5.jpg, catalina.out, management-server.log
Unable to launch system VM's
See attached logs
2013-10-15 13:31:40,061 DEBUG [cloud.storage.VolumeManagerImpl]
(consoleproxy-1:null) Unable to create
Vol[2|vm=2|ROOT]:java.lang.RuntimeException: File
[803eb6157bb83df98d96c4da27252fa8] ROOT-2/ROOT-2.vmdk was not found
2013-10-15 13:31:40,061 INFO [cloud.vm.VirtualMachineManagerImpl]
(consoleproxy-1:null) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:1] is
unreachable: Unable to create Vol[2|vm=2|ROOT]:java.lang.RuntimeException:
File [803eb6157bb83df98d96c4da27252fa8] ROOT-2/ROOT-2.vmdk was not found
at
com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2566)
at
com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2617)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:889)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:571)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManagerImpl.java:556)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyManagerImpl.java:928)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:1672)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:157)
at
com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111)
at
com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
at
com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)
at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-10-15 13:31:40,068 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(consoleproxy-1:null) Cleaning up resources for the vm
VM[ConsoleProxy|v-2-VM] in Starting state
type TEMPLATE copyAsync inspecting dest type VOLUME
2013-10-15 13:33:00,630 DEBUG [agent.transport.Request] (secstorage-1:null)
Seq 1-401276957: Waiting for Seq 401276956 Scheduling: { Cmd , MgmtId:
15929225863658, via: 1, Ver: v1, Flags: 100111,
[{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:b8766e32c0c838539a8f75c2cc62a30b,origUrl:http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova,uuid:e1eb1bf2-35c3-11e3-a10c-0e7ccfd961ea,id:8,format:OVA,accountId:1,checksum:8fde62b1089e5844a9cd3b9b953f9596,hvm:false,displayText:SystemVM
Template
[jira] [Commented] (CLOUDSTACK-5881) No QA running on jenkins.buildacloud.org
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13875339#comment-13875339 ] Sudha Ponnaganti commented on CLOUDSTACK-5881: -- Automation has been running at http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-smoke-matrix/1141/ Current failures is Stop VM is failing on Xen. Fix is being checked in and test results will be posted. No QA running on jenkins.buildacloud.org Key: CLOUDSTACK-5881 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5881 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: sebastien goasguen Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.3.0 There are no integration tests running on jenkins: http://jenkins.buildacloud.org/view/cloudstack-qa/ This means that 4.3 is untested... -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5881) No QA running on jenkins.buildacloud.org
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13875367#comment-13875367 ] Sudha Ponnaganti commented on CLOUDSTACK-5881: -- Also our lab has been running Daily regression and smoke tests - we can post them for community review. No QA running on jenkins.buildacloud.org Key: CLOUDSTACK-5881 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5881 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: sebastien goasguen Assignee: Srikanteswararao Talluri Priority: Blocker Fix For: 4.3.0 There are no integration tests running on jenkins: http://jenkins.buildacloud.org/view/cloudstack-qa/ This means that 4.3 is untested... -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5868) Default templates are still referring to 32 bit templates in DB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-5868: - Assignee: Sateesh Chodapuneedi Default templates are still referring to 32 bit templates in DB --- Key: CLOUDSTACK-5868 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5868 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template Affects Versions: 4.3.0 Environment: All HVs Reporter: Sudha Ponnaganti Assignee: Sateesh Chodapuneedi Priority: Blocker Fix For: 4.3.0 Default template location is referring to older templates. Need to switch to 4.3 ++---+--+++-+ | id | name | bits | url | type | hypervisor_type | ++---+--+++-+ | 1 | SystemVM Template (XenServer) | 32 | http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2 | SYSTEM | XenServer | | 8 | SystemVM Template (vSphere) | 32 | http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova | SYSTEM | VMware | ++---+--+++-+ -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CLOUDSTACK-5868) Default templates are still referring to 32 bit templates in DB
Sudha Ponnaganti created CLOUDSTACK-5868: Summary: Default templates are still referring to 32 bit templates in DB Key: CLOUDSTACK-5868 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5868 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Template Affects Versions: 4.3.0 Environment: All HVs Reporter: Sudha Ponnaganti Priority: Blocker Fix For: 4.3.0 Default template location is referring to older templates. Need to switch to 4.3 ++---+--+++-+ | id | name | bits | url | type | hypervisor_type | ++---+--+++-+ | 1 | SystemVM Template (XenServer) | 32 | http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2 | SYSTEM | XenServer | | 8 | SystemVM Template (vSphere) | 32 | http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova | SYSTEM | VMware | ++---+--+++-+ -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5868) Default templates are still referring to older templates in DB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-5868: - Summary: Default templates are still referring to older templates in DB (was: Default templates are still referring to 32 bit templates in DB) Default templates are still referring to older templates in DB -- Key: CLOUDSTACK-5868 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5868 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Template Affects Versions: 4.3.0 Environment: All HVs Reporter: Sudha Ponnaganti Assignee: Sateesh Chodapuneedi Priority: Blocker Fix For: 4.3.0 Default template location is referring to older templates. Need to switch to 4.3 ++---+--+++-+ | id | name | bits | url | type | hypervisor_type | ++---+--+++-+ | 1 | SystemVM Template (XenServer) | 32 | http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2 | SYSTEM | XenServer | | 8 | SystemVM Template (vSphere) | 32 | http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova | SYSTEM | VMware | ++---+--+++-+ -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CLOUDSTACK-5786) [Storage Migration] If the tags on the destination storage pool do not match the disk offering with which a volume is created; migration is allowed.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-5786. [Storage Migration] If the tags on the destination storage pool do not match the disk offering with which a volume is created; migration is allowed. Key: CLOUDSTACK-5786 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5786 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Environment: MSbuild 1/2/2014 vcenter 5.5 host 1host 2 ESXi 5.5 Reporter: angeline shen Assignee: Likitha Shetty Priority: Critical Fix For: 4.3.0 Attachments: management-server(3).log.gz, management-server(3).log.gz, vm10.png 1. SO 512tag1 storage tag: tag1 4 primary storage: PC1: tag3PC2: tag3PZ3: tag1 PZ4: 2.deploy VM 512tag1 with disk. ROOT vol on PZ3DATA vol on PC1 3. VM stop.ROOT vol volume migrate shows PZ4 (unsuitable) Migration FAIL 4. DATA vol volume migrate shows 6 primary storage PZ3 Migration FAIL -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CLOUDSTACK-5537) RabbitMQ EventBus integration is broken after spring modualarization
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-5537. RabbitMQ EventBus integration is broken after spring modualarization Key: CLOUDSTACK-5537 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5537 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Murali Reddy Assignee: Murali Reddy Fix For: 4.3.0 RabbitMQ EventBus integration is broken after spring modualarization. 'ComponentContext.getComponent(EventBus.class)' is not injecting RabbitMQ class that implements 'EventBus' interface. Also this bug is track, the necessary configuration changes required to enable the plug-in in 4.3 and above. Prescribed way of enabling rabbitMQ in 4.2 does not work any more after spring modularisation changes. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CLOUDSTACK-5012) Bad data inserted into physical network labels for Zone Create Wizard using VMWare
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-5012. Bad data inserted into physical network labels for Zone Create Wizard using VMWare -- Key: CLOUDSTACK-5012 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5012 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 Reporter: Jim Leary Assignee: Damodar Reddy T Priority: Critical Fix For: 4.3.0 When using the Zone create wizard and choosing VMWare, the physical network labels contain additional data, rendering any attempt to create a VMWare cluster unsuccessful. The Zone wizard must be cancelled and the physical network labels corrected, then manually create the cluster, primary and secondary storage for the Zone to function correctly. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CLOUDSTACK-5460) Getting error as Template 5 has not been completely downloaded to zone 1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-5460. Getting error as Template 5 has not been completely downloaded to zone 1 -- Key: CLOUDSTACK-5460 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5460 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Environment: CENTOS, TEMPLATE Reporter: rashid Assignee: Koushik Das Fix For: 4.3.0 Description CentOS 5.6(64-bit) no GUI (XenServer) HypervisorXenServer XenServerTools Version 6.1+ Type BUILTIN Ready No Status Eventhough after above status, still Template is listing while Vm provisioning. When tried further to create a vm, with that CENTOS template, got error as Template 5 has not been completely downloaded to zone 1 logs pasted below. INFO [c.c.a.m.AgentManagerImpl] (AgentMonitor-1:ctx-feb49ee0) Found the following agents behind on ping: [1] INFO [c.c.a.m.AgentManagerImpl] (AgentTaskPool-11:ctx-6a4f0e90) Investigating why host 1 has disconnected with event PingTimeout INFO [c.c.a.m.AgentManagerImpl] (AgentTaskPool-11:ctx-6a4f0e90) The state determined is Up INFO [c.c.a.m.AgentManagerImpl] (AgentTaskPool-11:ctx-6a4f0e90) Agent is determined to be up and running WARN [o.a.c.alerts] (CapacityChecker:ctx-c249e644) alertType:: 24 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: System Alert: Number of unallocated shared network IPs is low in availability zone NEWZONE ERROR [c.c.a.ApiServer] (734737616@qtp-452904833-9:ctx-56f15d31 ctx-7a92d786) unhandled exception executing api command: deployVirtualMachine com.cloud.utils.exception.CloudRuntimeException: Template 5 has not been completely downloaded to zone 1 at com.cloud.template.TemplateManagerImpl.getTemplateSize(TemplateManagerImpl.java:1715) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy158.getTemplateSize(Unknown Source) at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.allocateTemplatedVolume(VolumeOrchestrator.java:638) at com.cloud.vm.VirtualMachineManagerImpl$1.doInTransactionWithoutResult(VirtualMachineManagerImpl.java:401) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:25) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:21) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.vm.VirtualMachineManagerImpl.allocate(VirtualMachineManagerImpl.java:379) at org.apache.cloudstack.engine.orchestration.CloudOrchestrator.createVirtualMachine(CloudOrchestrator.java:217) at com.cloud.vm.UserVmManagerImpl$3.doInTransaction(UserVmManagerImpl.java:3043) at com.cloud.vm.UserVmManagerImpl$3.doInTransaction(UserVmManagerImpl.java:2959) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.vm.UserVmManagerImpl.commitUserVm(UserVmManagerImpl.java:2959) at com.cloud.vm.UserVmManagerImpl.createVirtualMachine(UserVmManagerImpl.java:2923) at com.cloud.vm.UserVmManagerImpl.createBasicSecurityGroupVirtualMachine(UserVmManagerImpl.java:2361) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at
[jira] [Commented] (CLOUDSTACK-5460) Getting error as Template 5 has not been completely downloaded to zone 1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13865957#comment-13865957 ] Sudha Ponnaganti commented on CLOUDSTACK-5460: -- Rashid, can you review and respond if this is still a problem thanks /sudha Getting error as Template 5 has not been completely downloaded to zone 1 -- Key: CLOUDSTACK-5460 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5460 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Environment: CENTOS, TEMPLATE Reporter: rashid Assignee: Koushik Das Fix For: 4.3.0 Description CentOS 5.6(64-bit) no GUI (XenServer) HypervisorXenServer XenServerTools Version 6.1+ Type BUILTIN Ready No Status Eventhough after above status, still Template is listing while Vm provisioning. When tried further to create a vm, with that CENTOS template, got error as Template 5 has not been completely downloaded to zone 1 logs pasted below. INFO [c.c.a.m.AgentManagerImpl] (AgentMonitor-1:ctx-feb49ee0) Found the following agents behind on ping: [1] INFO [c.c.a.m.AgentManagerImpl] (AgentTaskPool-11:ctx-6a4f0e90) Investigating why host 1 has disconnected with event PingTimeout INFO [c.c.a.m.AgentManagerImpl] (AgentTaskPool-11:ctx-6a4f0e90) The state determined is Up INFO [c.c.a.m.AgentManagerImpl] (AgentTaskPool-11:ctx-6a4f0e90) Agent is determined to be up and running WARN [o.a.c.alerts] (CapacityChecker:ctx-c249e644) alertType:: 24 // dataCenterId:: 1 // podId:: null // clusterId:: null // message:: System Alert: Number of unallocated shared network IPs is low in availability zone NEWZONE ERROR [c.c.a.ApiServer] (734737616@qtp-452904833-9:ctx-56f15d31 ctx-7a92d786) unhandled exception executing api command: deployVirtualMachine com.cloud.utils.exception.CloudRuntimeException: Template 5 has not been completely downloaded to zone 1 at com.cloud.template.TemplateManagerImpl.getTemplateSize(TemplateManagerImpl.java:1715) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy158.getTemplateSize(Unknown Source) at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.allocateTemplatedVolume(VolumeOrchestrator.java:638) at com.cloud.vm.VirtualMachineManagerImpl$1.doInTransactionWithoutResult(VirtualMachineManagerImpl.java:401) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:25) at com.cloud.utils.db.TransactionCallbackWithExceptionNoReturn.doInTransaction(TransactionCallbackWithExceptionNoReturn.java:21) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.vm.VirtualMachineManagerImpl.allocate(VirtualMachineManagerImpl.java:379) at org.apache.cloudstack.engine.orchestration.CloudOrchestrator.createVirtualMachine(CloudOrchestrator.java:217) at com.cloud.vm.UserVmManagerImpl$3.doInTransaction(UserVmManagerImpl.java:3043) at com.cloud.vm.UserVmManagerImpl$3.doInTransaction(UserVmManagerImpl.java:2959) at com.cloud.utils.db.Transaction.execute(Transaction.java:37) at com.cloud.vm.UserVmManagerImpl.commitUserVm(UserVmManagerImpl.java:2959) at com.cloud.vm.UserVmManagerImpl.createVirtualMachine(UserVmManagerImpl.java:2923) at com.cloud.vm.UserVmManagerImpl.createBasicSecurityGroupVirtualMachine(UserVmManagerImpl.java:2361) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
[jira] [Closed] (CLOUDSTACK-2913) Spurious error message during install at the end of the RPM build process.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-2913. pl reopen if this is still a problem Spurious error message during install at the end of the RPM build process. -- Key: CLOUDSTACK-2913 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2913 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.1.0 Environment: Centos. Reporter: Ron Wheeler Assignee: Rayees Namathponnan Priority: Blocker Labels: newbie Fix For: 4.3.0 While following the installation I got an error message at the end. Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.xrJFTd + umask 022 + cd /root/apache-cloudstack-4.1.0-src/packaging/centos63/../../dist/rpmbuild/BUILD + cd cloudstack-4.1.0 + '[' /root/apache-cloudstack-4.1.0-src/dist/rpmbuild/BUILDROOT/cloudstack-4.1.0-0.el6.x86_64 '!=' / ']' + rm -rf /root/apache-cloudstack-4.1.0-src/dist/rpmbuild/BUILDROOT/cloudstack-4.1.0-0.el6.x86_64 + exit 0 error: File /root/apache-cloudstack-4.1.0-src/dist/rpmbuild/ is not a regular file. The error reports a true fact but I am not sure why this is seen to be an error and why this was reported. It is unclear if the build actually finished but I do have 6 files. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13861532#comment-13861532 ] Sudha Ponnaganti commented on CLOUDSTACK-5709: -- Closing this as Nux has confirmed that it is working fine with revised version of KVM -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Friday, January 03, 2014 12:33 AM To: d...@cloudstack.apache.org Subject: RE: [VOTE] 3rd round of voting for ASF 4.2.1 RC On 03.01.2014 07:40, Nux! wrote: Guys, this is really confusing! First of all I could swear I had this feature working on me previously on a similar setup, second of all why has your colleague Sadhu said this is working[1]? Also Andrei Mikhailovsky claims in this same thread the feature is working, though he is facing other issues (launching new VMs from volume backups/snapshots). Ok, I think I got it. For EL6 (CentOS6) users the workaround is to use a patched version of KVM, then all the features start working (btw VM snapshots could work as well with this!). The confusion comes from the fact the issue is not present in Ubuntu latest for example since they package a newer kvm, so this differs from one distro to another. With the version from RHEV everything worked great and I'll test this soon with GlusterFS shared mount point as well. More here https://issues.apache.org/jira/browse/CLOUDSTACK-5709?focusedCommentId=13861329page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13861329 -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro Snapshots fail on ACS 4.2.1 SNAPSHOT Key: CLOUDSTACK-5709 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Snapshot Affects Versions: 4.2.1 Environment: CentOS 6.5 HV, NFS primary secondary storage Reporter: Nux Assignee: edison su Labels: fail, kvm, snapshot Fix For: 4.2.1 Snapshots fail and get stuck in Created on primary. Logs with Basic Zone install (after the runbook): http://tmp.nux.ro/t9P-snapfail.txt Logs with the same problem but with Adv zone and Shared Mount Point (glusterfs) as primary storage: http://tmp.nux.ro/T94-ACSgluster.txt AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-5709. -- Resolution: Fixed Updated KVM is needed Snapshots fail on ACS 4.2.1 SNAPSHOT Key: CLOUDSTACK-5709 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Snapshot Affects Versions: 4.2.1 Environment: CentOS 6.5 HV, NFS primary secondary storage Reporter: Nux Assignee: edison su Labels: fail, kvm, snapshot Fix For: 4.2.1 Snapshots fail and get stuck in Created on primary. Logs with Basic Zone install (after the runbook): http://tmp.nux.ro/t9P-snapfail.txt Logs with the same problem but with Adv zone and Shared Mount Point (glusterfs) as primary storage: http://tmp.nux.ro/T94-ACSgluster.txt AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-5709: - Priority: Major (was: Blocker) Snapshots fail on ACS 4.2.1 SNAPSHOT Key: CLOUDSTACK-5709 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Snapshot Affects Versions: 4.2.1 Environment: CentOS 6.5 HV, NFS primary secondary storage Reporter: Nux Assignee: edison su Labels: fail, kvm, snapshot Fix For: 4.2.1 Snapshots fail and get stuck in Created on primary. Logs with Basic Zone install (after the runbook): http://tmp.nux.ro/t9P-snapfail.txt Logs with the same problem but with Adv zone and Shared Mount Point (glusterfs) as primary storage: http://tmp.nux.ro/T94-ACSgluster.txt AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-5709: - Priority: Blocker (was: Major) Snapshots fail on ACS 4.2.1 SNAPSHOT Key: CLOUDSTACK-5709 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Snapshot Affects Versions: 4.2.1 Environment: CentOS 6.5 HV, NFS primary secondary storage Reporter: Nux Assignee: edison su Priority: Blocker Labels: fail, kvm, snapshot Fix For: 4.2.1 Snapshots fail and get stuck in Created on primary. Logs with Basic Zone install (after the runbook): http://tmp.nux.ro/t9P-snapfail.txt Logs with the same problem but with Adv zone and Shared Mount Point (glusterfs) as primary storage: http://tmp.nux.ro/T94-ACSgluster.txt AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (CLOUDSTACK-4308) [Snapshot][KVM] UI - KVM.snapshot.enabled=FALSE UI should not allow setup recurring snapshot
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-4308. [Snapshot][KVM] UI - KVM.snapshot.enabled=FALSE UI should not allow setup recurring snapshot - Key: CLOUDSTACK-4308 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4308 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API Affects Versions: 4.2.0 Environment: 4.2 MS, hypervisor: KVM, Reporter: Fang Wang Assignee: Jessica Wang Fix For: 4.2.0 KVM: the default snapshot setting for 4.2 MS has a global flag: kvm.snapshot.enabled default value is set to FALSE. With this default setting, we should disable the recurring snapshot from UI. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-5709: - Fix Version/s: 4.2.1 Snapshots fail on ACS 4.2.1 SNAPSHOT Key: CLOUDSTACK-5709 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Snapshot Affects Versions: 4.2.1 Environment: CentOS 6.5 HV, NFS primary secondary storage Reporter: Nux Labels: fail, kvm, snapshot Fix For: 4.2.1 Snapshots fail and get stuck in Created on primary. Logs with Basic Zone install (after the runbook): http://tmp.nux.ro/t9P-snapfail.txt Logs with the same problem but with Adv zone and Shared Mount Point (glusterfs) as primary storage: http://tmp.nux.ro/T94-ACSgluster.txt AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13859981#comment-13859981 ] Sudha Ponnaganti commented on CLOUDSTACK-5709: -- CentOS 6.5 is nor supported yet right?? Also need to review edison's comments from below mail thread to understand the actual issue. -Original Message- From: Nux! [mailto:n...@li.nux.ro] Sent: Monday, December 23, 2013 6:35 AM To: d...@cloudstack.apache.org Subject: Re: [VOTE] 3rd round of voting for ASF 4.2.1 RC On 23.12.2013 05:42, Abhinandan Prateek wrote: It gives me immense pleasure to inform that the vote to label this ASF 4.2.1 RC as the GA release has been passed with following stats: Can someone check KVM volume snapshots before declaring this GA? It's been consistently broken for me in 4.2.1-SNAPSHOT with NFS as well as GlusterFS shared mount point. It was working in 4.2.0 afaicr. In the ACS release(since 4.0), KVM snapshot only works when CLVM is used as primary storage, otherwise, taking snapshot in KVM will fail, as there is no formal way to backup snapshot from primary storage to secondary storage. I've sent several emails about this as well as bothering people in CLOUDSTACK-5393. http://www.mail-archive.com/dev@cloudstack.apache.org/msg20123.html HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro Snapshots fail on ACS 4.2.1 SNAPSHOT Key: CLOUDSTACK-5709 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Snapshot Affects Versions: 4.2.1 Environment: CentOS 6.5 HV, NFS primary secondary storage Reporter: Nux Labels: fail, kvm, snapshot Fix For: 4.2.1 Snapshots fail and get stuck in Created on primary. Logs with Basic Zone install (after the runbook): http://tmp.nux.ro/t9P-snapfail.txt Logs with the same problem but with Adv zone and Shared Mount Point (glusterfs) as primary storage: http://tmp.nux.ro/T94-ACSgluster.txt AFAIK this is a 4.2.1 release blocker. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5665) XEN patch/hotfix certification - XS 6.0.2 XS602E030 patch installation fail
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-5665:
-
Description:
XEN hotfix installation procedure
1. Hosts master slave installed with
XS 6.0.2 base + Hotfix XS602E001 to XS602E029 + CSPs
2. Basic zone with cluster of above master slave hosts
security group default with NO security rules
Deploy two VMs
3. MS: master host put to maintenance mode - VMs migrate to slave host
4. MS: unmanage cluster
5. master host: install hotfix XS602E030 + CSP , reboot master
6. MS: master host cancel maintenance mode
7. MS: manage cluster
8. MS: slave host put to maintenance mode, VMs FAIL migrate to master
Unable to complete hotfix installation
2013-12-26 16:51:25,307 INFO [xen.resource.CitrixResourceBase]
(DirectAgent-56:null) VM does not exist on
XenServerc6c75483-b35b-4a7c-9e2d-2274e34dd437
2013-12-26 16:51:25,307 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-56:null) Seq 1-265617550: Response Received:
2013-12-26 16:51:25,307 DEBUG [agent.transport.Request] (DirectAgent-56:null)
Seq 1-265617550: Processing: { Ans: , MgmtId: 7692017993539, via: 1, Ver: v1,
Flags: 110, [{com.cloud.agent.api.StopAnswer:{result:true,details:VM
does not exist,wait:0}}] }
2013-12-26 16:51:25,307 DEBUG [agent.manager.AgentAttache]
(DirectAgent-56:null) Seq 1-265617550: Unable to find listener.
2013-12-26 16:51:25,307 DEBUG [agent.manager.AgentAttache]
(DirectAgent-56:null) Seq 1-265617550: No more commands found
2013-12-26 16:51:25,313 DEBUG [vm.dao.VMInstanceDaoImpl] (HA-Worker-3:work-19)
Unable to update VM[DomainRouter|r-4-VM]: DB Data={Host=4; State=Running;
updated=13; time=Thu Dec 26 16:51:25 PST 2013} New Data: {Host=4;
State=Stopping; updated=12; time=Thu Dec 26 16:51:25 PST 2013} Stale Data:
{Host=4; State=Running; updated=11; time=Thu Dec 26 16:51:22 PST 2013}
2013-12-26 16:51:25,313 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(HA-Worker-3:work-19) Unable to stop VM due to VM is being operated on.
2013-12-26 16:51:25,313 WARN [cloud.ha.HighAvailabilityManagerImpl]
(HA-Worker-3:work-19) Unable to migrate vm from 4
2013-12-26 16:51:25,314 DEBUG [cloud.resource.ResourceManagerImpl]
(HA-Worker-3:work-19) No next resource state for host 4 while current state is
ErrorInMaintenance with event UnableToMigrate
com.cloud.utils.fsm.NoTransitionException: No next resource state found for
current state =ErrorInMaintenance event =UnableToMigrate
at
com.cloud.resource.ResourceManagerImpl.resourceStateTransitTo(ResourceManagerImpl.java:1178)
at
com.cloud.resource.ResourceManagerImpl.maintenanceFailed(ResourceManagerImpl.java:2313)
at
com.cloud.ha.HighAvailabilityManagerImpl.migrate(HighAvailabilityManagerImpl.java:602)
at
com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.run(HighAvailabilityManagerImpl.java:858)
2013-12-26 16:51:25,314 INFO [cloud.ha.HighAvailabilityManagerImpl]
(HA-Worker-3:work-19) Completed HAWork[19-Migration-4-Running-Migrating]
2013-12-26 16:51:25,324 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-57:null) Task failed! Task record: uuid:
38ce6cd4-9ab2-7e46-4d10-dafe25a83084
nameLabel: Async.VM.pool_migrate
nameDescription:
allowedOperations: []
currentOperations: {}
created: Thu Dec 26 16:55:03 PST 2013
finished: Thu Dec 26 16:55:03 PST 2013
status: failure
residentOn: com.xensource.xenapi.Host@40561b9c
progress: 1.0
type: none/
result:
errorInfo: [VM_REQUIRES_SR,
OpaqueRef:6e9c09e8-9ed5-1e21-2048-d848a084a15a,
OpaqueRef:eec84d31-9691-1ba4-f7bb-39db42ac8628]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
2013-12-26 16:51:25,332 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-57:null) Unable to migrate VM(s-1-VM) from
host(d044a044-1a30-4c01-ae83-11d2631a4ffe) due to Task failed! Task record:
uuid: 38ce6cd4-9ab2-7e46-4d10-dafe25a83084
nameLabel: Async.VM.pool_migrate
nameDescription:
allowedOperations: []
currentOperations: {}
created: Thu Dec 26 16:55:03 PST 2013
finished: Thu Dec 26 16:55:03 PST 2013
status: failure
residentOn: com.xensource.xenapi.Host@40561b9c
progress: 1.0
type: none/
result:
errorInfo: [VM_REQUIRES_SR,
OpaqueRef:6e9c09e8-9ed5-1e21-2048-d848a084a15a,
OpaqueRef:eec84d31-9691-1ba4-f7bb-39db42ac8628]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
Task failed! Task record: uuid:
38ce6cd4-9ab2-7e46-4d10-dafe25a83084
nameLabel: Async.VM.pool_migrate
nameDescription:
:
residentOn:
[jira] [Updated] (CLOUDSTACK-5598) XEN patch/hotfix certification - XS 6.2 SP1 patch installation fail
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-5598:
-
Environment:
hostXS 6.2 + hot fix installed :
XS62E001
XS62E002
XS62E004
XS62E005
XS62E007
XS62E008
XS62E009
XS62E010
XS62E011
XS62E012
XS62E013
was:
MS 3.0.7 Patch DCloudStack-PATCH_D-3.0.7-7-rhel6.3.tar.gz
hostXS 6.2 + hot fix installed :
XS62E001
XS62E002
XS62E004
XS62E005
XS62E007
XS62E008
XS62E009
XS62E010
XS62E011
XS62E012
XS62E013
XEN patch/hotfix certification - XS 6.2 SP1 patch installation fail
---
Key: CLOUDSTACK-5598
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5598
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: pre-4.0.0
Environment: hostXS 6.2 + hot fix installed :
XS62E001
XS62E002
XS62E004
XS62E005
XS62E007
XS62E008
XS62E009
XS62E010
XS62E011
XS62E012
XS62E013
Reporter: angeline shen
Priority: Critical
Fix For: pre-4.0.0
Per http://wiki-ccp.citrix.com/pages/viewpage.action?pageId=11829631
Xen Patch installation procedure
1. completed steps 1 thru 7 to upgrade master XEN host to XS 6.2 + 6.2 SP1
2. On slave host, perform step 8: on MS put slave host in maintenance mode
Result: On slave host: all guest VMs fail to migrate to master host, slave
host remained in Preparemaintenance mode
MS Log:
2013-12-19 18:51:37,965 DEBUG [cloud.capacity.CapacityManagerImpl]
(HA-Worker-0:work-2) CPU STATS after allocation: for host: 1, old used: 2100,
old reserved: 0, actual total: 9044, total with overprovisioning: 9044; new
us
ed:2600, reserved:0; requested cpu:500,alloc_from_last:false
2013-12-19 18:51:37,965 DEBUG [cloud.capacity.CapacityManagerImpl]
(HA-Worker-0:work-2) RAM STATS after allocation: for host: 1, old used:
2818572288, old reserved: 0, total: 16001258112; new used: 3087007744,
reserved: 0;
requested mem: 268435456,alloc_from_last:false
2013-12-19 18:51:37,976 DEBUG [agent.transport.Request] (HA-Worker-0:work-2)
Seq 5-357629969: Waiting for Seq 357629965 Scheduling: { Cmd , MgmtId:
7692017993539, via: 5, Ver: v1, Flags: 100111, [{MigrateCommand:{vmName
:s-1-VM,destIp:10.223.51.3,hostGuid:95273a98-5144-42a8-8fb9-2e9761ff2320,isWindows:false,wait:0}}]
}
2013-12-19 18:51:38,146 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-11:null) Task failed! Task record: uuid:
4ea260eb-f447-cf59-fc0a-ab830d87f9d4
nameLabel: Async.VM.pool_migrate
nameDescription:
allowedOperations: []currentOperations: {} created: Thu
Dec 19 18:54:55 PST 2013 finished: Thu Dec 19 18:54:55 PST 2013
status: FAILURE
residentOn: com.xensource.xenapi.Host@6d9f1105
progress: 1.0
type: none/ result: errorInfo:
[VM_REQUIRES_SR, OpaqueRef:b68a7638-2937-58ea-0f5d-52cc3e2f6905,
OpaqueRef:fb25c62b-174a-2a50-fdc0-9ff47c37170c]
otherConfig: {}subtaskOf:
com.xensource.xenapi.Task@aaf13f6f subtasks: [] 2013-12-19
18:51:38,149 WARN [xen.resource.CitrixResourceBase] (DirectAgent-11:null)
Unable to migrate VM(i-2-3-VM) from
host(f6c18d41-fa40-440b-932d-f84bf64e5772) due to Task failed! Task record:
uuid: 4ea260eb-f447-cf59-fc0a-ab830d87f9d4
nameLabel: Async.VM.pool_migrate nameDescription:
allowedOperations: []
currentOperations: {}
created: Thu Dec 19 18:54:55 PST 2013
finished: Thu Dec 19 18:54:55 PST 2013
status: FAILURE
residentOn: com.xensource.xenapi.Host@6d9f1105
progress: 1.0
type: none/
result:
errorInfo: [VM_REQUIRES_SR,
OpaqueRef:b68a7638-2937-58ea-0f5d-52cc3e2f6905,
OpaqueRef:fb25c62b-174a-2a50-fdc0-9ff47c37170c]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
Task failed! Task record: uuid:
4ea260eb-f447-cf59-fc0a-ab830d87f9d4
nameLabel: Async.VM.pool_migrate
nameDescription:
allowedOperations: []
currentOperations: {} created: Thu Dec 19 18:54:55 PST 2013
finished: Thu Dec 19 18:54:55 PST 2013
status: FAILURE
residentOn: com.xensource.xenapi.Host@6d9f1105
progress: 1.0
type: none/
result:
errorInfo: [VM_REQUIRES_SR,
OpaqueRef:b68a7638-2937-58ea-0f5d-52cc3e2f6905,
OpaqueRef:fb25c62b-174a-2a50-fdc0-9ff47c37170c]
[jira] [Updated] (CLOUDSTACK-5598) XEN patch/hotfix certification - XS 6.2 SP1 patch installation fail
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-5598:
-
Description:
Xen Patch installation procedure
1. completed steps 1 thru 7 to upgrade master XEN host to XS 6.2 + 6.2 SP1
2. On slave host, perform step 8: on MS put slave host in maintenance mode
Result: On slave host: all guest VMs fail to migrate to master host, slave
host remained in Preparemaintenance mode
MS Log:
2013-12-19 18:51:37,965 DEBUG [cloud.capacity.CapacityManagerImpl]
(HA-Worker-0:work-2) CPU STATS after allocation: for host: 1, old used: 2100,
old reserved: 0, actual total: 9044, total with overprovisioning: 9044; new us
ed:2600, reserved:0; requested cpu:500,alloc_from_last:false
2013-12-19 18:51:37,965 DEBUG [cloud.capacity.CapacityManagerImpl]
(HA-Worker-0:work-2) RAM STATS after allocation: for host: 1, old used:
2818572288, old reserved: 0, total: 16001258112; new used: 3087007744,
reserved: 0;
requested mem: 268435456,alloc_from_last:false
2013-12-19 18:51:37,976 DEBUG [agent.transport.Request] (HA-Worker-0:work-2)
Seq 5-357629969: Waiting for Seq 357629965 Scheduling: { Cmd , MgmtId:
7692017993539, via: 5, Ver: v1, Flags: 100111, [{MigrateCommand:{vmName
:s-1-VM,destIp:10.223.51.3,hostGuid:95273a98-5144-42a8-8fb9-2e9761ff2320,isWindows:false,wait:0}}]
}
2013-12-19 18:51:38,146 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-11:null) Task failed! Task record: uuid:
4ea260eb-f447-cf59-fc0a-ab830d87f9d4
nameLabel: Async.VM.pool_migrate
nameDescription:
allowedOperations: []currentOperations: {} created: Thu Dec
19 18:54:55 PST 2013 finished: Thu Dec 19 18:54:55 PST 2013
status: FAILURE
residentOn: com.xensource.xenapi.Host@6d9f1105
progress: 1.0
type: none/ result: errorInfo:
[VM_REQUIRES_SR, OpaqueRef:b68a7638-2937-58ea-0f5d-52cc3e2f6905,
OpaqueRef:fb25c62b-174a-2a50-fdc0-9ff47c37170c]
otherConfig: {}subtaskOf:
com.xensource.xenapi.Task@aaf13f6f subtasks: [] 2013-12-19
18:51:38,149 WARN [xen.resource.CitrixResourceBase] (DirectAgent-11:null)
Unable to migrate VM(i-2-3-VM) from host(f6c18d41-fa40-440b-932d-f84bf64e5772)
due to Task failed! Task record: uuid:
4ea260eb-f447-cf59-fc0a-ab830d87f9d4
nameLabel: Async.VM.pool_migrate nameDescription:
allowedOperations: []
currentOperations: {}
created: Thu Dec 19 18:54:55 PST 2013
finished: Thu Dec 19 18:54:55 PST 2013
status: FAILURE
residentOn: com.xensource.xenapi.Host@6d9f1105
progress: 1.0
type: none/
result:
errorInfo: [VM_REQUIRES_SR,
OpaqueRef:b68a7638-2937-58ea-0f5d-52cc3e2f6905,
OpaqueRef:fb25c62b-174a-2a50-fdc0-9ff47c37170c]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
Task failed! Task record: uuid:
4ea260eb-f447-cf59-fc0a-ab830d87f9d4
nameLabel: Async.VM.pool_migrate
nameDescription:
allowedOperations: []
currentOperations: {} created: Thu Dec 19 18:54:55 PST 2013
finished: Thu Dec 19 18:54:55 PST 2013
status: FAILURE
residentOn: com.xensource.xenapi.Host@6d9f1105
progress: 1.0
type: none/
result:
errorInfo: [VM_REQUIRES_SR,
OpaqueRef:b68a7638-2937-58ea-0f5d-52cc3e2f6905,
OpaqueRef:fb25c62b-174a-2a50-fdc0-9ff47c37170c]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.checkForSuccess(CitrixResourceBase.java:3178)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.migrateVM(CitrixResourceBase.java:3324)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2877)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:441)
at
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:55)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:217)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
[jira] [Updated] (CLOUDSTACK-5630) [Automation]snapshot tests are failing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-5630: - Assignee: Chandan Purushothama [Automation]snapshot tests are failing -- Key: CLOUDSTACK-5630 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5630 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.3.0 Environment: xenserver 62 advanced zone Reporter: Srikanteswararao Talluri Assignee: Chandan Purushothama Fix For: 4.3.0 Creating this bug as a place holder for the following failures, needs further analysis, test_03_snapshots_per_account FAILED Check Snapshot state is Running or not test_03_snapshots_per_domain FAILED Check Snapshot state is Running or not test_02_accountSnapshotClean FAILED Snapshot was not found on NFS test_04_snapshot_limitFAILED False is not True test_01_createVM_snapshotTemplate FAILED False is not True test_02_snapshot_data_diskFAILED False is not True -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (CLOUDSTACK-5393) [Automation] Failed to create snapshot from ROOT volume in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-5393:
-
Priority: Critical (was: Major)
[Automation] Failed to create snapshot from ROOT volume in KVM
--
Key: CLOUDSTACK-5393
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5393
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Snapshot
Affects Versions: 4.3.0
Environment: KVM (RHEL 6.3)
Branch : 4.3
Reporter: Rayees Namathponnan
Assignee: Min Chen
Priority: Critical
Fix For: 4.3.0
Attachments: agent1.rar, agent2.rar, management-server.rar, ssvm.rar
Steps to reproduce
1) Create advanced zone in KVM
2) Deploy VM
3 ) Stop VM
4 ) Create snapshot from root volume
Snapshot creation failed with below exception
2013-12-05 15:39:44,194 DEBUG [c.c.a.t.Request] (Job-Executor-64:ctx-1b710e00
ctx-3cf3df4e) Seq 1-1244399478: Received: { Ans: , MgmtId: 29066118877352,
via: 1, Ver: v1, Flags: 10, { CreateObjectAnswer } }
2013-12-05 15:39:44,284 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
(Job-Executor-64:ctx-1b710e00 ctx-3cf3df4e) copyAsync inspecting src type
SNAPSHOT copyAsync inspecting dest type SNAPSHOT
2013-12-05 15:39:44,332 DEBUG [c.c.a.t.Request] (Job-Executor-64:ctx-1b710e00
ctx-3cf3df4e) Seq 2-332864214: Sending { Cmd , MgmtId: 29066118877352, via:
2(Rack2Host12.lab.vmops.com), Ver: v1, Flags: 100011, [{org.apache.cl
oudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.SnapshotObjectTO:{path:/mnt/fff90cb5-06dd-33b3-8815-d78c08ca01d9/a44ddf93-9fa2-497f-aff6-cf4951128215/8f7d268f-1a96-4d70-9c48-cb7f6cc935a8
,volume:{uuid:a44ddf93-9fa2-497f-aff6-cf4951128215,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:fff90cb5-06dd-33b3-8815-d78c08ca01d9,id:1,poolType:NetworkFilesyst
em,host:10.223.110.232,path:/export/home/rayees/SC_QA_AUTO4/primary,port:2049,url:NetworkFilesystem://10.223.110.232//export/home/rayees/SC_QA_AUTO4/primary/?ROLE=PrimarySTOREUUID=fff90cb5-06dd-33b3-8815-d78c08
ca01d9}},name:ROOT-919,size:8589934592,path:a44ddf93-9fa2-497f-aff6-cf4951128215,volumeId:988,vmName:i-2-919-QA,accountId:2,format:QCOW2,id:988,deviceId:0,hypervisorType:KVM},parentSnapshotPath
:/mnt/fff90cb5-06dd-33b3-8815-d78c08ca01d9/a44ddf93-9fa2-497f-aff6-cf4951128215/d43b61bc-4ade-4753-b1d9-c0398388147d,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:fff90cb5-06dd-33b3-8815-d78c08ca01d9,id:1,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/rayees/SC_QA_AUTO4/primary,port:2049,url:NetworkFilesystem://10.223.110.232//export/home/rayees/SC_QA_AUTO4/primary/?ROLE=PrimarySTOREUUID=fff90cb5-06dd-33b3-8815-d78c08ca01d9}},vmName:i-2-919-QA,name:QA-eb54bbfa-12d5-49b5-808f-864dddedc1fd_ROOT-919_20131205233943,hypervisorType:KVM,id:54,quiescevm:false}},destTO:{org.apache.cloudstack.storage.to.SnapshotObjectTO:{path:snapshots/2/988,volume:{uuid:a44ddf93-9fa2-497f-aff6-cf4951128215,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:fff90cb5-06dd-33b3-8815-d78c08ca01d9,id:1,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/rayees/SC_QA_AUTO4/primary,port:2049,url:NetworkFilesystem://10.223.110.232//export/home/rayees/SC_QA_AUTO4/primary/?ROLE=PrimarySTOREUUID=fff90cb5-06dd-33b3-8815-d78c08ca01d9}},name:ROOT-919,size:8589934592,path:a44ddf93-9fa2-497f-aff6-cf4951128215,volumeId:988,vmName:i-2-919-QA,accountId:2,format:QCOW2,id:988,deviceId:0,hypervisorType:KVM},dataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.223.110.232:/export/home/rayees/SC_QA_AUTO4/secondary,_role:Image}},vmName:i-2-919-QA,name:QA-eb54bbfa-12d5-49b5-808f-864dddedc1fd_ROOT-919_20131205233943,hypervisorType:KVM,id:54,quiescevm:false}},executeInSequence:false,wait:21600}}]
}
2013-12-05 15:39:44,501 DEBUG [c.c.a.t.Request]
(StatsCollector-3:ctx-3ac54662) Seq 1-1244399477: Received: { Ans: , MgmtId:
29066118877352, via: 1, Ver: v1, Flags: 10, { GetVmStatsAnswer } }
2013-12-05 15:39:44,900 DEBUG [c.c.a.t.Request] (AgentManager-Handler-1:null)
Seq 2-332864214: Processing: { Ans: , MgmtId: 29066118877352, via: 2, Ver:
v1, Flags: 10,
[{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:/usr/share/cloudstack-common/scripts/storage/qcow2/managesnapshot.sh:
line 178: 26840 Floating point exception(core dumped) $qemu_img convert -f
qcow2 -O qcow2 -s $snapshotname $disk $destPath/$destName /dev/nullFailed
to backup 8f7d268f-1a96-4d70-9c48-cb7f6cc935a8 for disk
/mnt/fff90cb5-06dd-33b3-8815-d78c08ca01d9/a44ddf93-9fa2-497f-aff6-cf4951128215
to
[jira] [Closed] (CLOUDSTACK-4952) [event framework] The topic grammar - eventSource.eventCategory.eventType.resourceType.resourceUuid is incorrect, eventType.resourceType should swap
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-4952. [event framework] The topic grammar - eventSource.eventCategory.eventType.resourceType.resourceUuid is incorrect, eventType.resourceType should swap - Key: CLOUDSTACK-4952 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4952 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Nitin Mehta Fix For: 4.3.0 -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (CLOUDSTACK-4875) VMWARE: vCenter 5.5 - SYSTEM VM: Unable to create deployment for VM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13843804#comment-13843804
]
Sudha Ponnaganti commented on CLOUDSTACK-4875:
--
4.3 is first time VMWare 5.5 is being supported. This was not supported in 4.2
VMWARE: vCenter 5.5 - SYSTEM VM: Unable to create deployment for VM
---
Key: CLOUDSTACK-4875
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4875
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: SystemVM, VMware
Affects Versions: 4.2.1
Environment: Master with vCenter 5.5 / ESXi 5.5
Reporter: Parth Jagirdar
Assignee: Likitha Shetty
Priority: Blocker
Fix For: 4.3.0
Attachments: VC5.5.jpg, catalina.out, management-server.log
Unable to launch system VM's
See attached logs
2013-10-15 13:31:40,061 DEBUG [cloud.storage.VolumeManagerImpl]
(consoleproxy-1:null) Unable to create
Vol[2|vm=2|ROOT]:java.lang.RuntimeException: File
[803eb6157bb83df98d96c4da27252fa8] ROOT-2/ROOT-2.vmdk was not found
2013-10-15 13:31:40,061 INFO [cloud.vm.VirtualMachineManagerImpl]
(consoleproxy-1:null) Unable to contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:1] is
unreachable: Unable to create Vol[2|vm=2|ROOT]:java.lang.RuntimeException:
File [803eb6157bb83df98d96c4da27252fa8] ROOT-2/ROOT-2.vmdk was not found
at
com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2566)
at
com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2617)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:889)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:571)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManagerImpl.java:556)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyManagerImpl.java:928)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:1672)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:157)
at
com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111)
at
com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
at
com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)
at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-10-15 13:31:40,068 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(consoleproxy-1:null) Cleaning up resources for the vm
VM[ConsoleProxy|v-2-VM] in Starting state
type TEMPLATE copyAsync inspecting dest type VOLUME
2013-10-15 13:33:00,630 DEBUG [agent.transport.Request] (secstorage-1:null)
Seq 1-401276957: Waiting for Seq 401276956 Scheduling: { Cmd , MgmtId:
15929225863658, via: 1, Ver: v1, Flags: 100111,
[{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:b8766e32c0c838539a8f75c2cc62a30b,origUrl:http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova,uuid:e1eb1bf2-35c3-11e3-a10c-0e7ccfd961ea,id:8,format:OVA,accountId:1,checksum:8fde62b1089e5844a9cd3b9b953f9596,hvm:false,displayText:SystemVM
Template
[jira] [Updated] (CLOUDSTACK-4197) Allow creating a VM without virtual CD-ROM drive
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-4197: - Fix Version/s: 4.3.0 Allow creating a VM without virtual CD-ROM drive Key: CLOUDSTACK-4197 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4197 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.2.0 Reporter: Kirk Kosinski Priority: Minor Labels: hypervisor, netscaler Fix For: 4.3.0 Currently all VMs that CloudStack creates will include a virtual CD-ROM drive. In some cases, such as with virtual appliances (e.g. NetScaler VPX), a CD-ROM drive is not needed or even unsupported. It would be useful if CloudStack could deploy a VM without a CD-ROM drive to allow such cases. Perhaps such functionality could be added using new OS Types, for example: Other - No CD-ROM (32-bit) Other - No CD-ROM (64-bit) Other PV - No CD-ROM (32-bit) Other PV - No CD-ROM (64-bit) Or maybe it could be added on a per VM or per template basis with a new configuration parameter. This might be more flexible since some customers might want to use arbitrary OS types for VMs with no CD-ROM. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-5349) [Automation] VOLUME.CREATE missing in events table
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-5349: - Assignee: Nitin Mehta [Automation] VOLUME.CREATE missing in events table -- Key: CLOUDSTACK-5349 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5349 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Environment: ALL branch 4.3 Reporter: Rayees Namathponnan Assignee: Nitin Mehta Priority: Blocker Fix For: 4.3.0 # Validate the following # 1. Create a VM. Verify usage_events table contains VM .create, VM.start , Network.offering.assign , Volume.create events # 2. Stop the VM. Verify usage_events table contains network.offerings.remove ,VM .stop Events for the created account. # 3. Destroy the VM after some time. Verify usage_events table containsVM.Destroy and volume .delete Event for the created account # 4. Delete the account VOLUME.CREATE missing in events table, below test case failing due to this integration.component.test_usage.TestVmUsage.test_01_vm_usage mysql select type from usage_event where account_id = '103'; +-+ | type| +-+ | VM.CREATE | | NETWORK.OFFERING.ASSIGN | | VM.START| | SG.ASSIGN | | VM.STOP | | NETWORK.OFFERING.REMOVE | | SG.REMOVE | | VM.DESTROY | | VOLUME.DELETE | +-+ 9 rows in set (0.00 sec) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-5350) [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-5350: - Assignee: frank zhang [Automation] Failed to attach volume to VM, if the vm is created with option startvm=false -- Key: CLOUDSTACK-5350 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5350 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Volumes Affects Versions: 4.3.0 Environment: KVM (RHEL 6.3) Branch : 4.3 Reporter: Rayees Namathponnan Assignee: frank zhang Priority: Blocker Fix For: 4.3.0 Regression automation failure test_stopped_vm.py:test_04_deploy_startvm_false_attach_volume Steps to reproduce # Validate the following: 1. deploy Vm with the startvm=false. Attach volume to the instance 2. listVM command should return the deployed VM.State of this VM should be Stopped. 3. Attach volume should be successful Actual Result Attach volume failed with below error 2013-12-03 08:45:50,190 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator] (Job-Executor-8:ctx-780454c7 ctx-c09f3d6f) List of pools in ascending order of number of volumes for account id: 516 is: [] 2013-12-03 08:45:50,190 WARN [o.a.c.e.o.VolumeOrchestrator] (Job-Executor-8:ctx-780454c7 ctx-c09f3d6f) Unable to find suitable primary storage whe n creating volume DataDisk 2013-12-03 08:45:50,208 ERROR [c.c.a.ApiAsyncJobDispatcher] (Job-Executor-8:ctx-780454c7) Unexpected exception while executing org.apache.cloudstac k.api.command.user.volume.AttachVolumeCmd com.cloud.utils.exception.CloudRuntimeException: Unable to find suitable primary storage when creating volume DataDisk at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.createVolume(VolumeOrchestrator.java:399) at org.apache.cloudstack.engine.orchestration.VolumeOrchestrator.createVolumeOnPrimaryStorage(VolumeOrchestrator.java:697) at com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1086) at sun.reflect.GeneratedMethodAccessor681.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:50) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy232.attachVolumeToVM(Unknown Source) at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:123) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161) at com.cloud.api.ApiAsyncJobDispatcher.runJobInContext(ApiAsyncJobDispatcher.java:109) at com.cloud.api.ApiAsyncJobDispatcher$1.run(ApiAsyncJobDispatcher.java:66) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:63) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:520) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at
[jira] [Updated] (CLOUDSTACK-5353) [Automation] listVpnUsers API returns null
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-5353:
-
Assignee: Alena Prokharchyk
[Automation] listVpnUsers API returns null
---
Key: CLOUDSTACK-5353
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5353
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: API, Management Server
Affects Versions: 4.3.0
Environment: Branch ; 4.3
Reporter: Rayees Namathponnan
Assignee: Alena Prokharchyk
Priority: Blocker
Fix For: 4.3.0
Steps:
***
1.deploy the advance zone with hypervisor as KVM
2.deployvm on new network
3. Acquire new IP
4.enable vpn on Ip
5.create Vpn users
Expected result
Newly created user should be displayed same page
Actual Result
New added user not displayed
also below API call does not return anything
http://10.223.49.195:8096/?command=listVpnUserslistall=true
Firebug
1)
http://10.223.49.195:8080/client/api?command=addVpnUserresponse=jsonsessionkey=RfqSp9FX7ZZhKDOc6CWZLEekFO4%3Daccount=admindomainid=8c62b19a-5bbb-11e3-a447-1a6f7bb0d0a8password=dsdsusername=sddsds
{ addvpnuserresponse :
{id:8cedbb84-e4fa-4508-9465-6ad993377e72,jobid:d3377654-ad52-4b61-b746-525e788224de}
}
2)
http://10.223.49.195:8080/client/api?command=queryAsyncJobResultjobId=d3377654-ad52-4b61-b746-525e788224deresponse=jsonsessionkey=RfqSp9FX7ZZhKDOc6CWZLEekFO4%3D_=1386100530785
{ queryasyncjobresultresponse :
{accountid:d644a994-5bbb-11e3-a447-1a6f7bb0d0a8,userid:d644e0b2-5bbb-11e3-a447-1a6f7bb0d0a8,cmd:org.apache.cloudstack.api.command.user.vpn.AddVpnUserCmd,jobstatus:1,jobprocstatus:0,jobresultcode:0,jobresulttype:object,jobresult:{vpnuser:{id:8cedbb84-e4fa-4508-9465-6ad993377e72,username:sddsds,account:admin,domainid:8c62b19a-5bbb-11e3-a447-1a6f7bb0d0a8,domain:ROOT}},created:2013-12-03T11:55:27-0800,jobid:d3377654-ad52-4b61-b746-525e788224de}
3)
http://10.223.49.195:8080/client/api?command=listVpnUsersresponse=jsonsessionkey=RfqSp9FX7ZZhKDOc6CWZLEekFO4%3Ddomainid=8c62b19a-5bbb-11e3-a447-1a6f7bb0d0a8account=admin_=1386100530852
_ 1386100530852
account admin
command listVpnUsers
domainid 8c62b19a-5bbb-11e3-a447-1a6f7bb0d0a8
response json
sessionkeyRfqSp9FX7ZZhKDOc6CWZLEekFO4=
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (CLOUDSTACK-5343) Volume limit applied to project/account does not count root disks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-5343: - Assignee: Prachi Damle Volume limit applied to project/account does not count root disks - Key: CLOUDSTACK-5343 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5343 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Storage Controller Affects Versions: 4.3.0 Reporter: Gaurav Aradhye Assignee: Prachi Damle Fix For: 4.3.0 1. Create any project or account. 2. Set the volume limit as 1. 3. Deploy an instance without data disk in project/account. 4. Now you can see the root disk in the volumes, but if you list the account/project, then the volume count still shows as 0. 5. Now add new data disk. 6. Check volume count, now it shows it as 1 (But it should have shown as 2, and it should have failed at this stage only saying limit exceeded.) 7. Add another data disk (Now it will fail) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-5342) Add NIC to virtual machine fails in KVM
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-5342:
-
Assignee: Jayapal Reddy
Add NIC to virtual machine fails in KVM
---
Key: CLOUDSTACK-5342
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5342
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Controller
Affects Versions: 4.3.0
Environment: KVM advanced
Reporter: Gaurav Aradhye
Assignee: Jayapal Reddy
Fix For: 4.3.0
Add network to VM test cases fail in KVM with following error.
Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext :
u'Unable to add NIC to VM[User|VM-e9350ee5-bf2e-418c-91d6-1535dcb4d488]'}
The same test cases execute successfully on XenServer. As per the feature
specification (see
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+Networks+to+VMs),
Add network to VM feature should be supported on KVM too.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Closed] (CLOUDSTACK-4585) [VMWare] [Upgrade] Failed to start instance after reverting the VM snapshot on a Private Zone which was created prior to upgrade
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti closed CLOUDSTACK-4585.
[VMWare] [Upgrade] Failed to start instance after reverting the VM snapshot
on a Private Zone which was created prior to upgrade
-
Key: CLOUDSTACK-4585
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4585
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Snapshot
Affects Versions: 4.2.1
Reporter: Sudha Ponnaganti
Assignee: Kelven Yang
Priority: Blocker
Fix For: 4.2.1
I have an upgraded setup from 307 Patch B to 4.2 . I have one VMWARE private
zone before upgrade.
After upgrade I created VM snapshot for one of the instance In this zone.
Later reverted to this VM snapshot. Now VM’s are failing to start saying
“Unable to create a deployment for VM[User|host13i1], Please check the
affinity groups provided, there may not be sufficient capacity to follow them”
=
2013-08-31 20:33:16,949 WARN [vmware.resource.VmwareResource]
(DirectAgent-452:10.102.192.13) StartCommand failed due to Exception:
java.lang.RuntimeException
Message: Invalid configuration for device '0'.
java.lang.RuntimeException: Invalid configuration for device '0'.
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:378)
at
com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:835)
at
com.cloud.hypervisor.vmware.mo.VirtualMachineMO.tearDownDevices(VirtualMachineMO.java:1643)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2675)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:519)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-08-31 20:33:16,952 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-452:null) Seq 12-1859846507: Response Received:
2013-08-31 20:33:16,953 DEBUG [agent.transport.Request]
(DirectAgent-452:null) Seq 12-1859846507: Processing: { Ans: , MgmtId:
227594284004867, via: 12, Ver: v1, Flags: 110,
[{com.cloud.agent.api.StartAnswer:{vm:{id:38,name:i-3-38-VM,bootloader:HVM,type:User,cpus:1,minSpeed:200,maxSpeed:200,minRam:536870912,maxRam:536870912,hostName:host13i1,arch:x86_64,os:CentOS
5.3
(64-bit),bootArgs:,rebootOnCrash:false,enableHA:false,limitCpuUse:false,enableDynamicallyScaleVm:false,vncPassword:425de971cf2ec463,params:{nicAdapter:E1000,vmware.reserve.cpu:false,nestedVirtualizationFlag:false,Message.ReservedCapacityFreed.Flag:false,rootDiskController:ide,vmware.reserve.mem:false},uuid:d51c5b43-0201-4095-8b4c-643df2b2f4e2,disks:[{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:499111c0-9bb3-4921-a370-0c8f5de8579b,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:5bf1f4d7-b301-39f1-85dc-c0af114d68b4,id:203,poolType:NetworkFilesystem,host:10.102.192.100,path:/cpg_vol/sailaja/zwps1,port:2049}},name:ROOT-38,size:2147483648,path:ROOT-38-03,volumeId:47,vmName:i-3-38-VM,accountId:3,chainInfo:{\diskDeviceBusName\:\ide0:1\,\diskChain\:[\[5bf1f4d7b30139f185dcc0af114d68b4]
i-3-38-VM/ROOT-38.vmdk\,\[5bf1f4d7b30139f185dcc0af114d68b4]
[jira] [Closed] (CLOUDSTACK-4924) AcountCleanup: never release the ip address if the network failed to delete
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-4924. AcountCleanup: never release the ip address if the network failed to delete --- Key: CLOUDSTACK-4924 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4924 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 Reporter: Alena Prokharchyk Assignee: Alena Prokharchyk Fix For: 4.2.1 During the account cleanup process, cloudStack code: destroys the networks calls ipRelease for the account ip addresses. This call was added to cover the Basic zone scenario when there are public ips assigned to the account exist, and they have to be de-allocated explicitly w/o calling the destroyNetwork Bug: ipRelease call should never be made in the accountCleanup thread when the destroyNetwork call failed. Otherwise you end up with the public ips still programmed on the VR that wasn't destroyed, and released in the DB. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Closed] (CLOUDSTACK-4060) [UI] When the only sg is default, it should be selected automatically.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-4060. [UI] When the only sg is default, it should be selected automatically. -- Key: CLOUDSTACK-4060 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4060 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: Ahmad Emneina Assignee: Jessica Wang Fix For: 4.2.1 When the only sg is default, it should be selected automatically. even when deploying and def sec group isnt selected, the vm is deployed to that security group. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Closed] (CLOUDSTACK-4058) [UI] Under host details we show ACS version and not host version
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-4058. [UI] Under host details we show ACS version and not host version Key: CLOUDSTACK-4058 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4058 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, UI, VMware Affects Versions: 4.2.0 Reporter: Ahmad Emneina Assignee: Jessica Wang Fix For: 4.2.1 Attachments: jessica_UI_change_1.jpg On the host details pane, version shows cloudstack version and not esxi version. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (CLOUDSTACK-4894) [UI] destroyVm API: add support to force expunge the vm immediately
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13825623#comment-13825623 ] Sudha Ponnaganti commented on CLOUDSTACK-4894: -- validated - closing [UI] destroyVm API: add support to force expunge the vm immediately Key: CLOUDSTACK-4894 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4894 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, UI Affects Versions: 4.2.0 Reporter: Alena Prokharchyk Assignee: Jessica Wang Fix For: 4.2.1 When destroyVM API is called, the vm gets destroyed only in the DB. The actual expunge is being taken care later on by expunge thread (configured using expunge.interval and expunge.delay params). As we keep on getting the requests on adding a support for forceful expunge - when vm is expunged immediately after the call is made - it would make sense to introduce some flag to destroyVm command, controlling the behavior. So destroyVm will get new parameter - expunge (boolean, false by default). When true is passed as a value, the vm will be expunged right away. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Closed] (CLOUDSTACK-4894) [UI] destroyVm API: add support to force expunge the vm immediately
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-4894. [UI] destroyVm API: add support to force expunge the vm immediately Key: CLOUDSTACK-4894 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4894 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, UI Affects Versions: 4.2.0 Reporter: Alena Prokharchyk Assignee: Jessica Wang Fix For: 4.2.1 When destroyVM API is called, the vm gets destroyed only in the DB. The actual expunge is being taken care later on by expunge thread (configured using expunge.interval and expunge.delay params). As we keep on getting the requests on adding a support for forceful expunge - when vm is expunged immediately after the call is made - it would make sense to introduce some flag to destroyVm command, controlling the behavior. So destroyVm will get new parameter - expunge (boolean, false by default). When true is passed as a value, the vm will be expunged right away. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Closed] (CLOUDSTACK-5082) 3.0.6 to ASF 4.2.1 Upgrade: alert.smtp.timeout and alert.smtp.connectiontimeout configuration parameters are missing on the Upgraded Setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-5082. validated in 4.2.1 3.0.6 to ASF 4.2.1 Upgrade: alert.smtp.timeout and alert.smtp.connectiontimeout configuration parameters are missing on the Upgraded Setup -- Key: CLOUDSTACK-5082 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5082 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Upgrade Affects Versions: 4.2.1 Reporter: Chandan Purushothama Assignee: Anshul Gangwar Priority: Critical Fix For: 4.2.1 The following parameters are missing on the Upgraded Setup. mysql select * from configuration where name like alert.smtp.%timeout; +--+--+---+--+---+---+ | category | instance | component | name | value | description | +--+--+---+--+---+---+ | Alert| DEFAULT | management-server | alert.smtp.connectiontimeout | 3 | Socket connection timeout value in milliseconds. -1 for infinite timeout. | | Alert| DEFAULT | management-server | alert.smtp.timeout | 3 | Socket I/O timeout value in milliseconds. -1 for infinite timeout. | +--+--+---+--+---+---+ 2 rows in set (0.00 sec) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Closed] (CLOUDSTACK-5083) 3.0.6 to ASF 4.2.1 Upgrade: baremetal.ipmi.lan.interface configuration parameter are missing on the Upgraded Setup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-5083. validated in 4.2.1 3.0.6 to ASF 4.2.1 Upgrade: baremetal.ipmi.lan.interface configuration parameter are missing on the Upgraded Setup Key: CLOUDSTACK-5083 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5083 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Upgrade Affects Versions: 4.2.1 Reporter: Chandan Purushothama Assignee: frank zhang Priority: Critical Fix For: 4.2.1 The following parameters are missing on the Upgraded Setup. mysql select * from configuration where name like baremetal%; +--+--+---+--+-++ | category | instance | component | name | value | description | +--+--+---+--+-++ | Advanced | DEFAULT | management-server | baremetal.ipmi.lan.interface | default | option specified in -I option of impitool. candidates are: open/bmc/lipmi/lan/lanplus/free/imb, see ipmitool man page for details. default valule 'default' means using default option of ipmitool | +--+--+---+--+-++ 1 row in set (0.00 sec) -- This message was sent by Atlassian JIRA (v6.1#6144)
