[jira] [Resolved] (CLOUDSTACK-2386) SRX:F5: fail to set firewall rule for icmp protocol

[Jayapal Reddy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jayapal Reddy resolved CLOUDSTACK-2386.
---

Resolution: Fixed

 SRX:F5: fail to set firewall rule for icmp protocol 
 

 Key: CLOUDSTACK-2386
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2386
 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: sadhu suresh
Assignee: Jayapal Reddy
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.rar


 steps:
 1. create a network offering with src and F5 in line mone
 2.create a sharednetwork using above NO
 3.deploy a vm using above shared network
 4.acquire an IP and enabled static nat
 5.configure the firewall on tcp protocol  on 80 port
 6.configure the firewall on ICMP protocol o
 actual result:
 able to configure the firewall on tcp protocol but fail to configure  the 
 firewall on ICMP protocol
 output of show firewall command for above acquired IP
 root# show firewall filter untrust 
 term 10-147-49-130-8 {
 from {
 source-address {
 0.0.0.0/0;
 }
 destination-address {
 10.147.49.130/32;
 }
 protocol tcp;
 destination-port 80-80;
 }
 then {
 count 10-147-49-130-i;
 accept;
 }
 }

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2659) Advanced Zone - during VM deployment need to check network permissions for shared account-specific guest networks too

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666024#comment-13666024
 ] 

ASF subversion and git services commented on CLOUDSTACK-2659:
-

Commit 51cf797d5ef69060c95dcb0fce47b2d96f16e26e in branch refs/heads/master 
from Prachi Damle pra...@cloud.com
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=51cf797 ]

CLOUDSTACK-2659 Advanced Zone - during VM deployment need to check network 
permissions for shared account-specific guest networks too

Changes:
- Check network permissions for account specific shared networks as well
- Changes to error to include network uuid instead of id


 Advanced Zone - during VM deployment need to check network permissions for 
 shared account-specific guest networks too
 -

 Key: CLOUDSTACK-2659
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2659
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Reporter: Prachi Damle
Assignee: Prachi Damle
 Fix For: 4.2.0


 Set up - Advanced Zone
 Create an account-specific shared network for a user account
 Deploy VM request for any other account using the above created shared 
 network does not fail 
 Expected Behavior:
 DeployVM request for any other account should fail

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-2648) [Multiple_IP_Ranges] Reboot or start/stop router vm deletes the ip alises created on VR in case of multiple subnets

[Bharat Kumar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bharat Kumar reassigned CLOUDSTACK-2648:


Assignee: Bharat Kumar

 [Multiple_IP_Ranges] Reboot or start/stop router vm deletes the ip alises 
 created on VR in case of multiple subnets
 ---

 Key: CLOUDSTACK-2648
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2648
 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
 Environment: Latest build on master: 
 CloudStack-non-OSS-MASTER-394-rhel6.3.tar.gz
Reporter: Sanjeev N
Assignee: Bharat Kumar
Priority: Critical
 Fix For: 4.2.0

 Attachments: management-server.rar, SMlog


 Reboot or start/stop router vm deletes the ip alises created on VR in case of 
 multiple subnets
 Steps to Reproduce:
 =
 1.Bring up CS in basic zone with xenserver6.1 
 2.Exhaust all the guest IP addresses in primary ip range by deploying guest 
 vms
 3.Add new guest IP range in new subnet 
 4.Deploy guest vms using the ip addresses from the new range
 5.Reboot or stop/start VR
 Observations:
 
 After step4 ip alias gets created on VR with IP address from the new subnet.
 After reboot or stop/start of the VR ip alias is getting removed from the VR.
 Verified the SMlog and found the following command getting executed with the 
 VR is rebooted related to ip alias:
 [22250] 2013-05-23 11:13:30.654474   VMOPS enter  deleteipAlias 
 [22250] 2013-05-23 11:13:30.654559  ['bin/bash', 
 '/opt/xensource/bin/deleteipAlias.sh', '169.254.3.21', '', 
 '18:10.147.43.132:255.255.255.192-21:10.147.43.195:255.255.255.192-']
 [22250] 2013-05-23 11:13:31.338199pread SUCCESS
 [22250] 2013-05-23 11:13:31.338311   VMOPS exit  deleteipAlias 
 IP aliases information is being passed to deleteipAlias.sh and due to which 
 ip alias are getting removed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-2644) [Multiple_IP_Ranges] user data service on VR does not work in case of multiple subnets

[Bharat Kumar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bharat Kumar reassigned CLOUDSTACK-2644:


Assignee: Bharat Kumar

 [Multiple_IP_Ranges] user data service on VR does not work in case of 
 multiple subnets
 --

 Key: CLOUDSTACK-2644
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2644
 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
 Environment: Latest build on master: 
 CloudStack-non-OSS-MASTER-394-rhel6.3.tar.gz
Reporter: Sanjeev N
Assignee: Bharat Kumar
Priority: Critical
 Fix For: 4.2.0


 user data service on VR does not work in case of multiple subnets
 Steps to reproduce:
 
 1.Bring up CS in basic zone with xenserver6.1
 2.Exhaust all the guest IP addresses in primary ip range
 3.Add new guest IP range in new subnet
 4.Deploy guest vm with user data using the IP address in new ip range.
 http://10.147.59.126:8096/client/api?command=deployVirtualMachineserviceofferingid=ab7ad806-65c2-4a12-8b6c-ddb3135b5d24templateid=d3b13472-c2d2-11e2-ac35-06045a66zoneid=e4b7da5e-80d1-43d0-ac15-a987f725b80cuserdata=TXVsdGlwbGUgSVAgUmFuZ2VzIG11bHRpcGxlIFN1Ym5ldHMgVGVzdA==
 5.Fetch the user data 
 Expected behavior:
 
 from the guest vm executing the following command should fetch the guest vm 
 userdata provided while deploying guest vm:
 curl http://10.147.43.195/latest/user-data
 Actual Result:
 =
 fetching userdata failed :
 [root@e3e13452-7e1e-4939-95c0-c64c333d6937 ~]# curl 
 http://10.147.43.195/latest/user-data
 curl: (7) couldn't connect to host
 Observations:
 
 On VR userdata service is running as a web server and listening on primary IP 
 address and port 80.
 Following is the content of the /etc/apache2/port.conf  :
 # If you just change the port or add more ports here, you will likely also
 # have to change the VirtualHost statement in
 # /etc/apache2/sites-enabled/000-default
 # This is also true if you have upgraded from before 2.2.9-3 (i.e. from
 # Debian etch). See /usr/share/doc/apache2.2-common/NEWS.Debian.gz and
 # README.Debian.gz
 NameVirtualHost 10.147.43.6:80
 Listen 10.147.43.6:80
 IfModule mod_ssl.c
 # If you add NameVirtualHost *:443 here, you will also have to change
 # the VirtualHost statement in /etc/apache2/sites-available/default-ssl
 # to VirtualHost *:443
 # Server Name Indication for SSL named virtual hosts is currently not
 # supported by MSIE on Windows XP.
 Listen 10.147.43.6:443
 /IfModule
 IfModule mod_gnutls.c
 Listen 10.147.43.6:443
 /IfModule
 But in case of multiple IP subnets, for every subnet one ip alis gets created 
 on router vm with IP address from each subnet. So the guest vm deployed in 
 new subnet can't fetch the userdata since there is no userdata service 
 listening on the ip alias address belongs to that subnet.
 Either userdata service should listen on 0.0.0.0 ip address or for every ip 
 alis address one entry should be created in /etc/apache2/ports.conf file to 
 provide user data service to the guest vms in each subnet.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-2641) [Multiple_IP_Ranges] Failure in deleting guest IP range should mark nic_ip_alias state to Revoked

[Bharat Kumar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bharat Kumar reassigned CLOUDSTACK-2641:


Assignee: Bharat Kumar

 [Multiple_IP_Ranges] Failure in deleting guest IP range should mark 
 nic_ip_alias state to Revoked 
 --

 Key: CLOUDSTACK-2641
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2641
 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
 Environment: Latest build from master branch: 
 CloudStack-non-OSS-MASTER-394-rhel6.3.tar.gz
Reporter: Sanjeev N
Assignee: Bharat Kumar
Priority: Critical
 Fix For: 4.2.0


 Failure in deleting guest IP range should mark ip alias state in nic_ip_alias 
 table to Revoked 
 Steps to Reproduce:
 =
 1.Bring up CS in basic zone with xenserver 6.1
 2.Exhaust all the guest IP ranges from the primary IP range added during zone 
 creation
 3.Add another guest IP range in new CIDR
 4.Deploy guest vm
 5.Set expunge interval to a small value say 60 secs, and restart management 
 server
 6.Destroy the guest vm deployed at step4
 7.After vm expunge, delete the guest IP range added at step3
 Expected Result:
 =
 In case of successful deletion of the guest IP range , ip alias created on VR 
 should be deleted and the entry from nic_ip_alias table should be removed.
 Actual Result:
 
 Due to bug CLOUDSTACK-2621, IP range deletion failed and alias IP address 
 remained in allocated state in user_ip_address table but ip alias was removed 
 from the backend(from the VR).
 nic ip alias state shows active in the DB.
 Impact:
 ==
 Since the deletion failed, if the user wants to use the ip range and tries to 
 deploy vm using this guest IP range, guest vms does not get the IP address 
 since VR does not have ip alias to server dhcp request in this guest range.
 CS does not try to recreate ip alias on VR since nic_ip_alias table shows the 
 state as active.
 mysql select * from nic_ip_alias\G;
 *** 1. row ***
 id: 1
   uuid: 757537e5-2c30-47ef-9534-9624ff908af0
 nic_id: 9
ip4_address: 10.147.43.132
ip6_address: NULL
netmask: 255.255.255.192
gateway: 10.147.43.129
 start_ip_of_subnet: 10.147.43.129
 network_id: 204
   vmId: 4
alias_count: 18
created: 2013-05-22 15:14:21
 account_id: 2
  domain_id: 1
  state: active
 1 row in set (0.00 sec)
 ERROR:
 No query specified

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2663) request for adding networkupgrade support to shared network

[sadhu suresh (JIRA)]

sadhu suresh created CLOUDSTACK-2663:


 Summary: request for adding networkupgrade support to shared 
network 
 Key: CLOUDSTACK-2663
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2663
 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: sadhu suresh
Priority: Minor


In case of shared networks, there is no support for network upgrade.Right now  
this support applicable to isolated networks  .

 when we try to upgrade the networking offering its failing  with below  message
http://10.147.59.194:8096/client/api?command=updateNetworkid=221networkofferingid=ecef78b3-01d7-4730-9560-13eac7195c4fchangecidr=falseresponse=xml


NetworkOffering and domain suffix upgrade can be perfomed for Isolated 
networks only



It will be good ,if we add this support in future.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2664) Upgrade failure while removing Firewall service for SG shared network offering

[Kishan Kavala (JIRA)]

Kishan Kavala created CLOUDSTACK-2664:
-

 Summary: Upgrade failure while removing Firewall service for SG 
shared network offering
 Key: CLOUDSTACK-2664
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2664
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Kishan Kavala
 Fix For: 4.2.0


Incorrect SQL is causing below exception during 41 to 42 upgrade :

com.cloud.utils.exception.CloudRuntimeException: Unable to remove Firewall 
service for SG shared network offering.
at 
com.cloud.upgrade.dao.Upgrade410to420.removeFirewallServiceFromSharedNetworkOfferingWithSGService(Upgrade410to420.java:767)
at 
com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:78)
at 
com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:239)
at 
com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:364)
at 
com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
at 
com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have 
an error in your SQL syntax; check the manual that corresponds to your MySQL 
server version for the right syntax to use near 'where network_offering_id=5 
and service='Firewall'' at line 1
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:525)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1053)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4074)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4006)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2468)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2629)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2719)
at 
com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155)
at 
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2450)
at 
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2371)
at 
com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2355)
at 
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at 
org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at 
com.cloud.upgrade.dao.Upgrade410to420.removeFirewallServiceFromSharedNetworkOfferingWithSGService(Upgrade410to420.java:764)


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-2664) Upgrade failure while removing Firewall service for SG shared network offering

[Kishan Kavala (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kishan Kavala reassigned CLOUDSTACK-2664:
-

Assignee: Kishan Kavala

 Upgrade failure while removing Firewall service for SG shared network offering
 --

 Key: CLOUDSTACK-2664
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2664
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Kishan Kavala
Assignee: Kishan Kavala
 Fix For: 4.2.0


 Incorrect SQL is causing below exception during 41 to 42 upgrade :
 com.cloud.utils.exception.CloudRuntimeException: Unable to remove Firewall 
 service for SG shared network offering.
   at 
 com.cloud.upgrade.dao.Upgrade410to420.removeFirewallServiceFromSharedNetworkOfferingWithSGService(Upgrade410to420.java:767)
   at 
 com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:78)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:239)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:364)
   at 
 com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
   at 
 com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
   at java.util.TimerThread.mainLoop(Timer.java:555)
   at java.util.TimerThread.run(Timer.java:505)
 Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You 
 have an error in your SQL syntax; check the manual that corresponds to your 
 MySQL server version for the right syntax to use near 'where 
 network_offering_id=5 and service='Firewall'' at line 1
   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:525)
   at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
   at com.mysql.jdbc.Util.getInstance(Util.java:386)
   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1053)
   at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4074)
   at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4006)
   at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2468)
   at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2629)
   at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2719)
   at 
 com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155)
   at 
 com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2450)
   at 
 com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2371)
   at 
 com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2355)
   at 
 org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
   at 
 org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
   at 
 com.cloud.upgrade.dao.Upgrade410to420.removeFirewallServiceFromSharedNetworkOfferingWithSGService(Upgrade410to420.java:764)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2664) Upgrade failure while removing Firewall service for SG shared network offering

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666040#comment-13666040
 ] 

ASF subversion and git services commented on CLOUDSTACK-2664:
-

Commit 3b48299a0395916ad3dc8a95b6d98afd96ecf251 in branch refs/heads/master 
from [~kishan]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3b48299 ]

CLOUDSTACK-2664: Fixed delete query. Added log message when 
CloudRuntimeException is thrown during upgrade


 Upgrade failure while removing Firewall service for SG shared network offering
 --

 Key: CLOUDSTACK-2664
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2664
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Kishan Kavala
Assignee: Kishan Kavala
 Fix For: 4.2.0


 Incorrect SQL is causing below exception during 41 to 42 upgrade :
 com.cloud.utils.exception.CloudRuntimeException: Unable to remove Firewall 
 service for SG shared network offering.
   at 
 com.cloud.upgrade.dao.Upgrade410to420.removeFirewallServiceFromSharedNetworkOfferingWithSGService(Upgrade410to420.java:767)
   at 
 com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:78)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:239)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:364)
   at 
 com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
   at 
 com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
   at java.util.TimerThread.mainLoop(Timer.java:555)
   at java.util.TimerThread.run(Timer.java:505)
 Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You 
 have an error in your SQL syntax; check the manual that corresponds to your 
 MySQL server version for the right syntax to use near 'where 
 network_offering_id=5 and service='Firewall'' at line 1
   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:525)
   at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
   at com.mysql.jdbc.Util.getInstance(Util.java:386)
   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1053)
   at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4074)
   at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4006)
   at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2468)
   at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2629)
   at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2719)
   at 
 com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155)
   at 
 com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2450)
   at 
 com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2371)
   at 
 com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2355)
   at 
 org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
   at 
 org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
   at 
 com.cloud.upgrade.dao.Upgrade410to420.removeFirewallServiceFromSharedNetworkOfferingWithSGService(Upgrade410to420.java:764)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666041#comment-13666041
 ] 

ASF subversion and git services commented on CLOUDSTACK-528:


Commit 3e02a76f001b14ad25e5fdc55efc137457e5e52b in branch refs/heads/master 
from [~kishan]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3e02a76 ]

CLOUDSTACK-528: Config value has to be encrypted for Hidden category configs


 Failed to create secondary storage
 --

 Key: CLOUDSTACK-528
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.0.0, 4.1.0
 Environment: CentOS 
Reporter: Tamas Monos
Assignee: Wei Zhou
Priority: Blocker
 Fix For: 4.1.0


  Hi,
 I cannot add secondary storage to my existing Zone. This prevents the 
 platform from operating.
 API call via GUI captured by tcpdump:
 http://sandbox.veber.co.uk/client/api?command=addSecondaryStoragezoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloudresponse=jsonsessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D_=1353673985114
 Result:
 Unable to connect due to 
 java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data 
 center: null
 at 
 com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501)
 at 
 com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551)
 at 
 com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
 at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
 at 
 org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
 at 
 org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
 at 
 org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2012-11-23 12:32:58,518 INFO  [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-23:null) server resources successfully discovered by 
 SecondaryStorage
 2012-11-23 12:32:58,518 WARN  [cloud.api.ApiDispatcher] 
 (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to 
 add secondary storage
 Debug:
 mysql select uuid from data_center where name='Watford';
 +--+
 | uuid |
 +--+
 | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 |
 +--+
 The Zone ID matches but API throws exception while the IS is supplied in the 
 query.
 Scenario:
 I have upgraded from 3.0.2 to 4.0.0. Due to the upgrade scripts did not 
 update the systemVMs to the new template I've applied a workaround and 
 recreated the systemVMs with the new templates. After that I've enabled 
 storage clean-up and the cleanup script destroyed everything on 

[jira] [Created] (CLOUDSTACK-2665) [Object_Store_Refactor] UI: Default cent OS template Ready field shows NO in UI whereas it shows YES in DB

[Sanjeev N (JIRA)]

Sanjeev N created CLOUDSTACK-2665:
-

 Summary: [Object_Store_Refactor] UI: Default cent OS template 
Ready field shows NO in UI whereas it shows YES in DB
 Key: CLOUDSTACK-2665
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2665
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: UI
Affects Versions: 4.2.0
 Environment: Latest build from object_store branch
Reporter: Sanjeev N
 Fix For: 4.2.0


Default cent OS template Ready field shows NO in UI whereas it shows YES in DB

Steps to Reproduce:
=
1.Bring up CS in advanced zone with s3 as the secondary storage provider
2.Wait for the SSVM to come up
3.After SSVM is up, it downloads the default cent os template to S3 image store 
and once the download is successful template state will be marked Ready.

mysql select * from vm_template where id=5\G;
*** 1. row ***
id: 5
   unique_name: centos56-x86_64-xen
  name: CentOS 5.6(64-bit) no GUI (XenServer)
  uuid: 162ea93c-c469-11e2-9096-06ab465f
public: 1
  featured: 1
  type: BUILTIN
   hvm: 0
  bits: 64
   url: http://10.147.28.7/templates/builtin/centos56-x86_64.vhd.bz2
format: VHD
   created: 2013-05-24 07:57:19
   removed: NULL
account_id: 1
  checksum: 905cec879afd9c9d22ecc8036131a180
  display_text: CentOS 5.6(64-bit) no GUI (XenServer)
   enable_password: 0
 enable_sshkey: 0
   guest_os_id: 12
  bootable: 1
   prepopulate: 0
   cross_zones: 1
   extractable: 1
   hypervisor_type: XenServer
source_template_id: NULL
  template_tag: NULL
  sort_key: 0
  size: 374730926
 state: Ready
  update_count: 3
   updated: 2013-05-24 12:18:52
1 row in set (0.00 sec)

ERROR:
No query specified

Attached screen shot to describe the bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-2664) Upgrade failure while removing Firewall service for SG shared network offering

[Kishan Kavala (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kishan Kavala resolved CLOUDSTACK-2664.
---

Resolution: Fixed

 Upgrade failure while removing Firewall service for SG shared network offering
 --

 Key: CLOUDSTACK-2664
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2664
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Kishan Kavala
Assignee: Kishan Kavala
 Fix For: 4.2.0


 Incorrect SQL is causing below exception during 41 to 42 upgrade :
 com.cloud.utils.exception.CloudRuntimeException: Unable to remove Firewall 
 service for SG shared network offering.
   at 
 com.cloud.upgrade.dao.Upgrade410to420.removeFirewallServiceFromSharedNetworkOfferingWithSGService(Upgrade410to420.java:767)
   at 
 com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:78)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:239)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:364)
   at 
 com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
   at 
 com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
   at java.util.TimerThread.mainLoop(Timer.java:555)
   at java.util.TimerThread.run(Timer.java:505)
 Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You 
 have an error in your SQL syntax; check the manual that corresponds to your 
 MySQL server version for the right syntax to use near 'where 
 network_offering_id=5 and service='Firewall'' at line 1
   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:525)
   at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
   at com.mysql.jdbc.Util.getInstance(Util.java:386)
   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1053)
   at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4074)
   at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4006)
   at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2468)
   at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2629)
   at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2719)
   at 
 com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155)
   at 
 com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2450)
   at 
 com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2371)
   at 
 com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2355)
   at 
 org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
   at 
 org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
   at 
 com.cloud.upgrade.dao.Upgrade410to420.removeFirewallServiceFromSharedNetworkOfferingWithSGService(Upgrade410to420.java:764)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-105) /tmp/stream-unix.####.###### stale sockets causing inodes to run out on Xenserver

[Stephen Turner (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666121#comment-13666121
 ] 

Stephen Turner commented on CLOUDSTACK-105:
---

Thanks, Caleb. Any news from your experiment?

 /tmp/stream-unix..## stale sockets causing inodes to run out on 
 Xenserver
 -

 Key: CLOUDSTACK-105
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-105
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Third-Party Bugs
Affects Versions: pre-4.0.0
 Environment: Xenserver 6.0.2
 Cloudstack 3.0.2
Reporter: Caleb Call
Assignee: Devdeep Singh
 Fix For: 4.1.0

 Attachments: messages


 We came across an interesting issue in one of our clusters.  We ran out of 
 inodes on all of our cluster members (since when does this happen in 2012?).  
 When this happened, it in turn made the / filesystem a read-only filesystem 
 which in turn made all the hosts go in to emergency maintenance mode and as a 
 result get marked down by Cloudstack.  We found that it was caused by 
 hundreds of thousands of stale socket files in /tmp named 
 stream-unix..##.  To resolve the issue, we had to delete those 
 stale socket files (find /tmp -name *stream* -mtime +7 -exec rm -v {} \;), 
 then kill and restart xapi, then correct the emergency maintenance mode.  
 These hosts had only been up for 45 days before this issue occurred.  
 In our scouring of the interwebs, the only other instance we've been able to 
 find of this (or similar) happening is in the same setup we are currently 
 running. Xenserver 6.0.2 with CS 3.0.2.  Do these stream-unix sockets have 
 anything to do with Cloudstack?  I would think if this was a Xenserver issue 
 (bug), there would be a lot more on the internet about this happening.  For a 
 temporary workaround, we've added a cronjob to cleanup these files but we'd 
 really like to address the actual issue that's causing these sockets to 
 become stale and not get cleaned-up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2667) ScaleVM: marvin test_scalevm test fails to scale the vm to new offering

