[jira] [Updated] (CLOUDSTACK-7006) Template ID is missing in ROOT volume usages
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lemasle updated CLOUDSTACK-7006: Description: In previous versions of CloudStack, the template ID was recorded for ROOT volume usages, when the VM is created from a template. Since CloudStack 4.2, the template ID isn't recorded anymore, due to a regression in the EVENT_VOLUME_CREATE event publishing: In commit https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=730d04508507409065a432e2aac931225947f268, the last EVENT_VOLUME_CREATE misses the template id, that was previously set. It seems a simple copy-paste error. was: In previous versions of CloudStack, the template ID was recorded for ROOT volume usages. Since CloudStack 4.2, the template ID isn't recorded anymore, due to a regression in the EVENT_VOLUME_CREATE event publishing: In commit https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=730d04508507409065a432e2aac931225947f268, the last EVENT_VOLUME_CREATE misses the template id, that was previously set. It seems a simple copy-paste error. Template ID is missing in ROOT volume usages Key: CLOUDSTACK-7006 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7006 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Usage Affects Versions: 4.2.0, 4.2.1, 4.3.0, 4.4.0 Reporter: Olivier Lemasle Assignee: Olivier Lemasle Priority: Minor In previous versions of CloudStack, the template ID was recorded for ROOT volume usages, when the VM is created from a template. Since CloudStack 4.2, the template ID isn't recorded anymore, due to a regression in the EVENT_VOLUME_CREATE event publishing: In commit https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=730d04508507409065a432e2aac931225947f268, the last EVENT_VOLUME_CREATE misses the template id, that was previously set. It seems a simple copy-paste error. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6980) UI for RegisterTemplate API does not expose requireshvm parameter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-6980: --- Assignee: Jessica Wang UI for RegisterTemplate API does not expose requireshvm parameter - Key: CLOUDSTACK-6980 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6980 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Kishan Kavala Assignee: Jessica Wang requireshvm parameter should be false for LXC templates. UI does not provide option to set this parameter to false for RegisterTemplate API -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6885) system-vm rsyslog logs rotation does not work properly
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047535#comment-14047535
]
Sonal Ojha commented on CLOUDSTACK-6885:
The log files could be rotated on the systemvm with :
logrotate -f /etc/logrotate.d/rsyslog
Changing the reload argument with rotate didnt help.
system-vm rsyslog logs rotation does not work properly
--
Key: CLOUDSTACK-6885
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6885
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: SystemVM
Affects Versions: 4.3.0
Reporter: JF Vincent
Assignee: Sonal Ojha
Priority: Critical
rsyslog reload synthax is bad in the logrotate.d/rsyslog setting resulting in
potential FULL on /var/ and critical failures on the VR.
See below please :
root@r-1346-SANDBOX:/var/log# more /etc/logrotate.d/rsyslog
/var/log/syslog
{
rotate 7
daily
missingok
notifempty
delaycompress
compress
postrotate
invoke-rc.d rsyslog reload /dev/null
endscript
}
/var/log/mail.info
/var/log/mail.warn
/var/log/mail.err
/var/log/mail.log
/var/log/daemon.log
/var/log/kern.log
/var/log/auth.log
/var/log/user.log
/var/log/lpr.log
/var/log/cron.log
/var/log/debug
/var/log/messages
{
rotate 10
daily
missingok
notifempty
compress
delaycompress
sharedscripts
postrotate
invoke-rc.d rsyslog reload /dev/null
endscript
}
root@r-1346-SANDBOX:/var/log# /etc/init.d/rsyslog reload
Usage: /etc/init.d/rsyslog {start|stop|rotate|restart|force-reload|status}
root@r-1346-SANDBOX:/var/log# /etc/init.d/rsyslog rotate
[ ok ] Closing open files: rsyslogd.
reload argument in the invoke-rc.d line shoud be replaced by rotate
argument.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6976) Support for SecStorageFirewallCfgCommand for simulator.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6976. - Resolution: Fixed Support for SecStorageFirewallCfgCommand for simulator. - Key: CLOUDSTACK-6976 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6976 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Simulator Affects Versions: 4.4.0 Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.4.0, 4.5.0 Simulator currently, does not support SecStorageFirewallCfgCommand and throws up below error. Added support for this command now. [c.c.a.m.AgentManagerImpl] (Simulator-Agent-Mgr-1:ctx-6381ef3d) Unsupported Command: Unsupported command issued:com.cloud.agent.api.SecStorageFirewallCfgCommand. Are you sure you got the right type of server? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6976) Support for SecStorageFirewallCfgCommand for simulator.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-6976. --- Support for SecStorageFirewallCfgCommand for simulator. - Key: CLOUDSTACK-6976 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6976 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Simulator Affects Versions: 4.4.0 Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.4.0, 4.5.0 Simulator currently, does not support SecStorageFirewallCfgCommand and throws up below error. Added support for this command now. [c.c.a.m.AgentManagerImpl] (Simulator-Agent-Mgr-1:ctx-6381ef3d) Unsupported Command: Unsupported command issued:com.cloud.agent.api.SecStorageFirewallCfgCommand. Are you sure you got the right type of server? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6856) Fixed few TCs failing in master.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-6856. - Resolution: Fixed Fixed few TCs failing in master. Key: CLOUDSTACK-6856 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6856 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, marvin Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Fix For: 4.5.0 1. Fixed few cases failing because of some data corruption. 2. Added proper to retries to few cases where check is done immediately after operation. 3. Added setup.py changes. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-5937) Exception When running Simulator
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla resolved CLOUDSTACK-5937. - Resolution: Fixed This is fixed. Exception When running Simulator Key: CLOUDSTACK-5937 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5937 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Infra Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Exception when running simulator : ERROR [c.c.c.AgentHookBase] (AgentConnectTaskPool-29:ctx-7e568cd1) Unexpected exception when sending http handling startup command(time out) to the console proxy resource for proxy:37 java.lang.NullPointerException at com.cloud.consoleproxy.AgentHookBase.startAgentHttpHandlerInVM(AgentHookBase.java:218) at com.cloud.consoleproxy.ConsoleProxyListener.processConnect(ConsoleProxyListener.java:71) at com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:495) at com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:999) at com.cloud.agent.manager.AgentManagerImpl.access$000(AgentManagerImpl.java:117) at com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.runInContext(AgentManagerImpl.java:1082) 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6997) conntrack set to a very low value on router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047557#comment-14047557 ] ASF subversion and git services commented on CLOUDSTACK-6997: - Commit 004d616322ba55d83407545f5b10c95ce48f75b5 in cloudstack's branch refs/heads/4.4-forward from Jayapal [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=004d616 ] CLOUDSTACK-6997: Increase proc ip_conntrack_max conntrack set to a very low value on router --- Key: CLOUDSTACK-6997 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6997 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: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.4.0 Set ip_conntrack_max to 1 million ip conntrack value which is in sysctl.conf is not applied on VR. Debian wheezy sysctl.conf is not got loaded on boot time. There is bug in debian https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-5937) Exception When running Simulator
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santhosh Kumar Edukulla closed CLOUDSTACK-5937. --- Exception When running Simulator Key: CLOUDSTACK-5937 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5937 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Infra Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla Exception when running simulator : ERROR [c.c.c.AgentHookBase] (AgentConnectTaskPool-29:ctx-7e568cd1) Unexpected exception when sending http handling startup command(time out) to the console proxy resource for proxy:37 java.lang.NullPointerException at com.cloud.consoleproxy.AgentHookBase.startAgentHttpHandlerInVM(AgentHookBase.java:218) at com.cloud.consoleproxy.ConsoleProxyListener.processConnect(ConsoleProxyListener.java:71) at com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:495) at com.cloud.agent.manager.AgentManagerImpl.handleConnectedAgent(AgentManagerImpl.java:999) at com.cloud.agent.manager.AgentManagerImpl.access$000(AgentManagerImpl.java:117) at com.cloud.agent.manager.AgentManagerImpl$HandleAgentConnectTask.runInContext(AgentManagerImpl.java:1082) 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7007) LXC: Enable security group support
Abhinandan Prateek created CLOUDSTACK-7007: -- Summary: LXC: Enable security group support Key: CLOUDSTACK-7007 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7007 Project: CloudStack Issue Type: Task Security Level: Public (Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.5.0 Reporter: Abhinandan Prateek Assignee: Kishan Kavala Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7008) LXC: Native snapshot support
Abhinandan Prateek created CLOUDSTACK-7008: -- Summary: LXC: Native snapshot support Key: CLOUDSTACK-7008 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7008 Project: CloudStack Issue Type: Task Security Level: Public (Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.5.0 Reporter: Abhinandan Prateek Assignee: Kishan Kavala Fix For: Future -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7006) Template ID is missing in ROOT volume usages
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047635#comment-14047635 ] ASF subversion and git services commented on CLOUDSTACK-7006: - Commit caa102c23d352d8e9f2f8a4f4159a3fc7d776f26 in cloudstack's branch refs/heads/4.3 from [~olemasle] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=caa102c ] CLOUDSTACK-7006: Restore template ID in ROOT volume usages Signed-off-by: Sebastien Goasguen run...@gmail.com Template ID is missing in ROOT volume usages Key: CLOUDSTACK-7006 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7006 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Usage Affects Versions: 4.2.0, 4.2.1, 4.3.0, 4.4.0 Reporter: Olivier Lemasle Assignee: Olivier Lemasle Priority: Minor In previous versions of CloudStack, the template ID was recorded for ROOT volume usages, when the VM is created from a template. Since CloudStack 4.2, the template ID isn't recorded anymore, due to a regression in the EVENT_VOLUME_CREATE event publishing: In commit https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=730d04508507409065a432e2aac931225947f268, the last EVENT_VOLUME_CREATE misses the template id, that was previously set. It seems a simple copy-paste error. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7009) [Automation]serviceofferingdetails needs to be handled properly in base.py
Srikanteswararao Talluri created CLOUDSTACK-7009: Summary: [Automation]serviceofferingdetails needs to be handled properly in base.py Key: CLOUDSTACK-7009 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7009 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Critical Fix For: 4.5.0 enhance base.py to handle the serviceofferingdetails we should be able to format the API request in the form of serviceofferingdetails[1].key=pciDevice serviceofferingdetails[1].value=Group of NVIDIA Corporation GK107GL [GRID K1] GPUs serviceofferingdetails[2].key=vgpuType serviceofferingdetails[2].value=GRID K120Q -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7009) [Automation]serviceofferingdetails needs to be handled properly in base.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047668#comment-14047668 ] ASF subversion and git services commented on CLOUDSTACK-7009: - Commit a34faae919b280fe6009e2608c95f59eafdfac48 in cloudstack's branch refs/heads/4.4-forward from SrikanteswaraRao Talluri [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a34faae ] CLOUDSTACK-7009: add ability to handle serviceofferingdetails to base.py to support creation of service offering upon passing details in the following format serviceofferingdetails[1].key=pciDevice serviceofferingdetails[1].value=Group of NVIDIA Corporation GK107GL [GRID K1] GPUs serviceofferingdetails[2].key=vgpuType serviceofferingdetails[2].value=GRID K120Q [Automation]serviceofferingdetails needs to be handled properly in base.py -- Key: CLOUDSTACK-7009 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7009 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Critical Fix For: 4.5.0 enhance base.py to handle the serviceofferingdetails we should be able to format the API request in the form of serviceofferingdetails[1].key=pciDevice serviceofferingdetails[1].value=Group of NVIDIA Corporation GK107GL [GRID K1] GPUs serviceofferingdetails[2].key=vgpuType serviceofferingdetails[2].value=GRID K120Q -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7009) [Automation]serviceofferingdetails needs to be handled properly in base.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047670#comment-14047670 ] ASF subversion and git services commented on CLOUDSTACK-7009: - Commit 2148a1a64d6d652b7aa24077d331a85173ce in cloudstack's branch refs/heads/master from SrikanteswaraRao Talluri [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2148a1a ] CLOUDSTACK-7009: add ability to handle serviceofferingdetails to base.py to support creation of service offering upon passing details in the following format serviceofferingdetails[1].key=pciDevice serviceofferingdetails[1].value=Group of NVIDIA Corporation GK107GL [GRID K1] GPUs serviceofferingdetails[2].key=vgpuType serviceofferingdetails[2].value=GRID K120Q [Automation]serviceofferingdetails needs to be handled properly in base.py -- Key: CLOUDSTACK-7009 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7009 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Critical Fix For: 4.5.0 enhance base.py to handle the serviceofferingdetails we should be able to format the API request in the form of serviceofferingdetails[1].key=pciDevice serviceofferingdetails[1].value=Group of NVIDIA Corporation GK107GL [GRID K1] GPUs serviceofferingdetails[2].key=vgpuType serviceofferingdetails[2].value=GRID K120Q -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7009) [Automation]serviceofferingdetails needs to be handled properly in base.py
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri resolved CLOUDSTACK-7009. -- Resolution: Fixed [Automation]serviceofferingdetails needs to be handled properly in base.py -- Key: CLOUDSTACK-7009 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7009 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.5.0 Reporter: Srikanteswararao Talluri Assignee: Srikanteswararao Talluri Priority: Critical Fix For: 4.5.0 enhance base.py to handle the serviceofferingdetails we should be able to format the API request in the form of serviceofferingdetails[1].key=pciDevice serviceofferingdetails[1].value=Group of NVIDIA Corporation GK107GL [GRID K1] GPUs serviceofferingdetails[2].key=vgpuType serviceofferingdetails[2].value=GRID K120Q -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7010) Add domain to createZones in marvin
John Dilley created CLOUDSTACK-7010: --- Summary: Add domain to createZones in marvin Key: CLOUDSTACK-7010 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7010 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.4.0 Reporter: John Dilley Marvin does not support domain names in createZones -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-7003) Arithmetic exception while creating a vdi on nfs volume in managed storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Tutkowski reassigned CLOUDSTACK-7003: -- Assignee: Mike Tutkowski Arithmetic exception while creating a vdi on nfs volume in managed storage. --- Key: CLOUDSTACK-7003 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7003 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: punith Assignee: Mike Tutkowski it seems we have a bug while creating a nfs disk on managed storage, file - CitrixResourceBase.java api - createVdi long unavailableSrSpace = sr.getPhysicalUtilisation(conn); 6216 long maxNumberOfTries = (totalSrSpace / unavailableSrSpace = 1) ? (totalSrSpace / unavailableSrSpace) : 1; since while creation nfs disk does not have a meta data written on it like in iscsi , unavailableSrSpace might turn out to be 0(zero), hence throwing an divide bt zero exception. sometimes the unavailable -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7003) Arithmetic exception while creating a vdi on nfs volume in managed storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047800#comment-14047800 ] ASF subversion and git services commented on CLOUDSTACK-7003: - Commit 03b1e86bde7c58b04e2fa33a3aab884d6af322ad in cloudstack's branch refs/heads/master from [~mike-tutkowski] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=03b1e86 ] CLOUDSTACK-7003 Arithmetic exception while creating a vdi on nfs volume in managed storage. --- Key: CLOUDSTACK-7003 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7003 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: punith it seems we have a bug while creating a nfs disk on managed storage, file - CitrixResourceBase.java api - createVdi long unavailableSrSpace = sr.getPhysicalUtilisation(conn); 6216 long maxNumberOfTries = (totalSrSpace / unavailableSrSpace = 1) ? (totalSrSpace / unavailableSrSpace) : 1; since while creation nfs disk does not have a meta data written on it like in iscsi , unavailableSrSpace might turn out to be 0(zero), hence throwing an divide bt zero exception. sometimes the unavailable -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7003) Arithmetic exception while creating a vdi on nfs volume in managed storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047810#comment-14047810 ] Mike Tutkowski commented on CLOUDSTACK-7003: Punith - Can you fetch this fix and perform a test of your own to see if the logic is OK for you? If it's OK, can you close out this ticket? Thanks! Arithmetic exception while creating a vdi on nfs volume in managed storage. --- Key: CLOUDSTACK-7003 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7003 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: punith Assignee: Mike Tutkowski it seems we have a bug while creating a nfs disk on managed storage, file - CitrixResourceBase.java api - createVdi long unavailableSrSpace = sr.getPhysicalUtilisation(conn); 6216 long maxNumberOfTries = (totalSrSpace / unavailableSrSpace = 1) ? (totalSrSpace / unavailableSrSpace) : 1; since while creation nfs disk does not have a meta data written on it like in iscsi , unavailableSrSpace might turn out to be 0(zero), hence throwing an divide bt zero exception. sometimes the unavailable -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7003) Arithmetic exception while creating a vdi on nfs volume in managed storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Tutkowski resolved CLOUDSTACK-7003. Resolution: Fixed Resolved in 03b1e86bde7c58b04e2fa33a3aab884d6af322ad Arithmetic exception while creating a vdi on nfs volume in managed storage. --- Key: CLOUDSTACK-7003 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7003 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: punith Assignee: Mike Tutkowski it seems we have a bug while creating a nfs disk on managed storage, file - CitrixResourceBase.java api - createVdi long unavailableSrSpace = sr.getPhysicalUtilisation(conn); 6216 long maxNumberOfTries = (totalSrSpace / unavailableSrSpace = 1) ? (totalSrSpace / unavailableSrSpace) : 1; since while creation nfs disk does not have a meta data written on it like in iscsi , unavailableSrSpace might turn out to be 0(zero), hence throwing an divide bt zero exception. sometimes the unavailable -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7011) [Automation] MS log getting created with owner root instead of cloud, and logs not capturing
Rayees Namathponnan created CLOUDSTACK-7011: --- Summary: [Automation] MS log getting created with owner root instead of cloud, and logs not capturing Key: CLOUDSTACK-7011 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7011 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.4.0 Environment: 4.4-forward RPM build Reporter: Rayees Namathponnan Priority: Critical Fix For: 4.4.0 Steps to reproduce 1 ) Create RPM build from centos 2) Install MS 3) Uninstall MS and Delete MS 4) Install MS again 5) Setup MS Expected result Installation should be succeeded, and during setup MS, logs should be captured in MS log Result MS log user is root and nothing capturing in MS log, see the permission below -rw-rw-r--. 1 cloud cloud 12518422 Jun 30 09:50 access_log.2014-06-30.txt -rw-rw-r--. 1 cloud cloud 38500897 Jun 30 09:50 apilog.log -rw-r--r--. 1 root root 0 Jun 30 00:27 api-server.log -rw-rw-r--. 1 cloud cloud0 Jun 30 00:27 catalina.2014-06-30.log -rw-r--r--. 1 cloud cloud 24646600 Jun 30 09:50 catalina.out -rw-rw-r--. 1 cloud cloud0 Jun 30 00:27 host-manager.2014-06-30.log -rw-rw-r--. 1 cloud cloud 874 Jun 30 00:43 localhost.2014-06-30.log -rw-r--r--. 1 root root 0 Jun 30 00:27 management-server.log -rw-rw-r--. 1 cloud cloud0 Jun 30 00:27 manager.2014-06-30.log -rw-r--r--. 1 root root 4479 Jun 30 00:27 setupManagement.log -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6997) conntrack set to a very low value on router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047904#comment-14047904 ] ASF subversion and git services commented on CLOUDSTACK-6997: - Commit d4a903fd6e935b7a2166e71496945fb0e74c13c8 in cloudstack's branch refs/heads/4.4 from Jayapal [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d4a903f ] CLOUDSTACK-6997: Increase proc ip_conntrack_max (cherry picked from commit 004d616322ba55d83407545f5b10c95ce48f75b5) conntrack set to a very low value on router --- Key: CLOUDSTACK-6997 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6997 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: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.4.0 Set ip_conntrack_max to 1 million ip conntrack value which is in sysctl.conf is not applied on VR. Debian wheezy sysctl.conf is not got loaded on boot time. There is bug in debian https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7012) [Atomation] Vcenter Hang during 4.4 automation runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-7012: Description: This issue observed with 4.4 automation run with Vcenter 5.0, during BVT run VM deployment fail, if you try to connect VCenter from console gets below error Call ServiceInstance.RetrieveContent for object ServiceInstance on Server 10.223.52.12 failed. I was using same VCenter more 1.5 year, i never faced this issue earlier, then i tried to run automation with 4.2 and 4.3 build last week i didnt observe this issue, i think some of the changes in CS causing VCenter to hang Observed below error in MS Log INFO [c.c.h.v.u.VmwareContext] (DirectAgentCronJob-455:ctx-71dce779) New VmwareContext object, current outstanding count: 451 INFO [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-455:ctx-71dce779) Scan hung worker VM to recycle INFO [c.c.h.v.u.VmwareContext] (DirectAgent-17:ctx-d197a13b 10.223.250.131) New VmwareContext object, current outstanding count: 452 was: This issue observed with 4.4 automation run with Vcenter 5.0, during BVT deployment failed, if you try to connect VCenter from console gets below error Call ServiceInstance.RetrieveContent for object ServiceInstance on Server 10.223.52.12 failed. I was using same VCenter more 1.5 year, i never faced this issue earlier, then i tried to run automation with 4.2 and 4.3 build last week i didnt observe this issue, i think some of the changes in CS causing VCenter to hang Observed below error in MS Log INFO [c.c.h.v.u.VmwareContext] (DirectAgentCronJob-455:ctx-71dce779) New VmwareContext object, current outstanding count: 451 INFO [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-455:ctx-71dce779) Scan hung worker VM to recycle INFO [c.c.h.v.u.VmwareContext] (DirectAgent-17:ctx-d197a13b 10.223.250.131) New VmwareContext object, current outstanding count: 452 [Atomation] Vcenter Hang during 4.4 automation runs --- Key: CLOUDSTACK-7012 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7012 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.4.0 Environment: VCenter 5.0 Exi 5.0 Reporter: Rayees Namathponnan Priority: Critical Fix For: 4.4.0 This issue observed with 4.4 automation run with Vcenter 5.0, during BVT run VM deployment fail, if you try to connect VCenter from console gets below error Call ServiceInstance.RetrieveContent for object ServiceInstance on Server 10.223.52.12 failed. I was using same VCenter more 1.5 year, i never faced this issue earlier, then i tried to run automation with 4.2 and 4.3 build last week i didnt observe this issue, i think some of the changes in CS causing VCenter to hang Observed below error in MS Log INFO [c.c.h.v.u.VmwareContext] (DirectAgentCronJob-455:ctx-71dce779) New VmwareContext object, current outstanding count: 451 INFO [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-455:ctx-71dce779) Scan hung worker VM to recycle INFO [c.c.h.v.u.VmwareContext] (DirectAgent-17:ctx-d197a13b 10.223.250.131) New VmwareContext object, current outstanding count: 452 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7012) [Atomation] Vcenter Hang during 4.4 automation runs
Rayees Namathponnan created CLOUDSTACK-7012: --- Summary: [Atomation] Vcenter Hang during 4.4 automation runs Key: CLOUDSTACK-7012 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7012 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.4.0 Environment: VCenter 5.0 Exi 5.0 Reporter: Rayees Namathponnan Priority: Critical Fix For: 4.4.0 This issue observed with 4.4 automation run with Vcenter 5.0, during BVT deployment failed, if you try to connect VCenter from console gets below error Call ServiceInstance.RetrieveContent for object ServiceInstance on Server 10.223.52.12 failed. I was using same VCenter more 1.5 year, i never faced this issue earlier, then i tried to run automation with 4.2 and 4.3 build last week i didnt observe this issue, i think some of the changes in CS causing VCenter to hang Observed below error in MS Log INFO [c.c.h.v.u.VmwareContext] (DirectAgentCronJob-455:ctx-71dce779) New VmwareContext object, current outstanding count: 451 INFO [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-455:ctx-71dce779) Scan hung worker VM to recycle INFO [c.c.h.v.u.VmwareContext] (DirectAgent-17:ctx-d197a13b 10.223.250.131) New VmwareContext object, current outstanding count: 452 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7012) [Atomation] Vcenter Hang during 4.4 automation runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-7012: Description: This issue observed with 4.4 automation run with Vcenter 5.0, during BVT run VM deployment fail, if you try to connect VCenter from console gets below error Call ServiceInstance.RetrieveContent for object ServiceInstance on Server 10.223.52.12 failed. I was using same VCenter more 1.5 year, i never faced this issue earlier, then i tried to run automation with 4.2 and 4.3 build last week i didnt observe this issue, i think some of the changes in CS 4.4 causing VCenter to hang Observed below error in MS Log INFO [c.c.h.v.u.VmwareContext] (DirectAgentCronJob-455:ctx-71dce779) New VmwareContext object, current outstanding count: 451 INFO [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-455:ctx-71dce779) Scan hung worker VM to recycle INFO [c.c.h.v.u.VmwareContext] (DirectAgent-17:ctx-d197a13b 10.223.250.131) New VmwareContext object, current outstanding count: 452 was: This issue observed with 4.4 automation run with Vcenter 5.0, during BVT run VM deployment fail, if you try to connect VCenter from console gets below error Call ServiceInstance.RetrieveContent for object ServiceInstance on Server 10.223.52.12 failed. I was using same VCenter more 1.5 year, i never faced this issue earlier, then i tried to run automation with 4.2 and 4.3 build last week i didnt observe this issue, i think some of the changes in CS causing VCenter to hang Observed below error in MS Log INFO [c.c.h.v.u.VmwareContext] (DirectAgentCronJob-455:ctx-71dce779) New VmwareContext object, current outstanding count: 451 INFO [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-455:ctx-71dce779) Scan hung worker VM to recycle INFO [c.c.h.v.u.VmwareContext] (DirectAgent-17:ctx-d197a13b 10.223.250.131) New VmwareContext object, current outstanding count: 452 [Atomation] Vcenter Hang during 4.4 automation runs --- Key: CLOUDSTACK-7012 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7012 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.4.0 Environment: VCenter 5.0 Exi 5.0 Reporter: Rayees Namathponnan Priority: Critical Fix For: 4.4.0 This issue observed with 4.4 automation run with Vcenter 5.0, during BVT run VM deployment fail, if you try to connect VCenter from console gets below error Call ServiceInstance.RetrieveContent for object ServiceInstance on Server 10.223.52.12 failed. I was using same VCenter more 1.5 year, i never faced this issue earlier, then i tried to run automation with 4.2 and 4.3 build last week i didnt observe this issue, i think some of the changes in CS 4.4 causing VCenter to hang Observed below error in MS Log INFO [c.c.h.v.u.VmwareContext] (DirectAgentCronJob-455:ctx-71dce779) New VmwareContext object, current outstanding count: 451 INFO [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-455:ctx-71dce779) Scan hung worker VM to recycle INFO [c.c.h.v.u.VmwareContext] (DirectAgent-17:ctx-d197a13b 10.223.250.131) New VmwareContext object, current outstanding count: 452 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7012) [Atomation] Vcenter Hang during 4.4 automation runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan updated CLOUDSTACK-7012: Attachment: catalina.rar [Atomation] Vcenter Hang during 4.4 automation runs --- Key: CLOUDSTACK-7012 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7012 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.4.0 Environment: VCenter 5.0 Exi 5.0 Reporter: Rayees Namathponnan Priority: Critical Fix For: 4.4.0 Attachments: catalina.rar This issue observed with 4.4 automation run with Vcenter 5.0, during BVT run VM deployment fail, if you try to connect VCenter from console gets below error Call ServiceInstance.RetrieveContent for object ServiceInstance on Server 10.223.52.12 failed. I was using same VCenter more 1.5 year, i never faced this issue earlier, then i tried to run automation with 4.2 and 4.3 build last week i didnt observe this issue, i think some of the changes in CS 4.4 causing VCenter to hang Observed below error in MS Log INFO [c.c.h.v.u.VmwareContext] (DirectAgentCronJob-455:ctx-71dce779) New VmwareContext object, current outstanding count: 451 INFO [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-455:ctx-71dce779) Scan hung worker VM to recycle INFO [c.c.h.v.u.VmwareContext] (DirectAgent-17:ctx-d197a13b 10.223.250.131) New VmwareContext object, current outstanding count: 452 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-7005) [Automation] Failed to start MS with latest 4.4 RPM builds
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan resolved CLOUDSTACK-7005. - Resolution: Fixed Assignee: Ian Duffy I an fixed this [Automation] Failed to start MS with latest 4.4 RPM builds -- Key: CLOUDSTACK-7005 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7005 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.4.0 Environment: RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Ian Duffy Priority: Blocker Fix For: 4.4.0 Attachments: management.rar Create RPM build from 4.4-forward branch Setup MS and start Result Failed to start MS with below error 2014-06-29 07:43:12,465 INFO [c.c.c.ClusterManagerImpl] (main:null) Start configuring cluster manager : ClusterManagerImpl 2014-06-29 07:43:12,466 INFO [c.c.c.ClusterManagerImpl] (main:null) Cluster node IP : 10.223.49.197 2014-06-29 07:43:12,479 INFO [c.c.c.ClusterManagerImpl] (main:null) Cluster manager is configured. 2014-06-29 07:43:12,648 DEBUG [c.c.u.c.DBEncryptionUtil] (main:null) Error while decrypting: 6 2014-06-29 07:43:29,465 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.CloudStackAccountDaoImpl_EnhancerByCloudStack_f8e983ac is it due to below check-in ? https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blobdiff;f=setup/db/db/schema-430to440.sql;h=6c9783a9781993a5bb7127083baa2efaad69e8fb;hp=0293986167cd663a72d0849ab51073fc5f84da31;hb=96412e3e58fd1ced9d269e4552aaa6410bedf556;hpb=2498f65683bd529b2b03bac9a6cfd2fdbf65aca2 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-7005) [Automation] Failed to start MS with latest 4.4 RPM builds
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan closed CLOUDSTACK-7005. --- Verified with latest build [Automation] Failed to start MS with latest 4.4 RPM builds -- Key: CLOUDSTACK-7005 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7005 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.4.0 Environment: RHEL 6.3 Reporter: Rayees Namathponnan Assignee: Ian Duffy Priority: Blocker Fix For: 4.4.0 Attachments: management.rar Create RPM build from 4.4-forward branch Setup MS and start Result Failed to start MS with below error 2014-06-29 07:43:12,465 INFO [c.c.c.ClusterManagerImpl] (main:null) Start configuring cluster manager : ClusterManagerImpl 2014-06-29 07:43:12,466 INFO [c.c.c.ClusterManagerImpl] (main:null) Cluster node IP : 10.223.49.197 2014-06-29 07:43:12,479 INFO [c.c.c.ClusterManagerImpl] (main:null) Cluster manager is configured. 2014-06-29 07:43:12,648 DEBUG [c.c.u.c.DBEncryptionUtil] (main:null) Error while decrypting: 6 2014-06-29 07:43:29,465 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.CloudStackAccountDaoImpl_EnhancerByCloudStack_f8e983ac is it due to below check-in ? https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blobdiff;f=setup/db/db/schema-430to440.sql;h=6c9783a9781993a5bb7127083baa2efaad69e8fb;hp=0293986167cd663a72d0849ab51073fc5f84da31;hb=96412e3e58fd1ced9d269e4552aaa6410bedf556;hpb=2498f65683bd529b2b03bac9a6cfd2fdbf65aca2 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7012) [Atomation] Vcenter Hang during 4.4 automation runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-7012: --- Assignee: Kelven Yang [Atomation] Vcenter Hang during 4.4 automation runs --- Key: CLOUDSTACK-7012 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7012 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.4.0 Environment: VCenter 5.0 Exi 5.0 Reporter: Rayees Namathponnan Assignee: Kelven Yang Priority: Critical Fix For: 4.4.0 Attachments: catalina.rar This issue observed with 4.4 automation run with Vcenter 5.0, during BVT run VM deployment fail, if you try to connect VCenter from console gets below error Call ServiceInstance.RetrieveContent for object ServiceInstance on Server 10.223.52.12 failed. I was using same VCenter more 1.5 year, i never faced this issue earlier, then i tried to run automation with 4.2 and 4.3 build last week i didnt observe this issue, i think some of the changes in CS 4.4 causing VCenter to hang Observed below error in MS Log INFO [c.c.h.v.u.VmwareContext] (DirectAgentCronJob-455:ctx-71dce779) New VmwareContext object, current outstanding count: 451 INFO [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-455:ctx-71dce779) Scan hung worker VM to recycle INFO [c.c.h.v.u.VmwareContext] (DirectAgent-17:ctx-d197a13b 10.223.250.131) New VmwareContext object, current outstanding count: 452 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-7012) [Atomation] Vcenter Hang during 4.4 automation runs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047995#comment-14047995 ] Animesh Chaturvedi commented on CLOUDSTACK-7012: Kelven can you check on this? [Atomation] Vcenter Hang during 4.4 automation runs --- Key: CLOUDSTACK-7012 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7012 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.4.0 Environment: VCenter 5.0 Exi 5.0 Reporter: Rayees Namathponnan Assignee: Kelven Yang Priority: Critical Fix For: 4.4.0 Attachments: catalina.rar This issue observed with 4.4 automation run with Vcenter 5.0, during BVT run VM deployment fail, if you try to connect VCenter from console gets below error Call ServiceInstance.RetrieveContent for object ServiceInstance on Server 10.223.52.12 failed. I was using same VCenter more 1.5 year, i never faced this issue earlier, then i tried to run automation with 4.2 and 4.3 build last week i didnt observe this issue, i think some of the changes in CS 4.4 causing VCenter to hang Observed below error in MS Log INFO [c.c.h.v.u.VmwareContext] (DirectAgentCronJob-455:ctx-71dce779) New VmwareContext object, current outstanding count: 451 INFO [c.c.h.v.r.VmwareResource] (DirectAgentCronJob-455:ctx-71dce779) Scan hung worker VM to recycle INFO [c.c.h.v.u.VmwareContext] (DirectAgent-17:ctx-d197a13b 10.223.250.131) New VmwareContext object, current outstanding count: 452 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7013) [Automation] AttributeError: type object 'TestFailureScenariosRemoveNicFromVM' has no attribute 'append'
Chandan Purushothama created CLOUDSTACK-7013:
Summary: [Automation] AttributeError: type object
'TestFailureScenariosRemoveNicFromVM' has no attribute 'append'
Key: CLOUDSTACK-7013
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7013
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
Priority: Critical
Fix For: 4.4.0
==
Bug in test script:
==
cls.account =
Account.create(cls.api_client,cls.services[account],domainid = cls.domain.id)
cls.append(cls.account) BUG: should be cls.__cleanup.append
cls.service_offering =
ServiceOffering.create(cls.api_client,cls.services[service_offering])
cls._cleanup.append(cls.service_offering)
Test Script Failure:
test_26_add_nic_insufficient_permission
(integration.component.test_add_remove_network.TestFailureScenariosAddNetworkToVM):
CRITICAL: EXCEPTION: test_26_add_nic_insufficient_permission: ['Traceback
(most recent call last):\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in run\n
self.setUp()\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in setUp\n
self.setupContext(ancestor)\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in
setupContext\ntry_run(context, names)\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n
return func()\n', ' File
/home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_add_remove_network.py,
line 1392, in setUpClass\ncls.append(cls.account)\n', AttributeError:
type object 'TestFailureScenariosRemoveNicFromVM' has no attribute 'append'\n]
- end captured logging -
Stacktrace
File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in run
self.setUp()
File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in
setUp
self.setupContext(ancestor)
File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in
setupContext
try_run(context, names)
File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in
try_run
return func()
File
/home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_add_remove_network.py,
line 1392, in setUpClass
cls.append(cls.account)
'type object \'TestFailureScenariosRemoveNicFromVM\' has no attribute
\'append\'\n begin captured logging
\ntest_26_add_nic_insufficient_permission
(integration.component.test_add_remove_network.TestFailureScenariosAddNetworkToVM):
DEBUG: Payload: {\'apiKey\':
u\'Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Q\',
\'id\': u\'853b13be-4f75-4ca9-9f7c-3cf303d3cc2d\', \'state\': \'Disabled\',
\'command\': \'updateNetworkOffering\', \'signature\':
\'pP6GEHIbIDVHMxeYxAyQahpCxbI=\', \'response\':
\'json\'}\ntest_26_add_nic_insufficient_permission
(integration.component.test_add_remove_network.TestFailureScenariosAddNetworkToVM):
DEBUG: Sending GET Cmd :
updateNetworkOffering===\nrequests.packages.urllib3.connectionpool: INFO:
Starting new HTTP connection (1):
10.220.153.217\nrequests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Qid=853b13be-4f75-4ca9-9f7c-3cf303d3cc2dstate=Disabledcommand=updateNetworkOfferingsignature=pP6GEHIbIDVHMxeYxAyQahpCxbI%3Dresponse=json
HTTP/1.1 200
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CLOUDSTACK-7014) [Automation] type object 'TestAffinityGroupsAdminUser' has no attribute '_TestAffinityGroupsAdminUser__cleanup - test_affinity_groups.py
Chandan Purushothama created CLOUDSTACK-7014: Summary: [Automation] type object 'TestAffinityGroupsAdminUser' has no attribute '_TestAffinityGroupsAdminUser__cleanup - test_affinity_groups.py Key: CLOUDSTACK-7014 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7014 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.4.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.4.0 == Bug in test script: == @classmethod def tearDownClass(cls): try: cls.api_client = super(TestAffinityGroupsAdminUser, cls).getClsTestClient().getApiClient() #Clean up, terminate the created templates cleanup_resources(cls.api_client, cls.__cleanup) BUG: It should be cls._cleanup except Exception as e: raise Exception(Warning: Exception during cleanup : %s % e) Test Script Failure: Warning: Exception during cleanup : type object 'TestAffinityGroupsAdminUser' has no attribute '_TestAffinityGroupsAdminUser__cleanup' begin captured logging test_07_delete_aff_grp_of_other_user (integration.component.test_affinity_groups.TestAffinityGroupsAdminUser): CRITICAL: EXCEPTION: test_07_delete_aff_grp_of_other_user: ['Traceback (most recent call last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n self.tearDown()\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\n self.teardownContext(ancestor)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\ntry_run(context, names)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n return func()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 1501, in tearDownClass\nraise Exception(Warning: Exception during cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type object 'TestAffinityGroupsAdminUser' has no attribute '_TestAffinityGroupsAdminUser__cleanup'\n] - end captured logging - Stacktrace File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run self.tearDown() File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown self.teardownContext(ancestor) File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext try_run(context, names) File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run return func() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 1501, in tearDownClass raise Exception(Warning: Exception during cleanup : %s % e) 'Warning: Exception during cleanup : type object \'TestAffinityGroupsAdminUser\' has no attribute \'_TestAffinityGroupsAdminUser__cleanup\'\n begin captured logging \ntest_07_delete_aff_grp_of_other_user (integration.component.test_affinity_groups.TestAffinityGroupsAdminUser): CRITICAL: EXCEPTION: test_07_delete_aff_grp_of_other_user: [\'Traceback (most recent call last):\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n self.tearDown()\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\\nself.teardownContext(ancestor)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\\ntry_run(context, names)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\\n return func()\\n\', \' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 1501, in tearDownClass\\nraise Exception(Warning: Exception during cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type object \'TestAffinityGroupsAdminUser\' has no attribute \'_TestAffinityGroupsAdminUser__cleanup\'\\n]\n- end captured logging -' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7014) [Automation] type object 'TestAffinityGroupsAdminUser' has no attribute '_TestAffinityGroupsAdminUser__cleanup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7014: - Summary: [Automation] type object 'TestAffinityGroupsAdminUser' has no attribute '_TestAffinityGroupsAdminUser__cleanup (was: [Automation] type object 'TestAffinityGroupsAdminUser' has no attribute '_TestAffinityGroupsAdminUser__cleanup - test_affinity_groups.py) [Automation] type object 'TestAffinityGroupsAdminUser' has no attribute '_TestAffinityGroupsAdminUser__cleanup --- Key: CLOUDSTACK-7014 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7014 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.4.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.4.0 == Bug in test script: == @classmethod def tearDownClass(cls): try: cls.api_client = super(TestAffinityGroupsAdminUser, cls).getClsTestClient().getApiClient() #Clean up, terminate the created templates cleanup_resources(cls.api_client, cls.__cleanup) BUG: It should be cls._cleanup except Exception as e: raise Exception(Warning: Exception during cleanup : %s % e) Test Script Failure: Warning: Exception during cleanup : type object 'TestAffinityGroupsAdminUser' has no attribute '_TestAffinityGroupsAdminUser__cleanup' begin captured logging test_07_delete_aff_grp_of_other_user (integration.component.test_affinity_groups.TestAffinityGroupsAdminUser): CRITICAL: EXCEPTION: test_07_delete_aff_grp_of_other_user: ['Traceback (most recent call last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n self.tearDown()\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\nself.teardownContext(ancestor)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\ntry_run(context, names)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n return func()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 1501, in tearDownClass\nraise Exception(Warning: Exception during cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type object 'TestAffinityGroupsAdminUser' has no attribute '_TestAffinityGroupsAdminUser__cleanup'\n] - end captured logging - Stacktrace File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run self.tearDown() File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown self.teardownContext(ancestor) File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext try_run(context, names) File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run return func() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 1501, in tearDownClass raise Exception(Warning: Exception during cleanup : %s % e) 'Warning: Exception during cleanup : type object \'TestAffinityGroupsAdminUser\' has no attribute \'_TestAffinityGroupsAdminUser__cleanup\'\n begin captured logging \ntest_07_delete_aff_grp_of_other_user (integration.component.test_affinity_groups.TestAffinityGroupsAdminUser): CRITICAL: EXCEPTION: test_07_delete_aff_grp_of_other_user: [\'Traceback (most recent call last):\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n self.tearDown()\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\\nself.teardownContext(ancestor)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\\ntry_run(context, names)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\\nreturn func()\\n\', \' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 1501, in tearDownClass\\nraise Exception(Warning: Exception during cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type object \'TestAffinityGroupsAdminUser\' has no attribute
[jira] [Closed] (CLOUDSTACK-7006) Template ID is missing in ROOT volume usages
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen closed CLOUDSTACK-7006. -- Resolution: Fixed Fix Version/s: 4.3.1 Template ID is missing in ROOT volume usages Key: CLOUDSTACK-7006 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7006 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Usage Affects Versions: 4.2.0, 4.2.1, 4.3.0, 4.4.0 Reporter: Olivier Lemasle Assignee: Olivier Lemasle Priority: Minor Fix For: 4.3.1 In previous versions of CloudStack, the template ID was recorded for ROOT volume usages, when the VM is created from a template. Since CloudStack 4.2, the template ID isn't recorded anymore, due to a regression in the EVENT_VOLUME_CREATE event publishing: In commit https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=730d04508507409065a432e2aac931225947f268, the last EVENT_VOLUME_CREATE misses the template id, that was previously set. It seems a simple copy-paste error. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6297) Cloudstack Fails to Launch on Ubuntu missing MySQL Driver
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048047#comment-14048047 ] sebastien goasguen commented on CLOUDSTACK-6297: I believe this is resolved in the latest 4.3 branch. I was able to setup cloudstack on ubuntu 14.04. Cloudstack Fails to Launch on Ubuntu missing MySQL Driver - Key: CLOUDSTACK-6297 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6297 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Environment: Ubuntu Server 13.10 Reporter: Joshua Rogers Priority: Critical Fix For: 4.3.1 On Ubuntu Server 13.10, installing Cloudstack 4.3 as specified in the documentation does not produce a runnable system. Cloudstack-management dies shortly after it starts with a stack trace indicating that it can't find the MySQL driver (trace listed below.) This continues to occur after running apt-get install libmysql-java cp /usr/share/java/mysql-connector-java-5.1.25.jar /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/ reboot --- Stack Trace --- 2014-03-27 20:53:11,112 INFO [c.c.u.d.T.Transaction] (main:null) Is Data Base High Availiability enabled? Ans : false 2014-03-27 20:53:11,186 ERROR [c.c.u.d.Merovingian2] (main:null) Unable to get a new db connection java.sql.SQLException: No suitable driver found for jdbc:mysql://localhost:3306/cloud?autoReconnect=trueprepStmtCacheSize=517cachePrepStmts=true at java.sql.DriverManager.getConnection(DriverManager.java:635) at java.sql.DriverManager.getConnection(DriverManager.java:195) at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582) at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188) at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106) at com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithException(TransactionLegacy.java:204) at com.cloud.utils.db.Merovingian2.init(Merovingian2.java:68) at com.cloud.utils.db.Merovingian2.createLockMaster(Merovingian2.java:80) at com.cloud.server.LockMasterListener.init(LockMasterListener.java:33) 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:534) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:121) at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:280) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1045) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:949) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:628) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) at
[jira] [Resolved] (CLOUDSTACK-6297) Cloudstack Fails to Launch on Ubuntu missing MySQL Driver
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-6297. Resolution: Fixed Fix Version/s: 4.3.1 Cloudstack Fails to Launch on Ubuntu missing MySQL Driver - Key: CLOUDSTACK-6297 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6297 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Environment: Ubuntu Server 13.10 Reporter: Joshua Rogers Priority: Critical Fix For: 4.3.1 On Ubuntu Server 13.10, installing Cloudstack 4.3 as specified in the documentation does not produce a runnable system. Cloudstack-management dies shortly after it starts with a stack trace indicating that it can't find the MySQL driver (trace listed below.) This continues to occur after running apt-get install libmysql-java cp /usr/share/java/mysql-connector-java-5.1.25.jar /usr/share/cloudstack-management/webapps/client/WEB-INF/lib/ reboot --- Stack Trace --- 2014-03-27 20:53:11,112 INFO [c.c.u.d.T.Transaction] (main:null) Is Data Base High Availiability enabled? Ans : false 2014-03-27 20:53:11,186 ERROR [c.c.u.d.Merovingian2] (main:null) Unable to get a new db connection java.sql.SQLException: No suitable driver found for jdbc:mysql://localhost:3306/cloud?autoReconnect=trueprepStmtCacheSize=517cachePrepStmts=true at java.sql.DriverManager.getConnection(DriverManager.java:635) at java.sql.DriverManager.getConnection(DriverManager.java:195) at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582) at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188) at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106) at com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithException(TransactionLegacy.java:204) at com.cloud.utils.db.Merovingian2.init(Merovingian2.java:68) at com.cloud.utils.db.Merovingian2.createLockMaster(Merovingian2.java:80) at com.cloud.server.LockMasterListener.init(LockMasterListener.java:33) 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:534) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:121) at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:280) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1045) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:949) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:628) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) at org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:141)
[jira] [Commented] (CLOUDSTACK-5853) cannot deploy vm with differing service storage tag and data disk storage tag
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048057#comment-14048057 ] sebastien goasguen commented on CLOUDSTACK-5853: Can someone update this and close the ticket or not ? [~prachidamle] ? thx cannot deploy vm with differing service storage tag and data disk storage tag - Key: CLOUDSTACK-5853 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5853 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.0, 4.3.0, 4.4.0 Reporter: Marcus Sorensen Assignee: Marcus Sorensen Priority: Critical Fix For: 4.4.0 Create two storage pools, one with storage tag X, one with storage tag Y. Create a service offering with storage tag X. Create a disk offering with storage tag Y. Attempt to deploy a virtual machine with a datadisk, using given offerings, it fails. Deployment planner keeps a global object 'avoid'. It loops through each volume to be created, asking storage allocators for matching pools, passing this avoid object. First disk matches a pool or pools, adds ALL other pools to avoid object, then deployment planner attaches matching pools to a list for that disk. Second disk matches a pool, adds all other pools to avoid object, then deployment planner says wait, matching pool is in avoid, can't use it. Oops. In fact, at this point ALL pools are in avoid (unless there are other pools that have both tags). Need to remove matching pool from the avoid set during each select phase. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6209) Building noredist packages for ubuntu doesn't include vmware jars in systemvm.iso
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sebastien goasguen resolved CLOUDSTACK-6209. Resolution: Fixed wiki doc issue Building noredist packages for ubuntu doesn't include vmware jars in systemvm.iso - Key: CLOUDSTACK-6209 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6209 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Packaging, SystemVM Affects Versions: 4.2.0, 4.3.0, 4.4.0 Environment: Ubuntu 12.04.4 LTS Reporter: David Bierce Building Debian/Ubuntu packages with support for VMware completes but doesn't include the VMware jars in the Systemvm.iso. Building using the guide here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#HowtobuildCloudStack-BuildingDEBpackages With the actual options of: mvn clean install -P deps -Dnoredist; export ACS_BUILD_OPTS=-Dnoredist; dpkg-buildpackage Building with the follow options creates a usable build with correct systevm.iso: mvn install -P deps -Dnoredist -Dnonoss; export ACS_BUILD_OPTS=-Dnoredist -Dnonoss; dpkg-buildpackage -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6209) Building noredist packages for ubuntu doesn't include vmware jars in systemvm.iso
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048076#comment-14048076 ] sebastien goasguen commented on CLOUDSTACK-6209: Made a note on the wiki Building noredist packages for ubuntu doesn't include vmware jars in systemvm.iso - Key: CLOUDSTACK-6209 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6209 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Packaging, SystemVM Affects Versions: 4.2.0, 4.3.0, 4.4.0 Environment: Ubuntu 12.04.4 LTS Reporter: David Bierce Building Debian/Ubuntu packages with support for VMware completes but doesn't include the VMware jars in the Systemvm.iso. Building using the guide here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#HowtobuildCloudStack-BuildingDEBpackages With the actual options of: mvn clean install -P deps -Dnoredist; export ACS_BUILD_OPTS=-Dnoredist; dpkg-buildpackage Building with the follow options creates a usable build with correct systevm.iso: mvn install -P deps -Dnoredist -Dnonoss; export ACS_BUILD_OPTS=-Dnoredist -Dnonoss; dpkg-buildpackage -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-5935) Problem with VMware snapshot when datastore has a space in its name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Tutkowski closed CLOUDSTACK-5935. -- Duplicate of 5933 Problem with VMware snapshot when datastore has a space in its name --- Key: CLOUDSTACK-5935 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5935 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.3.0 Environment: Management Server on Ubuntu 12.04.1 ESXi 5.1 Reporter: Mike Tutkowski Fix For: 4.4.0 I have two hosts in my VMware cluster. I elected to have vSphere Client use its default names for the datastore of each host's local storage. These names are the following: datastore1 and datastore1 (1) Note the presence of a space in the second datastore name. This space causes our creation of a VM snapshot to return to the management server an incorrect path field. For example, let's say the path in the DB of our root disk is abcxyz before the VM snapshot. After the VM snapshot, it should be abcxyz-01; however, it is still abcxyz. The problem is in this method in VmwareStorageManagerImpl: extractSnapshotBaseFileName That method is treating the space character as a delimiter. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Reopened] (CLOUDSTACK-5934) Problem with VMware snapshot when datastore has a space in its name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Tutkowski reopened CLOUDSTACK-5934: Problem with VMware snapshot when datastore has a space in its name --- Key: CLOUDSTACK-5934 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5934 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.3.0 Environment: Management Server on Ubuntu 12.04.1 ESXi 5.1 Reporter: Mike Tutkowski Fix For: 4.4.0 I have two hosts in my VMware cluster. I elected to have vSphere Client use its default names for the datastore of each host's local storage. These names are the following: datastore1 and datastore1 (1) Note the presence of a space in the second datastore name. This space causes our creation of a VM snapshot to return to the management server an incorrect path field. For example, let's say the path in the DB of our root disk is abcxyz before the VM snapshot. After the VM snapshot, it should be abcxyz-01; however, it is still abcxyz. The problem is in this method in VmwareStorageManagerImpl: extractSnapshotBaseFileName That method is treating the space character as a delimiter. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-5934) Problem with VMware snapshot when datastore has a space in its name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Tutkowski resolved CLOUDSTACK-5934. Resolution: Duplicate Duplicate of 5933 Problem with VMware snapshot when datastore has a space in its name --- Key: CLOUDSTACK-5934 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5934 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.3.0 Environment: Management Server on Ubuntu 12.04.1 ESXi 5.1 Reporter: Mike Tutkowski Fix For: 4.4.0 I have two hosts in my VMware cluster. I elected to have vSphere Client use its default names for the datastore of each host's local storage. These names are the following: datastore1 and datastore1 (1) Note the presence of a space in the second datastore name. This space causes our creation of a VM snapshot to return to the management server an incorrect path field. For example, let's say the path in the DB of our root disk is abcxyz before the VM snapshot. After the VM snapshot, it should be abcxyz-01; however, it is still abcxyz. The problem is in this method in VmwareStorageManagerImpl: extractSnapshotBaseFileName That method is treating the space character as a delimiter. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6634) DOC: update the ldap section of the admin guide
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048090#comment-14048090 ] sebastien goasguen commented on CLOUDSTACK-6634: [~rajanik] Care to submit a pull request ? I know you can :) DOC: update the ldap section of the admin guide --- Key: CLOUDSTACK-6634 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6634 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.3.0 Reporter: Rajani Karuturi Labels: ldap Fix For: 4.4.0 http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.3/accounts.html#using-an-ldap-server-for-user-authentication there are changes/enhancements in the way ldap server is configured since 4.3 documentation needs to be updated with the latest info. https://cwiki.apache.org/confluence/display/CLOUDSTACK/LDAP+user+provisioning -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-5934) Problem with VMware snapshot when datastore has a space in its name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Tutkowski resolved CLOUDSTACK-5934. Resolution: Fixed Duplicate of 5933 Problem with VMware snapshot when datastore has a space in its name --- Key: CLOUDSTACK-5934 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5934 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.3.0 Environment: Management Server on Ubuntu 12.04.1 ESXi 5.1 Reporter: Mike Tutkowski Fix For: 4.4.0 I have two hosts in my VMware cluster. I elected to have vSphere Client use its default names for the datastore of each host's local storage. These names are the following: datastore1 and datastore1 (1) Note the presence of a space in the second datastore name. This space causes our creation of a VM snapshot to return to the management server an incorrect path field. For example, let's say the path in the DB of our root disk is abcxyz before the VM snapshot. After the VM snapshot, it should be abcxyz-01; however, it is still abcxyz. The problem is in this method in VmwareStorageManagerImpl: extractSnapshotBaseFileName That method is treating the space character as a delimiter. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-5935) Problem with VMware snapshot when datastore has a space in its name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Tutkowski resolved CLOUDSTACK-5935. Resolution: Duplicate Duplicate of 5933 Problem with VMware snapshot when datastore has a space in its name --- Key: CLOUDSTACK-5935 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5935 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.3.0 Environment: Management Server on Ubuntu 12.04.1 ESXi 5.1 Reporter: Mike Tutkowski Fix For: 4.4.0 I have two hosts in my VMware cluster. I elected to have vSphere Client use its default names for the datastore of each host's local storage. These names are the following: datastore1 and datastore1 (1) Note the presence of a space in the second datastore name. This space causes our creation of a VM snapshot to return to the management server an incorrect path field. For example, let's say the path in the DB of our root disk is abcxyz before the VM snapshot. After the VM snapshot, it should be abcxyz-01; however, it is still abcxyz. The problem is in this method in VmwareStorageManagerImpl: extractSnapshotBaseFileName That method is treating the space character as a delimiter. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-5934) Problem with VMware snapshot when datastore has a space in its name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Tutkowski closed CLOUDSTACK-5934. -- Duplicate of 5933 Problem with VMware snapshot when datastore has a space in its name --- Key: CLOUDSTACK-5934 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5934 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.3.0 Environment: Management Server on Ubuntu 12.04.1 ESXi 5.1 Reporter: Mike Tutkowski Fix For: 4.4.0 I have two hosts in my VMware cluster. I elected to have vSphere Client use its default names for the datastore of each host's local storage. These names are the following: datastore1 and datastore1 (1) Note the presence of a space in the second datastore name. This space causes our creation of a VM snapshot to return to the management server an incorrect path field. For example, let's say the path in the DB of our root disk is abcxyz before the VM snapshot. After the VM snapshot, it should be abcxyz-01; however, it is still abcxyz. The problem is in this method in VmwareStorageManagerImpl: extractSnapshotBaseFileName That method is treating the space character as a delimiter. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-5933) Problem with VMware snapshot when datastore has a space in its name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Tutkowski updated CLOUDSTACK-5933: --- Affects Version/s: (was: 4.5.0) 4.3.0 Problem with VMware snapshot when datastore has a space in its name --- Key: CLOUDSTACK-5933 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5933 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.3.0 Environment: Management Server on Ubuntu 12.04.1 ESXi 5.1 Reporter: Mike Tutkowski Fix For: 4.5.0 I have two hosts in my VMware cluster. I elected to have vSphere Client use its default names for the datastore of each host's local storage. These names are the following: datastore1 and datastore1 (1) Note the presence of a space in the second datastore name. This space causes our creation of a VM snapshot to return to the management server an incorrect path field. For example, let's say the path in the DB of our root disk is abcxyz before the VM snapshot. After the VM snapshot, it should be abcxyz-01; however, it is still abcxyz. The problem is in this method in VmwareStorageManagerImpl: extractSnapshotBaseFileName That method is treating the space character as a delimiter. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-5933) Problem with VMware snapshot when datastore has a space in its name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Tutkowski updated CLOUDSTACK-5933: --- Fix Version/s: (was: 4.4.0) 4.5.0 Problem with VMware snapshot when datastore has a space in its name --- Key: CLOUDSTACK-5933 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5933 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.3.0 Environment: Management Server on Ubuntu 12.04.1 ESXi 5.1 Reporter: Mike Tutkowski Fix For: 4.5.0 I have two hosts in my VMware cluster. I elected to have vSphere Client use its default names for the datastore of each host's local storage. These names are the following: datastore1 and datastore1 (1) Note the presence of a space in the second datastore name. This space causes our creation of a VM snapshot to return to the management server an incorrect path field. For example, let's say the path in the DB of our root disk is abcxyz before the VM snapshot. After the VM snapshot, it should be abcxyz-01; however, it is still abcxyz. The problem is in this method in VmwareStorageManagerImpl: extractSnapshotBaseFileName That method is treating the space character as a delimiter. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-5933) Problem with VMware snapshot when datastore has a space in its name
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Tutkowski updated CLOUDSTACK-5933: --- Affects Version/s: (was: 4.3.0) 4.5.0 Problem with VMware snapshot when datastore has a space in its name --- Key: CLOUDSTACK-5933 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5933 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.3.0 Environment: Management Server on Ubuntu 12.04.1 ESXi 5.1 Reporter: Mike Tutkowski Fix For: 4.5.0 I have two hosts in my VMware cluster. I elected to have vSphere Client use its default names for the datastore of each host's local storage. These names are the following: datastore1 and datastore1 (1) Note the presence of a space in the second datastore name. This space causes our creation of a VM snapshot to return to the management server an incorrect path field. For example, let's say the path in the DB of our root disk is abcxyz before the VM snapshot. After the VM snapshot, it should be abcxyz-01; however, it is still abcxyz. The problem is in this method in VmwareStorageManagerImpl: extractSnapshotBaseFileName That method is treating the space character as a delimiter. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7015) [Automation] type object 'TestDeleteAffinityGroups' has no attribute '_TestDeleteAffinityGroups__cleanup'
Chandan Purushothama created CLOUDSTACK-7015: Summary: [Automation] type object 'TestDeleteAffinityGroups' has no attribute '_TestDeleteAffinityGroups__cleanup' Key: CLOUDSTACK-7015 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7015 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.4.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.4.0 == Bug in test script: == @classmethod def tearDownClass(cls): try: cls.api_client = super(TestDeployVMAffinityGroups, cls).getClsTestClient().getApiClient() #Clean up, terminate the created templates cleanup_resources(cls.api_client, cls.__cleanup) BUG: It should be cls._cleanup except Exception as e: raise Exception(Warning: Exception during cleanup : %s % e) Error Message Warning: Exception during cleanup : type object 'TestDeleteAffinityGroups' has no attribute '_TestDeleteAffinityGroups__cleanup' begin captured logging test_09_delete_aff_grp_root_admin (integration.component.test_affinity_groups.TestDeleteAffinityGroups): CRITICAL: EXCEPTION: test_09_delete_aff_grp_root_admin: ['Traceback (most recent call last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n self.tearDown()\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\n self.teardownContext(ancestor)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\ntry_run(context, names)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n return func()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 599, in tearDownClass\nraise Exception(Warning: Exception during cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type object 'TestDeleteAffinityGroups' has no attribute '_TestDeleteAffinityGroups__cleanup'\n] - end captured logging - Stacktrace File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run self.tearDown() File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown self.teardownContext(ancestor) File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext try_run(context, names) File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run return func() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 599, in tearDownClass raise Exception(Warning: Exception during cleanup : %s % e) 'Warning: Exception during cleanup : type object \'TestDeleteAffinityGroups\' has no attribute \'_TestDeleteAffinityGroups__cleanup\'\n begin captured logging \ntest_09_delete_aff_grp_root_admin (integration.component.test_affinity_groups.TestDeleteAffinityGroups): CRITICAL: EXCEPTION: test_09_delete_aff_grp_root_admin: [\'Traceback (most recent call last):\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n self.tearDown()\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\\nself.teardownContext(ancestor)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\\ntry_run(context, names)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\\n return func()\\n\', \' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 599, in tearDownClass\\nraise Exception(Warning: Exception during cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type object \'TestDeleteAffinityGroups\' has no attribute \'_TestDeleteAffinityGroups__cleanup\'\\n]\n- end captured logging -' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6274) Scope issue attaching a disk to a VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Tutkowski updated CLOUDSTACK-6274: --- Fix Version/s: (was: 4.4.0) 4.5.0 Scope issue attaching a disk to a VM Key: CLOUDSTACK-6274 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6274 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: Ubuntu 12.04 Reporter: Mike Tutkowski Assignee: Mike Tutkowski Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7015) [Automation] type object 'TestDeleteAffinityGroups' has no attribute '_TestDeleteAffinityGroups__cleanup'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7015: - Description: == Bug in test script: == @classmethod def tearDownClass(cls): try: cls.api_client = super(TestDeleteAffinityGroups, cls).getClsTestClient().getApiClient() #Clean up, terminate the created templates cleanup_resources(cls.api_client, cls.__cleanup) BUG: It should be cls._cleanup except Exception as e: raise Exception(Warning: Exception during cleanup : %s % e) Error Message Warning: Exception during cleanup : type object 'TestDeleteAffinityGroups' has no attribute '_TestDeleteAffinityGroups__cleanup' begin captured logging test_09_delete_aff_grp_root_admin (integration.component.test_affinity_groups.TestDeleteAffinityGroups): CRITICAL: EXCEPTION: test_09_delete_aff_grp_root_admin: ['Traceback (most recent call last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n self.tearDown()\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\n self.teardownContext(ancestor)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\ntry_run(context, names)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n return func()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 599, in tearDownClass\nraise Exception(Warning: Exception during cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type object 'TestDeleteAffinityGroups' has no attribute '_TestDeleteAffinityGroups__cleanup'\n] - end captured logging - Stacktrace File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run self.tearDown() File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown self.teardownContext(ancestor) File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext try_run(context, names) File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run return func() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 599, in tearDownClass raise Exception(Warning: Exception during cleanup : %s % e) 'Warning: Exception during cleanup : type object \'TestDeleteAffinityGroups\' has no attribute \'_TestDeleteAffinityGroups__cleanup\'\n begin captured logging \ntest_09_delete_aff_grp_root_admin (integration.component.test_affinity_groups.TestDeleteAffinityGroups): CRITICAL: EXCEPTION: test_09_delete_aff_grp_root_admin: [\'Traceback (most recent call last):\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n self.tearDown()\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\\nself.teardownContext(ancestor)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\\ntry_run(context, names)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\\n return func()\\n\', \' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 599, in tearDownClass\\nraise Exception(Warning: Exception during cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type object \'TestDeleteAffinityGroups\' has no attribute \'_TestDeleteAffinityGroups__cleanup\'\\n]\n- end captured logging -' was: == Bug in test script: == @classmethod def tearDownClass(cls): try: cls.api_client = super(TestDeployVMAffinityGroups, cls).getClsTestClient().getApiClient() #Clean up, terminate the created templates cleanup_resources(cls.api_client, cls.__cleanup) BUG: It should be cls._cleanup except Exception as e: raise Exception(Warning: Exception during cleanup : %s % e) Error Message Warning: Exception during cleanup : type object 'TestDeleteAffinityGroups' has no attribute '_TestDeleteAffinityGroups__cleanup' begin captured logging test_09_delete_aff_grp_root_admin (integration.component.test_affinity_groups.TestDeleteAffinityGroups): CRITICAL: EXCEPTION: test_09_delete_aff_grp_root_admin: ['Traceback (most recent call last):\n', ' File
[jira] [Updated] (CLOUDSTACK-6815) CallContext contains incorrect UUID for Account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Tutkowski updated CLOUDSTACK-6815: --- Fix Version/s: (was: Future) 4.5.0 CallContext contains incorrect UUID for Account --- Key: CLOUDSTACK-6815 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6815 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: Ubuntu 12.04 Reporter: Mike Tutkowski Fix For: 4.5.0 Copy/paste of an e-mail I sent to CloudStack dev@: Hi, I noticed while executing the createStoragePool command that the following does not work entirely as expected: Account csAccount = CallContext.current().getCallingAccount(); The Account that is returned has the expected name and id, but its UUID is not correct. For example, I see the account name of admin and an id of 2 (in my case, both are correct); however, the UUID is different each time I run the createStoragePool command. I assume the UUID should be what's in the account table for the applicable row, right? Anyone have any thoughts on this? Thanks! -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7016) [Automation] type object 'TestDeployVMAffinityGroups' has no attribute '_TestDeployVMAffinityGroups__cleanup
Chandan Purushothama created CLOUDSTACK-7016: Summary: [Automation] type object 'TestDeployVMAffinityGroups' has no attribute '_TestDeployVMAffinityGroups__cleanup Key: CLOUDSTACK-7016 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7016 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.4.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.4.0 == Bug in test script: == @classmethod def tearDownClass(cls): try: cls.api_client = super(TestDeployVMAffinityGroups, cls).getClsTestClient().getApiClient() #Clean up, terminate the created templates cleanup_resources(cls.api_client, cls.__cleanup) BUG: It should be cls._cleanup except Exception as e: raise Exception(Warning: Exception during cleanup : %s % e) = Error Message: = Warning: Exception during cleanup : type object 'TestDeployVMAffinityGroups' has no attribute '_TestDeployVMAffinityGroups__cleanup' begin captured logging test_10_deploy_vm_by_aff_grp_name_and_id (integration.component.test_affinity_groups.TestDeployVMAffinityGroups): CRITICAL: EXCEPTION: test_10_deploy_vm_by_aff_grp_name_and_id: ['Traceback (most recent call last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n self.tearDown()\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\n self.teardownContext(ancestor)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\ntry_run(context, names)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n return func()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 1154, in tearDownClass\nraise Exception(Warning: Exception during cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type object 'TestDeployVMAffinityGroups' has no attribute '_TestDeployVMAffinityGroups__cleanup'\n] - end captured logging - Stacktrace File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run self.tearDown() File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown self.teardownContext(ancestor) File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext try_run(context, names) File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run return func() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 1154, in tearDownClass raise Exception(Warning: Exception during cleanup : %s % e) 'Warning: Exception during cleanup : type object \'TestDeployVMAffinityGroups\' has no attribute \'_TestDeployVMAffinityGroups__cleanup\'\n begin captured logging \ntest_10_deploy_vm_by_aff_grp_name_and_id (integration.component.test_affinity_groups.TestDeployVMAffinityGroups): CRITICAL: EXCEPTION: test_10_deploy_vm_by_aff_grp_name_and_id: [\'Traceback (most recent call last):\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n self.tearDown()\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\\nself.teardownContext(ancestor)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\\ntry_run(context, names)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\\n return func()\\n\', \' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 1154, in tearDownClass\\nraise Exception(Warning: Exception during cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type object \'TestDeployVMAffinityGroups\' has no attribute \'_TestDeployVMAffinityGroups__cleanup\'\\n]\n- end captured logging -' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7017) Ordering of templates/offerings changes per add instance modal
Ian Duffy created CLOUDSTACK-7017: - Summary: Ordering of templates/offerings changes per add instance modal Key: CLOUDSTACK-7017 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7017 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API, UI Affects Versions: 4.5.0 Reporter: Ian Duffy (Not sure if this is UI related or due to the responses it gets from the API marking as both for now) When opening the add instance modal the ordering of the service offerings, templates and disk offerings is always different. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4364) Restore VM - needs to log usage event for volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048196#comment-14048196 ] ASF subversion and git services commented on CLOUDSTACK-4364: - Commit 1e7835488222471a565174ee1fdf8bb985fc9024 in cloudstack's branch refs/heads/4.4-forward from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1e78354 ] CLOUDSTACK-4364: Restore VM - log a usage event for newly created volume Restore VM - needs to log usage event for volume Key: CLOUDSTACK-4364 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4364 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: Nitin Mehta Assignee: Nitin Mehta Fix For: 4.4.0 Restore VM - needs to log usage event for volume so that any customer can charge for the newly creat4ed volume -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4364) Restore VM - needs to log usage event for volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048201#comment-14048201 ] ASF subversion and git services commented on CLOUDSTACK-4364: - Commit 0c9c5a71b4bcddf89381d6d3f66c5b83905c94d9 in cloudstack's branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0c9c5a7 ] CLOUDSTACK-4364: Restore VM - log a usage event for newly created volume Restore VM - needs to log usage event for volume Key: CLOUDSTACK-4364 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4364 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: Nitin Mehta Assignee: Nitin Mehta Fix For: 4.4.0 Restore VM - needs to log usage event for volume so that any customer can charge for the newly creat4ed volume -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-4364) Restore VM - needs to log usage event for volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-4364: Fix Version/s: (was: 4.4.0) 4.5.0 Restore VM - needs to log usage event for volume Key: CLOUDSTACK-4364 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4364 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: Nitin Mehta Assignee: Nitin Mehta Fix For: 4.5.0 Restore VM - needs to log usage event for volume so that any customer can charge for the newly creat4ed volume -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7018) Restore VM - missing destroyed usage event and decrementing resource count for volume
Nitin Mehta created CLOUDSTACK-7018: --- Summary: Restore VM - missing destroyed usage event and decrementing resource count for volume Key: CLOUDSTACK-7018 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7018 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Nitin Mehta Priority: Critical Restore VM - missing destroyed usage event and decrementing resource count for volume -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4364) Restore VM - needs to log usage event for volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048210#comment-14048210 ] Nitin Mehta commented on CLOUDSTACK-4364: - Filed CLOUDSTACK-7018 which I uncovered while fixing this bug. Restore VM - needs to log usage event for volume Key: CLOUDSTACK-4364 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4364 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: Nitin Mehta Assignee: Nitin Mehta Fix For: 4.5.0 Restore VM - needs to log usage event for volume so that any customer can charge for the newly creat4ed volume -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7019) [Automation] type object 'TestListAffinityGroups' has no attribute '_TestListAffinityGroups__cleanup
Chandan Purushothama created CLOUDSTACK-7019: Summary: [Automation] type object 'TestListAffinityGroups' has no attribute '_TestListAffinityGroups__cleanup Key: CLOUDSTACK-7019 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7019 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.4.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.4.0 == Bug in test script: == @classmethod def tearDownClass(cls): try: cls.api_client = super(TestListAffinityGroups, cls).getClsTestClient().getApiClient() #Clean up, terminate the created templates cleanup_resources(cls.api_client, cls.__cleanup) BUG: It should be cls._cleanup except Exception as e: raise Exception(Warning: Exception during cleanup : %s % e) Error Message Warning: Exception during cleanup : type object 'TestListAffinityGroups' has no attribute '_TestListAffinityGroups__cleanup' begin captured logging test_07_list_all_vms_in_aff_grp (integration.component.test_affinity_groups.TestListAffinityGroups): CRITICAL: EXCEPTION: test_07_list_all_vms_in_aff_grp: ['Traceback (most recent call last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\nself.tearDown()\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\n self.teardownContext(ancestor)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\ntry_run(context, names)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n return func()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 351, in tearDownClass\nraise Exception(Warning: Exception during cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type object 'TestListAffinityGroups' has no attribute '_TestListAffinityGroups__cleanup'\n] - end captured logging - Stacktrace File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run self.tearDown() File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown self.teardownContext(ancestor) File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext try_run(context, names) File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run return func() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 351, in tearDownClass raise Exception(Warning: Exception during cleanup : %s % e) 'Warning: Exception during cleanup : type object \'TestListAffinityGroups\' has no attribute \'_TestListAffinityGroups__cleanup\'\n begin captured logging \ntest_07_list_all_vms_in_aff_grp (integration.component.test_affinity_groups.TestListAffinityGroups): CRITICAL: EXCEPTION: test_07_list_all_vms_in_aff_grp: [\'Traceback (most recent call last):\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\nself.tearDown()\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\\nself.teardownContext(ancestor)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\\ntry_run(context, names)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\\n return func()\\n\', \' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 351, in tearDownClass\\nraise Exception(Warning: Exception during cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type object \'TestListAffinityGroups\' has no attribute \'_TestListAffinityGroups__cleanup\'\\n]\n- end captured logging -' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7020) [Automation] Exception: Warning: Exception during cleanup : type object 'TestTemplateUsage' has no attribute '_cleanup'
Chandan Purushothama created CLOUDSTACK-7020: Summary: [Automation] Exception: Warning: Exception during cleanup : type object 'TestTemplateUsage' has no attribute '_cleanup' Key: CLOUDSTACK-7020 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7020 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.4.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.4.0 === Bug in Script: === class TestTemplateUsage(cloudstackTestCase): @classmethod def setUpClass(cls): cls.testClient = super(TestTemplateUsage, cls).getClsTestClient() cls.api_client = cls.testClient.getApiClient() cls.services = Services().services # Get Zone, Domain and templates cls.domain = get_domain(cls.api_client) cls.zone = get_zone(cls.api_client, cls.testClient.getZoneForTests()) cls.services['mode'] = cls.zone.networktype cls.services[server][zoneid] = cls.zone.id template = get_template( cls.api_client, cls.zone.id, cls.services[ostype] ) cls.services[server][zoneid] = cls.zone.id try: cls.account = Account.create( cls.api_client, cls.services[account], domainid=cls.domain.id ) cls._cleanup.append(cls.account) --- BUG: _cleanup variable should be initialized to empty list. cls.services[account] = cls.account.name cls.service_offering = ServiceOffering.create( cls.api_client, cls.services[service_offering] ) cls._cleanup.append(cls.service_offering) #create virtual machine == Error Information: == test_01_snapshot_usage (integration.component.test_usage.TestSnapshotUsage): CRITICAL: EXCEPTION: test_01_snapshot_usage: ['Traceback (most recent call last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in run\nself.setUp()\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in setUp\n self.setupContext(ancestor)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in setupContext\ntry_run(context, names)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n return func()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py, line 702, in setUpClass\ncls.tearDownClass()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py, line 712, in tearDownClass\nraise Exception(Warning: Exception during cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type object 'TestTemplateUsage' has no attribute '_cleanup'\n] - end captured logging - Stacktrace File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in run self.setUp() File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in setUp self.setupContext(ancestor) File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in setupContext try_run(context, names) File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run return func() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py, line 702, in setUpClass cls.tearDownClass() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py, line 712, in tearDownClass raise Exception(Warning: Exception during cleanup : %s % e) 'Warning: Exception during cleanup : type object \'TestTemplateUsage\' has no attribute \'_cleanup\'\n -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7021) [Automation] type object 'TestUpdateVMAffinityGroups' has no attribute '_TestUpdateVMAffinityGroups__cleanup
Chandan Purushothama created CLOUDSTACK-7021: Summary: [Automation] type object 'TestUpdateVMAffinityGroups' has no attribute '_TestUpdateVMAffinityGroups__cleanup Key: CLOUDSTACK-7021 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7021 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.4.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.4.0 === Bug in Script: === @classmethod def tearDownClass(cls): try: cls.api_client = super(TestUpdateVMAffinityGroups, cls).getClsTestClient().getApiClient() #Clean up, terminate the created templates cleanup_resources(cls.api_client, cls.__cleanup) --- BUG: It should be cls._cleanup except Exception as e: raise Exception(Warning: Exception during cleanup : %s % e) = Error Message: = Warning: Exception during cleanup : type object 'TestUpdateVMAffinityGroups' has no attribute '_TestUpdateVMAffinityGroups__cleanup' begin captured logging test_05_update_aff_grp_on_running_vm (integration.component.test_affinity_groups.TestUpdateVMAffinityGroups): CRITICAL: EXCEPTION: test_05_update_aff_grp_on_running_vm: ['Traceback (most recent call last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n self.tearDown()\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\n self.teardownContext(ancestor)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\ntry_run(context, names)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n return func()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 870, in tearDownClass\nraise Exception(Warning: Exception during cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type object 'TestUpdateVMAffinityGroups' has no attribute '_TestUpdateVMAffinityGroups__cleanup'\n] - end captured logging - Stacktrace File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run self.tearDown() File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown self.teardownContext(ancestor) File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext try_run(context, names) File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run return func() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 870, in tearDownClass raise Exception(Warning: Exception during cleanup : %s % e) 'Warning: Exception during cleanup : type object \'TestUpdateVMAffinityGroups\' has no attribute \'_TestUpdateVMAffinityGroups__cleanup\'\n begin captured logging \ntest_05_update_aff_grp_on_running_vm (integration.component.test_affinity_groups.TestUpdateVMAffinityGroups): CRITICAL: EXCEPTION: test_05_update_aff_grp_on_running_vm: [\'Traceback (most recent call last):\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n self.tearDown()\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\\nself.teardownContext(ancestor)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\\ntry_run(context, names)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\\n return func()\\n\', \' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 870, in tearDownClass\\nraise Exception(Warning: Exception during cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type object \'TestUpdateVMAffinityGroups\' has no attribute \'_TestUpdateVMAffinityGroups__cleanup\'\\n]\n- end captured logging -' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7022) [Automation] AttributeError: type object 'TestVpnUsage' has no attribute 'sevice_offering'
Chandan Purushothama created CLOUDSTACK-7022:
Summary: [Automation] AttributeError: type object 'TestVpnUsage'
has no attribute 'sevice_offering'
Key: CLOUDSTACK-7022
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7022
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Automation, Test
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Priority: Critical
Fix For: 4.4.0
===
Bug in Script:
===
cls.service_offering = ServiceOffering.create(
cls.api_client,
cls.services[service_offering]
)
cls._cleanup.append(cls.sevice_offering) --- BUG: Typo in the
service_offering variable name
cls.virtual_machine = VirtualMachine.create(
cls.api_client,
cls.services[server],
templateid=template.id,
accountid=cls.account.name,
domainid=cls.account.domainid,
serviceofferingid=cls.service_offering.id
)
cls.public_ip = PublicIPAddress.create(
cls.api_client,
accountid=cls.virtual_machine.account,
zoneid=cls.virtual_machine.zoneid,
domainid=cls.virtual_machine.domainid,
services=cls.services[server]
)
return
=
Exception:
=
test_01_volume_usage (integration.component.test_usage.TestVolumeUsage):
CRITICAL: EXCEPTION: test_01_volume_usage: ['Traceback (most recent call
last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line
208, in run\nself.setUp()\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in setUp\n
self.setupContext(ancestor)\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in
setupContext\ntry_run(context, names)\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n
return func()\n', ' File
/home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py,
line 1482, in setUpClass\ncls._cleanup.append(cls.sevice_offering)\n',
AttributeError: type object 'TestVpnUsage' has no attribute
'sevice_offering'\n]
- end captured logging -
Stacktrace
File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in run
self.setUp()
File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in
setUp
self.setupContext(ancestor)
File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in
setupContext
try_run(context, names)
File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in
try_run
return func()
File
/home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py,
line 1482, in setUpClass
cls._cleanup.append(cls.sevice_offering)
'type object \'TestVpnUsage\' has no attribute
\'sevice_offering\'\n begin captured logging
\ntest_01_volume_usage
(integration.component.test_usage.TestVolumeUsage): DEBUG: Payload:
{\'signature\': \'aZ6mt3aURCG51ejqTw7v2/RuQFQ=\', \'apiKey\':
u\'Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Q\',
\'command\': \'deleteServiceOffering\', \'id\':
u\'3a72e88f-7886-42d3-be1a-99fd15908112\', \'response\':
\'json\'}\ntest_01_volume_usage
(integration.component.test_usage.TestVolumeUsage): DEBUG: Sending GET
Cmd :
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7015) [Automation] type object 'TestDeleteAffinityGroups' has no attribute '_TestDeleteAffinityGroups__cleanup'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7015: - Issue Type: Test (was: Bug) [Automation] type object 'TestDeleteAffinityGroups' has no attribute '_TestDeleteAffinityGroups__cleanup' - Key: CLOUDSTACK-7015 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7015 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.4.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.4.0 == Bug in test script: == @classmethod def tearDownClass(cls): try: cls.api_client = super(TestDeleteAffinityGroups, cls).getClsTestClient().getApiClient() #Clean up, terminate the created templates cleanup_resources(cls.api_client, cls.__cleanup) BUG: It should be cls._cleanup except Exception as e: raise Exception(Warning: Exception during cleanup : %s % e) Error Message Warning: Exception during cleanup : type object 'TestDeleteAffinityGroups' has no attribute '_TestDeleteAffinityGroups__cleanup' begin captured logging test_09_delete_aff_grp_root_admin (integration.component.test_affinity_groups.TestDeleteAffinityGroups): CRITICAL: EXCEPTION: test_09_delete_aff_grp_root_admin: ['Traceback (most recent call last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n self.tearDown()\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\nself.teardownContext(ancestor)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\ntry_run(context, names)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n return func()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 599, in tearDownClass\nraise Exception(Warning: Exception during cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type object 'TestDeleteAffinityGroups' has no attribute '_TestDeleteAffinityGroups__cleanup'\n] - end captured logging - Stacktrace File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run self.tearDown() File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown self.teardownContext(ancestor) File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext try_run(context, names) File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run return func() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 599, in tearDownClass raise Exception(Warning: Exception during cleanup : %s % e) 'Warning: Exception during cleanup : type object \'TestDeleteAffinityGroups\' has no attribute \'_TestDeleteAffinityGroups__cleanup\'\n begin captured logging \ntest_09_delete_aff_grp_root_admin (integration.component.test_affinity_groups.TestDeleteAffinityGroups): CRITICAL: EXCEPTION: test_09_delete_aff_grp_root_admin: [\'Traceback (most recent call last):\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n self.tearDown()\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\\nself.teardownContext(ancestor)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\\ntry_run(context, names)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\\nreturn func()\\n\', \' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 599, in tearDownClass\\nraise Exception(Warning: Exception during cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type object \'TestDeleteAffinityGroups\' has no attribute \'_TestDeleteAffinityGroups__cleanup\'\\n]\n- end captured logging -' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7019) [Automation] type object 'TestListAffinityGroups' has no attribute '_TestListAffinityGroups__cleanup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7019: - Issue Type: Test (was: Bug) [Automation] type object 'TestListAffinityGroups' has no attribute '_TestListAffinityGroups__cleanup Key: CLOUDSTACK-7019 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7019 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.4.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.4.0 == Bug in test script: == @classmethod def tearDownClass(cls): try: cls.api_client = super(TestListAffinityGroups, cls).getClsTestClient().getApiClient() #Clean up, terminate the created templates cleanup_resources(cls.api_client, cls.__cleanup) BUG: It should be cls._cleanup except Exception as e: raise Exception(Warning: Exception during cleanup : %s % e) Error Message Warning: Exception during cleanup : type object 'TestListAffinityGroups' has no attribute '_TestListAffinityGroups__cleanup' begin captured logging test_07_list_all_vms_in_aff_grp (integration.component.test_affinity_groups.TestListAffinityGroups): CRITICAL: EXCEPTION: test_07_list_all_vms_in_aff_grp: ['Traceback (most recent call last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n self.tearDown()\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\nself.teardownContext(ancestor)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\ntry_run(context, names)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n return func()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 351, in tearDownClass\nraise Exception(Warning: Exception during cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type object 'TestListAffinityGroups' has no attribute '_TestListAffinityGroups__cleanup'\n] - end captured logging - Stacktrace File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run self.tearDown() File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown self.teardownContext(ancestor) File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext try_run(context, names) File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run return func() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 351, in tearDownClass raise Exception(Warning: Exception during cleanup : %s % e) 'Warning: Exception during cleanup : type object \'TestListAffinityGroups\' has no attribute \'_TestListAffinityGroups__cleanup\'\n begin captured logging \ntest_07_list_all_vms_in_aff_grp (integration.component.test_affinity_groups.TestListAffinityGroups): CRITICAL: EXCEPTION: test_07_list_all_vms_in_aff_grp: [\'Traceback (most recent call last):\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n self.tearDown()\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\\nself.teardownContext(ancestor)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\\ntry_run(context, names)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\\nreturn func()\\n\', \' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 351, in tearDownClass\\nraise Exception(Warning: Exception during cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type object \'TestListAffinityGroups\' has no attribute \'_TestListAffinityGroups__cleanup\'\\n]\n- end captured logging -' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7016) [Automation] type object 'TestDeployVMAffinityGroups' has no attribute '_TestDeployVMAffinityGroups__cleanup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7016: - Issue Type: Test (was: Bug) [Automation] type object 'TestDeployVMAffinityGroups' has no attribute '_TestDeployVMAffinityGroups__cleanup Key: CLOUDSTACK-7016 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7016 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.4.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.4.0 == Bug in test script: == @classmethod def tearDownClass(cls): try: cls.api_client = super(TestDeployVMAffinityGroups, cls).getClsTestClient().getApiClient() #Clean up, terminate the created templates cleanup_resources(cls.api_client, cls.__cleanup) BUG: It should be cls._cleanup except Exception as e: raise Exception(Warning: Exception during cleanup : %s % e) = Error Message: = Warning: Exception during cleanup : type object 'TestDeployVMAffinityGroups' has no attribute '_TestDeployVMAffinityGroups__cleanup' begin captured logging test_10_deploy_vm_by_aff_grp_name_and_id (integration.component.test_affinity_groups.TestDeployVMAffinityGroups): CRITICAL: EXCEPTION: test_10_deploy_vm_by_aff_grp_name_and_id: ['Traceback (most recent call last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n self.tearDown()\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\nself.teardownContext(ancestor)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\ntry_run(context, names)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n return func()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 1154, in tearDownClass\nraise Exception(Warning: Exception during cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type object 'TestDeployVMAffinityGroups' has no attribute '_TestDeployVMAffinityGroups__cleanup'\n] - end captured logging - Stacktrace File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run self.tearDown() File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown self.teardownContext(ancestor) File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext try_run(context, names) File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run return func() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 1154, in tearDownClass raise Exception(Warning: Exception during cleanup : %s % e) 'Warning: Exception during cleanup : type object \'TestDeployVMAffinityGroups\' has no attribute \'_TestDeployVMAffinityGroups__cleanup\'\n begin captured logging \ntest_10_deploy_vm_by_aff_grp_name_and_id (integration.component.test_affinity_groups.TestDeployVMAffinityGroups): CRITICAL: EXCEPTION: test_10_deploy_vm_by_aff_grp_name_and_id: [\'Traceback (most recent call last):\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n self.tearDown()\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\\nself.teardownContext(ancestor)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\\ntry_run(context, names)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\\nreturn func()\\n\', \' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 1154, in tearDownClass\\nraise Exception(Warning: Exception during cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type object \'TestDeployVMAffinityGroups\' has no attribute \'_TestDeployVMAffinityGroups__cleanup\'\\n]\n- end captured logging -' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7020) [Automation] Exception: Warning: Exception during cleanup : type object 'TestTemplateUsage' has no attribute '_cleanup'
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7020: - Issue Type: Test (was: Bug) [Automation] Exception: Warning: Exception during cleanup : type object 'TestTemplateUsage' has no attribute '_cleanup' --- Key: CLOUDSTACK-7020 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7020 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.4.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.4.0 === Bug in Script: === class TestTemplateUsage(cloudstackTestCase): @classmethod def setUpClass(cls): cls.testClient = super(TestTemplateUsage, cls).getClsTestClient() cls.api_client = cls.testClient.getApiClient() cls.services = Services().services # Get Zone, Domain and templates cls.domain = get_domain(cls.api_client) cls.zone = get_zone(cls.api_client, cls.testClient.getZoneForTests()) cls.services['mode'] = cls.zone.networktype cls.services[server][zoneid] = cls.zone.id template = get_template( cls.api_client, cls.zone.id, cls.services[ostype] ) cls.services[server][zoneid] = cls.zone.id try: cls.account = Account.create( cls.api_client, cls.services[account], domainid=cls.domain.id ) cls._cleanup.append(cls.account) --- BUG: _cleanup variable should be initialized to empty list. cls.services[account] = cls.account.name cls.service_offering = ServiceOffering.create( cls.api_client, cls.services[service_offering] ) cls._cleanup.append(cls.service_offering) #create virtual machine == Error Information: == test_01_snapshot_usage (integration.component.test_usage.TestSnapshotUsage): CRITICAL: EXCEPTION: test_01_snapshot_usage: ['Traceback (most recent call last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in run\nself.setUp()\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in setUp\n self.setupContext(ancestor)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in setupContext\ntry_run(context, names)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n return func()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py, line 702, in setUpClass\ncls.tearDownClass()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py, line 712, in tearDownClass\nraise Exception(Warning: Exception during cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type object 'TestTemplateUsage' has no attribute '_cleanup'\n] - end captured logging - Stacktrace File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in run self.setUp() File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in setUp self.setupContext(ancestor) File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in setupContext try_run(context, names) File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run return func() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py, line 702, in setUpClass cls.tearDownClass() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py, line 712, in tearDownClass raise Exception(Warning: Exception during cleanup : %s % e) 'Warning: Exception during cleanup : type object \'TestTemplateUsage\' has no attribute \'_cleanup\'\n -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7022) [Automation] AttributeError: type object 'TestVpnUsage' has no attribute 'sevice_offering'
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Purushothama updated CLOUDSTACK-7022:
-
Issue Type: Test (was: Bug)
[Automation] AttributeError: type object 'TestVpnUsage' has no attribute
'sevice_offering'
--
Key: CLOUDSTACK-7022
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7022
Project: CloudStack
Issue Type: Test
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Automation, Test
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Priority: Critical
Fix For: 4.4.0
===
Bug in Script:
===
cls.service_offering = ServiceOffering.create(
cls.api_client,
cls.services[service_offering]
)
cls._cleanup.append(cls.sevice_offering) --- BUG: Typo in the
service_offering variable name
cls.virtual_machine = VirtualMachine.create(
cls.api_client,
cls.services[server],
templateid=template.id,
accountid=cls.account.name,
domainid=cls.account.domainid,
serviceofferingid=cls.service_offering.id
)
cls.public_ip = PublicIPAddress.create(
cls.api_client,
accountid=cls.virtual_machine.account,
zoneid=cls.virtual_machine.zoneid,
domainid=cls.virtual_machine.domainid,
services=cls.services[server]
)
return
=
Exception:
=
test_01_volume_usage (integration.component.test_usage.TestVolumeUsage):
CRITICAL: EXCEPTION: test_01_volume_usage: ['Traceback (most recent call
last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py,
line 208, in run\nself.setUp()\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in setUp\n
self.setupContext(ancestor)\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in
setupContext\ntry_run(context, names)\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n
return func()\n', ' File
/home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py,
line 1482, in setUpClass\ncls._cleanup.append(cls.sevice_offering)\n',
AttributeError: type object 'TestVpnUsage' has no attribute
'sevice_offering'\n]
- end captured logging -
Stacktrace
File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in
run
self.setUp()
File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in
setUp
self.setupContext(ancestor)
File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in
setupContext
try_run(context, names)
File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in
try_run
return func()
File
/home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_usage.py,
line 1482, in setUpClass
cls._cleanup.append(cls.sevice_offering)
'type object \'TestVpnUsage\' has no attribute
\'sevice_offering\'\n begin captured logging
\ntest_01_volume_usage
(integration.component.test_usage.TestVolumeUsage): DEBUG: Payload:
{\'signature\': \'aZ6mt3aURCG51ejqTw7v2/RuQFQ=\', \'apiKey\':
u\'Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Q\',
\'command\': \'deleteServiceOffering\', \'id\':
u\'3a72e88f-7886-42d3-be1a-99fd15908112\', \'response\':
\'json\'}\ntest_01_volume_usage
(integration.component.test_usage.TestVolumeUsage): DEBUG: Sending
GET Cmd :
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7014) [Automation] type object 'TestAffinityGroupsAdminUser' has no attribute '_TestAffinityGroupsAdminUser__cleanup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7014: - Issue Type: Test (was: Bug) [Automation] type object 'TestAffinityGroupsAdminUser' has no attribute '_TestAffinityGroupsAdminUser__cleanup --- Key: CLOUDSTACK-7014 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7014 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.4.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.4.0 == Bug in test script: == @classmethod def tearDownClass(cls): try: cls.api_client = super(TestAffinityGroupsAdminUser, cls).getClsTestClient().getApiClient() #Clean up, terminate the created templates cleanup_resources(cls.api_client, cls.__cleanup) BUG: It should be cls._cleanup except Exception as e: raise Exception(Warning: Exception during cleanup : %s % e) Test Script Failure: Warning: Exception during cleanup : type object 'TestAffinityGroupsAdminUser' has no attribute '_TestAffinityGroupsAdminUser__cleanup' begin captured logging test_07_delete_aff_grp_of_other_user (integration.component.test_affinity_groups.TestAffinityGroupsAdminUser): CRITICAL: EXCEPTION: test_07_delete_aff_grp_of_other_user: ['Traceback (most recent call last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n self.tearDown()\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\nself.teardownContext(ancestor)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\ntry_run(context, names)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n return func()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 1501, in tearDownClass\nraise Exception(Warning: Exception during cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type object 'TestAffinityGroupsAdminUser' has no attribute '_TestAffinityGroupsAdminUser__cleanup'\n] - end captured logging - Stacktrace File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run self.tearDown() File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown self.teardownContext(ancestor) File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext try_run(context, names) File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run return func() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 1501, in tearDownClass raise Exception(Warning: Exception during cleanup : %s % e) 'Warning: Exception during cleanup : type object \'TestAffinityGroupsAdminUser\' has no attribute \'_TestAffinityGroupsAdminUser__cleanup\'\n begin captured logging \ntest_07_delete_aff_grp_of_other_user (integration.component.test_affinity_groups.TestAffinityGroupsAdminUser): CRITICAL: EXCEPTION: test_07_delete_aff_grp_of_other_user: [\'Traceback (most recent call last):\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n self.tearDown()\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\\nself.teardownContext(ancestor)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\\ntry_run(context, names)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\\nreturn func()\\n\', \' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 1501, in tearDownClass\\nraise Exception(Warning: Exception during cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type object \'TestAffinityGroupsAdminUser\' has no attribute \'_TestAffinityGroupsAdminUser__cleanup\'\\n]\n- end captured logging -' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7021) [Automation] type object 'TestUpdateVMAffinityGroups' has no attribute '_TestUpdateVMAffinityGroups__cleanup
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7021: - Issue Type: Test (was: Bug) [Automation] type object 'TestUpdateVMAffinityGroups' has no attribute '_TestUpdateVMAffinityGroups__cleanup Key: CLOUDSTACK-7021 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7021 Project: CloudStack Issue Type: Test Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.4.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.4.0 === Bug in Script: === @classmethod def tearDownClass(cls): try: cls.api_client = super(TestUpdateVMAffinityGroups, cls).getClsTestClient().getApiClient() #Clean up, terminate the created templates cleanup_resources(cls.api_client, cls.__cleanup) --- BUG: It should be cls._cleanup except Exception as e: raise Exception(Warning: Exception during cleanup : %s % e) = Error Message: = Warning: Exception during cleanup : type object 'TestUpdateVMAffinityGroups' has no attribute '_TestUpdateVMAffinityGroups__cleanup' begin captured logging test_05_update_aff_grp_on_running_vm (integration.component.test_affinity_groups.TestUpdateVMAffinityGroups): CRITICAL: EXCEPTION: test_05_update_aff_grp_on_running_vm: ['Traceback (most recent call last):\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\n self.tearDown()\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\nself.teardownContext(ancestor)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\ntry_run(context, names)\n', ' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n return func()\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 870, in tearDownClass\nraise Exception(Warning: Exception during cleanup : %s % e)\n', Exception: Warning: Exception during cleanup : type object 'TestUpdateVMAffinityGroups' has no attribute '_TestUpdateVMAffinityGroups__cleanup'\n] - end captured logging - Stacktrace File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run self.tearDown() File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown self.teardownContext(ancestor) File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext try_run(context, names) File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run return func() File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 870, in tearDownClass raise Exception(Warning: Exception during cleanup : %s % e) 'Warning: Exception during cleanup : type object \'TestUpdateVMAffinityGroups\' has no attribute \'_TestUpdateVMAffinityGroups__cleanup\'\n begin captured logging \ntest_05_update_aff_grp_on_running_vm (integration.component.test_affinity_groups.TestUpdateVMAffinityGroups): CRITICAL: EXCEPTION: test_05_update_aff_grp_on_running_vm: [\'Traceback (most recent call last):\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 227, in run\\n self.tearDown()\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 350, in tearDown\\nself.teardownContext(ancestor)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 366, in teardownContext\\ntry_run(context, names)\\n\', \' File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\\nreturn func()\\n\', \' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_affinity_groups.py, line 870, in tearDownClass\\nraise Exception(Warning: Exception during cleanup : %s % e)\\n\', Exception: Warning: Exception during cleanup : type object \'TestUpdateVMAffinityGroups\' has no attribute \'_TestUpdateVMAffinityGroups__cleanup\'\\n]\n- end captured logging -' -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7013) [Automation] AttributeError: type object 'TestFailureScenariosRemoveNicFromVM' has no attribute 'append'
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Purushothama updated CLOUDSTACK-7013:
-
Issue Type: Test (was: Bug)
[Automation] AttributeError: type object
'TestFailureScenariosRemoveNicFromVM' has no attribute 'append'
-
Key: CLOUDSTACK-7013
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7013
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: Chandan Purushothama
Priority: Critical
Fix For: 4.4.0
==
Bug in test script:
==
cls.account =
Account.create(cls.api_client,cls.services[account],domainid =
cls.domain.id)
cls.append(cls.account) BUG: should be cls.__cleanup.append
cls.service_offering =
ServiceOffering.create(cls.api_client,cls.services[service_offering])
cls._cleanup.append(cls.service_offering)
Test Script Failure:
test_26_add_nic_insufficient_permission
(integration.component.test_add_remove_network.TestFailureScenariosAddNetworkToVM):
CRITICAL: EXCEPTION: test_26_add_nic_insufficient_permission: ['Traceback
(most recent call last):\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in run\n
self.setUp()\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in setUp\n
self.setupContext(ancestor)\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in
setupContext\ntry_run(context, names)\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n
return func()\n', ' File
/home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_add_remove_network.py,
line 1392, in setUpClass\ncls.append(cls.account)\n', AttributeError:
type object 'TestFailureScenariosRemoveNicFromVM' has no attribute
'append'\n]
- end captured logging -
Stacktrace
File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in
run
self.setUp()
File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in
setUp
self.setupContext(ancestor)
File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in
setupContext
try_run(context, names)
File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in
try_run
return func()
File
/home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_add_remove_network.py,
line 1392, in setUpClass
cls.append(cls.account)
'type object \'TestFailureScenariosRemoveNicFromVM\' has no attribute
\'append\'\n begin captured logging
\ntest_26_add_nic_insufficient_permission
(integration.component.test_add_remove_network.TestFailureScenariosAddNetworkToVM):
DEBUG: Payload: {\'apiKey\':
u\'Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Q\',
\'id\': u\'853b13be-4f75-4ca9-9f7c-3cf303d3cc2d\', \'state\': \'Disabled\',
\'command\': \'updateNetworkOffering\', \'signature\':
\'pP6GEHIbIDVHMxeYxAyQahpCxbI=\', \'response\':
\'json\'}\ntest_26_add_nic_insufficient_permission
(integration.component.test_add_remove_network.TestFailureScenariosAddNetworkToVM):
DEBUG: Sending GET Cmd :
updateNetworkOffering===\nrequests.packages.urllib3.connectionpool: INFO:
Starting new HTTP connection (1):
10.220.153.217\nrequests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Qid=853b13be-4f75-4ca9-9f7c-3cf303d3cc2dstate=Disabledcommand=updateNetworkOfferingsignature=pP6GEHIbIDVHMxeYxAyQahpCxbI%3Dresponse=json
HTTP/1.1 200
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CLOUDSTACK-7023) [Automation] DeleteTagsCmd failed due to Unable to find tags by parameters specified
Chandan Purushothama created CLOUDSTACK-7023:
Summary: [Automation] DeleteTagsCmd failed due to Unable to find
tags by parameters specified
Key: CLOUDSTACK-7023
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7023
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Automation, Test
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Fix For: 4.4.0
==
Test Script Code:
==
def test_07_iso_tag(self):
Test creation, listing and deletion tags on ISO
# Validate the following
# 1. Create a tag on ISO using createTags API
# 2. Delete above created tag using deleteTags API
iso = Iso.create(
self.apiclient,
self.services[iso],
account=self.account.name,
domainid=self.account.domainid
)
self.debug(ISO created with ID: %s % iso.id)
list_iso_response = Iso.list(self.apiclient,
id=iso.id)
self.assertEqual(
isinstance(list_iso_response, list),
True,
Check list response returns a valid list
)
self.debug(Creating a tag for the ISO)
tag = Tag.create(
self.apiclient,
resourceIds=iso.id,
resourceType='ISO',
tags={'OS': 'CentOS'}
)
self.debug(Tag created: %s % tag.__dict__)
tags = Tag.list(
self.apiclient,
listall=True,
resourceType='ISO',
account=self.account.name,
domainid=self.account.domainid,
key='OS',
value='CentOS'
)
self.assertEqual(
isinstance(tags, list),
True,
List tags should not return empty response
)
self.assertEqual(
tags[0].value,
'CentOS',
'The tag should have original value'
)
isos = Iso.list(
self.apiclient,
key='OS',
value='CentOS',
account=self.account.name,
domainid=self.account.domainid,
isofilter='all'
)
self.assertEqual(
isinstance(isos, list),
True,
List isos should not return an empty response
)
self.debug(Deleting the created tag..)
try:
tag.delete(
self.apiclient,
resourceIds=iso.id,
resourceType='ISO',
tags={'OS': 'CentOS'}
)
except Exception as e:
self.fail(Failed to delete the tag - %s % e)
self.debug(Verifying if tag is actually deleted!)
tags = Tag.list(
self.apiclient,
listall=True,
resourceType='ISO',
account=self.account.name,
domainid=self.account.domainid,
key='OS',
value='CentOS'
)
self.assertEqual(
tags,
None,
List tags should return empty response
)
return
===
Unable to find tags by parameters specified:
===
test_07_iso_tag (integration.component.test_tags.TestResourceTags): DEBUG:
Payload: {'account': u'test-TestResourceTags-BQG75M', 'domainid':
u'36c9d3ba-fc58-11e3-919f-4eba41a459a4', 'name': 'Dummy ISO', 'ispublic':
False, 'isextractable': True, 'zoneid':
u'89d23f5c-c768-4fb0-80aa-f970a6f2d70b', 'isfeatured': True, 'apiKey':
u'Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Q',
'displaytext': 'Dummy ISO', 'ostypeid':
u'36d0cf58-fc58-11e3-919f-4eba41a459a4', 'signature':
'X08iXXgAavZWTcv2LW4HEK+piz8=', 'url':
'http://people.apache.org/~tsp/dummy.iso', 'command': 'registerIso',
'response': 'json'}
test_07_iso_tag (integration.component.test_tags.TestResourceTags): DEBUG:
Sending GET Cmd : registerIso===
[jira] [Created] (CLOUDSTACK-7024) [Automation] Deletion of Account that manages a project failed during cleanup of TestTemplateUsage Tests
Chandan Purushothama created CLOUDSTACK-7024:
Summary: [Automation] Deletion of Account that manages a project
failed during cleanup of TestTemplateUsage Tests
Key: CLOUDSTACK-7024
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7024
Project: CloudStack
Issue Type: Test
Security Level: Public (Anyone can view this level - this is the default.)
Components: Automation, Test
Affects Versions: 4.4.0
Reporter: Chandan Purushothama
Priority: Critical
Fix For: 4.4.0
=
Error Message:
=
Warning: Exception during cleanup : Job failed: {jobprocstatus : 0, created :
u'2014-06-26T05:54:00+', cmd :
u'org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd', userid :
u'57dd7fb6-fc58-11e3-919f-4eba41a459a4', jobstatus : 2, jobid :
u'0cf64ae7-f95c-4c46-a3ce-42f2c318ed3d', jobresultcode : 530, jobresulttype :
u'object', jobresult : {errorcode : 530, errortext : uThe account id=313
manages project(s) with ids 40, and can't be removed}, accountid :
u'57dd7098-fc58-11e3-919f-4eba41a459a4'}
begin captured logging
test_01_template_usage
(integration.component.test_project_usage.TestTemplateUsage): DEBUG: Payload:
{'signature': 'umKBWTVC8csMC7iBWcrmlZP7Bns=', 'apiKey':
u'Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Q',
'command': 'deleteAccount', 'id': u'6096abdb-9fe1-45ef-af30-6ecca7210515',
'response': 'json'}
test_01_template_usage
(integration.component.test_project_usage.TestTemplateUsage): DEBUG:
Sending GET Cmd : deleteAccount===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.220.153.217
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?signature=umKBWTVC8csMC7iBWcrmlZP7Bns%3DapiKey=Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Qcommand=deleteAccountid=6096abdb-9fe1-45ef-af30-6ecca7210515response=json
HTTP/1.1 200 78
test_01_template_usage
(integration.component.test_project_usage.TestTemplateUsage): DEBUG: === Jobid:
0cf64ae7-f95c-4c46-a3ce-42f2c318ed3d Started ===
test_01_template_usage
(integration.component.test_project_usage.TestTemplateUsage): DEBUG: Payload:
{'signature': '6MrHAB+DBVozv8OPtH8iU4S5bOc=', 'apiKey':
u'Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Q',
'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
u'0cf64ae7-f95c-4c46-a3ce-42f2c318ed3d'}
test_01_template_usage
(integration.component.test_project_usage.TestTemplateUsage): DEBUG:
Sending GET Cmd : queryAsyncJobResult===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.220.153.217
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?signature=6MrHAB%2BDBVozv8OPtH8iU4S5bOc%3DapiKey=Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Qcommand=queryAsyncJobResultresponse=jsonjobid=0cf64ae7-f95c-4c46-a3ce-42f2c318ed3d
HTTP/1.1 200 343
test_01_template_usage
(integration.component.test_project_usage.TestTemplateUsage): DEBUG: Response :
{jobprocstatus : 0, created : u'2014-06-26T05:54:00+', cmd :
u'org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd', userid :
u'57dd7fb6-fc58-11e3-919f-4eba41a459a4', jobstatus : 0, jobid :
u'0cf64ae7-f95c-4c46-a3ce-42f2c318ed3d', jobresultcode : 0, accountid :
u'57dd7098-fc58-11e3-919f-4eba41a459a4'}
test_01_template_usage
(integration.component.test_project_usage.TestTemplateUsage): DEBUG: ===
JobId:0cf64ae7-f95c-4c46-a3ce-42f2c318ed3d is Still Processing, Will TimeOut
in:3595
test_01_template_usage
(integration.component.test_project_usage.TestTemplateUsage): DEBUG: Payload:
{'signature': '6MrHAB+DBVozv8OPtH8iU4S5bOc=', 'apiKey':
u'Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Q',
'command': 'queryAsyncJobResult', 'response': 'json', 'jobid':
u'0cf64ae7-f95c-4c46-a3ce-42f2c318ed3d'}
test_01_template_usage
(integration.component.test_project_usage.TestTemplateUsage): DEBUG:
Sending GET Cmd : queryAsyncJobResult===
requests.packages.urllib3.connectionpool: INFO: Starting new HTTP connection
(1): 10.220.153.217
requests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?signature=6MrHAB%2BDBVozv8OPtH8iU4S5bOc%3DapiKey=Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Qcommand=queryAsyncJobResultresponse=jsonjobid=0cf64ae7-f95c-4c46-a3ce-42f2c318ed3d
HTTP/1.1 200 486
test_01_template_usage
(integration.component.test_project_usage.TestTemplateUsage): DEBUG: Response :
{jobprocstatus : 0, created : u'2014-06-26T05:54:00+', cmd :
u'org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd', userid :
[jira] [Created] (CLOUDSTACK-7025) [Automation] Failed to deply virtual machine: 'TestAddNetworkToVirtualMachine' object has no attribute 'defaultNetworkId'
Chandan Purushothama created CLOUDSTACK-7025: Summary: [Automation] Failed to deply virtual machine: 'TestAddNetworkToVirtualMachine' object has no attribute 'defaultNetworkId' Key: CLOUDSTACK-7025 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7025 Project: CloudStack Issue Type: Test Security Level: Public (Anyone can view this level - this is the default.) Components: Automation, Test Affects Versions: 4.4.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.4.0 === Bug in Script: === try: virtual_machine = VirtualMachine.create( self.api_client, self.services[virtual_machine], accountid=self.account.name, domainid=self.account.domainid, serviceofferingid=self.service_offering.id, mode=self.zone.networktype, networkids=[self.defaultNetworkId]) -- BUG: There is no reference to defaultNetworkId specified anywhere before this code in the TestAddNetworkToVirtualMachine class self.cleanup.append(virtual_machine) except Exception as e: self.fail(Failed to deply virtual machine: %s % e) Error Message: Failed to deply virtual machine: 'TestAddNetworkToVirtualMachine' object has no attribute 'defaultNetworkId' begin captured stdout - === TestName: test_03_add_nw_multiple_times_1_isolated | Status : FAILED === - end captured stdout -- begin captured logging test_03_add_nw_multiple_times_1_isolated (integration.component.test_add_remove_network.TestAddNetworkToVirtualMachine): DEBUG: STARTED : TC: test_03_add_nw_multiple_times_1_isolated ::: test_03_add_nw_multiple_times_1_isolated (integration.component.test_add_remove_network.TestAddNetworkToVirtualMachine): CRITICAL: FAILED: test_03_add_nw_multiple_times_1_isolated: ['Traceback (most recent call last):\n', ' File /usr/lib/python2.7/unittest/case.py, line 332, in run\ntestMethod()\n', ' File /usr/local/lib/python2.7/dist-packages/ddt.py, line 114, in wrapper\n return func(self, *args, **kwargs)\n', ' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_add_remove_network.py, line 408, in test_03_add_nw_multiple_times\nself.fail(Failed to deply virtual machine: %s % e)\n', ' File /usr/lib/python2.7/unittest/case.py, line 413, in fail\nraise self.failureException(msg)\n', AssertionError: Failed to deply virtual machine: 'TestAddNetworkToVirtualMachine' object has no attribute 'defaultNetworkId'\n] - end captured logging - Stacktrace File /usr/lib/python2.7/unittest/case.py, line 332, in run testMethod() File /usr/local/lib/python2.7/dist-packages/ddt.py, line 114, in wrapper return func(self, *args, **kwargs) File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_add_remove_network.py, line 408, in test_03_add_nw_multiple_times self.fail(Failed to deply virtual machine: %s % e) File /usr/lib/python2.7/unittest/case.py, line 413, in fail raise self.failureException(msg) 'Failed to deply virtual machine: \'TestAddNetworkToVirtualMachine\' object has no attribute \'defaultNetworkId\'\n begin captured stdout -\n=== TestName: test_03_add_nw_multiple_times_1_isolated | Status : FAILED ===\n\n\n- end captured stdout --\n begin captured logging \ntest_03_add_nw_multiple_times_1_isolated (integration.component.test_add_remove_network.TestAddNetworkToVirtualMachine): DEBUG: STARTED : TC: test_03_add_nw_multiple_times_1_isolated :::\ntest_03_add_nw_multiple_times_1_isolated (integration.component.test_add_remove_network.TestAddNetworkToVirtualMachine): CRITICAL: FAILED: test_03_add_nw_multiple_times_1_isolated: [\'Traceback (most recent call last):\\n\', \' File /usr/lib/python2.7/unittest/case.py, line 332, in run\\ntestMethod()\\n\', \' File /usr/local/lib/python2.7/dist-packages/ddt.py, line 114, in wrapper\\n return func(self, *args, **kwargs)\\n\', \' File /home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_add_remove_network.py, line 408, in test_03_add_nw_multiple_times\\nself.fail(Failed to deply virtual machine: %s % e)\\n\', \' File /usr/lib/python2.7/unittest/case.py, line 413, in fail\\nraise self.failureException(msg)\\n\', AssertionError: Failed to deply virtual machine: \'TestAddNetworkToVirtualMachine\' object has no attribute
[jira] [Updated] (CLOUDSTACK-7013) [Automation] AttributeError: type object 'TestFailureScenariosRemoveNicFromVM' has no attribute 'append'
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Purushothama updated CLOUDSTACK-7013:
-
Description:
==
Bug in test script:
==
cls.account =
Account.create(cls.api_client,cls.services[account],domainid = cls.domain.id)
cls.append(cls.account) BUG: should be cls.__cleanup.append
cls.service_offering =
ServiceOffering.create(cls.api_client,cls.services[service_offering])
cls._cleanup.append(cls.service_offering)
Test Script Failure:
test_26_add_nic_insufficient_permission
(integration.component.test_add_remove_network.TestFailureScenariosAddNetworkToVM):
CRITICAL: EXCEPTION: test_26_add_nic_insufficient_permission: ['Traceback
(most recent call last):\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in run\n
self.setUp()\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in setUp\n
self.setupContext(ancestor)\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in
setupContext\ntry_run(context, names)\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n
return func()\n', ' File
/home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_add_remove_network.py,
line 1392, in setUpClass\ncls.append(cls.account)\n', AttributeError:
type object 'TestFailureScenariosRemoveNicFromVM' has no attribute 'append'\n]
- end captured logging -
Stacktrace
File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in run
self.setUp()
File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in
setUp
self.setupContext(ancestor)
File /usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in
setupContext
try_run(context, names)
File /usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in
try_run
return func()
File
/home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_add_remove_network.py,
line 1392, in setUpClass
cls.append(cls.account)
'type object \'TestFailureScenariosRemoveNicFromVM\' has no attribute
\'append\'\n begin captured logging
\ntest_26_add_nic_insufficient_permission
(integration.component.test_add_remove_network.TestFailureScenariosAddNetworkToVM):
DEBUG: Payload: {\'apiKey\':
u\'Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Q\',
\'id\': u\'853b13be-4f75-4ca9-9f7c-3cf303d3cc2d\', \'state\': \'Disabled\',
\'command\': \'updateNetworkOffering\', \'signature\':
\'pP6GEHIbIDVHMxeYxAyQahpCxbI=\', \'response\':
\'json\'}\ntest_26_add_nic_insufficient_permission
(integration.component.test_add_remove_network.TestFailureScenariosAddNetworkToVM):
DEBUG: Sending GET Cmd :
updateNetworkOffering===\nrequests.packages.urllib3.connectionpool: INFO:
Starting new HTTP connection (1):
10.220.153.217\nrequests.packages.urllib3.connectionpool: DEBUG: GET
/client/api?apiKey=Sng6IriYYMri4AHzMZOEdseGWMJBZ-mfmhG30ZJIjV__AynsK03iV0GbvMzhglLVIff8W5ujp6gnTEdNS7LJ5Qid=853b13be-4f75-4ca9-9f7c-3cf303d3cc2dstate=Disabledcommand=updateNetworkOfferingsignature=pP6GEHIbIDVHMxeYxAyQahpCxbI%3Dresponse=json
HTTP/1.1 200
was:
==
Bug in test script:
==
cls.account =
Account.create(cls.api_client,cls.services[account],domainid = cls.domain.id)
cls.append(cls.account) BUG: should be cls.__cleanup.append
cls.service_offering =
ServiceOffering.create(cls.api_client,cls.services[service_offering])
cls._cleanup.append(cls.service_offering)
Test Script Failure:
test_26_add_nic_insufficient_permission
(integration.component.test_add_remove_network.TestFailureScenariosAddNetworkToVM):
CRITICAL: EXCEPTION: test_26_add_nic_insufficient_permission: ['Traceback
(most recent call last):\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 208, in run\n
self.setUp()\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 291, in setUp\n
self.setupContext(ancestor)\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/suite.py, line 314, in
setupContext\ntry_run(context, names)\n', ' File
/usr/local/lib/python2.7/dist-packages/nose/util.py, line 470, in try_run\n
return func()\n', ' File
/home/jenkins/workspace/xenrt-reg-adv-xs/cloudstack.git/test/integration/component/test_add_remove_network.py,
line 1392, in setUpClass\ncls.append(cls.account)\n', AttributeError:
type object 'TestFailureScenariosRemoveNicFromVM' has no attribute 'append'\n]
- end captured logging -
[jira] [Resolved] (CLOUDSTACK-3540) edithosts.sh script may delete the active dhcphosts.txt entry
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Yang resolved CLOUDSTACK-3540. Resolution: Fixed edithosts.sh script may delete the active dhcphosts.txt entry - Key: CLOUDSTACK-3540 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3540 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Sheng Yang Assignee: Sheng Yang Priority: Critical Fix For: 4.1.1, 4.2.0 This would result in the user vm cannot get the IP address. The reason is some entries in the dhcphosts.txt may has been deleted due to the similar ip of following vms, when edithosts.sh want to purge the old entries, it deleted the active entries by mistake. e.g. 10.1.1.1 would result in 10.1.1.123 removed in dhcphosts.txt The bug is introduced with IPv6 change for edithosts.txt. I would fix it soon and push for 4.1.1 as well. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6997) conntrack set to a very low value on router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy resolved CLOUDSTACK-6997. --- Resolution: Fixed conntrack set to a very low value on router --- Key: CLOUDSTACK-6997 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6997 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: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.4.0 Set ip_conntrack_max to 1 million ip conntrack value which is in sysctl.conf is not applied on VR. Debian wheezy sysctl.conf is not got loaded on boot time. There is bug in debian https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6997) conntrack set to a very low value on router
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14048515#comment-14048515 ] ASF subversion and git services commented on CLOUDSTACK-6997: - Commit d5e686f2ecd0d3322e69770919b650957324be03 in cloudstack's branch refs/heads/master from Jayapal [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d5e686f ] CLOUDSTACK-6997: Increase proc ip_conntrack_max conntrack set to a very low value on router --- Key: CLOUDSTACK-6997 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6997 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: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.4.0 Set ip_conntrack_max to 1 million ip conntrack value which is in sysctl.conf is not applied on VR. Debian wheezy sysctl.conf is not got loaded on boot time. There is bug in debian https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-7026) mark the test_01_primary_storage_iscsi as test that requires hardware.
Bharat Kumar created CLOUDSTACK-7026: Summary: mark the test_01_primary_storage_iscsi as test that requires hardware. Key: CLOUDSTACK-7026 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7026 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: Bharat Kumar Assignee: Bharat Kumar Fix For: 4.4.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7026) test that requires hardware.mark the test_01_primary_storage_iscsi as test that requires hardware
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-7026: - Summary: test that requires hardware.mark the test_01_primary_storage_iscsi as test that requires hardware (was: mark the test_01_primary_storage_iscsi as test that requires hardware.) test that requires hardware.mark the test_01_primary_storage_iscsi as test that requires hardware -- Key: CLOUDSTACK-7026 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7026 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: Bharat Kumar Assignee: Bharat Kumar Fix For: 4.4.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-7026) mark the test_01_primary_storage_iscsi as test that requires hardware
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-7026: - Summary: mark the test_01_primary_storage_iscsi as test that requires hardware (was: test that requires hardware.mark the test_01_primary_storage_iscsi as test that requires hardware) mark the test_01_primary_storage_iscsi as test that requires hardware - Key: CLOUDSTACK-7026 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7026 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: Bharat Kumar Assignee: Bharat Kumar Fix For: 4.4.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