[Prasanna Santhanam (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanna Santhanam updated CLOUDSTACK-2667:
---

Priority: Critical  (was: Major)

 ScaleVM: marvin test_scalevm test fails to scale the vm to new offering
 ---

 Key: CLOUDSTACK-2667
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2667
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Test
Affects Versions: 4.2.0
Reporter: Prasanna Santhanam
Priority: Critical
 Fix For: 4.2.0


 http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-smoke-matrix/suite=test_scale_vm/lastCompletedBuild/testReport/integration.smoke.test_scale_vm/TestScaleVm/test_01_scale_vm/
 The above test has been consistently failing for the past 69 builds. Please 
 fix it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2667) ScaleVM: marvin test_scalevm test fails to scale the vm to new offering

[Prasanna Santhanam (JIRA)]

Prasanna Santhanam created CLOUDSTACK-2667:
--

 Summary: ScaleVM: marvin test_scalevm test fails to scale the vm 
to new offering
 Key: CLOUDSTACK-2667
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2667
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Test
Affects Versions: 4.2.0
Reporter: Prasanna Santhanam
 Fix For: 4.2.0


http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-smoke-matrix/suite=test_scale_vm/lastCompletedBuild/testReport/integration.smoke.test_scale_vm/TestScaleVm/test_01_scale_vm/

The above test has been consistently failing for the past 69 builds. Please fix 
it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Reopened] (CLOUDSTACK-2528) Object_Store_Refactor - Not able to download volumes.

[Sanjeev N (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjeev N reopened CLOUDSTACK-2528:
---


Observed NPE while executing extract volume cmd:
2013-05-24 10:43:54,790 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) 
===START===  10.146.0.15 -- GET  
command=extractVolumeid=497a4f9e-3af8-4535-825e-1153d61bd10azoneid=ab0cac49-0ba0-47b6-acc7-a79803852bc7mode=HTTP_DOWNLOADresponse=jsonsessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D_=1369386924092
2013-05-24 10:43:54,932 DEBUG [cloud.async.AsyncJobManagerImpl] 
(catalina-exec-12:null) submit async job-18, details: AsyncJobVO {id:18, 
userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId: 4, 
cmd: org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd, 
cmdOriginator: null, cmdInfo: 
{response:json,id:497a4f9e-3af8-4535-825e-1153d61bd10a,sessionkey:ixXFsVuKowmsD/QeRoCj8INv7Y0\u003d,ctxUserId:2,zoneid:ab0cac49-0ba0-47b6-acc7-a79803852bc7,httpmethod:GET,_:1369386924092,ctxAccountId:2,ctxStartEventId:64,mode:HTTP_DOWNLOAD},
 cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
processStatus: 0, resultCode: 0, result: null, initMsid: 7332683579487, 
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-24 10:43:54,935 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) 
===END===  10.146.0.15 -- GET  
command=extractVolumeid=497a4f9e-3af8-4535-825e-1153d61bd10azoneid=ab0cac49-0ba0-47b6-acc7-a79803852bc7mode=HTTP_DOWNLOADresponse=jsonsessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D_=1369386924092
2013-05-24 10:43:54,938 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-18:job-18) Executing 
org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd for job-18
2013-05-24 10:43:54,997 DEBUG [cloud.server.ManagementServerImpl] 
(Job-Executor-18:job-18) Extract Mode - HTTP_DOWNLOAD
2013-05-24 10:43:55,012 DEBUG [agent.transport.Request] 
(Job-Executor-18:job-18) Seq 1-698155503: Sending  { Cmd , MgmtId: 
7332683579487, via: 1, Ver: v1, Flags: 100111, 
[{com.cloud.agent.api.storage.CopyVolumeCommand:{volumeId:4,volumePath:0ebe4e49-0147-406a-8af5-17e1c3bb97af,pool:{id:1,uuid:c65a038a-750c-3b4f-bf26-7ce3b74e1c85,host:10.147.28.7,path:/export/home/sanjeev/pri_xen_os,port:2049,type:NetworkFilesystem},toSecondaryStorage:true,wait:10800}}]
 }
2013-05-24 10:43:55,012 DEBUG [agent.transport.Request] 
(Job-Executor-18:job-18) Seq 1-698155503: Executing:  { Cmd , MgmtId: 
7332683579487, via: 1, Ver: v1, Flags: 100111, 
[{com.cloud.agent.api.storage.CopyVolumeCommand:{volumeId:4,volumePath:0ebe4e49-0147-406a-8af5-17e1c3bb97af,pool:{id:1,uuid:c65a038a-750c-3b4f-bf26-7ce3b74e1c85,host:10.147.28.7,path:/export/home/sanjeev/pri_xen_os,port:2049,type:NetworkFilesystem},toSecondaryStorage:true,wait:10800}}]
 }
2013-05-24 10:43:55,013 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-434:null) Seq 1-698155503: Executing request
2013-05-24 10:43:55,103 WARN  [xen.resource.CitrixResourceBase] 
(DirectAgent-434:null) Catch Exception java.lang.NullPointerException due to 
java.lang.NullPointerException
java.lang.NullPointerException
at java.net.URI$Parser.parse(URI.java:3019)
at java.net.URI.init(URI.java:595)
at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:6447)
at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:557)
at 
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
at 
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:104)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-05-24 10:43:55,105 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-434:null) Seq 1-698155503: Response Received:
2013-05-24 10:43:55,106 DEBUG [agent.transport.Request] (DirectAgent-434:null) 
Seq 1-698155503: Processing:  { Ans: , MgmtId: 7332683579487, via: 1, Ver: v1, 
Flags: 110, 
[{com.cloud.agent.api.storage.CopyVolumeAnswer:{result:false,details:Catch
 Exception java.lang.NullPointerException due to 
java.lang.NullPointerException,wait:0}}] }

[jira] [Updated] (CLOUDSTACK-2528) Object_Store_Refactor - Not able to download volumes.

[Sanjeev N (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjeev N updated CLOUDSTACK-2528:
--

Attachment: management-server.rar

management server log file attached

 Object_Store_Refactor - Not able to download volumes.
 -

 Key: CLOUDSTACK-2528
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2528
 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
 Environment: Build from object_store
Reporter: Sangeetha Hariharan
Assignee: edison su
 Fix For: 4.2.0

 Attachments: management-server.rar


 1.Using UI/createVolume API create new volume.
 2.Bring volume to ready state.
 3.Download volume using UI/extractVolume API
 Volume downlaod fails.
 Following exception seen in management server logs:
 8ce-dbb58722c34czoneid=387432e3-2470-475b-ae39-f4ef14e91779mode=HTTP_DOWNLOADresponse=jsonsessionkey=s5BZB6QnqMRZJHgCPOGxdTxPjMY%3D_=1368668522760
 2013-05-15 17:45:02,547 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-14:null) submit async job-47, details: AsyncJobVO {id:47, 
 userId: 2, accountId: 2, sessionKey: null, instanceType: Volume, instanceId: 
 16, cmd: org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd, 
 cmdOriginator: null, cmdInfo: 
 {id:0e03eb25-8b1b-4f93-b8ce-dbb58722c34c,response:json,sessionkey:s5BZB6QnqMRZJHgCPOGxdTxPjMY\u003d,ctxUserId:2,zoneid:387432e3-2470-475b-ae39-f4ef14e91779,httpmethod:GET,_:1368668522760,ctxAccountId:2,ctxStartEventId:270,mode:HTTP_DOWNLOAD},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, result: null, initMsid: 206915885079359, 
 completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
 2013-05-15 17:45:02,548 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-11:job-47) Executing 
 org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd for job-47
 2013-05-15 17:45:02,550 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null) 
 ===END===  10.217.252.128 -- GET  
 command=extractVolumeid=0e03eb25-8b1b-4f93-b8ce-dbb58722c34czoneid=387432e3-2470-475b-ae39-f4ef14e91779mode=HTTP_DOWNLOADresponse=jsonsessionkey=s5BZB6QnqMRZJHgCPOGxdTxPjMY%3D_=1368668522760
 2013-05-15 17:45:02,598 DEBUG [cloud.server.ManagementServerImpl] 
 (Job-Executor-11:job-47) Extract Mode - HTTP_DOWNLOAD
 2013-05-15 17:45:02,604 DEBUG [agent.transport.Request] 
 (Job-Executor-11:job-47) Seq 1-1843200414: Sending  { Cmd , MgmtId: 
 206915885079359, via: 1, Ver: v1, Flags: 100111, 
 [{com.cloud.agent.api.storage.CopyVolumeCommand:{volumeId:16,volumePath:64bf190f-6e90-4fc1-86eb-5340c894e328,pool:{id:1,uuid:e97b5727-d157-3dc1-b32c-065b99806623,host:10.223.110.232,path:/export/home/sangeetha/campo-systemp-1/primary,port:2049,type:NetworkFilesystem},secondaryStorageURL:nfs://10.223.110.232/export/home/sangeetha/campo-systemp-1/secondary,toSecondaryStorage:true,wait:10800}}]
  }
 2013-05-15 17:45:02,604 DEBUG [agent.transport.Request] 
 (Job-Executor-11:job-47) Seq 1-1843200414: Executing:  { Cmd , MgmtId: 
 206915885079359, via: 1, Ver: v1, Flags: 100111, 
 [{com.cloud.agent.api.storage.CopyVolumeCommand:{volumeId:16,volumePath:64bf190f-6e90-4fc1-86eb-5340c894e328,pool:{id:1,uuid:e97b5727-d157-3dc1-b32c-065b99806623,host:10.223.110.232,path:/export/home/sangeetha/campo-systemp-1/primary,port:2049,type:NetworkFilesystem},secondaryStorageURL:nfs://10.223.110.232/export/home/sangeetha/campo-systemp-1/secondary,toSecondaryStorage:true,wait:10800}}]
  }
 2013-05-15 17:45:21,872 DEBUG [agent.transport.Request] 
 (Job-Executor-11:job-47) Seq 1-1843200414: Received:  { Ans: , MgmtId: 
 206915885079359, via: 1, Ver: v1, Flags: 110, { CopyVolumeAnswer } }
 2013-05-15 17:45:21,872 DEBUG [agent.manager.AgentAttache] 
 (DirectAgent-421:null) Seq 1-1843200414: No more commands found
 2013-05-15 17:45:21,964 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-11:job-47) Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd
 java.lang.ClassCastException: 
 org.apache.cloudstack.storage.image.store.ImageStoreImpl cannot be cast to 
 org.apache.cloudstack.storage.datastore.db.ImageStoreVO
 at 
 com.cloud.storage.upload.UploadMonitorImpl.createVolumeDownloadURL(UploadMonitorImpl.java:289)
 at 
 com.cloud.server.ManagementServerImpl.extractVolume(ManagementServerImpl.java:3439)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.volume.ExtractVolumeCmd.execute(ExtractVolumeCmd.java:131)

[jira] [Commented] (CLOUDSTACK-2354) Unable to create Windows VMs using ISO

[Nitin Mehta (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666158#comment-13666158
 ] 

Nitin Mehta commented on CLOUDSTACK-2354:
-

Thanks Stephen. Based on your comment I am assuming that atleast the windows 
ISOs we will never be able to deterministically find out when the PV drivers 
got installed. The reason is when we stop the vm from Cloudstack it actually 
destroys it on the XS and when you are deploying the vm you cant beforehand 
know whether the template/ISO has the PV drivers correct ? In fact this is true 
for any template that do not come with PV drivers correct ? We will now have to 
rely on the user to signal to us explicitly that he has installed PV drivers 
than finding out ourselves.

Also I had one observation to share that while deploying a windows template 
even though the dynamic_max  static_max it deployed fine for me. Any idea how ?
Another question is whether dynamic_max  static_max the only issue if PV 
drivers do no exist ? Can we deploy a vm with a setting like static_min = 
dynamic_min = X  dynamic_max = static_max = Memory_overprovisioning_factor * X 
? This would be useful for memory overprovisioning.
Is this documented somewhere that for DMC to work we need PV drivers and some 
related readings so that I am more informed on this ?

Thanks again for your prompt help

 Unable to create Windows VMs using ISO
 --

 Key: CLOUDSTACK-2354
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2354
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: ISO
Affects Versions: 4.2.0
 Environment: Build No.#256 
 (CloudStack-non-OSS-MASTER-256-rhel6.3.tar.gz)
 XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr 
 Server.
Reporter: Minying Bao
Assignee: Harikrishna Patnala
Priority: Blocker
 Fix For: 4.2.0

 Attachments: ISO_Win8.jpg, ISO_XP-Auto-Shutdown.JPG.jpg, 
 ISO_XP_State.JPG.jpg, management-server.log


 Repro Steps
 Setup the cloudstack environment as normal. (Configured NFS  CS-Mgr Servers)
 Launch browser, start CloudStack WebConsole and finish to build a cloud step 
 by step. (It should use workaround of build#256 when building a cloud.)
 Register the ISOs to the CloudStack as follows Win7, Win8, 2k8R2, XP. Wait 
 for Status showing Successfully Installed.
 Add instances from all above ISOs.
 Expected Result
 All the instances should be added successfully, and all the related VMs 
 should be launched successfully on XenServer Host.
 Actual Result
 Unable to create Windows VMs using ISO.
 VMs based on the Win8/Win7 ISOs - WebConsole show Error (refer to 
 screenshot ISO_Win8.jpg) 
 VMs based on the XP/W2k8r2 ISO - WebConsole show Running - Auto-shutdown 
 during the OS installation - WebConsole show Stopped (refer to screenshots 
 ISO_XP-Auto-Shutdown.JPG and ISO_XP_State.JPG ) 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2669) ScaleVm - resource limit and count logic missing

[Nitin Mehta (JIRA)]

Nitin Mehta created CLOUDSTACK-2669:
---

 Summary: ScaleVm - resource limit and count logic missing
 Key: CLOUDSTACK-2669
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2669
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Nitin Mehta




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2664) Upgrade failure while removing Firewall service for SG shared network offering

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666171#comment-13666171
 ] 

ASF subversion and git services commented on CLOUDSTACK-2664:
-

Commit 3b48299a0395916ad3dc8a95b6d98afd96ecf251 in branch 
refs/heads/rbd-snap-clone from [~kishan]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3b48299 ]

CLOUDSTACK-2664: Fixed delete query. Added log message when 
CloudRuntimeException is thrown during upgrade


 Upgrade failure while removing Firewall service for SG shared network offering
 --

 Key: CLOUDSTACK-2664
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2664
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Kishan Kavala
Assignee: Kishan Kavala
 Fix For: 4.2.0


 Incorrect SQL is causing below exception during 41 to 42 upgrade :
 com.cloud.utils.exception.CloudRuntimeException: Unable to remove Firewall 
 service for SG shared network offering.
   at 
 com.cloud.upgrade.dao.Upgrade410to420.removeFirewallServiceFromSharedNetworkOfferingWithSGService(Upgrade410to420.java:767)
   at 
 com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:78)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:239)
   at 
 com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:364)
   at 
 com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
   at 
 com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
   at java.util.TimerThread.mainLoop(Timer.java:555)
   at java.util.TimerThread.run(Timer.java:505)
 Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You 
 have an error in your SQL syntax; check the manual that corresponds to your 
 MySQL server version for the right syntax to use near 'where 
 network_offering_id=5 and service='Firewall'' at line 1
   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:525)
   at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
   at com.mysql.jdbc.Util.getInstance(Util.java:386)
   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1053)
   at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4074)
   at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4006)
   at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2468)
   at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2629)
   at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2719)
   at 
 com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155)
   at 
 com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2450)
   at 
 com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2371)
   at 
 com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2355)
   at 
 org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
   at 
 org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
   at 
 com.cloud.upgrade.dao.Upgrade410to420.removeFirewallServiceFromSharedNetworkOfferingWithSGService(Upgrade410to420.java:764)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2669) ScaleVm - resource limit and count logic missing

[Sailaja Mada (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666177#comment-13666177
 ] 

Sailaja Mada commented on CLOUDSTACK-2669:
--

I have created the bug for this issue : CLOUDSTACK-2298 Dynamic scaleup of 
CPU/Memory of instance is not updating Account/Domain resources usage

 ScaleVm - resource limit and count logic missing
 

 Key: CLOUDSTACK-2669
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2669
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Nitin Mehta



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2652) marvin.setup fails with TypeError: 'dict' object is not callable

[Prasanna Santhanam (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666178#comment-13666178
 ] 

Prasanna Santhanam commented on CLOUDSTACK-2652:


Are you perhaps facing the issue described here?
http://love-python.blogspot.in/2013/03/dict-object-is-not-callable-on-json.html

 marvin.setup fails with TypeError: 'dict' object is not callable
 

 Key: CLOUDSTACK-2652
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2652
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Test Tools
Reporter: Brian Muita
Priority: Minor

 $ mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/advanced.cfg -pl 
 :cloud-marvin integration-test
 [INFO] Scanning for projects...
 [INFO]
  
 [INFO] 
 
 [INFO] Building Apache CloudStack marvin 4.2.0-SNAPSHOT
 [INFO] 
 
 [INFO] 
 [INFO] --- gmaven-plugin:1.5:execute (setproperty) @ cloud-marvin ---
 [INFO] 
 [INFO] --- exec-maven-plugin:1.2.1:exec (generate-sources) @ cloud-marvin ---
 [INFO] 
 [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-marvin 
 ---
 [INFO] 
 [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ 
 cloud-marvin ---
 [INFO] 
 [INFO] --- exec-maven-plugin:1.2.1:exec (pre-integration-test) @ cloud-marvin 
 ---
 Traceback (most recent call last):
   File deployAndRun.py, line 47, in module
 deploy.deploy()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 472, in deploy
 self.loadCfg()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 423, in loadCfg
 apiKey, securityKey = self.registerApiKey()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 362, in registerApiKey
 listuserRes = self.testClient.getApiClient().listUsers(listuser)
   File 
 /workspace/cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 464, in listUsers
 response = self.connection.marvin_request(command, 
 response_type=response, method=method)
   File /workspace/cloudstack/tools/marvin/marvin/cloudstackConnection.py, 
 line 222, in marvin_request
 response = jsonHelper.getResultObj(response.json(), response_type)
 TypeError: 'dict' object is not callable
 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 7.470s
 [INFO] Finished at: Thu May 23 16:23:45 EAT 2013
 [INFO] Final Memory: 23M/81M
 [INFO] 
 
 [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
 (pre-integration-test) on project cloud-marvin: Command execution failed. 
 Process exited with an error: 1 (Exit value: 1) - [Help 1]
 [ERROR] 
 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
 switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR] 
 [ERROR] For more information about the errors and possible solutions, please 
 read the following articles:
 [ERROR] [Help 1] 
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-2652) marvin.setup fails with TypeError: 'dict' object is not callable

[Prasanna Santhanam (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanna Santhanam reassigned CLOUDSTACK-2652:
--

Assignee: Prasanna Santhanam

 marvin.setup fails with TypeError: 'dict' object is not callable
 

 Key: CLOUDSTACK-2652
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2652
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Test Tools
Reporter: Brian Muita
Assignee: Prasanna Santhanam
Priority: Minor

 $ mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/advanced.cfg -pl 
 :cloud-marvin integration-test
 [INFO] Scanning for projects...
 [INFO]
  
 [INFO] 
 
 [INFO] Building Apache CloudStack marvin 4.2.0-SNAPSHOT
 [INFO] 
 
 [INFO] 
 [INFO] --- gmaven-plugin:1.5:execute (setproperty) @ cloud-marvin ---
 [INFO] 
 [INFO] --- exec-maven-plugin:1.2.1:exec (generate-sources) @ cloud-marvin ---
 [INFO] 
 [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-marvin 
 ---
 [INFO] 
 [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ 
 cloud-marvin ---
 [INFO] 
 [INFO] --- exec-maven-plugin:1.2.1:exec (pre-integration-test) @ cloud-marvin 
 ---
 Traceback (most recent call last):
   File deployAndRun.py, line 47, in module
 deploy.deploy()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 472, in deploy
 self.loadCfg()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 423, in loadCfg
 apiKey, securityKey = self.registerApiKey()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 362, in registerApiKey
 listuserRes = self.testClient.getApiClient().listUsers(listuser)
   File 
 /workspace/cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 464, in listUsers
 response = self.connection.marvin_request(command, 
 response_type=response, method=method)
   File /workspace/cloudstack/tools/marvin/marvin/cloudstackConnection.py, 
 line 222, in marvin_request
 response = jsonHelper.getResultObj(response.json(), response_type)
 TypeError: 'dict' object is not callable
 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 7.470s
 [INFO] Finished at: Thu May 23 16:23:45 EAT 2013
 [INFO] Final Memory: 23M/81M
 [INFO] 
 
 [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
 (pre-integration-test) on project cloud-marvin: Command execution failed. 
 Process exited with an error: 1 (Exit value: 1) - [Help 1]
 [ERROR] 
 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
 switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR] 
 [ERROR] For more information about the errors and possible solutions, please 
 read the following articles:
 [ERROR] [Help 1] 
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2452) Usage:F5:SRX:usage manager failed with db exception due to undefiled field account.default (cloud_usage.account.default field is missing)

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666184#comment-13666184
 ] 

ASF subversion and git services commented on CLOUDSTACK-2452:
-

Commit ba67e5d56ed9e960e947925f82d2dda2204389ce in branch refs/heads/master 
from [~kishan]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ba67e5d ]

CLOUDSTACK-2452: Fixed account upgrade for usage. Added cloumn default. Updated 
usage response for PF , LB and VPN to return UUID instead of Id


 Usage:F5:SRX:usage manager failed with db exception due to undefiled field 
 account.default (cloud_usage.account.default field is missing)
 ---

 Key: CLOUDSTACK-2452
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2452
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Usage
Affects Versions: 4.2.0
Reporter: sadhu suresh
Priority: Critical

 Noticed usage manager failed with runtime exception: a undefined filed  
 account.default  exits in the request sql query by the usage manager , due 
 to this usage statistics job fail  with 
 i.e  account.default field is missing in the cloud_usage.account table.
 1.install the usage server
 2.configure the usage serve to query the usage statistics for every 10 min
 3.configure the lb and generate the load form VM 
 4.observe the usage statistics.
 actual results:
 usage job failed with runtime exception
 013-05-13 10:45:09,191 ERROR [cloud.usage.UsageManagerImpl] 
 (Usage-Job-1:null) Exception in usage manager
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@5508e44d: SELECT account.id, 
 account.account_name, account.type, account.domain_id, account.state, 
 account.removed, account.cleanup_needed, account.network_domain, 
 account.uuid, account.default_zone_id, account.default FROM account WHERE 
 account.id = 2
 at com.cloud.utils.db.GenericDaoBase.findById(GenericDaoBase.java:979)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.CGLIB$findById$35(generated)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195_FastClassByCloudStack_e3754c48.invoke(generated)
 at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.findById(generated)
 at 
 com.cloud.utils.db.GenericDaoBase.findByIdIncludingRemoved(GenericDaoBase.java:939)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.CGLIB$findByIdIncludingRemoved$36(generated)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195_FastClassByCloudStack_e3754c48.invoke(generated)
 at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.findByIdIncludingRemoved(generated)
 at 
 com.cloud.usage.UsageManagerImpl.createVolumeHelperEvent(UsageManagerImpl.java:1075)
 at 
 com.cloud.usage.UsageManagerImpl.createHelperRecord(UsageManagerImpl.java:764)
 at com.cloud.usage.UsageManagerImpl.parse(UsageManagerImpl.java:509)
 at com.cloud.usage.UsageManagerImpl.run(UsageManagerImpl.java:323)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at 
 java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:679)
 Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown 
 column 'account.default' in 'field list'
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
 Method)
 at 
 

[jira] [Commented] (CLOUDSTACK-2669) ScaleVm - resource limit and count logic missing

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666185#comment-13666185
 ] 

ASF subversion and git services commented on CLOUDSTACK-2669:
-

Commit 23baacba62e6169aeeaeabb3441b393ee5491851 in branch refs/heads/master 
from [~nitinme]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=23baacb ]

CLOUDSTACK-2669 - Adding resource limit and count logic for scale vm


 ScaleVm - resource limit and count logic missing
 

 Key: CLOUDSTACK-2669
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2669
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Nitin Mehta



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster

[Sanjeev N (JIRA)]

Sanjeev N created CLOUDSTACK-2670:
-

 Summary: [Object_Store_Refactor] UI/API: migrate volume does not 
show the available primary storages within the cluster
 Key: CLOUDSTACK-2670
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: API
Affects Versions: 4.2.0
 Environment: Latest build from object store branch: 
CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
Reporter: Sanjeev N
 Fix For: 4.2.0


Migrate volume does not show the available primary storages within the cluster

Steps to reproduce:

1.Bring up CS with xen cluster
2.Deploy guest vm
3.Add another primary storage to in the cluster
4.Stop the vm and try to migrate the root disk to another available primary 
storage in the cluster

Result:
==
migrate volume called findStoragePoolsFroMigration but the API returned blank 
response:
http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigrationid=1a4eb56e-4050-4688-b5d7-d721ce4439a2response=jsonsessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D_=1369391000834

{ findstoragepoolsformigrationresponse : { } }

So migrate volume page displays blank in storage pool drop down list in UI.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster

[Sanjeev N (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666191#comment-13666191
 ] 

Sanjeev N commented on CLOUDSTACK-2670:
---

mysql select * from storage_pool\G;
*** 1. row ***
   id: 1
 name: pri_xen_os
 uuid: c65a038a-750c-3b4f-bf26-7ce3b74e1c85
pool_type: NetworkFilesystem
 port: 2049
   data_center_id: 1
   pod_id: 1
   cluster_id: 1
  available_bytes: 2815279431680
   capacity_bytes: 5902284816384
 host_address: 10.147.28.7
user_info: NULL
 path: /export/home/sanjeev/pri_xen_os
  created: 2013-05-24 12:09:14
  removed: NULL
  update_time: NULL
   status: Up
storage_provider_name: DefaultPrimary
scope: CLUSTER
*** 2. row ***
   id: 2
 name: pri_xen_os2
 uuid: 05820c30-2a0e-33f7-b358-cc9c08864e10
pool_type: NetworkFilesystem
 port: 2049
   data_center_id: 1
   pod_id: 1
   cluster_id: 1
  available_bytes: 2776974163968
   capacity_bytes: 5902284816384
 host_address: 10.147.28.7
user_info: NULL
 path: /export/home/sanjeev/pri_xen_os2
  created: 2013-05-24 15:36:43
  removed: NULL
  update_time: NULL
   status: Up
storage_provider_name: DefaultPrimary
scope: CLUSTER
2 rows in set (0.00 sec)

ERROR:
No query specified


 [Object_Store_Refactor] UI/API: migrate volume does not show the available 
 primary storages within the cluster
 --

 Key: CLOUDSTACK-2670
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: Latest build from object store branch: 
 CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
Reporter: Sanjeev N
 Fix For: 4.2.0


 Migrate volume does not show the available primary storages within the cluster
 Steps to reproduce:
 
 1.Bring up CS with xen cluster
 2.Deploy guest vm
 3.Add another primary storage to in the cluster
 4.Stop the vm and try to migrate the root disk to another available primary 
 storage in the cluster
 Result:
 ==
 migrate volume called findStoragePoolsFroMigration but the API returned blank 
 response:
 http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigrationid=1a4eb56e-4050-4688-b5d7-d721ce4439a2response=jsonsessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D_=1369391000834
 { findstoragepoolsformigrationresponse : { } }
 So migrate volume page displays blank in storage pool drop down list in UI.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-2452) Usage:F5:SRX:usage manager failed with db exception due to undefiled field account.default (cloud_usage.account.default field is missing)

[Kishan Kavala (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kishan Kavala reassigned CLOUDSTACK-2452:
-

Assignee: Kishan Kavala

 Usage:F5:SRX:usage manager failed with db exception due to undefiled field 
 account.default (cloud_usage.account.default field is missing)
 ---

 Key: CLOUDSTACK-2452
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2452
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Usage
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Kishan Kavala
Priority: Critical

 Noticed usage manager failed with runtime exception: a undefined filed  
 account.default  exits in the request sql query by the usage manager , due 
 to this usage statistics job fail  with 
 i.e  account.default field is missing in the cloud_usage.account table.
 1.install the usage server
 2.configure the usage serve to query the usage statistics for every 10 min
 3.configure the lb and generate the load form VM 
 4.observe the usage statistics.
 actual results:
 usage job failed with runtime exception
 013-05-13 10:45:09,191 ERROR [cloud.usage.UsageManagerImpl] 
 (Usage-Job-1:null) Exception in usage manager
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@5508e44d: SELECT account.id, 
 account.account_name, account.type, account.domain_id, account.state, 
 account.removed, account.cleanup_needed, account.network_domain, 
 account.uuid, account.default_zone_id, account.default FROM account WHERE 
 account.id = 2
 at com.cloud.utils.db.GenericDaoBase.findById(GenericDaoBase.java:979)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.CGLIB$findById$35(generated)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195_FastClassByCloudStack_e3754c48.invoke(generated)
 at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.findById(generated)
 at 
 com.cloud.utils.db.GenericDaoBase.findByIdIncludingRemoved(GenericDaoBase.java:939)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.CGLIB$findByIdIncludingRemoved$36(generated)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195_FastClassByCloudStack_e3754c48.invoke(generated)
 at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.findByIdIncludingRemoved(generated)
 at 
 com.cloud.usage.UsageManagerImpl.createVolumeHelperEvent(UsageManagerImpl.java:1075)
 at 
 com.cloud.usage.UsageManagerImpl.createHelperRecord(UsageManagerImpl.java:764)
 at com.cloud.usage.UsageManagerImpl.parse(UsageManagerImpl.java:509)
 at com.cloud.usage.UsageManagerImpl.run(UsageManagerImpl.java:323)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at 
 java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:679)
 Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown 
 column 'account.default' in 'field list'
 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:532)
 at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
 at com.mysql.jdbc.Util.getInstance(Util.java:386)

[jira] [Resolved] (CLOUDSTACK-2452) Usage:F5:SRX:usage manager failed with db exception due to undefiled field account.default (cloud_usage.account.default field is missing)

[Kishan Kavala (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kishan Kavala resolved CLOUDSTACK-2452.
---

Resolution: Fixed

 Usage:F5:SRX:usage manager failed with db exception due to undefiled field 
 account.default (cloud_usage.account.default field is missing)
 ---

 Key: CLOUDSTACK-2452
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2452
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Usage
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Kishan Kavala
Priority: Critical

 Noticed usage manager failed with runtime exception: a undefined filed  
 account.default  exits in the request sql query by the usage manager , due 
 to this usage statistics job fail  with 
 i.e  account.default field is missing in the cloud_usage.account table.
 1.install the usage server
 2.configure the usage serve to query the usage statistics for every 10 min
 3.configure the lb and generate the load form VM 
 4.observe the usage statistics.
 actual results:
 usage job failed with runtime exception
 013-05-13 10:45:09,191 ERROR [cloud.usage.UsageManagerImpl] 
 (Usage-Job-1:null) Exception in usage manager
 com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
 com.mysql.jdbc.JDBC4PreparedStatement@5508e44d: SELECT account.id, 
 account.account_name, account.type, account.domain_id, account.state, 
 account.removed, account.cleanup_needed, account.network_domain, 
 account.uuid, account.default_zone_id, account.default FROM account WHERE 
 account.id = 2
 at com.cloud.utils.db.GenericDaoBase.findById(GenericDaoBase.java:979)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.CGLIB$findById$35(generated)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195_FastClassByCloudStack_e3754c48.invoke(generated)
 at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.findById(generated)
 at 
 com.cloud.utils.db.GenericDaoBase.findByIdIncludingRemoved(GenericDaoBase.java:939)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.CGLIB$findByIdIncludingRemoved$36(generated)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195_FastClassByCloudStack_e3754c48.invoke(generated)
 at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.user.dao.AccountDaoImpl_EnhancerByCloudStack_c97e9195.findByIdIncludingRemoved(generated)
 at 
 com.cloud.usage.UsageManagerImpl.createVolumeHelperEvent(UsageManagerImpl.java:1075)
 at 
 com.cloud.usage.UsageManagerImpl.createHelperRecord(UsageManagerImpl.java:764)
 at com.cloud.usage.UsageManagerImpl.parse(UsageManagerImpl.java:509)
 at com.cloud.usage.UsageManagerImpl.run(UsageManagerImpl.java:323)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at 
 java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:679)
 Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown 
 column 'account.default' in 'field list'
 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:532)
 at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
 at com.mysql.jdbc.Util.getInstance(Util.java:386)
 at 

[jira] [Resolved] (CLOUDSTACK-2298) Dynamic scaleup of CPU/Memory of instance is not updating Accout/Domain resources usage

[Nitin Mehta (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Mehta resolved CLOUDSTACK-2298.
-

Resolution: Fixed
  Assignee: Nitin Mehta

 Dynamic scaleup of CPU/Memory of instance is not updating Accout/Domain 
 resources usage
 ---

 Key: CLOUDSTACK-2298
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2298
 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: Sailaja Mada
Assignee: Nitin Mehta
 Fix For: 4.2.0


 Setup:  Advanced Networking Zone, Xen 6.1 , MS- RHEL 6.3
 Steps:
 1. Deploy  instance as ROOT admin with 2 GB memory offering
 2. Scaleup the VM to 6000 MB offering
 3. Verify the resources usage of account after scale up
 Observation:
 Dynamic scaleup of CPU/Memory of instance is not updating Accout/Domain 
 resources usage
 1) Resources usage before scaleup:
 cpulimitUnlimited/cpulimitcputotal2/cputotalcpuavailableUnlimited/cpuavailablememorylimitUnlimited/memorylimitmemorytotal2048/memorytotalmemoryavailableUnlimited/memoryavailable
 2) Resources usahe after scaleup
 cpulimitUnlimited/cpulimitcputotal2/cputotalcpuavailableUnlimited/cpuavailablememorylimitUnlimited/memorylimitmemorytotal2048/memorytotalmemoryavailableUnlimited/memoryavailable

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-2567) NPE when scaling of VM on unsupported hypervisor

[Nitin Mehta (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitin Mehta resolved CLOUDSTACK-2567.
-

Resolution: Fixed

 NPE when scaling of VM on unsupported hypervisor
 

 Key: CLOUDSTACK-2567
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2567
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server, XenServer
Affects Versions: 4.2.0
Reporter: Prasanna Santhanam
Assignee: Nitin Mehta
Priority: Critical
 Fix For: 4.2.0


 When running the scaleVM test on xen 6.0.2 server which doesn't have dynamic 
 memory control enabled following NullPointerException is observed:
 http://jenkins.buildacloud.org/job/test-smoke-matrix/suite=test_scale_vm/277/testReport/integration.smoke.test_scale_vm/TestScaleVm/test_01_scale_vm/
 Error Message
 Check service offering of the VM
   begin captured logging  
 testclient.testcase.TestScaleVm: DEBUG: Scaling VM-ID: 
 8d58d33d-0732-494e-ae69-e807d62d92c8 to service offering: 
 a06578e2-28e9-47a8-9a42-74f60650aa5a
 -  end captured logging  -
 Stacktrace
   File /usr/local/lib/python2.7/unittest/case.py, line 318, in run
 testMethod()
   File 
 /var/lib/jenkins/workspace/test-smoke-matrix/suite/test_scale_vm/test/integration/smoke/test_scale_vm.py,
  line 213, in test_01_scale_vm
 Check service offering of the VM
   File /usr/local/lib/python2.7/unittest/case.py, line 494, in assertEqual
 assertion_func(first, second, msg=msg)
   File /usr/local/lib/python2.7/unittest/case.py, line 902, in 
 assertMultiLineEqual
 self.fail(self._formatMessage(msg, standardMsg))
   File /usr/local/lib/python2.7/unittest/case.py, line 393, in fail
 raise self.failureException(msg)
 Check service offering of the VM
   begin captured logging  
 testclient.testcase.TestScaleVm: DEBUG: Scaling VM-ID: 
 8d58d33d-0732-494e-ae69-e807d62d92c8 to service offering: 
 a06578e2-28e9-47a8-9a42-74f60650aa5a
 -  end captured logging  -
 2013-05-18 15:28:37,451 ERROR [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-38:job-38) Unexpected exception while executing 
 org.apache.cloudstack.api.command.user.vm.ScaleVMCmd
 java.lang.NullPointerException
 at 
 com.cloud.vm.VirtualMachineManagerImpl.upgradeVmDb(VirtualMachineManagerImpl.java:2776)
 at 
 com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1154)
 at 
 com.cloud.vm.UserVmManagerImpl.upgradeVirtualMachine(UserVmManagerImpl.java:1084)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 org.apache.cloudstack.api.command.user.vm.ScaleVMCmd.execute(ScaleVMCmd.java:92)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
 at 
 com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Reopened] (CLOUDSTACK-2593) Object_Store_Refactor - Not able to migrate volumes between primary storages with in the same cluster.

[Sanjeev N (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjeev N reopened CLOUDSTACK-2593:
---


Verified on latest build from object_store branch and observer following 
exception while migrating volume:

API Fired:
http://10.147.59.119:8096/client/api?command=migrateVolumestorageid=05820c30-2a0e-33f7-b358-cc9c08864e10volumeid=1a4eb56e-4050-4688-b5d7-d721ce4439a2

Response:

2013-05-24 12:20:22,001 DEBUG [cloud.async.AsyncJobManagerImpl] 
(ApiServer-2:null) submit async job-25, details: AsyncJobVO {id:25, userId: 1, 
accountId: 1, sessionKey: null, instanceType: None, instanceId: null, cmd: 
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd, cmdOriginator: 
null, cmdInfo: 
{ctxUserId:1,storageid:05820c30-2a0e-33f7-b358-cc9c08864e10,httpmethod:GET,volumeid:1a4eb56e-4050-4688-b5d7-d721ce4439a2,ctxAccountId:1,ctxStartEventId:90},
 cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
processStatus: 0, resultCode: 0, result: null, initMsid: 7332683579487, 
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-05-24 12:20:22,009 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-25:job-25) Executing 
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd for job-25
2013-05-24 12:20:22,039 ERROR [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-25:job-25) Unexpected exception while executing 
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd
com.cloud.exception.InvalidParameterValueException: Volume needs to be detached 
from VM
at 
com.cloud.storage.VolumeManagerImpl.migrateVolume(VolumeManagerImpl.java:2062)
at 
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at 
org.apache.cloudstack.api.command.user.volume.MigrateVolumeCmd.execute(MigrateVolumeCmd.java:103)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at 
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-05-24 12:20:22,040 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-25:job-25) Complete async job-25, jobStatus: 2, resultCode: 530, 
result: Error Code: 530 Error text: Volume needs to be detached from VM
^C

volume id being passed to the API is root volume id.
Looks like migrate volume cmd expecting the VM ID to be set to detached for 
migrating the volume. But in case of root volume it will always be the VM ID. 
Only in case data disk volumes VM ID will be set to detached if the volume is 
detached from the VM.

mysql select * from storage_pool\G;
*** 1. row ***
   id: 1
 name: pri_xen_os
 uuid: c65a038a-750c-3b4f-bf26-7ce3b74e1c85
pool_type: NetworkFilesystem
 port: 2049
   data_center_id: 1
   pod_id: 1
   cluster_id: 1
  available_bytes: 2815279431680
   capacity_bytes: 5902284816384
 host_address: 10.147.28.7
user_info: NULL
 path: /export/home/sanjeev/pri_xen_os
  created: 2013-05-24 12:09:14
  removed: NULL
  update_time: NULL
   status: Up
storage_provider_name: DefaultPrimary
scope: CLUSTER
*** 2. row ***
   id: 2
 name: pri_xen_os2
 uuid: 05820c30-2a0e-33f7-b358-cc9c08864e10
pool_type: NetworkFilesystem
 port: 2049
   data_center_id: 1
   pod_id: 1
   cluster_id: 1
  available_bytes: 2776974163968
   capacity_bytes: 5902284816384
 host_address: 10.147.28.7
user_info: NULL
 path: /export/home/sanjeev/pri_xen_os2
  created: 2013-05-24 15:36:43
  removed: NULL
  update_time: NULL
   status: Up
storage_provider_name: DefaultPrimary
scope: CLUSTER
2 rows in set (0.00 sec)

ERROR:
No query specified



 Object_Store_Refactor - Not able to migrate volumes between primary storages 
 with in the same cluster.
 --

 Key: CLOUDSTACK-2593
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2593
  

[jira] [Commented] (CLOUDSTACK-2327) cloudstack-setup-agent does not properly detect openvswitch and fails if the brcompat driver is not loaded

[Hiroaki Kawai (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666206#comment-13666206
 ] 

Hiroaki Kawai commented on CLOUDSTACK-2327:
---

I'm creating a patch for this now. I'll put it on reviewboard after some more 
test locally.

brcompat is obsolete now, and is already dropped in release openvswitch 1.10.0, 
so I'd rather use ovs-vsctl.

 cloudstack-setup-agent does not properly detect openvswitch and fails if the 
 brcompat driver is not loaded
 --

 Key: CLOUDSTACK-2327
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2327
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM
Affects Versions: 4.1.0
Reporter: Hugo Trippaers
Assignee: Hugo Trippaers

 isBridge fails in the networking configuration is brcompat is not loaded. 
 Cloudstack-setup-agent should have a parameter that specifies if you want to 
 use traditional bridge or openvswitch

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2652) marvin.setup fails with TypeError: 'dict' object is not callable

[Brian Muita (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666230#comment-13666230
 ] 

Brian Muita commented on CLOUDSTACK-2652:
-

Yes, changing response.json() to response.json fixed this for me.

 marvin.setup fails with TypeError: 'dict' object is not callable
 

 Key: CLOUDSTACK-2652
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2652
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Test Tools
Reporter: Brian Muita
Assignee: Prasanna Santhanam
Priority: Minor

 $ mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/advanced.cfg -pl 
 :cloud-marvin integration-test
 [INFO] Scanning for projects...
 [INFO]
  
 [INFO] 
 
 [INFO] Building Apache CloudStack marvin 4.2.0-SNAPSHOT
 [INFO] 
 
 [INFO] 
 [INFO] --- gmaven-plugin:1.5:execute (setproperty) @ cloud-marvin ---
 [INFO] 
 [INFO] --- exec-maven-plugin:1.2.1:exec (generate-sources) @ cloud-marvin ---
 [INFO] 
 [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-marvin 
 ---
 [INFO] 
 [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ 
 cloud-marvin ---
 [INFO] 
 [INFO] --- exec-maven-plugin:1.2.1:exec (pre-integration-test) @ cloud-marvin 
 ---
 Traceback (most recent call last):
   File deployAndRun.py, line 47, in module
 deploy.deploy()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 472, in deploy
 self.loadCfg()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 423, in loadCfg
 apiKey, securityKey = self.registerApiKey()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 362, in registerApiKey
 listuserRes = self.testClient.getApiClient().listUsers(listuser)
   File 
 /workspace/cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 464, in listUsers
 response = self.connection.marvin_request(command, 
 response_type=response, method=method)
   File /workspace/cloudstack/tools/marvin/marvin/cloudstackConnection.py, 
 line 222, in marvin_request
 response = jsonHelper.getResultObj(response.json(), response_type)
 TypeError: 'dict' object is not callable
 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 7.470s
 [INFO] Finished at: Thu May 23 16:23:45 EAT 2013
 [INFO] Final Memory: 23M/81M
 [INFO] 
 
 [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
 (pre-integration-test) on project cloud-marvin: Command execution failed. 
 Process exited with an error: 1 (Exit value: 1) - [Help 1]
 [ERROR] 
 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
 switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR] 
 [ERROR] For more information about the errors and possible solutions, please 
 read the following articles:
 [ERROR] [Help 1] 
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2671) [VPC] [VMware] VPC router is failing configure vpc_privateGateway.sh

[venkata swamybabu budumuru (JIRA)]

venkata swamybabu budumuru created CLOUDSTACK-2671:
--

 Summary: [VPC] [VMware] VPC router is failing configure 
vpc_privateGateway.sh
 Key: CLOUDSTACK-2671
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2671
 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
 Environment: commit # 80a3c0535e0a8ad3edba3713a61d063a176191d8
Reporter: venkata swamybabu budumuru
Assignee: Jayapal Reddy
 Fix For: 4.2.0


Steps to reproduce :

1. Have a VMware cluster with ESX 5.1
2. Login as a non-ROOT domain user and try to create VPC

Observations:

(i) Router came up fine but, it failed to configure source nat ip on the router.

Here is the snippet of mgmt server log related to the issue.

2013-05-24 12:22:05,079 ERROR [utils.ssh.SshHelper] 
(DirectAgent-123:10.147.40.12) SSH execution of command 
/opt/cloud/bin/vpc_privateGateway.sh  -A  -l 10.147.44.64 -c eth1 -g 
10.147.44.1 -m 24 -n 10.147.44.0 has an error status code in return. result 
output: /opt/cloud/bin/vpc_privateGateway.sh: illegal option -- g
Usage:
 vpc_privateGateway.sh -A -l public-ip-address
 vpc_privateGateway.sh -D -l public-ip-address

2013-05-24 12:22:05,083 ERROR [vmware.resource.VmwareResource] 
(DirectAgent-123:10.147.40.12) Ip Assoc failure on applying one ip due to 
exception:
com.cloud.exception.InternalErrorException: Unable to configure source NAT for 
public IP address.
at 
com.cloud.hypervisor.vmware.resource.VmwareResource.assignVPCPublicIpAddress(VmwareResource.java:1533)
at 
com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:)
at 
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:474)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-05-24 12:22:05,086 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-123:null) Seq 1-1894842467: Cancelling because one of the answers 
is false and it is stop on error.

Attaching all the required logs along with db dump to the bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-2671) [VPC] [VMware] VPC router is failing configure vpc_privateGateway.sh

[venkata swamybabu budumuru (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

venkata swamybabu budumuru updated CLOUDSTACK-2671:
---

Attachment: logs.tgz

 [VPC] [VMware] VPC router is failing configure vpc_privateGateway.sh
 

 Key: CLOUDSTACK-2671
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2671
 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
 Environment: commit # 80a3c0535e0a8ad3edba3713a61d063a176191d8
Reporter: venkata swamybabu budumuru
Assignee: Jayapal Reddy
 Fix For: 4.2.0

 Attachments: logs.tgz


 Steps to reproduce :
 1. Have a VMware cluster with ESX 5.1
 2. Login as a non-ROOT domain user and try to create VPC
 Observations:
 (i) Router came up fine but, it failed to configure source nat ip on the 
 router.
 Here is the snippet of mgmt server log related to the issue.
 2013-05-24 12:22:05,079 ERROR [utils.ssh.SshHelper] 
 (DirectAgent-123:10.147.40.12) SSH execution of command 
 /opt/cloud/bin/vpc_privateGateway.sh  -A  -l 10.147.44.64 -c eth1 -g 
 10.147.44.1 -m 24 -n 10.147.44.0 has an error status code in return. result 
 output: /opt/cloud/bin/vpc_privateGateway.sh: illegal option -- g
 Usage:
  vpc_privateGateway.sh -A -l public-ip-address
  vpc_privateGateway.sh -D -l public-ip-address
 2013-05-24 12:22:05,083 ERROR [vmware.resource.VmwareResource] 
 (DirectAgent-123:10.147.40.12) Ip Assoc failure on applying one ip due to 
 exception:
 com.cloud.exception.InternalErrorException: Unable to configure source NAT 
 for public IP address.
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.assignVPCPublicIpAddress(VmwareResource.java:1533)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:474)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:679)
 2013-05-24 12:22:05,086 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-123:null) Seq 1-1894842467: Cancelling because one of the 
 answers is false and it is stop on error.
 Attaching all the required logs along with db dump to the bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2652) marvin.setup fails with TypeError: 'dict' object is not callable

[Brian Muita (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666243#comment-13666243
 ] 

Brian Muita commented on CLOUDSTACK-2652:
-

Ok my mistake. Was on 2.6. All sorted with 2.7...

 marvin.setup fails with TypeError: 'dict' object is not callable
 

 Key: CLOUDSTACK-2652
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2652
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Test Tools
Reporter: Brian Muita
Assignee: Prasanna Santhanam
Priority: Minor

 $ mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/advanced.cfg -pl 
 :cloud-marvin integration-test
 [INFO] Scanning for projects...
 [INFO]
  
 [INFO] 
 
 [INFO] Building Apache CloudStack marvin 4.2.0-SNAPSHOT
 [INFO] 
 
 [INFO] 
 [INFO] --- gmaven-plugin:1.5:execute (setproperty) @ cloud-marvin ---
 [INFO] 
 [INFO] --- exec-maven-plugin:1.2.1:exec (generate-sources) @ cloud-marvin ---
 [INFO] 
 [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-marvin 
 ---
 [INFO] 
 [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ 
 cloud-marvin ---
 [INFO] 
 [INFO] --- exec-maven-plugin:1.2.1:exec (pre-integration-test) @ cloud-marvin 
 ---
 Traceback (most recent call last):
   File deployAndRun.py, line 47, in module
 deploy.deploy()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 472, in deploy
 self.loadCfg()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 423, in loadCfg
 apiKey, securityKey = self.registerApiKey()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 362, in registerApiKey
 listuserRes = self.testClient.getApiClient().listUsers(listuser)
   File 
 /workspace/cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 464, in listUsers
 response = self.connection.marvin_request(command, 
 response_type=response, method=method)
   File /workspace/cloudstack/tools/marvin/marvin/cloudstackConnection.py, 
 line 222, in marvin_request
 response = jsonHelper.getResultObj(response.json(), response_type)
 TypeError: 'dict' object is not callable
 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 7.470s
 [INFO] Finished at: Thu May 23 16:23:45 EAT 2013
 [INFO] Final Memory: 23M/81M
 [INFO] 
 
 [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
 (pre-integration-test) on project cloud-marvin: Command execution failed. 
 Process exited with an error: 1 (Exit value: 1) - [Help 1]
 [ERROR] 
 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
 switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR] 
 [ERROR] For more information about the errors and possible solutions, please 
 read the following articles:
 [ERROR] [Help 1] 
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2672) Adding isVolatile parameter in service offering response object

[Harikrishna Patnala (JIRA)]

Harikrishna Patnala created CLOUDSTACK-2672:
---

 Summary: Adding isVolatile parameter in service offering response 
object
 Key: CLOUDSTACK-2672
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2672
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: API
Affects Versions: 4.2.0
Reporter: Harikrishna Patnala
Assignee: Harikrishna Patnala
Priority: Minor
 Fix For: 4.2.0


Missing isVolatile parameter in the response of service offering.
Need to add this in service offering response object.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2673) [Object_Store_Refactor] Failed to deploy guest vm using ISO with S3 being the storage provider

[Sanjeev N (JIRA)]

Sanjeev N created CLOUDSTACK-2673:
-

 Summary: [Object_Store_Refactor] Failed to deploy guest vm using 
ISO with S3 being the storage provider
 Key: CLOUDSTACK-2673
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2673
 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
 Environment: Latest build from object_store branch
Reporter: Sanjeev N
Priority: Blocker
 Fix For: 4.2.0


Failed to deploy guest vm using ISO with S3 being the storage provider

Steps to Reproduce:
=
1.Bring up CS in advanced zone with S3 as the secondary storage provider
2.Wait for the SSVM to come up
3.Register ISO to CS
4.Try to deploy guest vm using the registered ISO

Result:
==
Looks like CS is trying to mount the S3 URI after creating vhd and is failing:

2013-05-24 13:27:58,682 DEBUG [agent.transport.Request] 
(Job-Executor-27:job-27) Seq 1-698156160: Sending  { Cmd , MgmtId: 
7332683579487, via: 1, Ver: v1, Flags: 100011, 
[{org.apache.cloudstack.storage.command.CreateObjectCommand:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:82891103-1daf-4118-9fc8-10296e486d7c,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:c65a038a-750c-3b4f-bf26-7ce3b74e1c85,id:1,poolType:NetworkFilesystem,host:10.147.28.7,path:/export/home/sanjeev/pri_xen_os,port:2049}},name:ROOT-6,size:21474836480,volumeId:10,vmName:i-2-6-VM,accountId:2,format:VHD,id:10}},wait:0}}]
 }
2013-05-24 13:27:58,683 DEBUG [agent.transport.Request] 
(Job-Executor-27:job-27) Seq 1-698156160: Executing:  { Cmd , MgmtId: 
7332683579487, via: 1, Ver: v1, Flags: 100011, 
[{org.apache.cloudstack.storage.command.CreateObjectCommand:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:82891103-1daf-4118-9fc8-10296e486d7c,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:c65a038a-750c-3b4f-bf26-7ce3b74e1c85,id:1,poolType:NetworkFilesystem,host:10.147.28.7,path:/export/home/sanjeev/pri_xen_os,port:2049}},name:ROOT-6,size:21474836480,volumeId:10,vmName:i-2-6-VM,accountId:2,format:VHD,id:10}},wait:0}}]
 }
2013-05-24 13:27:58,684 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-69:null) Seq 1-698156160: Executing request
2013-05-24 13:27:58,779 DEBUG [xen.resource.CitrixResourceBase] 
(DirectAgent-69:null) SR retrieved for c65a038a-750c-3b4f-bf26-7ce3b74e1c85
2013-05-24 13:27:58,790 DEBUG [xen.resource.CitrixResourceBase] 
(DirectAgent-69:null) Checking c65a038a-750c-3b4f-bf26-7ce3b74e1c85 or SR 
e2e107fc-8b53-25e0-f793-c9d6909b5757 on 
XS[d20696c6-46d5-45b5-83d3-cfc5993bba74-10.147.40.14]
2013-05-24 13:27:59,034 DEBUG [agent.manager.DirectAgentAttache] 
(DirectAgent-69:null) Seq 1-698156160: Response Received:
2013-05-24 13:27:59,035 DEBUG [agent.transport.Request] (DirectAgent-69:null) 
Seq 1-698156160: Processing:  { Ans: , MgmtId: 7332683579487, via: 1, Ver: v1, 
Flags: 10, 
[{org.apache.cloudstack.storage.command.CreateObjectAnswer:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{name:ROOT-6,size:21474836480,path:0a90bd67-1f7d-4297-aebb-3cdc35231d7d,accountId:0,id:0}},result:true,wait:0}}]
 }
2013-05-24 13:27:59,035 DEBUG [agent.transport.Request] 
(Job-Executor-27:job-27) Seq 1-698156160: Received:  { Ans: , MgmtId: 
7332683579487, via: 1, Ver: v1, Flags: 10, { CreateObjectAnswer } }

2013-05-24 13:27:59,132 DEBUG [agent.transport.Request] 
(Job-Executor-27:job-27) Seq 1-698156161: Sending  { Cmd , MgmtId: 
7332683579487, via: 1, Ver: v1, Flags: 100111, 
[{com.cloud.agent.api.StartCommand:{vm:{id:6,name:i-2-6-VM,bootloader:CD,type:User,cpus:1,minSpeed:500,maxSpeed:500,minRam:536870912,maxRam:536870912,arch:x86_64,os:Windows
 8 

[jira] [Resolved] (CLOUDSTACK-1453) support restore for VM created from ISO

[Harikrishna Patnala (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harikrishna Patnala resolved CLOUDSTACK-1453.
-

Resolution: Fixed

 support restore for VM created from ISO
 ---

 Key: CLOUDSTACK-1453
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1453
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.2.0
Reporter: Harikrishna Patnala
Assignee: Harikrishna Patnala
 Fix For: 4.2.0




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2674) [Object_Store_Refactor]Secondary Storage garbage collector failed with NPE in case of S3 storage provider

[Sanjeev N (JIRA)]

Sanjeev N created CLOUDSTACK-2674:
-

 Summary: [Object_Store_Refactor]Secondary Storage garbage 
collector failed with NPE in case of S3 storage provider
 Key: CLOUDSTACK-2674
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2674
 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
 Environment: Latest build from object_store branch
Reporter: Sanjeev N
Priority: Critical
 Fix For: 4.2.0


Secondary Storage garbage collector failed with NPE in case of S3 storage 
provider

Steps to Reproduce:

1.Bring up CS in advanced zone with S3 as the secondary storage provider
2.After SSVM is up and running register ISO to CS
3.When the ISO is in ready state delete the iso
4.Wait for the Storage scavenger thread to run

Observations:

After deleting the ISO , it is marked as destroyed in template_store_ref table 
and also got deleted from S3 object store. But when secondary storage garbage 
collector ran it found 1 template to clean up on secondary storage(Image Store 
not on ImageCache store) since the iso state is in destroyed state and tried to 
clean it up.

Found NPE while trying to clean up from Image store:

013-05-24 14:11:01,976 DEBUG [cloud.storage.StorageManagerImpl] 
(StorageManager-Scavenger-1:null) Storage pool garbage collector found 0 
templates to clean up in storage pool: pri_xen_os
2013-05-24 14:11:01,979 DEBUG [cloud.storage.StorageManagerImpl] 
(StorageManager-Scavenger-1:null) Storage pool garbage collector found 0 
templates to clean up in storage pool: pri_xen_os2
2013-05-24 14:11:01,993 DEBUG [cloud.storage.StorageManagerImpl] 
(StorageManager-Scavenger-1:null) Secondary storage garbage collector found 1 
templates to cleanup on secondary storage host: 
9c5f76a7-507a-4ae1-b411-702e816bbf27
2013-05-24 14:11:01,999 WARN  [cloud.storage.StorageManagerImpl] 
(StorageManager-Scavenger-1:null) problem cleaning up templates in secondary 
storage store 9c5f76a7-507a-4ae1-b411-702e816bbf27
java.lang.NullPointerException
at 
com.cloud.template.TemplateManagerImpl.templateIsDeleteable(TemplateManagerImpl.java:952)
at 
com.cloud.storage.StorageManagerImpl.cleanupSecondaryStorage(StorageManagerImpl.java:1136)
at 
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at 
com.cloud.storage.StorageManagerImpl.cleanupStorage(StorageManagerImpl.java:1049)
at 
com.cloud.storage.StorageManagerImpl$StorageGarbageCollector.run(StorageManagerImpl.java:1354)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at 
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-05-24 14:11:02,004 DEBUG [cloud.storage.StorageManagerImpl] 
(StorageManager-Scavenger-1:null) Secondary storage garbage collector found 0 
volumes to cleanup on secondary storage host: 
9c5f76a7-507a-4ae1-b411-702e816bbf27

mysql select * from image_store\G;
*** 1. row ***
 id: 1
   name: nfs://10.147.28.7/export/home/sanjeev/sec_xen_os
image_provider_name: NFS
   protocol: nfs
url: nfs://10.147.28.7/export/home/sanjeev/sec_xen_os
 data_center_id: 1
  scope: ZONE
   role: ImageCache
   uuid: f521e766-fb84-4aeb-a0ab-83c2ccdfd56a
 parent: NULL
created: 2013-05-24 12:09:21
removed: NULL
 total_size: NULL
*** 2. row ***
 id: 2
   name: 9c5f76a7-507a-4ae1-b411-702e816bbf27
image_provider_name: S3
   protocol: http
url: NULL
 data_center_id: NULL
  scope: REGION
   role: Image
   uuid: 9c5f76a7-507a-4ae1-b411-702e816bbf27
 parent: NULL
created: 2013-05-24 12:09:21
removed: NULL
 total_size: NULL
2 rows in set (0.00 sec)

ERROR:
No query specified

mysql select * from template_store_ref where id=6\G;
*** 1. row 

[jira] [Commented] (CLOUDSTACK-2671) [VPC] [VMware] VPC router is failing configure vpc_privateGateway.sh

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666297#comment-13666297
 ] 

ASF subversion and git services commented on CLOUDSTACK-2671:
-

Commit d8f5f2ea10eca540c10e93469fd5307fe25f0959 in branch refs/heads/master 
from [~jayapal]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d8f5f2e ]

CLOUDSTACK-2671 Updated vpc private gateway scipt args


 [VPC] [VMware] VPC router is failing configure vpc_privateGateway.sh
 

 Key: CLOUDSTACK-2671
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2671
 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
 Environment: commit # 80a3c0535e0a8ad3edba3713a61d063a176191d8
Reporter: venkata swamybabu budumuru
Assignee: Jayapal Reddy
 Fix For: 4.2.0

 Attachments: logs.tgz


 Steps to reproduce :
 1. Have a VMware cluster with ESX 5.1
 2. Login as a non-ROOT domain user and try to create VPC
 Observations:
 (i) Router came up fine but, it failed to configure source nat ip on the 
 router.
 Here is the snippet of mgmt server log related to the issue.
 2013-05-24 12:22:05,079 ERROR [utils.ssh.SshHelper] 
 (DirectAgent-123:10.147.40.12) SSH execution of command 
 /opt/cloud/bin/vpc_privateGateway.sh  -A  -l 10.147.44.64 -c eth1 -g 
 10.147.44.1 -m 24 -n 10.147.44.0 has an error status code in return. result 
 output: /opt/cloud/bin/vpc_privateGateway.sh: illegal option -- g
 Usage:
  vpc_privateGateway.sh -A -l public-ip-address
  vpc_privateGateway.sh -D -l public-ip-address
 2013-05-24 12:22:05,083 ERROR [vmware.resource.VmwareResource] 
 (DirectAgent-123:10.147.40.12) Ip Assoc failure on applying one ip due to 
 exception:
 com.cloud.exception.InternalErrorException: Unable to configure source NAT 
 for public IP address.
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.assignVPCPublicIpAddress(VmwareResource.java:1533)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:474)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:679)
 2013-05-24 12:22:05,086 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-123:null) Seq 1-1894842467: Cancelling because one of the 
 answers is false and it is stop on error.
 Attaching all the required logs along with db dump to the bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2652) marvin.setup fails with TypeError: 'dict' object is not callable

[Prasanna Santhanam (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666299#comment-13666299
 ] 

Prasanna Santhanam commented on CLOUDSTACK-2652:


Thanks for the bug report. Since Marvin is installable on 2.6 as well, I'll try 
to put in a better fix for this issue. It can be confounding at first.

 marvin.setup fails with TypeError: 'dict' object is not callable
 

 Key: CLOUDSTACK-2652
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2652
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Test Tools
Reporter: Brian Muita
Assignee: Prasanna Santhanam
Priority: Minor

 $ mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/advanced.cfg -pl 
 :cloud-marvin integration-test
 [INFO] Scanning for projects...
 [INFO]
  
 [INFO] 
 
 [INFO] Building Apache CloudStack marvin 4.2.0-SNAPSHOT
 [INFO] 
 
 [INFO] 
 [INFO] --- gmaven-plugin:1.5:execute (setproperty) @ cloud-marvin ---
 [INFO] 
 [INFO] --- exec-maven-plugin:1.2.1:exec (generate-sources) @ cloud-marvin ---
 [INFO] 
 [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-marvin 
 ---
 [INFO] 
 [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ 
 cloud-marvin ---
 [INFO] 
 [INFO] --- exec-maven-plugin:1.2.1:exec (pre-integration-test) @ cloud-marvin 
 ---
 Traceback (most recent call last):
   File deployAndRun.py, line 47, in module
 deploy.deploy()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 472, in deploy
 self.loadCfg()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 423, in loadCfg
 apiKey, securityKey = self.registerApiKey()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 362, in registerApiKey
 listuserRes = self.testClient.getApiClient().listUsers(listuser)
   File 
 /workspace/cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 464, in listUsers
 response = self.connection.marvin_request(command, 
 response_type=response, method=method)
   File /workspace/cloudstack/tools/marvin/marvin/cloudstackConnection.py, 
 line 222, in marvin_request
 response = jsonHelper.getResultObj(response.json(), response_type)
 TypeError: 'dict' object is not callable
 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 7.470s
 [INFO] Finished at: Thu May 23 16:23:45 EAT 2013
 [INFO] Final Memory: 23M/81M
 [INFO] 
 
 [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
 (pre-integration-test) on project cloud-marvin: Command execution failed. 
 Process exited with an error: 1 (Exit value: 1) - [Help 1]
 [ERROR] 
 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
 switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR] 
 [ERROR] For more information about the errors and possible solutions, please 
 read the following articles:
 [ERROR] [Help 1] 
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2652) marvin.setup fails with TypeError: 'dict' object is not callable

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666318#comment-13666318
 ] 

ASF subversion and git services commented on CLOUDSTACK-2652:
-

Commit ed2ce2737133de6277bba0be9b7e10d3faaf887d in branch refs/heads/master 
from [~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ed2ce27 ]

CLOUDSTACK-2652: requests module differs on Python 2.6

On 2.6 response.json returns the JSOn in the response while on 2.7
response.json() is a method. Since Marvin installs on both platforms
fixing the error appropriately

Signed-off-by: Prasanna Santhanam t...@apache.org


 marvin.setup fails with TypeError: 'dict' object is not callable
 

 Key: CLOUDSTACK-2652
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2652
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Test Tools
Reporter: Brian Muita
Assignee: Prasanna Santhanam
Priority: Minor

 $ mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/advanced.cfg -pl 
 :cloud-marvin integration-test
 [INFO] Scanning for projects...
 [INFO]
  
 [INFO] 
 
 [INFO] Building Apache CloudStack marvin 4.2.0-SNAPSHOT
 [INFO] 
 
 [INFO] 
 [INFO] --- gmaven-plugin:1.5:execute (setproperty) @ cloud-marvin ---
 [INFO] 
 [INFO] --- exec-maven-plugin:1.2.1:exec (generate-sources) @ cloud-marvin ---
 [INFO] 
 [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-marvin 
 ---
 [INFO] 
 [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ 
 cloud-marvin ---
 [INFO] 
 [INFO] --- exec-maven-plugin:1.2.1:exec (pre-integration-test) @ cloud-marvin 
 ---
 Traceback (most recent call last):
   File deployAndRun.py, line 47, in module
 deploy.deploy()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 472, in deploy
 self.loadCfg()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 423, in loadCfg
 apiKey, securityKey = self.registerApiKey()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 362, in registerApiKey
 listuserRes = self.testClient.getApiClient().listUsers(listuser)
   File 
 /workspace/cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 464, in listUsers
 response = self.connection.marvin_request(command, 
 response_type=response, method=method)
   File /workspace/cloudstack/tools/marvin/marvin/cloudstackConnection.py, 
 line 222, in marvin_request
 response = jsonHelper.getResultObj(response.json(), response_type)
 TypeError: 'dict' object is not callable
 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 7.470s
 [INFO] Finished at: Thu May 23 16:23:45 EAT 2013
 [INFO] Final Memory: 23M/81M
 [INFO] 
 
 [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
 (pre-integration-test) on project cloud-marvin: Command execution failed. 
 Process exited with an error: 1 (Exit value: 1) - [Help 1]
 [ERROR] 
 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
 switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR] 
 [ERROR] For more information about the errors and possible solutions, please 
 read the following articles:
 [ERROR] [Help 1] 
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1191) Implement RBD snapshotting, backups and cloning

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666321#comment-13666321
 ] 

ASF subversion and git services commented on CLOUDSTACK-1191:
-

Commit bef3a2edb7f23035a7d397d2d68caf6cecc0f497 in branch 
refs/heads/rbd-snap-clone from Wido den Hollander w...@widodh.nl
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bef3a2e ]

CLOUDSTACK-1191: rbd: Use cloning for deploying templates instead of a copy

RBD format 2 supports cloning (aka layering) where one base image can serve
as a parent image for multiple child images.

This enables fast deployment of a large amount of virtual machines, but it also
saves spaces on the Ceph cluster and improves performance due to better caching.

Qemu-img doesn't support RBD format 2 (yet), so to enable these functions the
RADOS/RBD Java bindings are required.

This patch also enables deployment of System VMs on RBD storage pools. Since we
no longer require a patchdisk for passing the boot arguments we are able to 
deploy
these VMs on RBD.


 Implement RBD snapshotting, backups and cloning
 ---

 Key: CLOUDSTACK-1191
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1191
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Snapshot, Storage Controller, Volumes
Affects Versions: 4.2.0
Reporter: Wido den Hollander
Assignee: Wido den Hollander
  Labels: ceph, kvm, libvirt, rbd
 Fix For: 4.2.0


 The current RBD implementation lacks these features.
 The new storage subsystem will allow us to implement these features as 
 described on the wiki: 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/RBD+improvements+based+on+new+Storage+subsystem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2652) marvin.setup fails with TypeError: 'dict' object is not callable

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666322#comment-13666322
 ] 

ASF subversion and git services commented on CLOUDSTACK-2652:
-

Commit ed2ce2737133de6277bba0be9b7e10d3faaf887d in branch 
refs/heads/rbd-snap-clone from [~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ed2ce27 ]

CLOUDSTACK-2652: requests module differs on Python 2.6

On 2.6 response.json returns the JSOn in the response while on 2.7
response.json() is a method. Since Marvin installs on both platforms
fixing the error appropriately

Signed-off-by: Prasanna Santhanam t...@apache.org


 marvin.setup fails with TypeError: 'dict' object is not callable
 

 Key: CLOUDSTACK-2652
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2652
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Test Tools
Reporter: Brian Muita
Assignee: Prasanna Santhanam
Priority: Minor

 $ mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/advanced.cfg -pl 
 :cloud-marvin integration-test
 [INFO] Scanning for projects...
 [INFO]
  
 [INFO] 
 
 [INFO] Building Apache CloudStack marvin 4.2.0-SNAPSHOT
 [INFO] 
 
 [INFO] 
 [INFO] --- gmaven-plugin:1.5:execute (setproperty) @ cloud-marvin ---
 [INFO] 
 [INFO] --- exec-maven-plugin:1.2.1:exec (generate-sources) @ cloud-marvin ---
 [INFO] 
 [INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-marvin 
 ---
 [INFO] 
 [INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ 
 cloud-marvin ---
 [INFO] 
 [INFO] --- exec-maven-plugin:1.2.1:exec (pre-integration-test) @ cloud-marvin 
 ---
 Traceback (most recent call last):
   File deployAndRun.py, line 47, in module
 deploy.deploy()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 472, in deploy
 self.loadCfg()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 423, in loadCfg
 apiKey, securityKey = self.registerApiKey()
   File /workspace/cloudstack/tools/marvin/marvin/deployDataCenter.py, line 
 362, in registerApiKey
 listuserRes = self.testClient.getApiClient().listUsers(listuser)
   File 
 /workspace/cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py,
  line 464, in listUsers
 response = self.connection.marvin_request(command, 
 response_type=response, method=method)
   File /workspace/cloudstack/tools/marvin/marvin/cloudstackConnection.py, 
 line 222, in marvin_request
 response = jsonHelper.getResultObj(response.json(), response_type)
 TypeError: 'dict' object is not callable
 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 7.470s
 [INFO] Finished at: Thu May 23 16:23:45 EAT 2013
 [INFO] Final Memory: 23M/81M
 [INFO] 
 
 [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
 (pre-integration-test) on project cloud-marvin: Command execution failed. 
 Process exited with an error: 1 (Exit value: 1) - [Help 1]
 [ERROR] 
 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
 switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR] 
 [ERROR] For more information about the errors and possible solutions, please 
 read the following articles:
 [ERROR] [Help 1] 
 http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2671) [VPC] [VMware] VPC router is failing configure vpc_privateGateway.sh

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666323#comment-13666323
 ] 

ASF subversion and git services commented on CLOUDSTACK-2671:
-

Commit d8f5f2ea10eca540c10e93469fd5307fe25f0959 in branch 
refs/heads/rbd-snap-clone from [~jayapal]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d8f5f2e ]

CLOUDSTACK-2671 Updated vpc private gateway scipt args


 [VPC] [VMware] VPC router is failing configure vpc_privateGateway.sh
 

 Key: CLOUDSTACK-2671
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2671
 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
 Environment: commit # 80a3c0535e0a8ad3edba3713a61d063a176191d8
Reporter: venkata swamybabu budumuru
Assignee: Jayapal Reddy
 Fix For: 4.2.0

 Attachments: logs.tgz


 Steps to reproduce :
 1. Have a VMware cluster with ESX 5.1
 2. Login as a non-ROOT domain user and try to create VPC
 Observations:
 (i) Router came up fine but, it failed to configure source nat ip on the 
 router.
 Here is the snippet of mgmt server log related to the issue.
 2013-05-24 12:22:05,079 ERROR [utils.ssh.SshHelper] 
 (DirectAgent-123:10.147.40.12) SSH execution of command 
 /opt/cloud/bin/vpc_privateGateway.sh  -A  -l 10.147.44.64 -c eth1 -g 
 10.147.44.1 -m 24 -n 10.147.44.0 has an error status code in return. result 
 output: /opt/cloud/bin/vpc_privateGateway.sh: illegal option -- g
 Usage:
  vpc_privateGateway.sh -A -l public-ip-address
  vpc_privateGateway.sh -D -l public-ip-address
 2013-05-24 12:22:05,083 ERROR [vmware.resource.VmwareResource] 
 (DirectAgent-123:10.147.40.12) Ip Assoc failure on applying one ip due to 
 exception:
 com.cloud.exception.InternalErrorException: Unable to configure source NAT 
 for public IP address.
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.assignVPCPublicIpAddress(VmwareResource.java:1533)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:)
 at 
 com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:474)
 at 
 com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:679)
 2013-05-24 12:22:05,086 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-123:null) Seq 1-1894842467: Cancelling because one of the 
 answers is false and it is stop on error.
 Attaching all the required logs along with db dump to the bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1191) Implement RBD snapshotting, backups and cloning

[Wido den Hollander (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666338#comment-13666338
 ] 

Wido den Hollander commented on CLOUDSTACK-1191:


The commits above enable the usage of RBD format 2 and it allows System VMs to 
be deployed on RBD.

Snapshotting and creating backups hasn't been implemented yet.

 Implement RBD snapshotting, backups and cloning
 ---

 Key: CLOUDSTACK-1191
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1191
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Snapshot, Storage Controller, Volumes
Affects Versions: 4.2.0
Reporter: Wido den Hollander
Assignee: Wido den Hollander
  Labels: ceph, kvm, libvirt, rbd
 Fix For: 4.2.0


 The current RBD implementation lacks these features.
 The new storage subsystem will allow us to implement these features as 
 described on the wiki: 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/RBD+improvements+based+on+new+Storage+subsystem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1191) Implement RBD snapshotting, backups and cloning

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666336#comment-13666336
 ] 

ASF subversion and git services commented on CLOUDSTACK-1191:
-

Commit bef3a2edb7f23035a7d397d2d68caf6cecc0f497 in branch refs/heads/master 
from Wido den Hollander w...@widodh.nl
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bef3a2e ]

CLOUDSTACK-1191: rbd: Use cloning for deploying templates instead of a copy

RBD format 2 supports cloning (aka layering) where one base image can serve
as a parent image for multiple child images.

This enables fast deployment of a large amount of virtual machines, but it also
saves spaces on the Ceph cluster and improves performance due to better caching.

Qemu-img doesn't support RBD format 2 (yet), so to enable these functions the
RADOS/RBD Java bindings are required.

This patch also enables deployment of System VMs on RBD storage pools. Since we
no longer require a patchdisk for passing the boot arguments we are able to 
deploy
these VMs on RBD.


 Implement RBD snapshotting, backups and cloning
 ---

 Key: CLOUDSTACK-1191
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1191
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: KVM, Snapshot, Storage Controller, Volumes
Affects Versions: 4.2.0
Reporter: Wido den Hollander
Assignee: Wido den Hollander
  Labels: ceph, kvm, libvirt, rbd
 Fix For: 4.2.0


 The current RBD implementation lacks these features.
 The new storage subsystem will allow us to implement these features as 
 described on the wiki: 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/RBD+improvements+based+on+new+Storage+subsystem

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2675) Missing network_id on restarting/host adding to a new shared network

[Tomasz Zieba (JIRA)]

Tomasz Zieba created CLOUDSTACK-2675:


 Summary: Missing network_id on restarting/host adding to a new 
shared network
 Key: CLOUDSTACK-2675
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2675
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Network Controller
Affects Versions: 4.0.2
 Environment: CloudStack 4.0.2, 
Reporter: Tomasz Zieba


I have got the same situation as follows: 
http://mail-archives.apache.org/mod_mbox/cloudstack-users/201304.mbox/%3c4b77b928-a3c5-4742-8ac3-652af4a7c...@ringplus.net%3E





--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2354) Unable to create Windows VMs using ISO

[Stephen Turner (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666378#comment-13666378
 ] 

Stephen Turner commented on CLOUDSTACK-2354:


I guess I haven't quite understood your workflow. In XenCenter, you are blocked 
from changing the dynamic range until tools are present. But if you alter the 
memory properties of a VM with tools, and then create a template from it, it 
will retain those settings. How are your templates with PV tools created? Can't 
you set the memory properties when you create that template?

 Unable to create Windows VMs using ISO
 --

 Key: CLOUDSTACK-2354
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2354
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: ISO
Affects Versions: 4.2.0
 Environment: Build No.#256 
 (CloudStack-non-OSS-MASTER-256-rhel6.3.tar.gz)
 XenServer6.1 for Host Server, CentOS6.3 for NFS server and CloudStack-Mgr 
 Server.
Reporter: Minying Bao
Assignee: Harikrishna Patnala
Priority: Blocker
 Fix For: 4.2.0

 Attachments: ISO_Win8.jpg, ISO_XP-Auto-Shutdown.JPG.jpg, 
 ISO_XP_State.JPG.jpg, management-server.log


 Repro Steps
 Setup the cloudstack environment as normal. (Configured NFS  CS-Mgr Servers)
 Launch browser, start CloudStack WebConsole and finish to build a cloud step 
 by step. (It should use workaround of build#256 when building a cloud.)
 Register the ISOs to the CloudStack as follows Win7, Win8, 2k8R2, XP. Wait 
 for Status showing Successfully Installed.
 Add instances from all above ISOs.
 Expected Result
 All the instances should be added successfully, and all the related VMs 
 should be launched successfully on XenServer Host.
 Actual Result
 Unable to create Windows VMs using ISO.
 VMs based on the Win8/Win7 ISOs - WebConsole show Error (refer to 
 screenshot ISO_Win8.jpg) 
 VMs based on the XP/W2k8r2 ISO - WebConsole show Running - Auto-shutdown 
 during the OS installation - WebConsole show Stopped (refer to screenshots 
 ISO_XP-Auto-Shutdown.JPG and ISO_XP_State.JPG ) 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-681) Dedicate Pod, Cluster or Host to a domain

[Saksham Srivastava (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666390#comment-13666390
 ] 

Saksham Srivastava commented on CLOUDSTACK-681:
---

Available for review at :
https://reviews.apache.org/r/11379/ and https://reviews.apache.org/r/11380/

 Dedicate Pod, Cluster or Host to a domain
 -

 Key: CLOUDSTACK-681
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-681
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: pre-4.0.0
Reporter: deepti dohare
Assignee: Devdeep Singh
 Fix For: 4.2.0


 Currently in CloudStack architecture, domains can have dedicated zones but 
 not pods, clusters or hosts. Dedicating a zone might be very expensive 
 offering for an end users, whereas dedicating a pod, cluster or a host may be 
 more economical. 
 This feature will allow Root-Admin to dedicate resources to a specific domain 
 that needs private infrastructure for additional security or performance 
 guarantees.
 Requirements described at: 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Private+Host%2C+Cluster%2C+Pod
 Release Planning: 
 Dev List Discussion: 
 http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201212.mbox/browser
 Functional Spec: 
 https://cwiki.apache.org/CLOUDSTACK/dedicated-resources-private-zone-pod-cluster-host-functional-spec.html
 Feature Branch: Will come in as reviews

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2656) UUID column for all 4.0 schema entities should be populated when they are upgraded to 4.1

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666393#comment-13666393
 ] 

ASF subversion and git services commented on CLOUDSTACK-2656:
-

Commit 672fe2e72b5cea647e4cb28176468f19b5ce9405 in branch refs/heads/4.1 from 
[~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=672fe2e ]

CLOUDSTACK-2656: UUID column for all 4.0 schema entities should be
populated when they are upgraded to 4.1


 UUID column for all 4.0 schema entities should be populated when they are 
 upgraded to 4.1
 -

 Key: CLOUDSTACK-2656
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2656
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.1.0
Reporter: Min Chen
Assignee: Min Chen
 Fix For: 4.1.0


 For all 4.0 schema entities, some of them have empty UUID column due to 
 historical reasons, which may fail at some search by passing db id for old 
 applications. In schema-40to410.sql, we should populate those empty UUID 
 columns with their db ids to not break any old apps after upgrade. Two db 
 tables are missed in this sql, that is, snapshot_policy and 
 dc_storage_network_ip_range.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2587) netscaler_pod_ref DB upgrade is missing from 3.0.2 to 4.x

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666394#comment-13666394
 ] 

ASF subversion and git services commented on CLOUDSTACK-2587:
-

Commit 21b8a0442517516ed04bbc4c08f7c615d5dc4a88 in branch refs/heads/4.1 from 
Chip Childers chip.child...@gmail.com
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=21b8a04 ]

CLOUDSTACK-2587: netscaler_pod_ref DB upgrade is missing from 3.0.2 to
4.x

added missing schema as part of 4.0 to 4.1 upgrade


 netscaler_pod_ref DB upgrade is missing from 3.0.2 to 4.x
 -

 Key: CLOUDSTACK-2587
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2587
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.0.0, 4.1.0
Reporter: Murali Reddy
Assignee: Murali Reddy
 Fix For: 4.2.0


 netscaler_pod_ref DB upgrade is missing from 3.0.2 to 4.x

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-2656) UUID column for all 4.0 schema entities should be populated when they are upgraded to 4.1

[Chip Childers (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chip Childers resolved CLOUDSTACK-2656.
---

Resolution: Fixed

 UUID column for all 4.0 schema entities should be populated when they are 
 upgraded to 4.1
 -

 Key: CLOUDSTACK-2656
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2656
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.1.0
Reporter: Min Chen
Assignee: Min Chen
 Fix For: 4.1.0


 For all 4.0 schema entities, some of them have empty UUID column due to 
 historical reasons, which may fail at some search by passing db id for old 
 applications. In schema-40to410.sql, we should populate those empty UUID 
 columns with their db ids to not break any old apps after upgrade. Two db 
 tables are missed in this sql, that is, snapshot_policy and 
 dc_storage_network_ip_range.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-862) [DOC] Document new L3 functionality for Nicira NVP support.

[Chip Childers (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chip Childers resolved CLOUDSTACK-862.
--

Resolution: Fixed

 [DOC] Document new L3 functionality for Nicira NVP support. 
 

 Key: CLOUDSTACK-862
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-862
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc
Reporter: David Nalley
Assignee: Hugo Trippaers
 Fix For: 4.1.0


 Document the new L3 functionality for Nicira NVP support

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2676) Add Not Null Constraint to UUID columns for cloudstack schema to avoid empty UUID column

[Min Chen (JIRA)]

Min Chen created CLOUDSTACK-2676:


 Summary: Add Not Null Constraint to UUID columns for cloudstack 
schema to avoid empty UUID column
 Key: CLOUDSTACK-2676
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2676
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.2.0
Reporter: Min Chen
 Fix For: 4.2.0


To make sure that we have a consistent upgrade base for all 4.1 customers 
later, in schema-410to420.sql, we have added sql scripts to populate UUID 
column of all pre-4.1 schema tables with values from their ID column if UUID 
column is NULL. To make this work properly, we require that all UUID columns 
should be populated with values when you add new data into both pre-4.1 schema 
or post-4.1 schema. To properly enforce this, we should add Not Null constraint 
at DB level to UUID columns for cloudstack schema. We need to make sure you add 
those constraints after upgrading the data.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666411#comment-13666411
 ] 

ASF subversion and git services commented on CLOUDSTACK-528:


Commit c559c40c3178873177b9f46c46e6c60b5598f2eb in branch refs/heads/4.1 from 
[~chipchilders]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c559c40 ]

CLOUDSTACK-528: Adding a corrective update to remove the extra space characters 
that exist after running older versions of schema-302to40.sql

Signed-off-by: Chip Childers chip.child...@gmail.com


 Failed to create secondary storage
 --

 Key: CLOUDSTACK-528
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.0.0, 4.1.0
 Environment: CentOS 
Reporter: Tamas Monos
Assignee: Wei Zhou
Priority: Blocker
 Fix For: 4.1.0


  Hi,
 I cannot add secondary storage to my existing Zone. This prevents the 
 platform from operating.
 API call via GUI captured by tcpdump:
 http://sandbox.veber.co.uk/client/api?command=addSecondaryStoragezoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloudresponse=jsonsessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D_=1353673985114
 Result:
 Unable to connect due to 
 java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data 
 center: null
 at 
 com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501)
 at 
 com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551)
 at 
 com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
 at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
 at 
 org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
 at 
 org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
 at 
 org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2012-11-23 12:32:58,518 INFO  [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-23:null) server resources successfully discovered by 
 SecondaryStorage
 2012-11-23 12:32:58,518 WARN  [cloud.api.ApiDispatcher] 
 (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to 
 add secondary storage
 Debug:
 mysql select uuid from data_center where name='Watford';
 +--+
 | uuid |
 +--+
 | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 |
 +--+
 The Zone ID matches but API throws exception while the IS is supplied in the 
 query.
 Scenario:
 I have upgraded from 3.0.2 to 4.0.0. Due to the upgrade scripts did not 
 update the systemVMs to the new template I've applied a workaround and 
 recreated the 

[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666413#comment-13666413
 ] 

ASF subversion and git services commented on CLOUDSTACK-528:


Commit 09d2fe6a7ddc208f77edf931ed3d57b0afcc2055 in branch refs/heads/master 
from [~chipchilders]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=09d2fe6 ]

CLOUDSTACK-528: Adding a corrective update to remove the extra space characters 
that exist after running older versions of schema-302to40.sql

Signed-off-by: Chip Childers chip.child...@gmail.com


 Failed to create secondary storage
 --

 Key: CLOUDSTACK-528
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.0.0, 4.1.0
 Environment: CentOS 
Reporter: Tamas Monos
Assignee: Wei Zhou
Priority: Blocker
 Fix For: 4.1.0


  Hi,
 I cannot add secondary storage to my existing Zone. This prevents the 
 platform from operating.
 API call via GUI captured by tcpdump:
 http://sandbox.veber.co.uk/client/api?command=addSecondaryStoragezoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloudresponse=jsonsessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D_=1353673985114
 Result:
 Unable to connect due to 
 java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data 
 center: null
 at 
 com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501)
 at 
 com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551)
 at 
 com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
 at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
 at 
 org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
 at 
 org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
 at 
 org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2012-11-23 12:32:58,518 INFO  [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-23:null) server resources successfully discovered by 
 SecondaryStorage
 2012-11-23 12:32:58,518 WARN  [cloud.api.ApiDispatcher] 
 (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to 
 add secondary storage
 Debug:
 mysql select uuid from data_center where name='Watford';
 +--+
 | uuid |
 +--+
 | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 |
 +--+
 The Zone ID matches but API throws exception while the IS is supplied in the 
 query.
 Scenario:
 I have upgraded from 3.0.2 to 4.0.0. Due to the upgrade scripts did not 
 update the systemVMs to the new template I've applied a workaround and 
 recreated 

[jira] [Assigned] (CLOUDSTACK-2665) [Object_Store_Refactor] UI: Default cent OS template Ready field shows NO in UI whereas it shows YES in DB

[Min Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Min Chen reassigned CLOUDSTACK-2665:


Assignee: Min Chen

 [Object_Store_Refactor] UI: Default cent OS template Ready field shows NO 
 in UI whereas it shows YES in DB
 

 Key: CLOUDSTACK-2665
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2665
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: UI
Affects Versions: 4.2.0
 Environment: Latest build from object_store branch
Reporter: Sanjeev N
Assignee: Min Chen
 Fix For: 4.2.0

 Attachments: Snapshot.JPG


 Default cent OS template Ready field shows NO in UI whereas it shows YES in 
 DB
 Steps to Reproduce:
 =
 1.Bring up CS in advanced zone with s3 as the secondary storage provider
 2.Wait for the SSVM to come up
 3.After SSVM is up, it downloads the default cent os template to S3 image 
 store and once the download is successful template state will be marked Ready.
 mysql select * from vm_template where id=5\G;
 *** 1. row ***
 id: 5
unique_name: centos56-x86_64-xen
   name: CentOS 5.6(64-bit) no GUI (XenServer)
   uuid: 162ea93c-c469-11e2-9096-06ab465f
 public: 1
   featured: 1
   type: BUILTIN
hvm: 0
   bits: 64
url: 
 http://10.147.28.7/templates/builtin/centos56-x86_64.vhd.bz2
 format: VHD
created: 2013-05-24 07:57:19
removed: NULL
 account_id: 1
   checksum: 905cec879afd9c9d22ecc8036131a180
   display_text: CentOS 5.6(64-bit) no GUI (XenServer)
enable_password: 0
  enable_sshkey: 0
guest_os_id: 12
   bootable: 1
prepopulate: 0
cross_zones: 1
extractable: 1
hypervisor_type: XenServer
 source_template_id: NULL
   template_tag: NULL
   sort_key: 0
   size: 374730926
  state: Ready
   update_count: 3
updated: 2013-05-24 12:18:52
 1 row in set (0.00 sec)
 ERROR:
 No query specified
 Attached screen shot to describe the bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-2674) [Object_Store_Refactor]Secondary Storage garbage collector failed with NPE in case of S3 storage provider

[Min Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Min Chen reassigned CLOUDSTACK-2674:


Assignee: Min Chen

 [Object_Store_Refactor]Secondary Storage garbage collector failed with NPE in 
 case of S3 storage provider
 -

 Key: CLOUDSTACK-2674
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2674
 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
 Environment: Latest build from object_store branch
Reporter: Sanjeev N
Assignee: Min Chen
Priority: Critical
 Fix For: 4.2.0


 Secondary Storage garbage collector failed with NPE in case of S3 storage 
 provider
 Steps to Reproduce:
 
 1.Bring up CS in advanced zone with S3 as the secondary storage provider
 2.After SSVM is up and running register ISO to CS
 3.When the ISO is in ready state delete the iso
 4.Wait for the Storage scavenger thread to run
 Observations:
 
 After deleting the ISO , it is marked as destroyed in template_store_ref 
 table and also got deleted from S3 object store. But when secondary storage 
 garbage collector ran it found 1 template to clean up on secondary 
 storage(Image Store not on ImageCache store) since the iso state is in 
 destroyed state and tried to clean it up.
 Found NPE while trying to clean up from Image store:
 013-05-24 14:11:01,976 DEBUG [cloud.storage.StorageManagerImpl] 
 (StorageManager-Scavenger-1:null) Storage pool garbage collector found 0 
 templates to clean up in storage pool: pri_xen_os
 2013-05-24 14:11:01,979 DEBUG [cloud.storage.StorageManagerImpl] 
 (StorageManager-Scavenger-1:null) Storage pool garbage collector found 0 
 templates to clean up in storage pool: pri_xen_os2
 2013-05-24 14:11:01,993 DEBUG [cloud.storage.StorageManagerImpl] 
 (StorageManager-Scavenger-1:null) Secondary storage garbage collector found 1 
 templates to cleanup on secondary storage host: 
 9c5f76a7-507a-4ae1-b411-702e816bbf27
 2013-05-24 14:11:01,999 WARN  [cloud.storage.StorageManagerImpl] 
 (StorageManager-Scavenger-1:null) problem cleaning up templates in secondary 
 storage store 9c5f76a7-507a-4ae1-b411-702e816bbf27
 java.lang.NullPointerException
 at 
 com.cloud.template.TemplateManagerImpl.templateIsDeleteable(TemplateManagerImpl.java:952)
 at 
 com.cloud.storage.StorageManagerImpl.cleanupSecondaryStorage(StorageManagerImpl.java:1136)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.storage.StorageManagerImpl.cleanupStorage(StorageManagerImpl.java:1049)
 at 
 com.cloud.storage.StorageManagerImpl$StorageGarbageCollector.run(StorageManagerImpl.java:1354)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at 
 java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:679)
 2013-05-24 14:11:02,004 DEBUG [cloud.storage.StorageManagerImpl] 
 (StorageManager-Scavenger-1:null) Secondary storage garbage collector found 0 
 volumes to cleanup on secondary storage host: 
 9c5f76a7-507a-4ae1-b411-702e816bbf27
 mysql select * from image_store\G;
 *** 1. row ***
  id: 1
name: nfs://10.147.28.7/export/home/sanjeev/sec_xen_os
 image_provider_name: NFS
protocol: nfs
 url: nfs://10.147.28.7/export/home/sanjeev/sec_xen_os
  data_center_id: 1
   scope: ZONE
role: ImageCache
uuid: f521e766-fb84-4aeb-a0ab-83c2ccdfd56a
  parent: NULL
 created: 2013-05-24 12:09:21
 removed: NULL
  total_size: NULL
 *** 2. row ***
  id: 2
name: 9c5f76a7-507a-4ae1-b411-702e816bbf27
 image_provider_name: S3
protocol: http
 url: NULL
  data_center_id: NULL
   scope: REGION
 

[jira] [Commented] (CLOUDSTACK-2492) System VM Clock Drift

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666425#comment-13666425
 ] 

ASF subversion and git services commented on CLOUDSTACK-2492:
-

Commit 03c693fc85e299c135c16dbb16226d7b7ffa3c8b in branch refs/heads/4.1 from 
[~chipchilders]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=03c693f ]

CLOUDSTACK-2492: Adding the XenServer system VM time sync issue to the 4.1.0 
known issues list

Signed-off-by: Chip Childers chip.child...@gmail.com


 System VM Clock Drift
 -

 Key: CLOUDSTACK-2492
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2492
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: ISO
Affects Versions: pre-4.0.0
 Environment: devcloud/Xen
Reporter: John Burwell
Assignee: Chiradeep Vittal
Priority: Blocker
  Labels: documentaion
 Fix For: 4.2.0


 Testing of S3-backed Secondary Storage has revealed that the SSVM (and likely 
 all other system VMs) have no provision for clock synchronization (e.g. NTP 
 to dom0 for Xen, vmware-tools for VMWare, etc).  In particular, the S3 
 protocol is sensitive to drift between clients and S3.  As an example, the 
 following is the stack trace caused by clock drift S3:
 2013-05-14 06:51:55,400 DEBUG [cloud.utils.S3Utils] (agentRequest-Handler-3:) 
 Putting directory 
 /mnt/SecStorage/93fd0cb0-033b-3248-bcd0-ef6d460635ef/template/tmpl/1/5 in S3 
 bucket jsb-cloudstack-templates.
 2013-05-14 06:51:55,401 DEBUG [cloud.utils.S3Utils] (agentRequest-Handler-3:) 
 Creating S3 client with configuration: [protocol: https, connectionTimeOut: 
 5, maxErrorRetry: 3, socketTimeout: 5]
 2013-05-14 06:51:55,403 DEBUG [storage.resource.NfsSecondaryStorageResource] 
 (agentRequest-Handler-3:) Determining key using account id 1 and template id 5
 2013-05-14 06:51:55,403 DEBUG [cloud.utils.S3Utils] (agentRequest-Handler-3:) 
 Putting file 
 /mnt/SecStorage/93fd0cb0-033b-3248-bcd0-ef6d460635ef/template/tmpl/1/5/template.properties
  into bucket jsb-cloudstack-templates with key 
 template/tmpl/1/5/template.properties.
 2013-05-14 06:51:55,578 ERROR [storage.resource.NfsSecondaryStorageResource] 
 (agentRequest-Handler-3:) Failed to upload template id 5
 Status Code: 403, AWS Service: Amazon S3, AWS Request ID: 970A274E132A9ACB, 
 AWS Error Code: RequestTimeTooSkewed, AWS Error Message: The difference 
 between the request time and the current time is too large., S3 Extended 
 Request ID: 9w8a6YBxTn+WlBg96s9stxWuuP8oQ7ksZtg6++wVRHJfE2qmucrilhoEJVetJui4
 at 
 com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:609)
 at 
 com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:309)
 at 
 com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:164)
 at 
 com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:2863)
 at 
 com.amazonaws.services.s3.AmazonS3Client.putObject(AmazonS3Client.java:1100)
 at 
 com.amazonaws.services.s3.AmazonS3Client.putObject(AmazonS3Client.java:963)
 at com.cloud.utils.S3Utils.putDirectory(S3Utils.java:282)
 at 
 com.cloud.storage.resource.NfsSecondaryStorageResource.execute(NfsSecondaryStorageResource.java:414)
 at 
 com.cloud.storage.resource.NfsSecondaryStorageResource.executeRequest(NfsSecondaryStorageResource.java:212)
 at com.cloud.agent.Agent.processRequest(Agent.java:525)
 at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:852)
 at com.cloud.utils.nio.Task.run(Task.java:83)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 In addition to impacting S3, this clock drift also makes log correlation 
 between the management server and system VMs very difficult, if not, 
 impossible.  Finally, there are suspicions that the clock drift could also 
 impact operation of console proxy and virtual router VMs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-659) Enable storage xenmotion support in XenServer 6.1

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666433#comment-13666433
 ] 

ASF subversion and git services commented on CLOUDSTACK-659:


Commit 6fcc94f78f724fcda391355ef8945cf6d7e79533 in branch 
refs/heads/vmware-storage-motion from Sateesh Chodapuneedi sate...@apache.org
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6fcc94f ]

CLOUDSTACK-659

Fixing migrate volume.


 Enable storage xenmotion support in XenServer 6.1
 -

 Key: CLOUDSTACK-659
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-659
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Devdeep Singh
Assignee: Devdeep Singh
 Fix For: 4.2.0


 XenServer introduced support for Storage XenMotion in the latest version 
 (6.1). Storage XenMotion allows VMs to be moved from one host to another, 
 where the VMs are not located on storage shared between the two hosts. It 
 provides the option to live migrate a VM’s disks along with the VM itself. It 
 is now possible to migrate a VM from one resource pool to another, or to 
 migrate a VM whose disks are on local storage, or even to migrate a VM’s 
 disks from one storage repository to another, all while the VM is running.
 This issue is to track this feature request.
 Release Planning:
 Dev list discussions:
   http://markmail.org/message/numdk6pdab2hekdp
   http://markmail.org/message/cskrdafitghy7o6q
 Functional Spec: 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer
 Feature branch: via reviewboard

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-659) Enable storage xenmotion support in XenServer 6.1

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666434#comment-13666434
 ] 

ASF subversion and git services commented on CLOUDSTACK-659:


Commit df77912c5de666f9a9506bf8525b256c276892b0 in branch 
refs/heads/vmware-storage-motion from Sateesh Chodapuneedi sate...@apache.org
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=df77912 ]

CLOUDSTACK-659
Support for storage migration in Cloudstack deployment over VMware

Added VmwareStorageMotionStrategy to application context.

Signed-off-by: Sateesh Chodapuneedi sate...@apache.org


 Enable storage xenmotion support in XenServer 6.1
 -

 Key: CLOUDSTACK-659
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-659
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Devdeep Singh
Assignee: Devdeep Singh
 Fix For: 4.2.0


 XenServer introduced support for Storage XenMotion in the latest version 
 (6.1). Storage XenMotion allows VMs to be moved from one host to another, 
 where the VMs are not located on storage shared between the two hosts. It 
 provides the option to live migrate a VM’s disks along with the VM itself. It 
 is now possible to migrate a VM from one resource pool to another, or to 
 migrate a VM whose disks are on local storage, or even to migrate a VM’s 
 disks from one storage repository to another, all while the VM is running.
 This issue is to track this feature request.
 Release Planning:
 Dev list discussions:
   http://markmail.org/message/numdk6pdab2hekdp
   http://markmail.org/message/cskrdafitghy7o6q
 Functional Spec: 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enabling+Storage+XenMotion+for+XenServer
 Feature branch: via reviewboard

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2548) [Automation] Failed to delete public IP range

[Rayees Namathponnan (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666439#comment-13666439
 ] 

Rayees Namathponnan commented on CLOUDSTACK-2548:
-

https://reviews.apache.org/r/11297/diff/

 [Automation] Failed to delete public IP range 
 --

 Key: CLOUDSTACK-2548
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2548
 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
 Environment: Master build : Latest 
 Issue found : During BVT automation run on KVM
Reporter: Rayees Namathponnan
Assignee: Bharat Kumar
Priority: Blocker
 Fix For: 4.2.0


 Test case : test/integration/smoke/test_public_ip_range.py
 Steps to reproduce 
 Step 1 : Create advance zone,  and add IP range [In my case added 
 10.223.122.124 to 10.223.122.126]
 Step 2 : Delete this IP range 
 Actual Result
 Release IP range operation failed with below error 
 One of the ips in the range is used to provide Dhcp service to this subnet. 
 cannot delete this range as
 If you look the DB, ip range  10.223.122.124 to  10.223.122.126 is not 
 allocated 
 mysql select * from user_ip_address where state!=Free;
 ++--++---+---+++-+++---+---+-+---++-+---++---+
 | id | uuid | account_id | domain_id | 
 public_ip_address | data_center_id | source_nat | allocated   | 
 vlan_db_id | one_to_one_nat | vm_id | state | mac_address | 
 source_network_id | network_id | physical_network_id | is_system | vpc_id | 
 dnat_vmip |
 ++--++---+---+++-+++---+---+-+---++-+---++---+
 |  2 | ddd29f48-54ba-4b76-b493-c62948f1 | 38 | 1 | 
 10.223.122.67 |  1 |  1 | 2013-05-16 18:01:34 |   
1 |  0 |  NULL | Allocated |  60 |   200 | 
241 | 200 | 0 |   NULL | NULL  |
 |  3 | e4f7899b-1d5b-4c7c-91bd-38af7db1945a |  4 | 1 | 
 10.223.122.68 |  1 |  1 | 2013-05-16 03:54:34 |   
1 |  0 |  NULL | Releasing |  61 |   200 | 
209 | 200 | 0 |   NULL | NULL  |
 |  4 | ab3b333a-bad2-427f-ad7d-6d9f3cac5336 |  1 | 1 | 
 10.223.122.69 |  1 |  0 | 2013-05-16 04:56:39 |   
1 |  0 |  NULL | Allocated |  62 |   200 | 
   NULL | 200 | 0 |   NULL | NULL  |
 |  6 | 73fe34aa-bdce-4f58-bc54-40fe6584a2da |  2 | 1 | 
 10.223.122.71 |  1 |  1 | 2013-05-16 05:43:59 |   
1 |  0 |  NULL | Allocated |  64 |   200 | 
230 | 200 | 0 |   NULL | NULL  |
 | 23 | b97b3062-a82d-487a-8d56-4355ce72d3c7 |  2 | 1 | 
 10.223.122.88 |  1 |  1 | 2013-05-16 05:23:12 |   
1 |  0 |  NULL | Allocated |  81 |   200 | 
227 | 200 | 0 |   NULL | NULL  |
 | 32 | 3d1f0625-90a0-4632-9cfb-aed018efa51c |  2 | 1 | 
 10.223.122.97 |  1 |  1 | 2013-05-16 05:52:11 |   
1 |  0 |  NULL | Allocated |  90 |   200 | 
232 | 200 | 0 |   NULL | NULL  |
 | 52 | 851757d9-92f2-493c-98f6-3bd01b0c2d3b |  1 | 1 | 
 10.223.122.117|  1 |  0 | 2013-05-16 04:54:09 |   
1 |  0 |  NULL | Allocated | 110 |   200 | 
   NULL | 200 | 0 |   NULL | NULL  |
 | 60 | eede24f6-6587-4f75-8e2a-7063ffd2c833 |  1 | 1 | 
 10.223.121.132|  2 |  0 | 2013-05-16 03:39:09 |   
2 |  0 |  NULL | Allocated |  61 |   204 | 
   NULL | 201 | 0 |   NULL | NULL  |
 | 63 | a720338f-15f8-4d47-acc0-da6a2917406d |  1 | 1 | 
 10.223.121.135|  2 |  0 | 2013-05-16 03:39:17 |   
2 | 

[jira] [Created] (CLOUDSTACK-2677) cloudstack UI - network menu - add guest network dialog only allows to add Isolated network here, but not shared notwork. Change label to make it clear.

[Jessica Wang (JIRA)]

Jessica Wang created CLOUDSTACK-2677:


 Summary: cloudstack UI - network menu - add guest network dialog 
only allows to add Isolated network here, but not shared notwork. Change label 
to make it clear.
 Key: CLOUDSTACK-2677
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2677
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Jessica Wang
Assignee: Jessica Wang




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2377) change memory size to 128mb for the tiny service offering

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666470#comment-13666470
 ] 

ASF subversion and git services commented on CLOUDSTACK-2377:
-

Commit 6975f6bac6b33d208bd68750457369ef0178c50f in branch refs/heads/master 
from Jessica Wang jessicaw...@apache.org
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6975f6b ]

CLOUDSTACK-2377: UI - network menu - add guest network dialog only allows to 
add Isolated network, but not shared network. Change label to make it clear.


 change memory size to 128mb  for the tiny service offering
 --

 Key: CLOUDSTACK-2377
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2377
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Test
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Srikanteswararao Talluri
 Fix For: 4.2.0


 change memory size to 128mb  for the tiny service offering

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-2677) cloudstack UI - network menu - add guest network dialog only allows to add Isolated network here, but not shared notwork. Change label to make it clear.

[Jessica Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang resolved CLOUDSTACK-2677.
--

Resolution: Fixed

Author: Jessica Wang 
jessicaw...@apache.org#mailto:jessicaw...@apache.org
Author date:21 minutes ago (Fri May 24 10:08:55 2013)
Commit date:20 minutes ago (Fri May 24 10:09:44 2013)
Commit hash:6975f6bac6b33d208bd68750457369ef0178c50f

CLOUDSTACK-2377: UI - network menu - add guest network dialog only allows to 
add Isolated network, but not shared network. Change label to make it clear.

Contained in branches: master
Contained in no tag

 cloudstack UI - network menu - add guest network dialog only allows to add 
 Isolated network here, but not shared notwork. Change label to make it clear.
 

 Key: CLOUDSTACK-2677
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2677
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Jessica Wang
Assignee: Jessica Wang



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2678) cloudstack UI for Portable IP Ranges.

[Jessica Wang (JIRA)]

Jessica Wang created CLOUDSTACK-2678:


 Summary: cloudstack UI for Portable IP Ranges.
 Key: CLOUDSTACK-2678
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2678
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Jessica Wang
Assignee: Jessica Wang




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2678) cloudstack UI for Portable IP Ranges.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666488#comment-13666488
 ] 

ASF subversion and git services commented on CLOUDSTACK-2678:
-

Commit 3d16e82547c311c1f0cd22065d587556d70d511a in branch refs/heads/master 
from Jessica Wang jessicaw...@apache.org
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3d16e82 ]

CLOUDSTACK-2678: portable IP ranges - regions detailView - add viewAll path to 
Portable IP Ranges listView.


 cloudstack UI for Portable IP Ranges.
 -

 Key: CLOUDSTACK-2678
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2678
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Jessica Wang
Assignee: Jessica Wang



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-2637) Object_Store_Refactor - DB Exception encountered when trying to upload volume.

[edison su (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

edison su reassigned CLOUDSTACK-2637:
-

Assignee: edison su

 Object_Store_Refactor - DB Exception encountered when trying to upload volume.
 --

 Key: CLOUDSTACK-2637
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2637
 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
 Environment: build from object_store
Reporter: Sangeetha Hariharan
Assignee: edison su
Priority: Critical
 Fix For: 4.2.0


 Object_Store_Refactor - DB Exception encountered when trying to upload volume.
 Steps to reproduce the problem:
 Deploy a Vm.
 Attach a data disk to it.
 Write some changes to the data disk.
 Take a snapshot of the datadisk.
 Download this volume.
 Now Upload this volume using uploadVolume command.
 This operation fails with following error message:
 DB Exception on: com.mysql.jdbc.JDBC4PreparedStatement@47c83c76: INSERT INTO 
 volume_store_ref (volume_store_ref.store_id, volume_store_ref.volume_id, 
 volume_store_ref.zone_id, volume_store_ref.created, 
 volume_store_ref.last_updated, volume_store_ref.download_pct, 
 volume_store_ref.size, volume_store_ref.physical_size, 
 volume_store_ref.download_state, volume_store_ref.checksum, 
 volume_store_ref.local_path, volume_store_ref.error_str, 
 volume_store_ref.job_id, volume_store_ref.install_path, volume_store_ref.url, 
 volume_store_ref.format, volume_store_ref.destroyed, 
 volume_store_ref.update_count, volume_store_ref.updated, 
 volume_store_ref.state) VALUES (1, 10, 0, '2013-05-22 23:26:12', null, 0, 0, 
 0, null, null, null, null, null, _binary'volumes/2/10', null, null, 0, 0, 
 null, 'Allocated')
 013-05-22 16:26:12,464 INFO  [cloud.api.ApiServer] (catalina-exec-6:null) 
 (userId=2 accountId=2 sessionId=D91C4E4C17F0583A30B61BA0525D7FF8) 
 10.216.51.144 -- GET 
 command=uploadVolumeresponse=jsonsessionkey=YVb5KPqcM3%2B%2BRpKwK3nTB2j6PTg%3Dname=volfromtestzoneId=9c88115b-ff6e-47af-9033-e592da1f395cformat=VHDurl=http%3A%2F%2F10.223.110.232%2Ftemplates%2Ftest%2F64163ecc-060a-4a80-a396-54e57a2bae27.vhd_=1369268599951
  200 { uploadvolumeresponse : 
 {jobid:0227985e-52ea-4605-87b3-c06e2df8bef7} }
 2013-05-22 16:26:15,524 INFO  [cloud.api.ApiServer] (catalina-exec-5:null) 
 (userId=2 accountId=2 sessionId=D91C4E4C17F0583A30B61BA0525D7FF8) 
 10.216.51.144 -- GET 
 command=queryAsyncJobResultjobId=0227985e-52ea-4605-87b3-c06e2df8bef7response=jsonsessionkey=YVb5KPqcM3%2B%2BRpKwK3nTB2j6PTg%3D_=1369268603245
  200 { queryasyncjobresultresponse : 
 {accountid:89db33ec-c193-11e2-8a23-6a01c7e420f0,userid:89dc6e24-c193-11e2-8a23-6a01c7e420f0,cmd:org.apache.cloudstack.api.command.user.volume.UploadVolumeCmd,jobstatus:2,jobprocstatus:0,jobresultcode:530,jobresulttype:object,jobresult:{errorcode:530,errortext:DB
  Exception on: com.mysql.jdbc.JDBC4PreparedStatement@47c83c76: INSERT INTO 
 volume_store_ref (volume_store_ref.store_id, volume_store_ref.volume_id, 
 volume_store_ref.zone_id, volume_store_ref.created, 
 volume_store_ref.last_updated, volume_store_ref.download_pct, 
 volume_store_ref.size, volume_store_ref.physical_size, 
 volume_store_ref.download_state, volume_store_ref.checksum, 
 volume_store_ref.local_path, volume_store_ref.error_str, 
 volume_store_ref.job_id, volume_store_ref.install_path, volume_store_ref.url, 
 volume_store_ref.format, volume_store_ref.destroyed, 
 volume_store_ref.update_count, volume_store_ref.updated, 
 volume_store_ref.state) VALUES (1, 10, 0, '2013-05-22 23:26:12', null, 0, 0, 
 0, null, null, null, null, null, _binary'volumes/2/10', null, null, 0, 0, 
 null, 
 'Allocated')},created:2013-05-22T16:26:12-0700,jobid:0227985e-52ea-4605-87b3-c06e2df8bef7}
  }
 Management server logs :
 2013-05-22 16:26:12,362 DEBUG [cloud.api.ApiServlet] (catalina-exec-6:null) 
 ===START===  10.216.51.144 -- GET  
 command=uploadVolumeresponse=jsonsessionkey=YVb5KPqcM3%2B%2BRpKwK3nTB2j6PTg%3Dname=volfromtestzoneId=9c88115b-ff6e-47af-9033-e592da1f395cformat=VHDurl=http%3A%2F%2F10.223.110.232%2Ftemplates%2Ftest%2F64163ecc-060a-4a80-a396-54e57a2bae27.vhd_=1369268599951
 2013-05-22 16:26:12,460 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-6:null) submit async job-50, details: AsyncJobVO {id:50, 
 userId: 2, accountId: 2, sessionKey: null, instanceType: None, instanceId: 
 null, cmd: org.apache.cloudstack.api.command.user.volume.UploadVolumeCmd, 
 cmdOriginator: null, cmdInfo: 
 

[jira] [Assigned] (CLOUDSTACK-2658) Object_Store_Refactor -VMWARE - Not able to create a template from root volume.

[edison su (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

edison su reassigned CLOUDSTACK-2658:
-

Assignee: edison su

 Object_Store_Refactor -VMWARE - Not able to create a template from root 
 volume.
 ---

 Key: CLOUDSTACK-2658
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2658
 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
 Environment: Build from object_store
Reporter: Sangeetha Hariharan
Assignee: edison su
Priority: Blocker
 Fix For: 4.2.0


 Object_Store_Refactor -VMWARE - Not able to create a template from root 
 volume.
 Steps to reproduce the problem:
 Deploy a Vm.
 Stop the Vm.
 Create a template from the root volume of this VM.
 This fails:
 Following exceptions seen in the management server logs:
 2013-05-23 16:51:13,134 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-16:null) submit async job-92, details: AsyncJobVO {id:92, us
 erId: 2, accountId: 2, sessionKey: null, instanceType: Template, instanceId: 
 214, cmd: org.apache.cloudstack.api.command.user.template.Crea
 teTemplateCmd, cmdOriginator: null, cmdInfo: 
 {sessionkey:P+gvqeH5SBRM6P1BzOT3B4mey7A\u003d,volumeId:672d38b3-07e7-4aa8-aeef-4d8f806c
 4006,ctxUserId:2,httpmethod:GET,osTypeId:fb9c1aa8-c3e8-11e2-b186-06f4b42b,isPublic:true,isfeatured:true,response
 :json,id:214,displayText:testfromvol,passwordEnabled:false,name:testfromvol,_:1369353090085,ctxAccountId:2,ctxSt
 artEventId:509}, cmdVersion: 0, callbackType: 0, callbackAddress: null, 
 status: 0, processStatus: 0, resultCode: 0, result: null, initMs
 id: 7647994577963, completeMsid: null, lastUpdated: null, lastPolled: null, 
 created: null}
 2013-05-23 16:51:13,141 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-89:job-92) Executing org.apache.cloudstack.api.command.user.t
 emplate.CreateTemplateCmd for job-92
 2013-05-23 16:51:13,163 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null) 
 ===END===  10.217.252.128 -- GET  command=createTemplaterespo
 nse=jsonsessionkey=P%2BgvqeH5SBRM6P1BzOT3B4mey7A%3DvolumeId=672d38b3-07e7-4aa8-aeef-4d8f806c4006name=testfromvoldisplayText=testfromvol
 osTypeId=fb9c1aa8-c3e8-11e2-b186-06f4b42bisPublic=truepasswordEnabled=falseisfeatured=true_=1369353090085
 2013-05-23 16:51:13,454 DEBUG [agent.transport.Request] 
 (Job-Executor-89:job-92) Seq 3-741736513: Sending  { Cmd , MgmtId: 
 7647994577963, v
 ia: 3, Ver: v1, Flags: 100111, 
 [{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.VolumeObje
 ctTO:{uuid:672d38b3-07e7-4aa8-aeef-4d8f806c4006,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO
 :{uuid:ed34ab6d-d394-35ee-892c-7fbe3685f300,id:1,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/sangeeth
 a/vmware-42/primary,port:2049}},name:ROOT-11,size:0,path:ROOT-11-11,volumeId:11,vmName:i-2-11-VM,accountId:2,format:
 OVA,id:11}},destTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/2/214,uuid:8ce8292b-876d-4477-ac6f
 -3632ee736f33,id:214,format:RAW,accountId:2,hvm:true,displayText:testfromvol,imageDataStore:{com.cloud.agent.api.to.NfsTO
 :{_url:nfs://10.223.110.232/export/home/sangeetha/vmware-42/secondary,_role:Image}},name:24c7f62c3-e68d-3fd9-8aea-efaa0cfeaec6
 }},wait:10800}}] }
 2013-05-23 16:51:13,743 DEBUG [agent.transport.Request] 
 (AgentManager-Handler-14:null) Seq 3-741736513: Processing:  { Ans: , MgmtId: 
 76479
 94577963, via: 3, Ver: v1, Flags: 110, 
 [{org.apache.cloudstack.storage.command.CopyCmdAnswer:{result:false,details:CreatePrivateTemp
 lateFromVolumeCommand exception: 
 java.lang.NullPointerException\ncom.cloud.storage.resource.VmwareStorageProcessor.createTemplateFromVolume
 (VmwareStorageProcessor.java:482)\ncom.cloud.storage.resource.VmwareStorageProcessor.createTemplateFromVolume(VmwareStorageProcessor.java:5
 75)\ncom.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:81)\ncom.cloud.storage.r
 esource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49)\ncom.cloud.storage.resource.Vm
 wareSecondaryStorageResourceHandler.executeRequest(VmwareSecondaryStorageResourceHandler.java:98)\ncom.cloud.storage.resource.PremiumSecond
 aryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:56)\ncom.cloud.agent.Agent.processRequest(Agent.java:525)\ncom.cloud
 .agent.Agent$AgentRequestHandler.doTask(Agent.java:852)\ncom.cloud.utils.nio.Task.run(Task.java:83)\njava.util.concurrent.ThreadPoolExecuto
 

[jira] [Assigned] (CLOUDSTACK-2660) Object_Store_Refactor - Vmware - Not able create snapshot of root volume.

[edison su (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

edison su reassigned CLOUDSTACK-2660:
-

Assignee: edison su

 Object_Store_Refactor - Vmware - Not able create snapshot of root volume.
 -

 Key: CLOUDSTACK-2660
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2660
 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
 Environment: Build from object_store
Reporter: Sangeetha Hariharan
Assignee: edison su
Priority: Blocker
 Fix For: 4.2.0


 Object_Store_Refactor - Vmware - Not able create snapshot of root volume.
 Steps to reprodude the problem:
 Deploy a Vm.
 Take a snaphot of the root Volume.
 Following error message is presented to the user:
 Failed to create snapshot due to an internal error creating snapshot for 
 volume 11
 2013-05-23 17:10:53,251 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (catalina-exec-23:null) submit async job-94, details: AsyncJobVO {id:94, 
 userId: 2, accountId: 2, sessionKey: null, instanceType: Snapshot, 
 instanceId: 2, cmd: 
 org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd, 
 cmdOriginator: null, cmdInfo: 
 {id:2,response:json,sessionkey:P+gvqeH5SBRM6P1BzOT3B4mey7A\u003d,ctxUserId:2,httpmethod:GET,volumeid:672d38b3-07e7-4aa8-aeef-4d8f806c4006,_:1369354270363,ctxAccountId:2,ctxStartEventId:517},
  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
 processStatus: 0, resultCode: 0, result: null, initMsid: 7647994577963, 
 completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
 2013-05-23 17:10:53,253 DEBUG [cloud.api.ApiServlet] (catalina-exec-23:null) 
 ===END===  10.217.252.128 -- GET  
 command=createSnapshotvolumeid=672d38b3-07e7-4aa8-aeef-4d8f806c4006response=jsonsessionkey=P%2BgvqeH5SBRM6P1BzOT3B4mey7A%3D_=1369354270363
 2013-05-23 17:10:53,278 DEBUG [cloud.async.AsyncJobManagerImpl] 
 (Job-Executor-91:job-94) Executing 
 org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd for job-94
 2013-05-23 17:10:53,300 INFO  [user.snapshot.CreateSnapshotCmd] 
 (Job-Executor-91:job-94) VOLSS: createSnapshotCmd starts:1369354253300
 2013-05-23 17:10:53,396 DEBUG [agent.transport.Request] 
 (Job-Executor-91:job-94) Seq 1-1481376195: Sending  { Cmd , MgmtId: 
 7647994577963, via: 1, Ver: v1, Flags: 100011, 
 [{org.apache.cloudstack.storage.command.CreateObjectCommand:{data:{org.apache.cloudstack.storage.to.SnapshotObjectTO:{volume:{uuid:672d38b3-07e7-4aa8-aeef-4d8f806c4006,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:ed34ab6d-d394-35ee-892c-7fbe3685f300,id:1,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/sangeetha/vmware-42/primary,port:2049}},name:ROOT-11,size:0,path:ROOT-11-11,volumeId:11,vmName:i-2-11-VM,accountId:2,format:OVA,id:11},dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:ed34ab6d-d394-35ee-892c-7fbe3685f300,id:1,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/sangeetha/vmware-42/primary,port:2049}},vmName:i-2-11-VM,name:new_ROOT-11_20130524001053,hypervisorType:VMware,id:2}},wait:0}}]
  }
 2013-05-23 17:10:53,397 DEBUG [agent.transport.Request] 
 (Job-Executor-91:job-94) Seq 1-1481376195: Executing:  { Cmd , MgmtId: 
 7647994577963, via: 1, Ver: v1, Flags: 100011, 
 [{org.apache.cloudstack.storage.command.CreateObjectCommand:{data:{org.apache.cloudstack.storage.to.SnapshotObjectTO:{volume:{uuid:672d38b3-07e7-4aa8-aeef-4d8f806c4006,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:ed34ab6d-d394-35ee-892c-7fbe3685f300,id:1,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/sangeetha/vmware-42/primary,port:2049}},name:ROOT-11,size:0,path:ROOT-11-11,volumeId:11,vmName:i-2-11-VM,accountId:2,format:OVA,id:11},dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:ed34ab6d-d394-35ee-892c-7fbe3685f300,id:1,poolType:NetworkFilesystem,host:10.223.110.232,path:/export/home/sangeetha/vmware-42/primary,port:2049}},vmName:i-2-11-VM,name:new_ROOT-11_20130524001053,hypervisorType:VMware,id:2}},wait:0}}]
  }
 2013-05-23 17:10:53,397 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-146:null) Seq 1-1481376195: Executing request
 2013-05-23 17:10:53,398 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-146:null) Seq 1-1481376195: Response Received:
 2013-05-23 17:10:53,398 DEBUG [agent.transport.Request] 
 (DirectAgent-146:null) Seq 1-1481376195: Processing:  { Ans: , MgmtId: 
 7647994577963, via: 1, Ver: v1, Flags: 10, 
 

[jira] [Assigned] (CLOUDSTACK-2673) [Object_Store_Refactor] Failed to deploy guest vm using ISO with S3 being the storage provider

[Min Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Min Chen reassigned CLOUDSTACK-2673:


Assignee: Min Chen

 [Object_Store_Refactor] Failed to deploy guest vm using ISO with S3 being the 
 storage provider
 --

 Key: CLOUDSTACK-2673
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2673
 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
 Environment: Latest build from object_store branch
Reporter: Sanjeev N
Assignee: Min Chen
Priority: Blocker
 Fix For: 4.2.0


 Failed to deploy guest vm using ISO with S3 being the storage provider
 Steps to Reproduce:
 =
 1.Bring up CS in advanced zone with S3 as the secondary storage provider
 2.Wait for the SSVM to come up
 3.Register ISO to CS
 4.Try to deploy guest vm using the registered ISO
 Result:
 ==
 Looks like CS is trying to mount the S3 URI after creating vhd and is failing:
 2013-05-24 13:27:58,682 DEBUG [agent.transport.Request] 
 (Job-Executor-27:job-27) Seq 1-698156160: Sending  { Cmd , MgmtId: 
 7332683579487, via: 1, Ver: v1, Flags: 100011, 
 [{org.apache.cloudstack.storage.command.CreateObjectCommand:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:82891103-1daf-4118-9fc8-10296e486d7c,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:c65a038a-750c-3b4f-bf26-7ce3b74e1c85,id:1,poolType:NetworkFilesystem,host:10.147.28.7,path:/export/home/sanjeev/pri_xen_os,port:2049}},name:ROOT-6,size:21474836480,volumeId:10,vmName:i-2-6-VM,accountId:2,format:VHD,id:10}},wait:0}}]
  }
 2013-05-24 13:27:58,683 DEBUG [agent.transport.Request] 
 (Job-Executor-27:job-27) Seq 1-698156160: Executing:  { Cmd , MgmtId: 
 7332683579487, via: 1, Ver: v1, Flags: 100011, 
 [{org.apache.cloudstack.storage.command.CreateObjectCommand:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{uuid:82891103-1daf-4118-9fc8-10296e486d7c,volumeType:ROOT,dataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:c65a038a-750c-3b4f-bf26-7ce3b74e1c85,id:1,poolType:NetworkFilesystem,host:10.147.28.7,path:/export/home/sanjeev/pri_xen_os,port:2049}},name:ROOT-6,size:21474836480,volumeId:10,vmName:i-2-6-VM,accountId:2,format:VHD,id:10}},wait:0}}]
  }
 2013-05-24 13:27:58,684 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-69:null) Seq 1-698156160: Executing request
 2013-05-24 13:27:58,779 DEBUG [xen.resource.CitrixResourceBase] 
 (DirectAgent-69:null) SR retrieved for c65a038a-750c-3b4f-bf26-7ce3b74e1c85
 2013-05-24 13:27:58,790 DEBUG [xen.resource.CitrixResourceBase] 
 (DirectAgent-69:null) Checking c65a038a-750c-3b4f-bf26-7ce3b74e1c85 or SR 
 e2e107fc-8b53-25e0-f793-c9d6909b5757 on 
 XS[d20696c6-46d5-45b5-83d3-cfc5993bba74-10.147.40.14]
 2013-05-24 13:27:59,034 DEBUG [agent.manager.DirectAgentAttache] 
 (DirectAgent-69:null) Seq 1-698156160: Response Received:
 2013-05-24 13:27:59,035 DEBUG [agent.transport.Request] (DirectAgent-69:null) 
 Seq 1-698156160: Processing:  { Ans: , MgmtId: 7332683579487, via: 1, Ver: 
 v1, Flags: 10, 
 [{org.apache.cloudstack.storage.command.CreateObjectAnswer:{data:{org.apache.cloudstack.storage.to.VolumeObjectTO:{name:ROOT-6,size:21474836480,path:0a90bd67-1f7d-4297-aebb-3cdc35231d7d,accountId:0,id:0}},result:true,wait:0}}]
  }
 2013-05-24 13:27:59,035 DEBUG [agent.transport.Request] 
 (Job-Executor-27:job-27) Seq 1-698156160: Received:  { Ans: , MgmtId: 
 7332683579487, via: 1, Ver: v1, Flags: 10, { CreateObjectAnswer } }
 2013-05-24 13:27:59,132 DEBUG [agent.transport.Request] 
 (Job-Executor-27:job-27) Seq 1-698156161: Sending  { Cmd , MgmtId: 
 7332683579487, via: 1, Ver: v1, Flags: 100111, 
 [{com.cloud.agent.api.StartCommand:{vm:{id:6,name:i-2-6-VM,bootloader:CD,type:User,cpus:1,minSpeed:500,maxSpeed:500,minRam:536870912,maxRam:536870912,arch:x86_64,os:Windows
  8 
 

[jira] [Commented] (CLOUDSTACK-2678) cloudstack UI for Portable IP Ranges.

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666512#comment-13666512
 ] 

ASF subversion and git services commented on CLOUDSTACK-2678:
-

Commit 3d16e82547c311c1f0cd22065d587556d70d511a in branch 
refs/heads/ui-vpc-redesign from Jessica Wang jessicaw...@apache.org
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3d16e82 ]

CLOUDSTACK-2678: portable IP ranges - regions detailView - add viewAll path to 
Portable IP Ranges listView.


 cloudstack UI for Portable IP Ranges.
 -

 Key: CLOUDSTACK-2678
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2678
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Jessica Wang
Assignee: Jessica Wang



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2377) change memory size to 128mb for the tiny service offering

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666513#comment-13666513
 ] 

ASF subversion and git services commented on CLOUDSTACK-2377:
-

Commit 6975f6bac6b33d208bd68750457369ef0178c50f in branch 
refs/heads/ui-vpc-redesign from Jessica Wang jessicaw...@apache.org
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6975f6b ]

CLOUDSTACK-2377: UI - network menu - add guest network dialog only allows to 
add Isolated network, but not shared network. Change label to make it clear.


 change memory size to 128mb  for the tiny service offering
 --

 Key: CLOUDSTACK-2377
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2377
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Test
Affects Versions: 4.2.0
Reporter: Srikanteswararao Talluri
Assignee: Srikanteswararao Talluri
 Fix For: 4.2.0


 change memory size to 128mb  for the tiny service offering

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-528) Failed to create secondary storage

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666514#comment-13666514
 ] 

ASF subversion and git services commented on CLOUDSTACK-528:


Commit 09d2fe6a7ddc208f77edf931ed3d57b0afcc2055 in branch 
refs/heads/ui-vpc-redesign from [~chipchilders]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=09d2fe6 ]

CLOUDSTACK-528: Adding a corrective update to remove the extra space characters 
that exist after running older versions of schema-302to40.sql

Signed-off-by: Chip Childers chip.child...@gmail.com


 Failed to create secondary storage
 --

 Key: CLOUDSTACK-528
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-528
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.0.0, 4.1.0
 Environment: CentOS 
Reporter: Tamas Monos
Assignee: Wei Zhou
Priority: Blocker
 Fix For: 4.1.0


  Hi,
 I cannot add secondary storage to my existing Zone. This prevents the 
 platform from operating.
 API call via GUI captured by tcpdump:
 http://sandbox.veber.co.uk/client/api?command=addSecondaryStoragezoneId=a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1url=nfs%3A%2F%2F192.168.1.2%2Fwatford_cloudresponse=jsonsessionkey=DGl3OmkfQRGwuIDZFoOpoF2WBJU%3D_=1353673985114
 Result:
 Unable to connect due to 
 java.lang.IllegalArgumentException: Host 192.168.1.4 sent incorrect data 
 center: null
 at 
 com.cloud.resource.ResourceManagerImpl.createHostVO(ResourceManagerImpl.java:1501)
 at 
 com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1629)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:720)
 at 
 com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:551)
 at 
 com.cloud.api.commands.AddSecondaryStorageCmd.execute(AddSecondaryStorageCmd.java:79)
 at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
 at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543)
 at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422)
 at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
 at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
 at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
 at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
 at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
 at 
 org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
 at 
 org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
 at 
 org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:679)
 2012-11-23 12:32:58,518 INFO  [cloud.resource.ResourceManagerImpl] 
 (catalina-exec-23:null) server resources successfully discovered by 
 SecondaryStorage
 2012-11-23 12:32:58,518 WARN  [cloud.api.ApiDispatcher] 
 (catalina-exec-23:null) class com.cloud.api.ServerApiException : Failed to 
 add secondary storage
 Debug:
 mysql select uuid from data_center where name='Watford';
 +--+
 | uuid |
 +--+
 | a8d21e6d-bc9e-4dc2-b996-fc22727cd9c1 |
 +--+
 The Zone ID matches but API throws exception while the IS is supplied in the 
 query.
 Scenario:
 I have upgraded from 3.0.2 to 4.0.0. Due to the upgrade scripts did not 
 update the systemVMs to the new template I've applied a workaround and 
 

[jira] [Commented] (CLOUDSTACK-2674) [Object_Store_Refactor]Secondary Storage garbage collector failed with NPE in case of S3 storage provider

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666515#comment-13666515
 ] 

ASF subversion and git services commented on CLOUDSTACK-2674:
-

Commit c614c6a424f33f582e6ce4a0e7bf4d72f5606bda in branch 
refs/heads/object_store from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c614c6a ]

CLOUDSTACK-2674: Secondary Storage garbage collector failed with NPE in
case of S3 storage provider.

 [Object_Store_Refactor]Secondary Storage garbage collector failed with NPE in 
 case of S3 storage provider
 -

 Key: CLOUDSTACK-2674
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2674
 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
 Environment: Latest build from object_store branch
Reporter: Sanjeev N
Assignee: Min Chen
Priority: Critical
 Fix For: 4.2.0


 Secondary Storage garbage collector failed with NPE in case of S3 storage 
 provider
 Steps to Reproduce:
 
 1.Bring up CS in advanced zone with S3 as the secondary storage provider
 2.After SSVM is up and running register ISO to CS
 3.When the ISO is in ready state delete the iso
 4.Wait for the Storage scavenger thread to run
 Observations:
 
 After deleting the ISO , it is marked as destroyed in template_store_ref 
 table and also got deleted from S3 object store. But when secondary storage 
 garbage collector ran it found 1 template to clean up on secondary 
 storage(Image Store not on ImageCache store) since the iso state is in 
 destroyed state and tried to clean it up.
 Found NPE while trying to clean up from Image store:
 013-05-24 14:11:01,976 DEBUG [cloud.storage.StorageManagerImpl] 
 (StorageManager-Scavenger-1:null) Storage pool garbage collector found 0 
 templates to clean up in storage pool: pri_xen_os
 2013-05-24 14:11:01,979 DEBUG [cloud.storage.StorageManagerImpl] 
 (StorageManager-Scavenger-1:null) Storage pool garbage collector found 0 
 templates to clean up in storage pool: pri_xen_os2
 2013-05-24 14:11:01,993 DEBUG [cloud.storage.StorageManagerImpl] 
 (StorageManager-Scavenger-1:null) Secondary storage garbage collector found 1 
 templates to cleanup on secondary storage host: 
 9c5f76a7-507a-4ae1-b411-702e816bbf27
 2013-05-24 14:11:01,999 WARN  [cloud.storage.StorageManagerImpl] 
 (StorageManager-Scavenger-1:null) problem cleaning up templates in secondary 
 storage store 9c5f76a7-507a-4ae1-b411-702e816bbf27
 java.lang.NullPointerException
 at 
 com.cloud.template.TemplateManagerImpl.templateIsDeleteable(TemplateManagerImpl.java:952)
 at 
 com.cloud.storage.StorageManagerImpl.cleanupSecondaryStorage(StorageManagerImpl.java:1136)
 at 
 com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
 at 
 com.cloud.storage.StorageManagerImpl.cleanupStorage(StorageManagerImpl.java:1049)
 at 
 com.cloud.storage.StorageManagerImpl$StorageGarbageCollector.run(StorageManagerImpl.java:1354)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at 
 java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
 at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:679)
 2013-05-24 14:11:02,004 DEBUG [cloud.storage.StorageManagerImpl] 
 (StorageManager-Scavenger-1:null) Secondary storage garbage collector found 0 
 volumes to cleanup on secondary storage host: 
 9c5f76a7-507a-4ae1-b411-702e816bbf27
 mysql select * from image_store\G;
 *** 1. row ***
  id: 1
name: nfs://10.147.28.7/export/home/sanjeev/sec_xen_os
 image_provider_name: NFS
protocol: nfs
 url: nfs://10.147.28.7/export/home/sanjeev/sec_xen_os
  data_center_id: 1
   scope: ZONE
role: ImageCache
uuid: f521e766-fb84-4aeb-a0ab-83c2ccdfd56a
  parent: NULL
 created: 

[jira] [Created] (CLOUDSTACK-2679) Install docs could point to more accurate XenServer download page

[John Kinsella (JIRA)]

John Kinsella created CLOUDSTACK-2679:
-

 Summary: Install docs could point to more accurate XenServer 
download page
 Key: CLOUDSTACK-2679
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2679
 Project: CloudStack
  Issue Type: Improvement
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Doc
Affects Versions: 4.0.2
Reporter: John Kinsella
 Fix For: 4.2.0


Somebody on twitter raised to my attention that the installation docs (eg 
Section 8.2.2 on 
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.2/html/Installation_Guide/citrix-xenserver-installation.html#system-requirements-xenserver-hosts
 ) point to a Citrix page that allows downloading of XenServer 6.1.  Apparently 
to download 6.0.2 (The version ACS officially supports) requires creating an 
account and looking in download archives. Would be good if we could make this a 
little more clear in the docs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CLOUDSTACK-2680) Async job expunge thread expunges not only inactive jobs, but also the jobs that are currently being processed

[Alena Prokharchyk (JIRA)]

Alena Prokharchyk created CLOUDSTACK-2680:
-

 Summary: Async job expunge thread expunges not only inactive jobs, 
but also the jobs that are currently being processed
 Key: CLOUDSTACK-2680
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2680
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Management Server
Affects Versions: 4.1.0
Reporter: Alena Prokharchyk
Assignee: Alena Prokharchyk
 Fix For: 4.2.0


Async Job Expunge thread that expunges jobs being in the async_job table for 
more than job.expire.minutes, expunge not only inactive (waiting) jobs, but 
also the jobs that are currently being processed. It affects all cloudStack 
jobs. It wasn't caught before because the default expire 
interval is 1 day, and the job would expire faster on the backend (30 mins is 
the default timeout). 

So here what happens in snapshot case: 

1) Set concurrent.snapshots.threshold.perhost=1, job.expire.minutes=15 mins 
2) First createSnapshot API was executed at X time. Async job1 was created. 
As there were no other snapshot jobs, the command was sent for execution to the 
backend. 
3) Second createSnapshot was executed at X + 30 seconds time. Async job2 was 
created. Job2 is sitting in the queue and waiting on a job1 to finish. 
4) The job1 didn't return back in 15 mins, and it was considered as expired by 
the AsyncJobManager, and removed from the queue (although it was already 
processed) 
5) The background process checking on the sync status for job2 (runs every 10 
seconds), found out that there is nothing blocking job2 any more, and sent it 
to the backend. 


The recommended fix would be: expire/expunge only inactive and already 
completed jobs. Don't touch the jobs that are currently being processed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster

[Min Chen (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666723#comment-13666723
 ] 

Min Chen commented on CLOUDSTACK-2670:
--

This behavior is as expected. In current implementation 
FindStoragePoolsForMigration we inherited from master branch, it will check if 
the volume is attached to a running VM. If the volume id given is not attached 
to a running VM, then it will not do migration, so return an empty set.

 [Object_Store_Refactor] UI/API: migrate volume does not show the available 
 primary storages within the cluster
 --

 Key: CLOUDSTACK-2670
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: Latest build from object store branch: 
 CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
Reporter: Sanjeev N
 Fix For: 4.2.0


 Migrate volume does not show the available primary storages within the cluster
 Steps to reproduce:
 
 1.Bring up CS with xen cluster
 2.Deploy guest vm
 3.Add another primary storage to in the cluster
 4.Stop the vm and try to migrate the root disk to another available primary 
 storage in the cluster
 Result:
 ==
 migrate volume called findStoragePoolsFroMigration but the API returned blank 
 response:
 http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigrationid=1a4eb56e-4050-4688-b5d7-d721ce4439a2response=jsonsessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D_=1369391000834
 { findstoragepoolsformigrationresponse : { } }
 So migrate volume page displays blank in storage pool drop down list in UI.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster

[Min Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Min Chen reassigned CLOUDSTACK-2670:


Assignee: Min Chen

 [Object_Store_Refactor] UI/API: migrate volume does not show the available 
 primary storages within the cluster
 --

 Key: CLOUDSTACK-2670
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: Latest build from object store branch: 
 CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
Reporter: Sanjeev N
Assignee: Min Chen
 Fix For: 4.2.0


 Migrate volume does not show the available primary storages within the cluster
 Steps to reproduce:
 
 1.Bring up CS with xen cluster
 2.Deploy guest vm
 3.Add another primary storage to in the cluster
 4.Stop the vm and try to migrate the root disk to another available primary 
 storage in the cluster
 Result:
 ==
 migrate volume called findStoragePoolsFroMigration but the API returned blank 
 response:
 http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigrationid=1a4eb56e-4050-4688-b5d7-d721ce4439a2response=jsonsessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D_=1369391000834
 { findstoragepoolsformigrationresponse : { } }
 So migrate volume page displays blank in storage pool drop down list in UI.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster

[Min Chen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Min Chen resolved CLOUDSTACK-2670.
--

Resolution: Not A Problem

 [Object_Store_Refactor] UI/API: migrate volume does not show the available 
 primary storages within the cluster
 --

 Key: CLOUDSTACK-2670
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: API
Affects Versions: 4.2.0
 Environment: Latest build from object store branch: 
 CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
Reporter: Sanjeev N
Assignee: Min Chen
 Fix For: 4.2.0


 Migrate volume does not show the available primary storages within the cluster
 Steps to reproduce:
 
 1.Bring up CS with xen cluster
 2.Deploy guest vm
 3.Add another primary storage to in the cluster
 4.Stop the vm and try to migrate the root disk to another available primary 
 storage in the cluster
 Result:
 ==
 migrate volume called findStoragePoolsFroMigration but the API returned blank 
 response:
 http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigrationid=1a4eb56e-4050-4688-b5d7-d721ce4439a2response=jsonsessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D_=1369391000834
 { findstoragepoolsformigrationresponse : { } }
 So migrate volume page displays blank in storage pool drop down list in UI.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1974) UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666777#comment-13666777
 ] 

ASF subversion and git services commented on CLOUDSTACK-1974:
-

Commit 11a7e46dfb8123b5ca96d34c41f401d91df332fa in branch refs/heads/master 
from Jessica Wang jessicaw...@apache.org
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=11a7e46 ]

CLOUDSTACK-1974: Dedicate Guest VLAN Range - UI - Infrastructure menu - 
physical network - Guest - Dedicated Guest VLAN Range tab - implement Release 
Dedicated VLAN Range action.


 UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant
 -

 Key: CLOUDSTACK-1974
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1974
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Jessica Wang
Assignee: Jessica Wang
 Fix For: 4.2.0




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1974) UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant

[Jessica Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang updated CLOUDSTACK-1974:
-

Attachment: dedicate_publicIpRange2.jpg

 UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant
 -

 Key: CLOUDSTACK-1974
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1974
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Jessica Wang
Assignee: Jessica Wang
 Fix For: 4.2.0

 Attachments: dedicateGuestVlanRange1.jpg, 
 dedicate_publicIpRange2.jpg, dedicate_publicIpRange3.jpg, 
 dedicate_publicIpRange4.jpg, dedicate_publicIpRange5.jpg, 
 dedicate_publicIpRange.jpg




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1974) UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant

[Jessica Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang updated CLOUDSTACK-1974:
-

Attachment: dedicate_publicIpRange3.jpg

 UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant
 -

 Key: CLOUDSTACK-1974
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1974
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Jessica Wang
Assignee: Jessica Wang
 Fix For: 4.2.0

 Attachments: dedicateGuestVlanRange1.jpg, 
 dedicate_publicIpRange2.jpg, dedicate_publicIpRange3.jpg, 
 dedicate_publicIpRange4.jpg, dedicate_publicIpRange5.jpg, 
 dedicate_publicIpRange.jpg




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1974) UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant

[Jessica Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang updated CLOUDSTACK-1974:
-

Attachment: dedicate_publicIpRange4.jpg

 UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant
 -

 Key: CLOUDSTACK-1974
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1974
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Jessica Wang
Assignee: Jessica Wang
 Fix For: 4.2.0

 Attachments: dedicateGuestVlanRange1.jpg, 
 dedicate_publicIpRange2.jpg, dedicate_publicIpRange3.jpg, 
 dedicate_publicIpRange4.jpg, dedicate_publicIpRange5.jpg, 
 dedicate_publicIpRange.jpg




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1974) UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant

[Jessica Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang updated CLOUDSTACK-1974:
-

Attachment: dedicate_publicIpRange5.jpg

 UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant
 -

 Key: CLOUDSTACK-1974
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1974
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Jessica Wang
Assignee: Jessica Wang
 Fix For: 4.2.0

 Attachments: dedicateGuestVlanRange1.jpg, 
 dedicate_publicIpRange2.jpg, dedicate_publicIpRange3.jpg, 
 dedicate_publicIpRange4.jpg, dedicate_publicIpRange5.jpg, 
 dedicate_publicIpRange.jpg




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1974) UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant

[Jessica Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang updated CLOUDSTACK-1974:
-

Attachment: dedicateGuestVlanRange1.jpg

 UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant
 -

 Key: CLOUDSTACK-1974
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1974
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Jessica Wang
Assignee: Jessica Wang
 Fix For: 4.2.0

 Attachments: dedicateGuestVlanRange1.jpg, 
 dedicate_publicIpRange2.jpg, dedicate_publicIpRange3.jpg, 
 dedicate_publicIpRange4.jpg, dedicate_publicIpRange5.jpg, 
 dedicate_publicIpRange.jpg




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1974) UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant

[Jessica Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang updated CLOUDSTACK-1974:
-

Attachment: dedicateGuestVlanRange2.jpg

 UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant
 -

 Key: CLOUDSTACK-1974
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1974
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Jessica Wang
Assignee: Jessica Wang
 Fix For: 4.2.0

 Attachments: dedicateGuestVlanRange1.jpg, 
 dedicateGuestVlanRange2.jpg, dedicate_publicIpRange2.jpg, 
 dedicate_publicIpRange3.jpg, dedicate_publicIpRange4.jpg, 
 dedicate_publicIpRange5.jpg, dedicate_publicIpRange.jpg




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1974) UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant

[Jessica Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang updated CLOUDSTACK-1974:
-

Attachment: dedicateGuestVlanRange4.jpg

 UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant
 -

 Key: CLOUDSTACK-1974
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1974
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Jessica Wang
Assignee: Jessica Wang
 Fix For: 4.2.0

 Attachments: dedicateGuestVlanRange1.jpg, 
 dedicateGuestVlanRange2.jpg, dedicateGuestVlanRange3.jpg, 
 dedicateGuestVlanRange4.jpg, dedicate_publicIpRange2.jpg, 
 dedicate_publicIpRange3.jpg, dedicate_publicIpRange4.jpg, 
 dedicate_publicIpRange5.jpg, dedicate_publicIpRange.jpg




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-1974) UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666828#comment-13666828
 ] 

ASF subversion and git services commented on CLOUDSTACK-1974:
-

Commit 7cc1e82210f12a615f1f3b425e8076a33ab471e1 in branch refs/heads/master 
from Jessica Wang jessicaw...@apache.org
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7cc1e82 ]

CLOUDSTACK-1974: Dedicate Guest VLAN Range - UI - Infrastructure menu - 
physical network - Guest - Release Dedicated VLAN Range action - change label 
and message.


 UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant
 -

 Key: CLOUDSTACK-1974
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1974
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Jessica Wang
Assignee: Jessica Wang
 Fix For: 4.2.0

 Attachments: dedicateGuestVlanRange1.jpg, 
 dedicateGuestVlanRange2.jpg, dedicateGuestVlanRange3.jpg, 
 dedicateGuestVlanRange4.jpg, dedicate_publicIpRange2.jpg, 
 dedicate_publicIpRange3.jpg, dedicate_publicIpRange4.jpg, 
 dedicate_publicIpRange5.jpg, dedicate_publicIpRange.jpg




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1974) UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant

[Jessica Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang updated CLOUDSTACK-1974:
-

Attachment: dedicateGuestVlanRange6.jpg

 UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant
 -

 Key: CLOUDSTACK-1974
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1974
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Jessica Wang
Assignee: Jessica Wang
 Fix For: 4.2.0

 Attachments: dedicateGuestVlanRange1.jpg, 
 dedicateGuestVlanRange2.jpg, dedicateGuestVlanRange3.jpg, 
 dedicateGuestVlanRange4.jpg, dedicateGuestVlanRange5.jpg, 
 dedicateGuestVlanRange6.jpg, dedicate_publicIpRange2.jpg, 
 dedicate_publicIpRange3.jpg, dedicate_publicIpRange4.jpg, 
 dedicate_publicIpRange5.jpg, dedicate_publicIpRange.jpg




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CLOUDSTACK-1974) UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant

[Jessica Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Wang updated CLOUDSTACK-1974:
-

Attachment: dedicateGuestVlanRange5.jpg

 UI for Dedicated Resources - Public IP Addresses and VLANs per Tenant
 -

 Key: CLOUDSTACK-1974
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1974
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Reporter: Jessica Wang
Assignee: Jessica Wang
 Fix For: 4.2.0

 Attachments: dedicateGuestVlanRange1.jpg, 
 dedicateGuestVlanRange2.jpg, dedicateGuestVlanRange3.jpg, 
 dedicateGuestVlanRange4.jpg, dedicateGuestVlanRange5.jpg, 
 dedicateGuestVlanRange6.jpg, dedicate_publicIpRange2.jpg, 
 dedicate_publicIpRange3.jpg, dedicate_publicIpRange4.jpg, 
 dedicate_publicIpRange5.jpg, dedicate_publicIpRange.jpg




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-747) nTier Apps 2.0 : Internal Load Balancing between the VPC tiers

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666831#comment-13666831
 ] 

ASF subversion and git services commented on CLOUDSTACK-747:


Commit d99fae07c7ee750452e346e69f582f0342280f2a in branch refs/heads/master 
from Jessica Wang jessicaw...@apache.org
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d99fae0 ]

CLOUDSTACK-747: Infrastructure menu - service providers - change display name 
of internalLbVm to be Internal LB VM.


  nTier Apps 2.0 : Internal Load Balancing between the VPC tiers
 ---

 Key: CLOUDSTACK-747
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-747
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Network Controller
Reporter: Kishan Kavala
Assignee: Brian Federle
 Fix For: 4.2.0


 This item is sub task (2.2) of 
 https://issues.apache.org/jira/browse/CLOUDSTACK-621 
 Currently, Load Balancing VPC VR is only supported on one of the Tiers of an 
 nTier Application. With this release, CloudStack should support load 
 balancing on all tiers of an nTier application.
 Use Case: Users would like to deploy a multi-tier application with the VR 
 load balancing each of the tiers. As a result, users would be able to provide 
 flexibility and elasticity at each tier of their application

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2563) NTier: Protocol '1' (ICMP) should be allowed to be specified with icmptype and icmpcode

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666836#comment-13666836
 ] 

ASF subversion and git services commented on CLOUDSTACK-2563:
-

Commit a1437ae82e9c686139c85ac9d3eb039bf968c014 in branch refs/heads/master 
from Sheng Yang sheng.y...@citrix.com
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a1437ae ]

CLOUDSTACK-2563: Network ACL: Allow protocol 1(icmp) paired with icmp type/code


 NTier: Protocol '1' (ICMP) should be allowed to be specified with icmptype 
 and icmpcode
 ---

 Key: CLOUDSTACK-2563
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2563
 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: Chandan Purushothama
Assignee: Sheng Yang
Priority: Critical
 Fix For: 4.2.0


 ===
 Observations:
 ===
 2013-05-17 11:53:13,826 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null) 
 ===START===  10.216.50.223 -- GET  
 command=createNetworkACLprotocol=1number=14aclid=c1c3e475-e293-429b-a50f-92bd6bf4f514action=Allowtraffictype=Ingresscidrlist=10.223.110.232/32icmpcode=-1icmptype=-1response=jsonsessionkey=vrpjOm3ZxVeFFeN%2FGQK1ZMn%2Bmf8%3D_=1368811395060
 2013-05-17 11:53:13,832 DEBUG [cloud.user.AccountManagerImpl] 
 (catalina-exec-3:null) Access to Acct[3-atoms] granted to Acct[3-atoms] by 
 DomainChecker_EnhancerByCloudStack_fcb6b9a3
 2013-05-17 11:53:13,835 DEBUG [cloud.user.AccountManagerImpl] 
 (catalina-exec-3:null) Access to [VPC [1-Atoms-VPC-1] granted to 
 Acct[3-atoms] by DomainChecker_EnhancerByCloudStack_fcb6b9a3
 2013-05-17 11:53:13,836 INFO  [cloud.api.ApiServer] (catalina-exec-3:null) 
 Can specify icmpCode and icmpType for ICMP protocol only
 2013-05-17 11:53:13,837 DEBUG [cloud.api.ApiServlet] (catalina-exec-3:null) 
 ===END===  10.216.50.223 -- GET  
 command=createNetworkACLprotocol=1number=14aclid=c1c3e475-e293-429b-a50f-92bd6bf4f514action=Allowtraffictype=Ingresscidrlist=10.223.110.232/32icmpcode=-1icmptype=-1response=jsonsessionkey=vrpjOm3ZxVeFFeN%2FGQK1ZMn%2Bmf8%3D_=1368811395060

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool

[Prachi Damle (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666843#comment-13666843
 ] 

Prachi Damle commented on CLOUDSTACK-2281:
--

Found the root-cause of this issue and fixed it via this ticket: 
https://issues.apache.org/jira/browse/CLOUDSTACK-2568

 VM fails to deploy due to planner selecting deleted pool
 

 Key: CLOUDSTACK-2281
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2281
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.1.0
Reporter: Marcus Sorensen
Assignee: Prachi Damle
 Fix For: 4.1.0

 Attachments: job9908.txt


 Having trouble tracking this down. Here's what I did:
 Created a 4.1 advanced zone
 added primary storage A
 deployed a template
 deployed vms
 added new primary storages
 migrated VMs from primary storage A to others
 removed initial primary storage A
 try to deploy new vm from template, not working. It looks like the allocator 
 correctly finds and decides to use pool id 204, but somehow deployment is 
 actually attempted on deleted pool 202. See Returning Deployment 
 Destination and DeploymentPlan is provided:
 2013-04-29 13:25:49,293 DEBUG [allocator.impl.FirstFitAllocator] 
 (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Found a suitable host, 
 adding to list: 19
 2013-04-29 13:25:49,294 DEBUG [allocator.impl.FirstFitAllocator] 
 (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Host Allocator returning 
 4 suitable hosts
 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) Checking suitable pools for volume (Id, Type): 
 (10663,ROOT)
 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) We need to allocate new storagepool for this volume
 2013-04-29 13:25:49,299 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) Calling StoragePoolAllocators to find suitable 
 pools
 2013-04-29 13:25:49,302 DEBUG 
 [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) 
 Looking for pools in dc: 1  pod:1  cluster:1
 2013-04-29 13:25:49,304 DEBUG 
 [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) 
 FirstFitStoragePoolAllocator has 1 pools to check for allocation
 2013-04-29 13:25:49,304 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) 
 Checking if storage pool is suitable, name: sansrv-row2-rack0 ,poolId: 204
 2013-04-29 13:25:49,304 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) 
 Is localStorageAllocationNeeded? false
 2013-04-29 13:25:49,305 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) 
 Is storage pool shared? true
 2013-04-29 13:25:49,309 DEBUG [cloud.storage.StorageManagerImpl] 
 (Job-Executor-10:job-9908) Checking pool 204 for storage, totalSize: 
 11984676742758, usedBytes: 879609302221, usedPct: 0.07339449541286318, 
 disable threshold: 0.85
 2013-04-29 13:25:49,327 DEBUG [cloud.storage.StorageManagerImpl] 
 (Job-Executor-10:job-9908) Checking pool: 204 for volume allocation 
 [Vol[10663|vm=6189|ROOT]], maxSize : 11984676742758, totalAllocatedSize : 
 588879744000, askingSize : 8589934592, allocated disable threshold: 0.85
 2013-04-29 13:25:49,327 DEBUG 
 [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) 
 FirstFitStoragePoolAllocator returning 1 suitable storage pools
 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) Trying to find a potenial host and associated 
 storage pools from the suitable host/pool lists for this VM
 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) Checking if host: 17 can access any suitable 
 storage pool for volume: ROOT
 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) Host: 17 can access pool: 204
 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) Found a potential host id: 17 name: ksrv2-000 and 
 associated storage pools for this VM
 2013-04-29 13:25:49,332 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) Returning Deployment Destination: 
 Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))]
  : 
 Dest[Zone(1)-Pod(1)-Cluster(1)-Host(17)-Storage(Volume(10663|ROOT--Pool(204))]
 2013-04-29 13:25:49,370 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-10:job-9908) VM state transitted from :Stopped to Starting with 
 event: StartRequestedvm's original host id: null new host id: null host id 
 before state transition: null
 

[jira] [Resolved] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool

[Prachi Damle (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prachi Damle resolved CLOUDSTACK-2281.
--

Resolution: Fixed

 VM fails to deploy due to planner selecting deleted pool
 

 Key: CLOUDSTACK-2281
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2281
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Management Server
Affects Versions: 4.1.0
Reporter: Marcus Sorensen
Assignee: Prachi Damle
 Fix For: 4.1.0

 Attachments: job9908.txt


 Having trouble tracking this down. Here's what I did:
 Created a 4.1 advanced zone
 added primary storage A
 deployed a template
 deployed vms
 added new primary storages
 migrated VMs from primary storage A to others
 removed initial primary storage A
 try to deploy new vm from template, not working. It looks like the allocator 
 correctly finds and decides to use pool id 204, but somehow deployment is 
 actually attempted on deleted pool 202. See Returning Deployment 
 Destination and DeploymentPlan is provided:
 2013-04-29 13:25:49,293 DEBUG [allocator.impl.FirstFitAllocator] 
 (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Found a suitable host, 
 adding to list: 19
 2013-04-29 13:25:49,294 DEBUG [allocator.impl.FirstFitAllocator] 
 (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Host Allocator returning 
 4 suitable hosts
 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) Checking suitable pools for volume (Id, Type): 
 (10663,ROOT)
 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) We need to allocate new storagepool for this volume
 2013-04-29 13:25:49,299 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) Calling StoragePoolAllocators to find suitable 
 pools
 2013-04-29 13:25:49,302 DEBUG 
 [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) 
 Looking for pools in dc: 1  pod:1  cluster:1
 2013-04-29 13:25:49,304 DEBUG 
 [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) 
 FirstFitStoragePoolAllocator has 1 pools to check for allocation
 2013-04-29 13:25:49,304 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) 
 Checking if storage pool is suitable, name: sansrv-row2-rack0 ,poolId: 204
 2013-04-29 13:25:49,304 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) 
 Is localStorageAllocationNeeded? false
 2013-04-29 13:25:49,305 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) 
 Is storage pool shared? true
 2013-04-29 13:25:49,309 DEBUG [cloud.storage.StorageManagerImpl] 
 (Job-Executor-10:job-9908) Checking pool 204 for storage, totalSize: 
 11984676742758, usedBytes: 879609302221, usedPct: 0.07339449541286318, 
 disable threshold: 0.85
 2013-04-29 13:25:49,327 DEBUG [cloud.storage.StorageManagerImpl] 
 (Job-Executor-10:job-9908) Checking pool: 204 for volume allocation 
 [Vol[10663|vm=6189|ROOT]], maxSize : 11984676742758, totalAllocatedSize : 
 588879744000, askingSize : 8589934592, allocated disable threshold: 0.85
 2013-04-29 13:25:49,327 DEBUG 
 [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) 
 FirstFitStoragePoolAllocator returning 1 suitable storage pools
 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) Trying to find a potenial host and associated 
 storage pools from the suitable host/pool lists for this VM
 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) Checking if host: 17 can access any suitable 
 storage pool for volume: ROOT
 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) Host: 17 can access pool: 204
 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) Found a potential host id: 17 name: ksrv2-000 and 
 associated storage pools for this VM
 2013-04-29 13:25:49,332 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-10:job-9908) Returning Deployment Destination: 
 Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))]
  : 
 Dest[Zone(1)-Pod(1)-Cluster(1)-Host(17)-Storage(Volume(10663|ROOT--Pool(204))]
 2013-04-29 13:25:49,370 DEBUG [cloud.capacity.CapacityManagerImpl] 
 (Job-Executor-10:job-9908) VM state transitted from :Stopped to Starting with 
 event: StartRequestedvm's original host id: null new host id: null host id 
 before state transition: null
 2013-04-29 13:25:49,370 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
 (Job-Executor-10:job-9908) Successfully transitioned to start state for 
 VM[User|marcus-deleteme] 

[jira] [Created] (CLOUDSTACK-2681) When failed to apply port forwarding rules, message showed: Failed to delete port forwarding rule

[Sheng Yang (JIRA)]

Sheng Yang created CLOUDSTACK-2681:
--

 Summary: When failed to apply port forwarding rules, message 
showed: Failed to delete port forwarding rule
 Key: CLOUDSTACK-2681
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2681
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.2.0
Reporter: Sheng Yang
Assignee: Sheng Yang
Priority: Minor
 Fix For: 4.2.0


Because after failed applying, mgmt server would try to revoke it, then failed 
again.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CLOUDSTACK-2682) Redundant router: Router switch to MASTER then immediately switch back to BACKUP would failed to work

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666850#comment-13666850
 ] 

ASF subversion and git services commented on CLOUDSTACK-2682:
-

Commit a21a4e5ac43af0f225b6e56e3e73ea7e570510d9 in branch refs/heads/master 
from Sheng Yang sheng.y...@citrix.com
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a21a4e5 ]

CLOUDSTACK-2682: Sleep 1 second before switch to BACKUP

To prevent backup.sh preempt master.sh when keepalived switch to MASTER then
back to BACKUP immediately.

Since it would take at least 3 seconds for BACKUP to switch to MASTER(vrrp
timeout), the fix won't cause chaos when keepalive try to switch to MASTER.


 Redundant router: Router switch to MASTER then immediately switch back to 
 BACKUP would failed to work
 -

 Key: CLOUDSTACK-2682
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2682
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
Affects Versions: 4.2.0
Reporter: Sheng Yang
Assignee: Sheng Yang
 Fix For: 4.2.0


 The scripts master.sh and backup.sh are called at the same time when the 
 backup RvR switch to MASTER then immediately back to BACKUP, because of the 
 file lock mechanism we're using, there is a chance that backup.sh may be 
 called 
 before master.sh, then result in router seems in MASTER state(though 
 keepalived 
 still reports BACKUP state). 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira