[jira] [Updated] (CLOUDSTACK-2251) Automation: Dedicated Resources - Public IP Addresses and VLANs per Tenant
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2251: - Summary: Automation: Dedicated Resources - Public IP Addresses and VLANs per Tenant (was: Automation: Set VMware cluster max. limit based on HV version) Automation: Dedicated Resources - Public IP Addresses and VLANs per Tenant --- Key: CLOUDSTACK-2251 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2251 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti 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-2259) Automation: Load Balancing using External Provider for Shared Networks
Sudha Ponnaganti created CLOUDSTACK-2259: Summary: Automation: Load Balancing using External Provider for Shared Networks Key: CLOUDSTACK-2259 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2259 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti -- 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-2260) Automation: Ability to delete Events and Alerts: Select multiple alerts and events.
Sudha Ponnaganti created CLOUDSTACK-2260: Summary: Automation: Ability to delete Events and Alerts: Select multiple alerts and events. Key: CLOUDSTACK-2260 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2260 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti -- 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-2262) Automation: health monitoring for load balanced instances
Sudha Ponnaganti created CLOUDSTACK-2262: Summary: Automation: health monitoring for load balanced instances Key: CLOUDSTACK-2262 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2262 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti -- 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-2263) QA : nTier Apps 2.0 Support for Netscaler as internal LB provider
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2263: - Summary: QA : nTier Apps 2.0 Support for Netscaler as internal LB provider (was: QA : nTier Apps 2.0 Support for Netscaler as LB) QA : nTier Apps 2.0 Support for Netscaler as internal LB provider - Key: CLOUDSTACK-2263 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2263 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti 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-2264) Automation: nTier Apps 2.0 Support Netscaler as internal LB provider
Sudha Ponnaganti created CLOUDSTACK-2264: Summary: Automation: nTier Apps 2.0 Support Netscaler as internal LB provider Key: CLOUDSTACK-2264 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2264 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti -- 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-2265) Automation : Health Monitoring for LB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti resolved CLOUDSTACK-2265. -- Resolution: Duplicate Assignee: Sudha Ponnaganti Automation : Health Monitoring for LB - Key: CLOUDSTACK-2265 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2265 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Reporter: Sudha Ponnaganti Assignee: Sudha Ponnaganti 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] [Closed] (CLOUDSTACK-2265) Automation : Health Monitoring for LB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-2265. Automation : Health Monitoring for LB - Key: CLOUDSTACK-2265 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2265 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Reporter: Sudha Ponnaganti Assignee: Sudha Ponnaganti 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] [Closed] (CLOUDSTACK-471) Limit resources using CPU/RAM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti closed CLOUDSTACK-471. --- Limit resources using CPU/RAM - Key: CLOUDSTACK-471 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-471 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.0.0 Reporter: Jasper Wonnink Assignee: Sanjay Tripathi Fix For: 4.2.0 Request was already in the old tracker but i would like to re-open it in this tracker. http://bugs.cloudstack.org/browse/CS-6668 We would like the ability to set resources limits based on CPU (or RAM). This way we can give a user access to 100 compute units (cores) and they can decide for themselves if they want 50 dual cores, 25 quadcores.. etc etc. -- 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-2268) Automation : Support remove network over VMware deployments with dvSwitch
Sudha Ponnaganti created CLOUDSTACK-2268: Summary: Automation : Support remove network over VMware deployments with dvSwitch Key: CLOUDSTACK-2268 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2268 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti -- 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-2271) Automation - Configurable setting to use linked clones or not on VMware
Sudha Ponnaganti created CLOUDSTACK-2271: Summary: Automation - Configurable setting to use linked clones or not on VMware Key: CLOUDSTACK-2271 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2271 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti -- 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-2272) Automation - DeployVM User data enhancement
Sudha Ponnaganti created CLOUDSTACK-2272: Summary: Automation - DeployVM User data enhancement Key: CLOUDSTACK-2272 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2272 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti -- 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-2273) Automation - Change account
Sudha Ponnaganti created CLOUDSTACK-2273: Summary: Automation - Change account Key: CLOUDSTACK-2273 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2273 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti -- 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-2273) Automation : Change Account membership
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-2273: - Summary: Automation : Change Account membership (was: Automation - Change account ) Automation : Change Account membership --- Key: CLOUDSTACK-2273 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2273 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti 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-2059) Support remove network over VMware deployments with dvSwitch
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ram Ganesh updated CLOUDSTACK-2059: --- Affects Version/s: 4.2.0 Support remove network over VMware deployments with dvSwitch Key: CLOUDSTACK-2059 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2059 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Sateesh Chodapuneedi Assignee: Sateesh Chodapuneedi Fix For: 4.2.0 Remove network from user VM is supported in VMware only for standard vSwitches. This need to be supported for dvSwitches as well. -- 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-2274) The detail view doesn't recover from loading status when trying to delete a zone with physical network on it
Isaac Chiang created CLOUDSTACK-2274: Summary: The detail view doesn't recover from loading status when trying to delete a zone with physical network on it Key: CLOUDSTACK-2274 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2274 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Environment: Mater Reporter: Isaac Chiang Priority: Minor When trying to delete a zone without removing the physical network first, it shows an error message with The zone is not deletable because there are pods in this zone. Once you close the message dialog, the detail view wont recover from loading stage. -- 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-2274) The detail view doesn't recover from loading status when trying to delete a zone with physical network on it
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isaac Chiang updated CLOUDSTACK-2274: - Attachment: Screen Shot 2013-04-29 at 11.05.17 AM.png Screen Shot 2013-04-29 at 11.05.11 AM.png The detail view doesn't recover from loading status when trying to delete a zone with physical network on it Key: CLOUDSTACK-2274 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2274 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Environment: Mater Reporter: Isaac Chiang Priority: Minor Labels: ui Attachments: Screen Shot 2013-04-29 at 11.05.11 AM.png, Screen Shot 2013-04-29 at 11.05.17 AM.png When trying to delete a zone without removing the physical network first, it shows an error message with The zone is not deletable because there are pods in this zone. Once you close the message dialog, the detail view wont recover from loading stage. -- 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-741) Granular Global Parameters
[ https://issues.apache.org/jira/browse/CLOUDSTACK-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644367#comment-13644367 ] ASF subversion and git services commented on CLOUDSTACK-741: Commit deaf9106ca557a938edf25bee65cf6b4eb3ac03f in branch refs/heads/master from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=deaf910 ] CLOUDSTACK-741: Granular Global Parameters and adding fixes for CLOUDSTACK-2176, CLOUDSTACK-2198, CLOUDSTACK-2200 Adding the zone, cluster, account level parameters The parameters at scope (zone/cluster/pool/account) can be updated by updateConfiguration API with additional parameter zoneid/clusterid/accountid/storagepoolid Whenever these scoped parameters are used in CS they get value from the corresponding details table if not defined get value from global parameter. Same with the listConfiguration API with additional parameter zoneid/clusterid/accountid/storagepoolid Granular Global Parameters -- Key: CLOUDSTACK-741 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-741 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Reporter: Manan Shah Assignee: Harikrishna Patnala Fix For: 4.2.0 Requirements described at: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Granular+Global+Config+Parameters Requirements discussion email thread link: -- 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-2275) Documentation for Egress Firewall Support
Radhika Nair created CLOUDSTACK-2275: Summary: Documentation for Egress Firewall Support Key: CLOUDSTACK-2275 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2275 Project: CloudStack Issue Type: Sub-task Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Reporter: Radhika Nair Assignee: Radhika Nair -- 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-1567) Document ability to delete events and alerts
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-1567. -- Resolution: Fixed Document ability to delete events and alerts Key: CLOUDSTACK-1567 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1567 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.2.0 Reporter: Jessica Tomechak Assignee: Radhika Nair Priority: Minor Fix For: 4.2.0 Attachments: events.html -- 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-492) Document procedure to choose default System Offering for System VMs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radhika Nair resolved CLOUDSTACK-492. - Resolution: Fixed Document procedure to choose default System Offering for System VMs --- Key: CLOUDSTACK-492 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-492 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.0.0 Reporter: Kirk Kosinski Assignee: Radhika Nair Priority: Minor Labels: adminguide While it is possible to manually change the System Offering for a particular System VM, a CloudStack administrator may want to change the System Offering used by default for System VMs. It would be useful for this procedure to be documented. The following procedure works for me on CloudStack 3.0.2 and 4.0.0-incubating. 1. Create a new system offering with the desired settings. This can be done via UI under the Service Offerings tab. 2. Back up the database. mysqldump -u root -p cloud | bzip2 cloud_backup.sql.bz2 3. Open a mysql prompt to be able to run queries in later steps on the cloud database. mysql -u cloud -p cloud 4. In the disk_offering table in the database, identify the original default offering and the new offering you wish to be used by default. Make a note of their id. select id,name,unique_name,type from disk_offering; 5. Set unique_name = NULL for the original default offering. It is important to use the correct value for id. update disk_offering set unique_name = NULL where id = 10; 6. For the new offering you wish to be used by default, set unique_name = 'Cloud.com-ConsoleProxy' (for the default CPVM offering) or 'Cloud.com-SecondaryStorage' (for the default SSVM offering). update disk_offering set unique_name = 'Cloud.com-ConsoleProxy' where id = 16; 7. Restart CloudStack. This is required because the default offerings are loaded into memory at start-up. service cloud-management restart 8. Destroy the existing CPVM or SSVM and wait for it to be recreated. The new CPVM or SSVM will be configured with the new offering. Note that CLOUDSTACK-338 seems to be requesting that the string used in unique_name be changed. When that happens, this procedure would need to be updated with the correct string. -- 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-2274) The detail view doesn't recover from loading status when trying to delete a zone with physical network on it
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Isaac Chiang reassigned CLOUDSTACK-2274: Assignee: Isaac Chiang The detail view doesn't recover from loading status when trying to delete a zone with physical network on it Key: CLOUDSTACK-2274 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2274 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Environment: Mater Reporter: Isaac Chiang Assignee: Isaac Chiang Priority: Minor Labels: ui Attachments: Screen Shot 2013-04-29 at 11.05.11 AM.png, Screen Shot 2013-04-29 at 11.05.17 AM.png When trying to delete a zone without removing the physical network first, it shows an error message with The zone is not deletable because there are pods in this zone. Once you close the message dialog, the detail view wont recover from loading stage. -- 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-2201) Failed to start MS after fresh installation
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644374#comment-13644374 ] Srikanteswararao Talluri commented on CLOUDSTACK-2201: -- Is some one looking at this? Failed to start MS after fresh installation Key: CLOUDSTACK-2201 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2201 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Install and Setup Affects Versions: 4.2.0 Environment: CentOS 6.3 build Branch master Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.2.0 Attachments: CLOUDSTACK-2201.rar Step 1 :Install MS from master branch build Step 2 : execute cloudstack-setup-databases cloud:password@localhost --deploy-as=root:password cloudstack-setup-management Actual result Failed to management server, with below error in MS log 2013-04-25 22:01:06,030 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) DB version = 4.0.0 Code Version = 4.2.0-SNAPSHOT 2013-04-25 22:01:06,030 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Database upgrade must be performed from 4.0.0 to 4.2.0-SNAPSHOT 2013-04-25 22:01:06,030 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) The end upgrade version is actually at 4.1.0 but our management server code version is at 4.2.0-SNAPSHOT 2013-04-25 22:01:06,036 ERROR [utils.component.ComponentContext] (Timer-1:null) System integrity check failed. Refuse to startup Is it happening due to below check-in ? Commit 099677a1244cd55fb98d3c40ee7881223dd9ac7c by chip.childers CLOUDSTACK-2172: adding database upgrade to 4.1.0 in PremiumDatabaseUpgradeChecker Add migration to 4.1.0 in the PremiumDatabaseUpgradeChecker, like in the DatabaseUpgradeChecker. -- 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-957) Localization -- Add UK keyboard support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi updated CLOUDSTACK-957: --- Status: Ready To Review (was: In Progress) Localization -- Add UK keyboard support --- Key: CLOUDSTACK-957 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-957 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: VNC Proxy Affects Versions: 4.1.0 Reporter: Fang Wang Assignee: Sanjay Tripathi Add UK keyboard support to Cloudstack -- 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-301) Nexus 1000v DVS integration is not functional
[ https://issues.apache.org/jira/browse/CLOUDSTACK-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sateesh Chodapuneedi resolved CLOUDSTACK-301. - Resolution: Fixed Nexus 1000v DVS integration is not functional - Key: CLOUDSTACK-301 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-301 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: pre-4.0.0 Reporter: Sailaja Mada Assignee: Sateesh Chodapuneedi Priority: Critical Fix For: 4.2.0 Attachments: api-server.log, catalina.out, management-server.log Setup: Management Server [ RHEL 6.3] ,VMWARE - ESXi5 , Nexus : Nexus1000v.4.2.1.SV1.5.1 Build :CloudStack-non-OSS-106.tar Steps: 1. Deploy VSM @ Vcenter 2. Create port-profile sailajapp 3. Set global setting vmware.use.nexus.vswitch to true 4. Tried to configure advanced Zone with traffic lable as sailajapp Observation: It Failed to add Cluster with Nexus Switch . ERROR Log: 2012-10-09 14:10:04,301 INFO [hypervisor.vmware.VmwareServerDiscoverer] (catalina-exec-23:null) Detected private network label : sailajapp 2012-10-09 14:10:04,303 INFO [hypervisor.vmware.VmwareServerDiscoverer] (catalina-exec-23:null) Detected public network label : sailajapp 2012-10-09 14:10:04,305 INFO [hypervisor.vmware.VmwareServerDiscoverer] (catalina-exec-23:null) Detected guest network label : sailajapp 2012-10-09 14:10:04,310 INFO [vmware.manager.VmwareManagerImpl] (catalina-exec-23:null) Found empty vsmMapVO. 2012-10-09 14:10:04,313 DEBUG [vmware.resource.VmwareContextFactory] (catalina-exec-23:null) initialize VmwareContext. url: https://10.102.125.241/sdk/vimService, username: administrator, password: f** 2012-10-09 14:10:13,505 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Skip capacity scan due to there is no Primary Storage UPintenance mode 2012-10-09 14:10:14,053 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 0 routers. 2012-10-09 14:10:19,354 INFO [vmware.manager.VmwareManagerImpl] (catalina-exec-23:null) Calling prepareNetwork : com.cloud.hypervisor.vmware.util.VmwareContext@40e83e52 2012-10-09 14:10:19,355 INFO [vmware.manager.VmwareManagerImpl] (catalina-exec-23:null) Preparing Network on sailajapp 2012-10-09 14:10:19,824 INFO [vmware.mo.HypervisorHostHelper] (catalina-exec-23:null) Found Ethernet port profile sailajapp 2012-10-09 14:10:20,298 INFO [vmware.mo.HypervisorHostHelper] (catalina-exec-23:null) Port profile cloud.private.untagged.0.1-sailajapp not found. 2012-10-09 14:10:20,298 ERROR [vmware.mo.HypervisorHostHelper] (catalina-exec-23:null) Failed to retrieve required credentials of Nexus VSM from database. 2012-10-09 14:10:20,301 WARN [hypervisor.vmware.VmwareServerDiscoverer] (catalina-exec-23:null) Unable to connect to Vmware vSphere server. service address: 10.102.125.241 2012-10-09 14:10:20,528 WARN [cloud.resource.ResourceManagerImpl] (catalina-exec-23:null) Unable to find the server resources at http://10.102.125.241/newdc/newcluster 2012-10-09 14:10:20,574 WARN [api.commands.AddClusterCmd] (catalina-exec-23:null) Exception: com.cloud.exception.DiscoveryException: Unable to add the external cluster at com.cloud.resource.ResourceManagerImpl.discoverCluster(ResourceManagerImpl.java:487) at com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34) at com.cloud.api.commands.AddClusterCmd.execute(AddClusterCmd.java:153) 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
[jira] [Commented] (CLOUDSTACK-2138) Web Client UI - Putting all translations files on master branch and automate with transifex upload/download
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644393#comment-13644393 ] ASF subversion and git services commented on CLOUDSTACK-2138: - Commit 509cfa98567f3d64b6da8bcb50c3d18e6d2bc122 in branch refs/heads/master from [~milamber] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=509cfa9 ] CLOUDSTACK-2138 - add a sync-transifex-ui.sh script to automate the exchange between CloudStack L10N resource files and Transifex CS-UI resource files Signed-off-by: Milamber milam...@apache.org Web Client UI - Putting all translations files on master branch and automate with transifex upload/download --- Key: CLOUDSTACK-2138 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2138 Project: CloudStack Issue Type: Task Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Milamber Assignee: Milamber Labels: ui Fix For: 4.2.0 This Jira ticket to follow this tasks: Add missing translations relative to 4.1 version (resources files and index.jsp) Make alphabetical order for keys in messages_xx.properties Convert all messages_xx.properties in ASCII with unicode Add a double-backslash before quote ( \\' ) in messages_xx.properties for some languages (to fix code errors in dictonary.jsp generated file) Create a script to automate the conversion and communication with transifex for upload/download (if it's possible with transifex client) -- 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-2146) system vm scaleup failed ;{ scalevirtualmachineresponse : {errorcode:530,cserrorcode:9999,errortext:Failed to scale vm} }
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harikrishna Patnala reassigned CLOUDSTACK-2146:
---
Assignee: Harikrishna Patnala
system vm scaleup failed ;{ scalevirtualmachineresponse :
{errorcode:530,cserrorcode:,errortext:Failed to scale vm} }
---
Key: CLOUDSTACK-2146
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2146
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: Hyp:Xenserver ;commit
2057221f4f1fd5afde422b367fc416d4e44275cb
Reporter: prashant kumar mishra
Assignee: Harikrishna Patnala
Priority: Critical
Fix For: 4.2.0
Attachments: access_log.2013-04-23.txt, apilog.log, catalina.out,
management-server.log, screenshot-1.jpg, SMlog, xensource.log
Tried to scaleup system vms ,it failed with API response {
scalevirtualmachineresponse :
{errorcode:530,cserrorcode:,errortext:Failed to scale vm} } and
db got updated with new serivce offering .
Steps to reproduce
-
1-Create a system offering for console pvm say s1(ram= 1GB,cpu=1GHZ)
2-Scale up vm using API
Expected
---
VM should get scaled up to new SO
Actual
1-Scaleup vm failed
2-New service offering got updated for console pvm in DB
BD
--
mysql select *from vm_instance where id=15\G;
*** 1. row ***
id: 15
name: v-15-VM
uuid: 0f8e8319-fdb3-4da1-b50c-aab2827d1c06
instance_name: v-15-VM
state: Running
vm_template_id: 1
guest_os_id: 133
private_mac_address: 06:53:c8:00:00:03
private_ip_address: 10.147.41.212
pod_id: 1
data_center_id: 1
host_id: 5
last_host_id: 5
proxy_id: 15
proxy_assign_time: 2013-04-23 11:37:51
vnc_password: kEsfw5aA0VPlVqY3ohN7gWFN3Cr9BGFM41J+fcWpPTM=
ha_enabled: 0
limit_cpu_use: 0
update_count: 7
update_time: 2013-04-23 11:30:36
created: 2013-04-23 11:24:07
removed: NULL
type: ConsoleProxy
vm_type: ConsoleProxy
account_id: 1
domain_id: 1
service_offering_id: 19
reservation_id: d1cf507f-6a1f-4f3d-a380-59f57815a0b3
hypervisor_type: XenServer
disk_offering_id: NULL
cpu: NULL
ram: NULL
owner: NULL
speed: NULL
host_name: NULL
display_name: NULL
desired_state: NULL
1 row in set (0.01 sec)
mysql select * from service_offering_view where id=19\G;
*** 1. row ***
id: 19
uuid: b970c088-b4ba-4693-8a79-57ab84ad5c2b
name: console
display_text: console
created: 2013-04-22 18:40:56
tags: NULL
removed: NULL
use_local_storage: 0
system_use: 1
cpu: 1
speed: 1000
ram_size: 1024
nw_rate: NULL
mc_rate: NULL
ha_enabled: 0
limit_cpu_use: 0
host_tag: NULL
default_use: 0
vm_type: consoleproxy
sort_key: 0
domain_id: NULL
domain_uuid: NULL
domain_name: NULL
domain_path: NULL
1 row in set (0.00 sec)
snippet of Management Server log
--
2013-04-23 10:03:03,095 DEBUG [agent.transport.Request]
(catalina-exec-24:null) Seq 5-264962068: Sending { Cmd , MgmtId:
7635042566263, via: 5, Ver: v1, Flags: 100111,
[{ScaleVmCommand:{vm:{id:1,name:v-15-VM,cpus:1,speed:1000,minRam:1024,maxRam:1024,rebootOnCrash:false,enableHA:false,limitCpuUse:false},vmName:v-15-VM,cpus:1,speed:1000,minRam:1024,maxRam:1024,wait:0}}]
}
2013-04-23 10:03:03,096 DEBUG [agent.transport.Request]
(catalina-exec-24:null) Seq 5-264962068: Executing: { Cmd , MgmtId:
7635042566263, via: 5, Ver: v1, Flags: 100111,
[{ScaleVmCommand:{vm:{id:1,name:v-15-VM,cpus:1,speed:1000,minRam:1024,maxRam:1024,rebootOnCrash:false,enableHA:false,limitCpuUse:false},vmName:v-15-VM,cpus:1,speed:1000,minRam:1024,maxRam:1024,wait:0}}]
}
2013-04-23 10:03:03,097 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-7:null) Seq 5-264962068: Executing request
2013-04-23 10:03:03,516 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-7:null) scaling VM v-15-VM is successful on host
com.xensource.xenapi.Host@d9987304
[jira] [Commented] (CLOUDSTACK-2138) Web Client UI - Putting all translations files on master branch and automate with transifex upload/download
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644435#comment-13644435 ] ASF subversion and git services commented on CLOUDSTACK-2138: - Commit 8e5186daf1ffdf6a8c011dd803bd7b7094af1654 in branch refs/heads/master from [~milamber] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8e5186d ] CLOUDSTACK-2138 - Add Arabic L10N, fix a issue with sed on OSX, detab some lines Web Client UI - Putting all translations files on master branch and automate with transifex upload/download --- Key: CLOUDSTACK-2138 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2138 Project: CloudStack Issue Type: Task Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Milamber Assignee: Milamber Labels: ui Fix For: 4.2.0 This Jira ticket to follow this tasks: Add missing translations relative to 4.1 version (resources files and index.jsp) Make alphabetical order for keys in messages_xx.properties Convert all messages_xx.properties in ASCII with unicode Add a double-backslash before quote ( \\' ) in messages_xx.properties for some languages (to fix code errors in dictonary.jsp generated file) Create a script to automate the conversion and communication with transifex for upload/download (if it's possible with transifex client) -- 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-2107) Only scaling up memory(ram) in not triggering vm live migration ;Unable to scale vm due to Catch exception com.xensource.xenapi.Types$HostNotEnoughFreeMemory when s
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harikrishna Patnala reassigned CLOUDSTACK-2107:
---
Assignee: Harikrishna Patnala
Only scaling up memory(ram) in not triggering vm live migration ;Unable to
scale vm due to Catch exception
com.xensource.xenapi.Types$HostNotEnoughFreeMemory when scaling VM:i-2-35-VM
due to Not enough host memory is available to perform this operation
Key: CLOUDSTACK-2107
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2107
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: prashant kumar mishra
Assignee: Harikrishna Patnala
Priority: Critical
Fix For: 4.2.0
Attachments: access_log.2013-04-19.txt, apilog.log, catalina.out,
management-server.log, RamScaleUp.png
For cpu scalup ,vms getting live migrated to other host in cluster if no
resources are available on current host ,but not in case of RAM Scaleup
Steps to reproduce
1-Create zone-pod-cluster with one host
2-Deploy vm so that no resource left on host
3-Add another host in same cluster
4- Try to scale up vm's ram (in new service offering keep cpu speed same as
previous ,increase ram by 500 MB)
Expected
--
since there is no resource left on current host vm should get live migrate to
other available host and scaleup should be successful .
Actual
-
scaleup failed due to not enough resource on current host,;CS did not try to
live migrate vm to other host on cluster
My observation
--
1-VM are getting live migrated in case of cpu scale up if current host does
not have resource
2-Tried to scaleup vm to service offering x failed but able to deploy a new
vm with same service offering
Service offering details
--
Tried to scaleup from SO 20 to SO 22
1-SO 22
mysql select * from service_offering_view where id=22 \G
*** 1. row ***
id: 22
uuid: 528443f5-f044-4e64-b1e1-87f6c0136921
name: smallcpu2ram
display_text: smallcpu2ram
created: 2013-04-18 18:48:17
tags: NULL
removed: NULL
use_local_storage: 0
system_use: 0
cpu: 1
speed: 1500
ram_size: 1024
nw_rate: NULL
mc_rate: NULL
ha_enabled: 0
limit_cpu_use: 0
host_tag: NULL
default_use: 0
vm_type: NULL
sort_key: 0
domain_id: NULL
domain_uuid: NULL
domain_name: NULL
domain_path: NULL
1 row in set (0.00 sec)
2-SO 20
mysql select * from service_offering_view where id=20 \G
*** 1. row ***
id: 20
uuid: 4bafd8c7-c8cc-42db-a630-61909556803b
name: smallcpu2
display_text: smallcpu2
created: 2013-04-18 18:39:59
tags: NULL
removed: NULL
use_local_storage: 0
system_use: 0
cpu: 1
speed: 1500
ram_size: 500
nw_rate: NULL
mc_rate: NULL
ha_enabled: 0
limit_cpu_use: 0
host_tag: NULL
default_use: 0
vm_type: NULL
sort_key: 5
domain_id: NULL
domain_uuid: NULL
domain_name: NULL
domain_path: NULL
1 row in set (0.00 sec)
Snippet of MS Log
---
2013-04-19 07:40:58,312 DEBUG [agent.transport.Request] (DirectAgent-12:null)
Seq 1-521863179: Processing: { Ans: , MgmtId: 7191687856187, via: 1, Ver:
v1, Flags: 110, [{ScaleVmAnswer:{result:false,details:Catch exception
com.xensource.xenapi.Types$HostNotEnoughFreeMemory when scaling VM:i-2-35-VM
due to Not enough host memory is available to perform this
operation,wait:0}}] }
2013-04-19 07:40:58,312 DEBUG [agent.transport.Request]
(catalina-exec-6:null) Seq 1-521863179: Received: { Ans: , MgmtId:
7191687856187, via: 1, Ver: v1, Flags: 110, { ScaleVmAnswer } }
2013-04-19 07:40:58,312 ERROR [cloud.vm.VirtualMachineManagerImpl]
(catalina-exec-6:null) Unable to scale vm due to Catch exception
com.xensource.xenapi.Types$HostNotEnoughFreeMemory when scaling VM:i-2-35-VM
due to Not enough host memory is available to perform this operation
2013-04-19 07:40:58,313 DEBUG
[jira] [Commented] (CLOUDSTACK-2276) NPE while attaching the volume to the instance which is created from ROOT Disk Snapshot
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644439#comment-13644439
]
Sailaja Mada commented on CLOUDSTACK-2276:
--
NPE is observed only when tried to attach the volume to the same instance[Which
root disk was used to create the snapshot and the snapshot to create volume).
NPE while attaching the volume to the instance which is created from ROOT
Disk Snapshot
---
Key: CLOUDSTACK-2276
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2276
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Storage Controller
Affects Versions: 4.2.0
Reporter: Sailaja Mada
Priority: Critical
Setup: Advanced Networking Zone with Xen 6.1 , MS -RHEL 6.3
Steps:
1. Deploy instance as ROOT admin
2. Create the snapshot from this instance ROOT disk
3. Create Volume from this snapshot
4. Try to attach this volume to the instance .
Observation:
NPE while attaching the volume to the instance which is created from ROOT
Disk Snapshot
2013-04-29 16:51:02,412 DEBUG [cloud.api.ApiServlet] (catalina-exec-2:null)
===END=== 10.144.6.19 -- GET
command=attachVolumeid=3c8487fd-a30f-42d6-bc14-e19ec6c4090cvirtualMachineId=cc2a94bb-bdf0-4d36-9f2c-a501c75f53ddresponse=jsonsessionkey=50KnW0aaOd0wvF2hspe71pXsfqI%3D_=1367234593280
2013-04-29 16:51:02,450 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-41:job-57) Executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd for job-57
2013-04-29 16:51:02,528 DEBUG [cloud.storage.StorageManagerImpl]
(Job-Executor-41:job-57) Checking pool: 1 for volume allocation
[Vol[26|vm=null|DATADISK]], maxSize : 1759218630656, totalAllocatedSize :
108885410816, askingSize : 21474836480, allocated disable threshold: 0.85
2013-04-29 16:51:02,530 DEBUG [cloud.storage.VolumeManagerImpl]
(Job-Executor-41:job-57) Trying to create
org.apache.cloudstack.storage.volume.VolumeObject@28b8ef9e on
org.apache.cloudstack.storage.datastore.DefaultPrimaryDataStore@57b82f5
2013-04-29 16:51:02,566 DEBUG [agent.transport.Request]
(Job-Executor-41:job-57) Seq 1-1019093539: Sending { Cmd , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 100111,
[{storage.CreateCommand:{volId:26,pool:{id:1,uuid:ba45e9e1-5b6f-3005-a920-00c02a73d9e1,host:10.102.192.100,path:/cpg_vol/sailaja/masterxenps,port:2049,type:NetworkFilesystem},diskCharacteristics:{size:21474836480,tags:[],type:DATADISK,name:VolumefromsnapshotofROOT15,useLocalStorage:false,recreatable:true,diskOfferingId:1,volumeId:26},templateUrl:c2f7de45-83c8-40a8-9937-a450b0d8660a,wait:0}}]
}
2013-04-29 16:51:02,577 DEBUG [agent.transport.Request]
(Job-Executor-41:job-57) Seq 1-1019093539: Executing: { Cmd , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 100111,
[{storage.CreateCommand:{volId:26,pool:{id:1,uuid:ba45e9e1-5b6f-3005-a920-00c02a73d9e1,host:10.102.192.100,path:/cpg_vol/sailaja/masterxenps,port:2049,type:NetworkFilesystem},diskCharacteristics:{size:21474836480,tags:[],type:DATADISK,name:VolumefromsnapshotofROOT15,useLocalStorage:false,recreatable:true,diskOfferingId:1,volumeId:26},templateUrl:c2f7de45-83c8-40a8-9937-a450b0d8660a,wait:0}}]
}
2013-04-29 16:51:02,592 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-343:null) Seq 1-1019093539: Executing request
2013-04-29 16:51:02,710 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-343:null) SR retrieved for ba45e9e1-5b6f-3005-a920-00c02a73d9e1
2013-04-29 16:51:02,726 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-343:null) Checking ba45e9e1-5b6f-3005-a920-00c02a73d9e1 or SR
527d8f70-7760-6381-04bf-2d7f86c7f037 on
XS[40d72111-4e51-4bda-9d2a-65de0f1bebb5-10.102.192.13]
2013-04-29 16:51:02,809 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-04-29 16:51:03,772 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-343:null) Succesfully created VDI for
com.cloud.agent.api.storage.CreateCommand. Uuid =
2f8bfe2f-3cf4-4924-899d-0409c776430b
2013-04-29 16:51:03,773 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-343:null) Seq 1-1019093539: Response Received:
2013-04-29 16:51:03,773 DEBUG [agent.transport.Request]
(DirectAgent-343:null) Seq 1-1019093539: Processing: { Ans: , MgmtId:
73143235720, via: 1, Ver: v1, Flags: 110,
[jira] [Commented] (CLOUDSTACK-741) Granular Global Parameters
[ https://issues.apache.org/jira/browse/CLOUDSTACK-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644470#comment-13644470 ] ASF subversion and git services commented on CLOUDSTACK-741: Commit deaf9106ca557a938edf25bee65cf6b4eb3ac03f in branch refs/heads/marvin_refactor from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=deaf910 ] CLOUDSTACK-741: Granular Global Parameters and adding fixes for CLOUDSTACK-2176, CLOUDSTACK-2198, CLOUDSTACK-2200 Adding the zone, cluster, account level parameters The parameters at scope (zone/cluster/pool/account) can be updated by updateConfiguration API with additional parameter zoneid/clusterid/accountid/storagepoolid Whenever these scoped parameters are used in CS they get value from the corresponding details table if not defined get value from global parameter. Same with the listConfiguration API with additional parameter zoneid/clusterid/accountid/storagepoolid Granular Global Parameters -- Key: CLOUDSTACK-741 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-741 Project: CloudStack Issue Type: New Feature Security Level: Public(Anyone can view this level - this is the default.) Reporter: Manan Shah Assignee: Harikrishna Patnala Fix For: 4.2.0 Requirements described at: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Granular+Global+Config+Parameters Requirements discussion email thread link: -- 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-2278) TEST Ticket - Please Ignore
Chip Childers created CLOUDSTACK-2278: - Summary: TEST Ticket - Please Ignore Key: CLOUDSTACK-2278 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2278 Project: CloudStack Issue Type: Wish Security Level: Public (Anyone can view this level - this is the default.) Reporter: Chip Childers Priority: Trivial We are going to test adding comments from irc with this ticket. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644495#comment-13644495 ] Nicolas Lamirault commented on CLOUDSTACK-2207: --- I did as it says on page 50, installing a new system template : VMware Name: systemvm-vmware-4.1.0 Description: systemvm-vmware-4.1.0 URL: http://download.cloud.com/templates/burbank/burbank- systemvm-08012012.ova Zone: Choose the zone where this hypervisor is used Hypervisor: VMware Format: OVA OS Type: Debian GNU/Linux 5.0 (32-bit) Extractable: no Password Enabled: no Public: no Featured: no Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present Key: CLOUDSTACK-2207 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2207 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Nicolas Lamirault Fix For: 4.1.0 We're trying to upgrade from 2.2.14 to 4.1.0. DatabaseUpgradeChecker failed : 2013-04-26 12:11:45,205 ERROR [utils.component.ComponentContext] (Timer-1:null) System integrity check failed. Refuse to startup com.cloud.utils.exception.CloudRuntimeException: 3.0.0 VMware SystemVm template not found. Cannot upgrade system Vms at com.cloud.upgrade.dao.Upgrade2214to30.updateSystemVms(Upgrade2214to30.java:713) at com.cloud.upgrade.dao.Upgrade2214to30.performDataMigration(Upgrade2214to30.java:82) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:258) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:379) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:91) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) According to the documentation, there is no VMware SystemVm 3.0.0 to install. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2138) Web Client UI - Putting all translations files on master branch and automate with transifex upload/download
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644521#comment-13644521 ] ASF subversion and git services commented on CLOUDSTACK-2138: - Commit 9ac03ffe076fb55598d5d846924191733b91ac16 in branch refs/heads/4.1 from [~milamber] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9ac03ff ] CLOUDSTACK-2138 - backport automate script to sync L10N resource files CS repo/transifex. First sync (upload source lang / download L10N resource files) Web Client UI - Putting all translations files on master branch and automate with transifex upload/download --- Key: CLOUDSTACK-2138 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2138 Project: CloudStack Issue Type: Task Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Milamber Assignee: Milamber Labels: ui Fix For: 4.2.0 This Jira ticket to follow this tasks: Add missing translations relative to 4.1 version (resources files and index.jsp) Make alphabetical order for keys in messages_xx.properties Convert all messages_xx.properties in ASCII with unicode Add a double-backslash before quote ( \\' ) in messages_xx.properties for some languages (to fix code errors in dictonary.jsp generated file) Create a script to automate the conversion and communication with transifex for upload/download (if it's possible with transifex client) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644552#comment-13644552
]
Nicolas Lamirault commented on CLOUDSTACK-2207:
---
Hello,
This issue seems blocker ...
In file 'server/src/com/cloud/upgrade/dao/Upgrade2214to30.java',
DatabaseUpgrade depends on systemvm-vmware-3.0.0 :
//VMware
s_logger.debug(Updating VMware System Vms);
try {
//Get 3.0.0 VMware system Vm template Id
pstmt = conn.prepareStatement(select id from
`cloud`.`vm_template` where name = 'systemvm-vmware-3.0.0' and removed is
null);
rs = pstmt.executeQuery();
if(rs.next()){
long templateId = rs.getLong(1);
rs.close();
pstmt.close();
// change template type to SYSTEM
pstmt = conn.prepareStatement(update `cloud`.`vm_template`
set type='SYSTEM' where id = ?);
pstmt.setLong(1, templateId);
pstmt.executeUpdate();
pstmt.close();
// update templete ID of system Vms
pstmt = conn.prepareStatement(update `cloud`.`vm_instance`
set vm_template_id = ? where type 'User' and hypervisor_type = 'VMware');
pstmt.setLong(1, templateId);
pstmt.executeUpdate();
pstmt.close();
} else {
if (VMware){
throw new CloudRuntimeException(3.0.0 VMware SystemVm
template not found. Cannot upgrade system Vms);
} else {
s_logger.warn(3.0.0 VMware SystemVm template not
found. VMware hypervisor is not used, so not failing upgrade);
}
}
} catch (SQLException e) {
throw new CloudRuntimeException(Error while updating VMware
systemVm template, e);
}
This upgrade (2.2.14 to 3.0) can't be done without this template.
Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
Key: CLOUDSTACK-2207
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2207
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: 4.1.0
Reporter: Nicolas Lamirault
Fix For: 4.1.0
We're trying to upgrade from 2.2.14 to 4.1.0.
DatabaseUpgradeChecker failed :
2013-04-26 12:11:45,205 ERROR [utils.component.ComponentContext]
(Timer-1:null) System integrity check failed. Refuse to startup
com.cloud.utils.exception.CloudRuntimeException: 3.0.0 VMware SystemVm
template not found. Cannot upgrade system Vms
at
com.cloud.upgrade.dao.Upgrade2214to30.updateSystemVms(Upgrade2214to30.java:713)
at
com.cloud.upgrade.dao.Upgrade2214to30.performDataMigration(Upgrade2214to30.java:82)
at
com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:258)
at
com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:379)
at
com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:91)
at
com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
According to the documentation, there is no VMware SystemVm 3.0.0 to install.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CLOUDSTACK-2279) Fail to clean up networks if expunge initially had a problem
Marcus Sorensen created CLOUDSTACK-2279: --- Summary: Fail to clean up networks if expunge initially had a problem Key: CLOUDSTACK-2279 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2279 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0, 4.2.0 Reporter: Marcus Sorensen Assignee: Marcus Sorensen Priority: Critical Fix For: 4.1.0, 4.2.0 Noticed today that I had some VMs stuck in expunging state. Looked into it and found that expunge had failed for reasons that are cleared now, but subsequent tries were failing because the IP was already released, and the usage event was getting a null pointer when trying to look up the account. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644607#comment-13644607 ] ASF IRC Bot commented on CLOUDSTACK-2207: - Comment from chipc via IRC: We need to s/systemvm-*-4.1.0/systemvm-*-3.0.0/gc in the release notes. Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present Key: CLOUDSTACK-2207 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2207 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.1.0 Reporter: Nicolas Lamirault Fix For: 4.1.0 We're trying to upgrade from 2.2.14 to 4.1.0. DatabaseUpgradeChecker failed : 2013-04-26 12:11:45,205 ERROR [utils.component.ComponentContext] (Timer-1:null) System integrity check failed. Refuse to startup com.cloud.utils.exception.CloudRuntimeException: 3.0.0 VMware SystemVm template not found. Cannot upgrade system Vms at com.cloud.upgrade.dao.Upgrade2214to30.updateSystemVms(Upgrade2214to30.java:713) at com.cloud.upgrade.dao.Upgrade2214to30.performDataMigration(Upgrade2214to30.java:82) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:258) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:379) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:91) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) According to the documentation, there is no VMware SystemVm 3.0.0 to install. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-2207) Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chip Childers updated CLOUDSTACK-2207: -- Component/s: Doc Priority: Critical (was: Major) Assignee: Chip Childers Upgrade from 2.2.14 to 4.1.0 failed due to system VM not present Key: CLOUDSTACK-2207 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2207 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Doc Affects Versions: 4.1.0 Reporter: Nicolas Lamirault Assignee: Chip Childers Priority: Critical Fix For: 4.1.0 We're trying to upgrade from 2.2.14 to 4.1.0. DatabaseUpgradeChecker failed : 2013-04-26 12:11:45,205 ERROR [utils.component.ComponentContext] (Timer-1:null) System integrity check failed. Refuse to startup com.cloud.utils.exception.CloudRuntimeException: 3.0.0 VMware SystemVm template not found. Cannot upgrade system Vms at com.cloud.upgrade.dao.Upgrade2214to30.updateSystemVms(Upgrade2214to30.java:713) at com.cloud.upgrade.dao.Upgrade2214to30.performDataMigration(Upgrade2214to30.java:82) at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:258) at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:379) at com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:91) at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:50) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) According to the documentation, there is no VMware SystemVm 3.0.0 to install. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-747) nTier Apps 2.0 : Internal Load Balancing between the tiers
[ https://issues.apache.org/jira/browse/CLOUDSTACK-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alena Prokharchyk updated CLOUDSTACK-747: - Summary: nTier Apps 2.0 : Internal Load Balancing between the tiers (was: nTier Apps 2.0 : Load Balancing on all Tiers) Changed the issue subject to Internal Load Balancing between the tiers as this is what needs to be implemented to support LB on all the tiers. The example of deployment would be: 1) Create VPC with 2 tiers: Web and App 2) Provide public LB on Web tier 3) Create internal LB on the App tier, so the instances from the Web tier can access. FS link: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Internal+Load+Balancing+between+VPC+tiers nTier Apps 2.0 : Internal Load Balancing between the 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: Alena Prokharchyk 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] [Updated] (CLOUDSTACK-2035) Fix source NAT configuration with Cisco VNMC/ASA
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] haroon abdelrahman updated CLOUDSTACK-2035: --- Priority: Critical (was: Major) Fix source NAT configuration with Cisco VNMC/ASA Key: CLOUDSTACK-2035 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2035 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.2.0 Reporter: Koushik Das Assignee: Koushik Das Priority: Critical Fix For: 4.2.0 Fix source NAT configuration with Cisco VNMC/ASA -- 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-2035) Fix source NAT configuration with Cisco VNMC/ASA
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644636#comment-13644636 ] Koushik Das commented on CLOUDSTACK-2035: - Out of office till 5/3. Fix source NAT configuration with Cisco VNMC/ASA Key: CLOUDSTACK-2035 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2035 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.2.0 Reporter: Koushik Das Assignee: Koushik Das Priority: Critical Fix For: 4.2.0 Fix source NAT configuration with Cisco VNMC/ASA -- 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-2281) VM fails to deploy due to planner selecting deleted pool
Marcus Sorensen created CLOUDSTACK-2281: --- Summary: VM fails to deploy due to planner selecting deleted pool Key: CLOUDSTACK-2281 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2281 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0 Reporter: Marcus Sorensen Priority: Blocker Fix For: 4.1.0 Having trouble tracking this down. Here's what I did: Created a 4.1 advanced zone added primary storage A deployed a template deployed vms added new primary storages migrated VMs from primary storage A to others removed initial primary storage A try to deploy new vm from template, not working. It looks like the allocator correctly finds and decides to use pool id 204, but somehow deployment is actually attempted on deleted pool 202. See Returning Deployment Destination and DeploymentPlan is provided: 2013-04-29 13:25:49,293 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Found a suitable host, adding to list: 19 2013-04-29 13:25:49,294 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Host Allocator returning 4 suitable hosts 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Checking suitable pools for volume (Id, Type): (10663,ROOT) 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) We need to allocate new storagepool for this volume 2013-04-29 13:25:49,299 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Calling StoragePoolAllocators to find suitable pools 2013-04-29 13:25:49,302 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) Looking for pools in dc: 1 pod:1 cluster:1 2013-04-29 13:25:49,304 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) FirstFitStoragePoolAllocator has 1 pools to check for allocation 2013-04-29 13:25:49,304 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Checking if storage pool is suitable, name: sansrv-row2-rack0 ,poolId: 204 2013-04-29 13:25:49,304 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Is localStorageAllocationNeeded? false 2013-04-29 13:25:49,305 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Is storage pool shared? true 2013-04-29 13:25:49,309 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-9908) Checking pool 204 for storage, totalSize: 11984676742758, usedBytes: 879609302221, usedPct: 0.07339449541286318, disable threshold: 0.85 2013-04-29 13:25:49,327 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-9908) Checking pool: 204 for volume allocation [Vol[10663|vm=6189|ROOT]], maxSize : 11984676742758, totalAllocatedSize : 588879744000, askingSize : 8589934592, allocated disable threshold: 0.85 2013-04-29 13:25:49,327 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) FirstFitStoragePoolAllocator returning 1 suitable storage pools 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Trying to find a potenial host and associated storage pools from the suitable host/pool lists for this VM 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Checking if host: 17 can access any suitable storage pool for volume: ROOT 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Host: 17 can access pool: 204 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Found a potential host id: 17 name: ksrv2-000 and associated storage pools for this VM 2013-04-29 13:25:49,332 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Returning Deployment Destination: Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(17)-Storage(Volume(10663|ROOT--Pool(204))] 2013-04-29 13:25:49,370 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-9908) VM state transitted from :Stopped to Starting with event: 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] reservation id = dd7783f0-800a-481a-a407-88ec5262a397 2013-04-29 13:25:49,387 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-9908) Trying to deploy VM, vm has dcId: 1 and podId: null 2013-04-29 13:25:49,387 DEBUG [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-10:job-9908)
[jira] [Commented] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644848#comment-13644848 ] ASF IRC Bot commented on CLOUDSTACK-2281: - Comment from chipc via IRC: Marcus, is it possible that the specific deployment planner in question doesn't exclude the appropriate states from it's selction list? VM fails to deploy due to planner selecting deleted pool Key: CLOUDSTACK-2281 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2281 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0 Reporter: Marcus Sorensen Priority: Blocker Fix For: 4.1.0 Having trouble tracking this down. Here's what I did: Created a 4.1 advanced zone added primary storage A deployed a template deployed vms added new primary storages migrated VMs from primary storage A to others removed initial primary storage A try to deploy new vm from template, not working. It looks like the allocator correctly finds and decides to use pool id 204, but somehow deployment is actually attempted on deleted pool 202. See Returning Deployment Destination and DeploymentPlan is provided: 2013-04-29 13:25:49,293 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Found a suitable host, adding to list: 19 2013-04-29 13:25:49,294 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Host Allocator returning 4 suitable hosts 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Checking suitable pools for volume (Id, Type): (10663,ROOT) 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) We need to allocate new storagepool for this volume 2013-04-29 13:25:49,299 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Calling StoragePoolAllocators to find suitable pools 2013-04-29 13:25:49,302 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) Looking for pools in dc: 1 pod:1 cluster:1 2013-04-29 13:25:49,304 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) FirstFitStoragePoolAllocator has 1 pools to check for allocation 2013-04-29 13:25:49,304 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Checking if storage pool is suitable, name: sansrv-row2-rack0 ,poolId: 204 2013-04-29 13:25:49,304 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Is localStorageAllocationNeeded? false 2013-04-29 13:25:49,305 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Is storage pool shared? true 2013-04-29 13:25:49,309 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-9908) Checking pool 204 for storage, totalSize: 11984676742758, usedBytes: 879609302221, usedPct: 0.07339449541286318, disable threshold: 0.85 2013-04-29 13:25:49,327 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-9908) Checking pool: 204 for volume allocation [Vol[10663|vm=6189|ROOT]], maxSize : 11984676742758, totalAllocatedSize : 588879744000, askingSize : 8589934592, allocated disable threshold: 0.85 2013-04-29 13:25:49,327 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) FirstFitStoragePoolAllocator returning 1 suitable storage pools 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Trying to find a potenial host and associated storage pools from the suitable host/pool lists for this VM 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Checking if host: 17 can access any suitable storage pool for volume: ROOT 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Host: 17 can access pool: 204 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Found a potential host id: 17 name: ksrv2-000 and associated storage pools for this VM 2013-04-29 13:25:49,332 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Returning Deployment Destination: Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(17)-Storage(Volume(10663|ROOT--Pool(204))] 2013-04-29 13:25:49,370 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-9908) VM state transitted from :Stopped to Starting with event: StartRequestedvm's original host id: null new host id: null host id before state transition: null
[jira] [Commented] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644853#comment-13644853 ] ASF IRC Bot commented on CLOUDSTACK-2281: - Comment from chipc via IRC: And is this actually a blocker severity? Does it still occur after the expunge interval has cleaned out the datastore in question? VM fails to deploy due to planner selecting deleted pool Key: CLOUDSTACK-2281 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2281 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.1.0 Reporter: Marcus Sorensen Priority: Blocker Fix For: 4.1.0 Having trouble tracking this down. Here's what I did: Created a 4.1 advanced zone added primary storage A deployed a template deployed vms added new primary storages migrated VMs from primary storage A to others removed initial primary storage A try to deploy new vm from template, not working. It looks like the allocator correctly finds and decides to use pool id 204, but somehow deployment is actually attempted on deleted pool 202. See Returning Deployment Destination and DeploymentPlan is provided: 2013-04-29 13:25:49,293 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Found a suitable host, adding to list: 19 2013-04-29 13:25:49,294 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Host Allocator returning 4 suitable hosts 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Checking suitable pools for volume (Id, Type): (10663,ROOT) 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) We need to allocate new storagepool for this volume 2013-04-29 13:25:49,299 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Calling StoragePoolAllocators to find suitable pools 2013-04-29 13:25:49,302 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) Looking for pools in dc: 1 pod:1 cluster:1 2013-04-29 13:25:49,304 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) FirstFitStoragePoolAllocator has 1 pools to check for allocation 2013-04-29 13:25:49,304 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Checking if storage pool is suitable, name: sansrv-row2-rack0 ,poolId: 204 2013-04-29 13:25:49,304 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Is localStorageAllocationNeeded? false 2013-04-29 13:25:49,305 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Is storage pool shared? true 2013-04-29 13:25:49,309 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-9908) Checking pool 204 for storage, totalSize: 11984676742758, usedBytes: 879609302221, usedPct: 0.07339449541286318, disable threshold: 0.85 2013-04-29 13:25:49,327 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-9908) Checking pool: 204 for volume allocation [Vol[10663|vm=6189|ROOT]], maxSize : 11984676742758, totalAllocatedSize : 588879744000, askingSize : 8589934592, allocated disable threshold: 0.85 2013-04-29 13:25:49,327 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) FirstFitStoragePoolAllocator returning 1 suitable storage pools 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Trying to find a potenial host and associated storage pools from the suitable host/pool lists for this VM 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Checking if host: 17 can access any suitable storage pool for volume: ROOT 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Host: 17 can access pool: 204 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Found a potential host id: 17 name: ksrv2-000 and associated storage pools for this VM 2013-04-29 13:25:49,332 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Returning Deployment Destination: Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(17)-Storage(Volume(10663|ROOT--Pool(204))] 2013-04-29 13:25:49,370 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-9908) VM state transitted from :Stopped to Starting with event: StartRequestedvm's original host id: null new host id: null host id before state transition: null
[jira] [Assigned] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Damle reassigned CLOUDSTACK-2281: Assignee: Prachi Damle 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 Priority: Blocker Fix For: 4.1.0 Having trouble tracking this down. Here's what I did: Created a 4.1 advanced zone added primary storage A deployed a template deployed vms added new primary storages migrated VMs from primary storage A to others removed initial primary storage A try to deploy new vm from template, not working. It looks like the allocator correctly finds and decides to use pool id 204, but somehow deployment is actually attempted on deleted pool 202. See Returning Deployment Destination and DeploymentPlan is provided: 2013-04-29 13:25:49,293 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Found a suitable host, adding to list: 19 2013-04-29 13:25:49,294 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Host Allocator returning 4 suitable hosts 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Checking suitable pools for volume (Id, Type): (10663,ROOT) 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) We need to allocate new storagepool for this volume 2013-04-29 13:25:49,299 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Calling StoragePoolAllocators to find suitable pools 2013-04-29 13:25:49,302 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) Looking for pools in dc: 1 pod:1 cluster:1 2013-04-29 13:25:49,304 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) FirstFitStoragePoolAllocator has 1 pools to check for allocation 2013-04-29 13:25:49,304 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Checking if storage pool is suitable, name: sansrv-row2-rack0 ,poolId: 204 2013-04-29 13:25:49,304 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Is localStorageAllocationNeeded? false 2013-04-29 13:25:49,305 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Is storage pool shared? true 2013-04-29 13:25:49,309 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-9908) Checking pool 204 for storage, totalSize: 11984676742758, usedBytes: 879609302221, usedPct: 0.07339449541286318, disable threshold: 0.85 2013-04-29 13:25:49,327 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-9908) Checking pool: 204 for volume allocation [Vol[10663|vm=6189|ROOT]], maxSize : 11984676742758, totalAllocatedSize : 588879744000, askingSize : 8589934592, allocated disable threshold: 0.85 2013-04-29 13:25:49,327 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) FirstFitStoragePoolAllocator returning 1 suitable storage pools 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Trying to find a potenial host and associated storage pools from the suitable host/pool lists for this VM 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Checking if host: 17 can access any suitable storage pool for volume: ROOT 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Host: 17 can access pool: 204 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Found a potential host id: 17 name: ksrv2-000 and associated storage pools for this VM 2013-04-29 13:25:49,332 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Returning Deployment Destination: Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(17)-Storage(Volume(10663|ROOT--Pool(204))] 2013-04-29 13:25:49,370 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-9908) VM state transitted from :Stopped to Starting with event: 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
[jira] [Commented] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644881#comment-13644881 ] Prachi Damle commented on CLOUDSTACK-2281: -- Marcus, Can you please provide the entire log for job-9908? 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 Priority: Blocker Fix For: 4.1.0 Having trouble tracking this down. Here's what I did: Created a 4.1 advanced zone added primary storage A deployed a template deployed vms added new primary storages migrated VMs from primary storage A to others removed initial primary storage A try to deploy new vm from template, not working. It looks like the allocator correctly finds and decides to use pool id 204, but somehow deployment is actually attempted on deleted pool 202. See Returning Deployment Destination and DeploymentPlan is provided: 2013-04-29 13:25:49,293 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Found a suitable host, adding to list: 19 2013-04-29 13:25:49,294 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Host Allocator returning 4 suitable hosts 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Checking suitable pools for volume (Id, Type): (10663,ROOT) 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) We need to allocate new storagepool for this volume 2013-04-29 13:25:49,299 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Calling StoragePoolAllocators to find suitable pools 2013-04-29 13:25:49,302 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) Looking for pools in dc: 1 pod:1 cluster:1 2013-04-29 13:25:49,304 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) FirstFitStoragePoolAllocator has 1 pools to check for allocation 2013-04-29 13:25:49,304 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Checking if storage pool is suitable, name: sansrv-row2-rack0 ,poolId: 204 2013-04-29 13:25:49,304 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Is localStorageAllocationNeeded? false 2013-04-29 13:25:49,305 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Is storage pool shared? true 2013-04-29 13:25:49,309 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-9908) Checking pool 204 for storage, totalSize: 11984676742758, usedBytes: 879609302221, usedPct: 0.07339449541286318, disable threshold: 0.85 2013-04-29 13:25:49,327 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-9908) Checking pool: 204 for volume allocation [Vol[10663|vm=6189|ROOT]], maxSize : 11984676742758, totalAllocatedSize : 588879744000, askingSize : 8589934592, allocated disable threshold: 0.85 2013-04-29 13:25:49,327 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) FirstFitStoragePoolAllocator returning 1 suitable storage pools 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Trying to find a potenial host and associated storage pools from the suitable host/pool lists for this VM 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Checking if host: 17 can access any suitable storage pool for volume: ROOT 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Host: 17 can access pool: 204 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Found a potential host id: 17 name: ksrv2-000 and associated storage pools for this VM 2013-04-29 13:25:49,332 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Returning Deployment Destination: Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(17)-Storage(Volume(10663|ROOT--Pool(204))] 2013-04-29 13:25:49,370 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-9908) VM state transitted from :Stopped to Starting with event: 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]
[jira] [Commented] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644917#comment-13644917 ] Prachi Damle commented on CLOUDSTACK-2281: -- Marcus, Also can you run following queries on your DB and paste the results here: That will be helpful to analyse the issue. Thank you! 1) SELECT * FROM `cloud`.`vm_reservation` where vm_id = 6189; 2) SELECT * FROM `cloud`.`volume_reservation`where vm_id = 6189; 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 Priority: Blocker Fix For: 4.1.0 Having trouble tracking this down. Here's what I did: Created a 4.1 advanced zone added primary storage A deployed a template deployed vms added new primary storages migrated VMs from primary storage A to others removed initial primary storage A try to deploy new vm from template, not working. It looks like the allocator correctly finds and decides to use pool id 204, but somehow deployment is actually attempted on deleted pool 202. See Returning Deployment Destination and DeploymentPlan is provided: 2013-04-29 13:25:49,293 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Found a suitable host, adding to list: 19 2013-04-29 13:25:49,294 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Host Allocator returning 4 suitable hosts 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Checking suitable pools for volume (Id, Type): (10663,ROOT) 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) We need to allocate new storagepool for this volume 2013-04-29 13:25:49,299 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Calling StoragePoolAllocators to find suitable pools 2013-04-29 13:25:49,302 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) Looking for pools in dc: 1 pod:1 cluster:1 2013-04-29 13:25:49,304 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) FirstFitStoragePoolAllocator has 1 pools to check for allocation 2013-04-29 13:25:49,304 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Checking if storage pool is suitable, name: sansrv-row2-rack0 ,poolId: 204 2013-04-29 13:25:49,304 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Is localStorageAllocationNeeded? false 2013-04-29 13:25:49,305 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Is storage pool shared? true 2013-04-29 13:25:49,309 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-9908) Checking pool 204 for storage, totalSize: 11984676742758, usedBytes: 879609302221, usedPct: 0.07339449541286318, disable threshold: 0.85 2013-04-29 13:25:49,327 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-9908) Checking pool: 204 for volume allocation [Vol[10663|vm=6189|ROOT]], maxSize : 11984676742758, totalAllocatedSize : 588879744000, askingSize : 8589934592, allocated disable threshold: 0.85 2013-04-29 13:25:49,327 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) FirstFitStoragePoolAllocator returning 1 suitable storage pools 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Trying to find a potenial host and associated storage pools from the suitable host/pool lists for this VM 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Checking if host: 17 can access any suitable storage pool for volume: ROOT 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Host: 17 can access pool: 204 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Found a potential host id: 17 name: ksrv2-000 and associated storage pools for this VM 2013-04-29 13:25:49,332 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Returning Deployment Destination: Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type--Pool(Id))] : Dest[Zone(1)-Pod(1)-Cluster(1)-Host(17)-Storage(Volume(10663|ROOT--Pool(204))] 2013-04-29 13:25:49,370 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-10:job-9908) VM state transitted
[jira] [Resolved] (CLOUDSTACK-2138) Web Client UI - Putting all translations files on master branch and automate with transifex upload/download
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milamber resolved CLOUDSTACK-2138. -- Resolution: Fixed Fix Version/s: 4.1.0 Web Client UI - Putting all translations files on master branch and automate with transifex upload/download --- Key: CLOUDSTACK-2138 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2138 Project: CloudStack Issue Type: Task Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Milamber Assignee: Milamber Labels: ui Fix For: 4.1.0, 4.2.0 This Jira ticket to follow this tasks: Add missing translations relative to 4.1 version (resources files and index.jsp) Make alphabetical order for keys in messages_xx.properties Convert all messages_xx.properties in ASCII with unicode Add a double-backslash before quote ( \\' ) in messages_xx.properties for some languages (to fix code errors in dictonary.jsp generated file) Create a script to automate the conversion and communication with transifex for upload/download (if it's possible with transifex client) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644940#comment-13644940 ] Marcus Sorensen commented on CLOUDSTACK-2281: - Sure, will attach. I just submitted a patch that fixes the NPE, and it fixed the problem, but I think it's just a bandaid since in this case it looks like we choose pool 204, then the deploy decides it wants to use 202, but then finds it's invalid and selects a new one. I'd rather 202 not be passed in the first place, but I can't see where it's coming from. Still, this patch is enough I think to downgrade the bug, and it's probably a good sanity check to have anyway. https://reviews.apache.org/r/10842/ 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 Priority: Blocker Fix For: 4.1.0 Having trouble tracking this down. Here's what I did: Created a 4.1 advanced zone added primary storage A deployed a template deployed vms added new primary storages migrated VMs from primary storage A to others removed initial primary storage A try to deploy new vm from template, not working. It looks like the allocator correctly finds and decides to use pool id 204, but somehow deployment is actually attempted on deleted pool 202. See Returning Deployment Destination and DeploymentPlan is provided: 2013-04-29 13:25:49,293 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Found a suitable host, adding to list: 19 2013-04-29 13:25:49,294 DEBUG [allocator.impl.FirstFitAllocator] (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Host Allocator returning 4 suitable hosts 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Checking suitable pools for volume (Id, Type): (10663,ROOT) 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) We need to allocate new storagepool for this volume 2013-04-29 13:25:49,299 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Calling StoragePoolAllocators to find suitable pools 2013-04-29 13:25:49,302 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) Looking for pools in dc: 1 pod:1 cluster:1 2013-04-29 13:25:49,304 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) FirstFitStoragePoolAllocator has 1 pools to check for allocation 2013-04-29 13:25:49,304 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Checking if storage pool is suitable, name: sansrv-row2-rack0 ,poolId: 204 2013-04-29 13:25:49,304 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Is localStorageAllocationNeeded? false 2013-04-29 13:25:49,305 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) Is storage pool shared? true 2013-04-29 13:25:49,309 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-9908) Checking pool 204 for storage, totalSize: 11984676742758, usedBytes: 879609302221, usedPct: 0.07339449541286318, disable threshold: 0.85 2013-04-29 13:25:49,327 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-10:job-9908) Checking pool: 204 for volume allocation [Vol[10663|vm=6189|ROOT]], maxSize : 11984676742758, totalAllocatedSize : 588879744000, askingSize : 8589934592, allocated disable threshold: 0.85 2013-04-29 13:25:49,327 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) FirstFitStoragePoolAllocator returning 1 suitable storage pools 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Trying to find a potenial host and associated storage pools from the suitable host/pool lists for this VM 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Checking if host: 17 can access any suitable storage pool for volume: ROOT 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Host: 17 can access pool: 204 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Found a potential host id: 17 name: ksrv2-000 and associated storage pools for this VM 2013-04-29 13:25:49,332 DEBUG [cloud.deploy.FirstFitPlanner] (Job-Executor-10:job-9908) Returning Deployment Destination:
[jira] [Updated] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Sorensen updated CLOUDSTACK-2281: Attachment: job9908.txt job 9908 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 Priority: Blocker 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)
[jira] [Commented] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644945#comment-13644945 ] Prachi Damle commented on CLOUDSTACK-2281: -- Agreed. I spotted the missing check for fixing the NPE as well, and it will fix your situation for now as planner will go and choose another pool. But I need to figure out why the old poolId was being passed by the deploy - that seems to be the root cause. 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 Priority: Blocker 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]
[jira] [Commented] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644966#comment-13644966 ] Prachi Damle commented on CLOUDSTACK-2281: -- Thanks for the logs Marcus, can you please provide the DB output too. 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 Priority: Blocker 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
[jira] [Commented] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644973#comment-13644973 ] Marcus Sorensen commented on CLOUDSTACK-2281: - Yes, I checked the reservation earlier as well and it looked correct: [root(marcus)@cloudcontrol1-test ~]# SELECT * FROM `cloud`.`vm_reservation` where vm_id = 6189;^C [root(marcus)@cloudcontrol1-test ~]# mysql -e 'SELECT * FROM `cloud`.`vm_reservation` where vm_id = 6189;' +-+--+---++++-+-+-+ | id | uuid | vm_id | data_center_id | pod_id | cluster_id | host_id | created | removed | +-+--+---++++-+-+-+ | 303 | 9c231db5-089b-4906-8ae8-d481c044cf55 | 6189 | 1 | 1 | 1 | 17 | 2013-04-29 19:25:49 | NULL| +-+--+---++++-+-+-+ [root(marcus)@cloudcontrol1-test ~]# mysql -e 'SELECT * FROM `cloud`.`volume_reservation`where vm_id = 6189;' +-+---+---+---+-+ | id | vm_reservation_id | vm_id | volume_id | pool_id | +-+---+---+---+-+ | 440 | 303 | 6189 | 10663 | 204 | +-+---+---+---+-+ 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 Priority: Blocker 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)
[jira] [Commented] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644988#comment-13644988 ] Prachi Damle commented on CLOUDSTACK-2281: -- Weird. Is there any other volume_reservation for same vm_reservation_id or any entry with pool Id 202? Were you deploying VMs simultaneously? 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 Priority: Blocker 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
[jira] [Assigned] (CLOUDSTACK-2282) Automation:Selenium: Configure headless mode
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Jagirdar reassigned CLOUDSTACK-2282: -- Assignee: Parth Jagirdar Automation:Selenium: Configure headless mode Key: CLOUDSTACK-2282 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2282 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, UI Affects Versions: 4.2.0 Environment: NA Reporter: Parth Jagirdar Assignee: Parth Jagirdar Fix For: 4.2.0 Configure headless mode for Selenium automation using PhatomJS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645026#comment-13645026 ] Prachi Damle commented on CLOUDSTACK-2281: -- Or do you see duplicate entries in vm_reservation table for same uuid? 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 Priority: Blocker 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
[jira] [Created] (CLOUDSTACK-2283) SRX - Delete Egress firewall rule failed
angeline shen created CLOUDSTACK-2283:
-
Summary: SRX - Delete Egress firewall rule failed
Key: CLOUDSTACK-2283
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2283
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: MSACS 2.0 build 4/24/13 7:48 PM revision:
299cccf779f75c3ba04d9ec7303bed88394c3562
host XS 6.0.2
Reporter: angeline shen
Assignee: Jayapal Reddy
Priority: Critical
Fix For: 4.2.0
MSACS 2.0 build 4/24/13 7:48 PM revision:
299cccf779f75c3ba04d9ec7303bed88394c3562
host XS 6.0.2
1. SRX network offering : isolated DHCP: virtual router DNS: virtual router
firewall: SRX userdata:virtual router sourceNAT: SRX staticNAT: SRX
portforward: SRX sourceNAT type: perzone
2. advance zone, add SRX device for firewall.
domain: ROOT admin
create VM with network of above networking offering.
Add egress ruleTCP port 22 22 for egress
3. Delete this egress rule failed:
2013-04-29 15:15:40,818 DEBUG [agent.transport.Request]
(Job-Executor-24:job-19) Seq 5-1743912980: Received: { Ans: , MgmtId:
6655051826959, via: 5, Ver: v1, Flags: 10, { Answer } }
2013-04-29 15:15:40,818 DEBUG [agent.manager.AgentManagerImpl]
(Job-Executor-24:job-19) Details from executing class
com.cloud.agent.api.routing.SetFirewallRulesCommand: Exception:
com.cloud.utils.exception.ExecutionException
Message: Failed to open a private configuration.
Stack: com.cloud.utils.exception.ExecutionException: Failed to open a private
configuration.
at
com.cloud.network.resource.JuniperSrxResource.openConfiguration(JuniperSrxResource.java:617)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:827)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:869)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:869)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:821)
at
com.cloud.network.resource.JuniperSrxResource.executeRequest(JuniperSrxResource.java:349)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-04-29 15:15:40,818 ERROR [cloud.network.ExternalFirewallDeviceManagerImpl]
(Job-Executor-24:job-19) External firewall was unable to apply static nat rules
to the SRX appliance in zone z1 due to: Exception:
com.cloud.utils.exception.ExecutionException
Message: Failed to open a private configuration.
Stack: com.cloud.utils.exception.ExecutionException: Failed to open a private
configuration.
at
com.cloud.network.resource.JuniperSrxResource.openConfiguration(JuniperSrxResource.java:617)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:827)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:869)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:869)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:821)
at
com.cloud.network.resource.JuniperSrxResource.executeRequest(JuniperSrxResource.java:349)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
.
[jira] [Updated] (CLOUDSTACK-2283) SRX - Delete Egress firewall rule failed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angeline shen updated CLOUDSTACK-2283:
--
Attachment: management-server.log.gz
SRX - Delete Egress firewall rule failed
Key: CLOUDSTACK-2283
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2283
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: MSACS 2.0 build 4/24/13 7:48 PM revision:
299cccf779f75c3ba04d9ec7303bed88394c3562
host XS 6.0.2
Reporter: angeline shen
Assignee: Jayapal Reddy
Priority: Critical
Fix For: 4.2.0
Attachments: management-server.log.gz
MSACS 2.0 build 4/24/13 7:48 PM revision:
299cccf779f75c3ba04d9ec7303bed88394c3562
host XS 6.0.2
1. SRX network offering : isolated DHCP: virtual router DNS: virtual router
firewall: SRX userdata:virtual router sourceNAT: SRX staticNAT: SRX
portforward: SRX sourceNAT type: perzone
2. advance zone, add SRX device for firewall.
domain: ROOT admin
create VM with network of above networking offering.
Add egress ruleTCP port 22 22 for egress
3. Delete this egress rule failed:
2013-04-29 15:15:40,818 DEBUG [agent.transport.Request]
(Job-Executor-24:job-19) Seq 5-1743912980: Received: { Ans: , MgmtId:
6655051826959, via: 5, Ver: v1, Flags: 10, { Answer } }
2013-04-29 15:15:40,818 DEBUG [agent.manager.AgentManagerImpl]
(Job-Executor-24:job-19) Details from executing class
com.cloud.agent.api.routing.SetFirewallRulesCommand: Exception:
com.cloud.utils.exception.ExecutionException
Message: Failed to open a private configuration.
Stack: com.cloud.utils.exception.ExecutionException: Failed to open a private
configuration.
at
com.cloud.network.resource.JuniperSrxResource.openConfiguration(JuniperSrxResource.java:617)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:827)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:869)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:869)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:821)
at
com.cloud.network.resource.JuniperSrxResource.executeRequest(JuniperSrxResource.java:349)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2013-04-29 15:15:40,818 ERROR
[cloud.network.ExternalFirewallDeviceManagerImpl] (Job-Executor-24:job-19)
External firewall was unable to apply static nat rules to the SRX appliance
in zone z1 due to: Exception: com.cloud.utils.exception.ExecutionException
Message: Failed to open a private configuration.
Stack: com.cloud.utils.exception.ExecutionException: Failed to open a private
configuration.
at
com.cloud.network.resource.JuniperSrxResource.openConfiguration(JuniperSrxResource.java:617)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:827)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:869)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:869)
at
com.cloud.network.resource.JuniperSrxResource.execute(JuniperSrxResource.java:821)
at
com.cloud.network.resource.JuniperSrxResource.executeRequest(JuniperSrxResource.java:349)
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
[jira] [Commented] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645059#comment-13645059 ] Marcus Sorensen commented on CLOUDSTACK-2281: - I tried it about five times, and the result was the same each time. I only see 1 entry for vm_reservation_id 303 I only see 1 entry for 9c231db5-089b-4906-8ae8-d481c044cf55 in vm_reservation. The part where I get lost is that even without triggering this bug, it looks like it goes into FirstFitPlanner, then advanceDeploy, then back into FirstFitPlanner. 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 Priority: Blocker 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))] :
[jira] [Commented] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645067#comment-13645067 ] Prachi Damle commented on CLOUDSTACK-2281: -- The part where I get lost is that even without triggering this bug, it looks like it goes into FirstFitPlanner, then advanceDeploy, then back into FirstFitPlanner. This is expected; the VM deployment is refactored and going through two stages: reserve and deploy. Earlier deploy used to take care of calling the planners and getting back a destination. Now we first do a reserve by calling planners and storing the destination the DB. Then the deploy gets called, and the reserved destination is passed back in. The deploy still calls the planners(to let other parts of code that arent yet refactored, work) - but planners don't do much now since the plan is already provided in this pass. 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 Priority: Blocker 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
[jira] [Commented] (CLOUDSTACK-2249) Automation: Add automtion for nTier Apps 2.0 Subtasks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645086#comment-13645086 ] Chandan Purushothama commented on CLOUDSTACK-2249: -- The Following N-Tier Features Test Plans are available at https://cwiki.apache.org/confluence/display/CLOUDSTACK/nTier+Apps+2.0 : 2.2 Load Balancing on all Tiers 2.3 Deployment of VM on a VPC Tier with one or more Shared Networks 2.6 Blacklist of Routes 2.14 Allow ACL on all level 4 protocols Test Plan 2.19 Add more than one Private GW to a VPC 2.20 Source NAT on Private Gateway 2.21 ACL on Private Gateway to the VPC FS of N-Tier Features are present at https://cwiki.apache.org/confluence/display/CLOUDSTACK/nTier+Apps+2.0+Functional+Spec Automation: Add automtion for nTier Apps 2.0 Subtasks - Key: CLOUDSTACK-2249 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2249 Project: CloudStack Issue Type: Sub-task Security Level: Public(Anyone can view this level - this is the default.) Reporter: Sudha Ponnaganti 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] [Commented] (CLOUDSTACK-2054) [Automation]Failed to upload volume with NPE
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13645173#comment-13645173 ] Sailaja Mada commented on CLOUDSTACK-2054: -- Rayees, I tried with latest build upload volume worked fine. There are issues with this volume while attaching to the instance . This is tracked as a different defect . Can you please retry this operation and update the ticket. [Automation]Failed to upload volume with NPE Key: CLOUDSTACK-2054 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2054 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Volumes Affects Versions: 4.2.0 Environment: KVM and VMware Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.2.0 Attachments: CLOUDSTACK-2054.rar Found this issue while executing regression test case test_upload_volumes.py Step 1 : Create master build, install and configure advanced zone Step 2 : upload volume .vhd file , size 1 GB Actual result Upload failed with NPE eryAsyncJobResultjobId=960459e9-a299-4552-a56c-d11522271c4dresponse=jsonsessionkey=vp9T6C4z5OzLwUgMljRFFe2bUo0%3D_=1366147860238 2013-04-16 17:34:00,975 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-2285) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.UploadVolumeCmd java.lang.NumberFormatException: null at java.lang.Long.parseLong(Long.java:401) at java.lang.Long.parseLong(Long.java:478) at com.cloud.utils.UriUtils.getRemoteSize(UriUtils.java:95) at com.cloud.storage.VolumeManagerImpl.validateVolume(VolumeManagerImpl.java:478) at com.cloud.storage.VolumeManagerImpl.uploadVolume(VolumeManagerImpl.java:377) at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) at com.cloud.storage.VolumeManagerImpl.uploadVolume(VolumeManagerImpl.java:175) at org.apache.cloudstack.api.command.user.volume.UploadVolumeCmd.execute(UploadVolumeCmd.java:121) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:164) 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:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) 2013-04-16 17:34:00,976 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-2285) Complete async job-2285, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: null 2013-04-16 17:34:01,620 DEBUG [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 2 is ready to launch secondary storage VM 2013-04-16 17:34:02,028 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 2 is ready to launch console proxy -- 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-2284) AWS Regions - Not able to add account/domain/user with same Id (External UUID) after deleting account/domain/user with this id.
Sangeetha Hariharan created CLOUDSTACK-2284:
---
Summary: AWS Regions - Not able to add account/domain/user with
same Id (External UUID) after deleting account/domain/user with this id.
Key: CLOUDSTACK-2284
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2284
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.2.0
Environment: Build from master
Reporter: Sangeetha Hariharan
Priority: Critical
Fix For: 4.2.0
AWS Regions - Not able to add account/domain/user with same Id (External UUID)
after deleting account/domain/user with this id.
Steps to reproduce the problem:
1. Add account/domain/user by passing External uuid in the accountid, userid
and domainid parameter to the createAccount/createDomain/createUser.
2. Creation of account/domain/user succeeds.
3. Delete the above created account/domain/user .
4. Deletion is successful.
5. Now try to Add account/domain/user by passing the same External uuid ( as
the one in step1 which are now deleted) in the accountid, userid and domainid
parameter to the createAccount/createDomain/createUser
Creation of account/domain/user fails with
api calls:
2013-04-29 18:49:44,694 INFO [cloud.api.ApiServer] (catalina-exec-5:null)
(userId=2 accountId=2 sessionId=null) 10.223.56
.66 -- GET
username=test-IUMDSHdomainid=2a50dd26-ad1d-11e2-acc8-068c76000429firstname=Testlastname=Useruserid=user1re
sponse=jsonapiKey=sSPm7HTehsVp4DQ00Y0SIFaiQ9aabqIX5ty3AzqS2ciu-748BPIexxMfadefR-k3Q9iMCeYxerQ10aSf0h3oUwcommand=createAc
countaccounttype=0signature=mRKIJdxa3mnVWCABrFh57UAkCyI%3Dpassword=passwordemail=test%40test.comaccountid=account1
20
0 { createaccountresponse : { account :
{id:account1,name:test-IUMDSH,accounttype:0,domainid:2a50dd26-ad
1d-11e2-acc8-068c76000429,domain:ROOT,vmlimit:20,vmtotal:0,vmavailable:20,iplimit:20,iptotal:0,ipava
ilable:18,volumelimit:20,volumetotal:0,volumeavailable:20,snapshotlimit:20,snapshottotal:0,snapshotava
ilable:20,templatelimit:20,templatetotal:0,templateavailable:20,projectlimit:Unlimited,projecttotal:0,
projectavailable:Unlimited,networklimit:20,networktotal:0,networkavailable:20,cpulimit:40,cputotal:0,c
puavailable:40,memorylimit:40960,memorytotal:0,memoryavailable:40960,primarystoragelimit:200,primarystor
agetotal:0,primarystorageavailable:200,secondarystoragelimit:400,secondarystoragetotal:0,secondarystorageavail
able:400,state:enabled,user:[{id:user1,username:test-IUMDSH,firstname:Test,lastname:User,email:
t...@test.com,created:2013-04-29T18:49:44-0700,state:enabled,account:test-IUMDSH,accounttype:0,domainid:
2a50dd26-ad1d-11e2-acc8-068c76000429,domain:ROOT,accountid:account1,iscallerchilddomain:false,isdefault:fals
e,jobstatus:0}],isdefault:false,jobstatus:0} } }
2013-04-29 20:16:14,970 INFO [cloud.api.ApiServer] (catalina-exec-7:null)
(userId=2 accountId=2 sessionId=null) 10.223.56.66 -- GET
username=test-EEZWQMdomainid=2a50dd26-ad1d-11e2-acc8-068c76000429firstname=Testlastname=Useruserid=user1response=jsonapiKey=sSPm7HTehsVp4DQ00Y0SIFaiQ9aabqIX5ty3AzqS2ciu-748BPIexxMfadefR-k3Q9iMCeYxerQ10aSf0h3oUwcommand=createAccountaccounttype=0signature=2uJfDxGam6oUI9qsR2tTUGaIOhI%3Dpassword=passwordemail=test%40test.comaccountid=account1
530 Entity already exists:
2013-04-29 18:58:03,584 INFO [cloud.api.ApiServer] (catalina-exec-2:null)
(userId=2 accountId=2 sessionId=9F0E4DDB3C5B109C6624B295300677A4)
10.217.252.128 -- GET
command=deleteAccountresponse=jsonsessionkey=kVuw1w4mpRqpRWJmCzdR4yUOXKc%3Did=account1_=1367287126884
200 { deleteaccountresponse :
{jobid:d4124909-af04-47f8-bfff-818e39ab7eaf} }
2013-04-29 20:16:14,970 INFO [cloud.api.ApiServer] (catalina-exec-7:null)
(userId=2 accountId=2 sessionId=null) 10.223.56.66 -- GET
username=test-EEZWQMdomainid=2a50dd26-ad1d-11e2-acc8-068c76000429firstname=Testlastname=Useruserid=user1response=jsonapiKey=sSPm7HTehsVp4DQ00Y0SIFaiQ9aabqIX5ty3AzqS2ciu-748BPIexxMfadefR-k3Q9iMCeYxerQ10aSf0h3oUwcommand=createAccountaccounttype=0signature=2uJfDxGam6oUI9qsR2tTUGaIOhI%3Dpassword=passwordemail=test%40test.comaccountid=account1
530 Entity already exists:
mysql select id,account_name,uuid,removed from account where uuid=account1;
++--+--+-+
| id | account_name | uuid | removed |
++--+--+-+
| 86 | test-IUMDSH | account1 | 2013-04-30 01:58:03 |
++--+--+-+
1 row in set (0.00 sec)
Management server logs:
2013-04-29 20:16:14,952 DEBUG [cloud.api.ApiServlet] (catalina-exec-7:null)
===START=== 10.223.56.66 -- GET username=tes
t-EEZWQMdomainid=2a50dd26-ad1d-11e2-acc8-068c76000429firstname=Testlastname=Useruserid=user1response=jsonapiKey=sSPm
[jira] [Updated] (CLOUDSTACK-2285) [GSLB] addNetscalerLoadBalancer with GSLB functionality shouldn't be exposed in basic zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkata swamybabu budumuru updated CLOUDSTACK-2285: --- Attachment: api.log.tgz [GSLB] addNetscalerLoadBalancer with GSLB functionality shouldn't be exposed in basic zone -- Key: CLOUDSTACK-2285 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2285 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 0e2ffe72aa641f4551cae63fbc36454c5934342f Reporter: venkata swamybabu budumuru Assignee: Murali Reddy Fix For: 4.2.0 Attachments: api.log.tgz Steps to reproduce : 1. Have a basic zone setup with at least one XEN cluster using the offering DefaultSharedNetworkOfferingWithSGService 2. Try addNetscalerLoadBalancer with GSLB enabled Observations: (i) It gets added successfully. command=addNetscalerLoadBalancerphysicalnetworkid=4dbe1d3c-1cee-4f88-aeca-45c4a8a76b4dusername=nsrootpassword=nsrootnetworkdevicetype=NetscalerVPXLoadBalancergslbprovider=truegslbproviderpublicip=1.1.1.1gslbproviderprivateip=1.1.1.1url=https://10.147.54.5?publicinterface=1/1privateinterface=1/2numretries=2lbdevicededicated=false; mysql select id,name,networktype from data_center where id=1; ++---+-+ | id | name | networktype | ++---+-+ | 1 | zone1 | Basic | ++---+-+ mysql select * from external_load_balancer_devices where id=2\G *** 1. row *** id: 2 uuid: 8c467bfc-7ac3-410a-92d7-11e5853a5d79 physical_network_id: 200 provider_name: Netscaler device_name: NetscalerVPXLoadBalancer capacity: 50 device_state: Enabled allocation_state: Free is_dedicated: 0 is_managed: 0 host_id: 15 parent_host_id: 0 is_gslb_provider: 1 gslb_site_publicip: NULL gslb_site_privateip: 1.1.1.1 (ii) There is no need for enabling GSLB functionality in basic zones created with above network offerings because there is no LB feature enabled in this case. May be having a check at the API level and allowing it only based on type of zone will help in this case but, if we are supporting GSLB for ELB enabled zones then we need to handle that situation as well. -- 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-1794) We are allowed to create Egress rules for Shared networks.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayapal Reddy resolved CLOUDSTACK-1794.
---
Resolution: Fixed
Egress rules is not supported for shared networks
We are allowed to create Egress rules for Shared networks.
--
Key: CLOUDSTACK-1794
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1794
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
Environment: Build from 4.1
Reporter: Sangeetha Hariharan
Assignee: Jayapal Reddy
Fix For: 4.1.0
We are allowed to create Egress rules for Shared networks.
Steps to reproduce the problem:
Set up - Advanced Zone
Create a shared network.
From Network tab , select this shared network and go to Egress tab and create
a egress rule.
Creation of egress rule succeed.
Expected Behavior:
There is no support for egress rule in shared network. API should error out.
apilog.log
2013-03-22 16:56:54,839 INFO [cloud.api.ApiServer] (catalina-exec-16:null)
(userId=2 accountId=2 sessionId=FB9EC7CB6FF657012432A2067C3414B9)
10.217.252.128 -- GET
command=createEgressFirewallRuleresponse=jsonsessionkey=H%2Ffj8xnB4it%2BUnoyU6Q%2FM3uT4gA%3Dprotocol=tcpcidrlist=0.0.0.0%2F0networkid=41305c7c-4206-4b3d-a5a3-b8c64d29d1b1startport=22endport=22_=136415912
200 { createegressfirewallruleresponse :
{id:3,jobid:ba51e1c7-e6fc-48cf-8210-191e35a42a48} }
2013-03-22 16:56:57,913 INFO [cloud.api.ApiServer] (catalina-exec-17:null)
(userId=2 accountId=2 sessionId=FB9EC7CB6FF657012432A2067C3414B9)
10.217.252.128 -- GET
command=queryAsyncJobResultjobId=ba51e1c7-e6fc-48cf-8210-191e35a42a48response=jsonsessionkey=H%2Ffj8xnB4it%2BUnoyU6Q%2FM3uT4gA%3D_=136419143
200 { queryasyncjobresultresponse :
{accountid:b1b53b7e-8fed-11e2-89d9-06d4460004b1,userid:b1b5e920-8fed-11e2-89d9-06d4460004b1,cmd:org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCmd,jobstatus:1,jobprocstatus:0,jobresultcode:0,jobresulttype:object,jobresult:{firewallrule:{id:f4aacb15-20e1-4ea1-af3f-e600c2373527,protocol:tcp,startport:22,endport:22,networkid:212,state:Active,cidrlist:0.0.0.0/0,tags:[]}},created:2013-03-22T16:56:54-0700,jobid:ba51e1c7-e6fc-48cf-8210-191e35a42a48}
}
management server log:
2013-03-22 16:56:54,835 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-16:null) submit async job-56, details: AsyncJobVO {id:56,
userId: 2, accountId: 2, sessionKey: null, instanceType: null, instanceId: 3,
cmd:
org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCmd,
cmdOriginator: null, cmdInfo:
{id:3,response:json,sessionkey:H/fj8xnB4it+UnoyU6Q/M3uT4gA\u003d,protocol:tcp,ctxUserId:2,cidrlist:0.0.0.0/0,startport:22,_:136415912,ctxAccountId:2,networkid:41305c7c-4206-4b3d-a5a3-b8c64d29d1b1,ctxStartEventId:140,endport:22},
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-03-22 16:56:54,836 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-56) Executing
org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCmd
for job-56
2013-03-22 16:56:54,839 DEBUG [cloud.api.ApiServlet] (catalina-exec-16:null)
===END=== 10.217.252.128 -- GET
command=createEgressFirewallRuleresponse=jsonsessionkey=H%2Ffj8xnB4it%2BUnoyU6Q%2FM3uT4gA%3Dprotocol=tcpcidrlist=0.0.0.0%2F0networkid=41305c7c-4206-4b3d-a5a3-b8c64d29d1b1startport=22endport=22_=136415912
2013-03-22 16:56:54,843 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-56) Sync job-56 execution on object network.212
2013-03-22 16:56:54,860 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-56) job
org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCmd
for job-56 was queued, processing the queue.
2013-03-22 16:56:54,876 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-56) Executing sync queue item: SyncQueueItemVO {id:9,
queueId: 9, contentType: AsyncJob, contentId: 56, lastProcessMsid:
206915885079359, lastprocessNumber: 1, lastProcessTime: Fri Mar 22 16:56:54
PDT 2013, created: Fri Mar 22 16:56:54 PDT 2013}
2013-03-22 16:56:54,878 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-8:job-56) Schedule queued job-56
2013-03-22 16:56:54,887 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-9:job-56) Executing
org.apache.cloudstack.api.command.user.firewall.CreateEgressFirewallRuleCmd
for job-56
2013-03-22 16:56:54,887 DEBUG [cloud.async.SyncQueueManagerImpl]
[jira] [Resolved] (CLOUDSTACK-2212) [Egress Rules] [Shared Network] Unable to configure egress rules as non-ROOT domain user
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy resolved CLOUDSTACK-2212. --- Resolution: Fixed Currently the for shared networks Egress rules is not supported. With the below bug fix it throws error when you configured egress for shared networks. https://issues.apache.org/jira/browse/CLOUDSTACK-1794 I raised a feature bug for egress rules for shared networks. https://issues.apache.org/jira/browse/CLOUDSTACK-2208 [Egress Rules] [Shared Network] Unable to configure egress rules as non-ROOT domain user Key: CLOUDSTACK-2212 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2212 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 0e2ffe72aa641f4551cae63fbc36454c5934342f Reporter: venkata swamybabu budumuru Assignee: Jayapal Reddy Fix For: 4.2.0 Attachments: logs.tgz Steps to Reproduce : 1. Create an advanced zone with 1 Xen cluster 2. Create a shared network offering with JuniperSRX servicing the firewall related functionalities select * from network_offerings id: 17 name: test uuid: ed856a34-71e9-4bef-ae71-b4781fb57626 unique_name: test display_text: test nw_rate: NULL mc_rate: 10 traffic_type: Guest tags: NULL system_only: 0 specify_vlan: 1 service_offering_id: NULL conserve_mode: 0 created: 2013-04-26 17:04:40 removed: NULL default: 0 availability: Optional dedicated_lb_service: 0 shared_source_nat_service: 1 sort_key: 0 redundant_router_service: 0 state: Enabled guest_type: Shared elastic_ip_service: 0 eip_associate_public_ip: 0 elastic_lb_service: 0 specify_ip_ranges: 1 inline: 0 is_persistent: 0 # select * from networks id: 211 name: SharedNet3 uuid: 9aded0d9-f60c-4d06-af6d-aed9dad43b31 display_text: SharedNet3 traffic_type: Guest broadcast_domain_type: Vlan broadcast_uri: vlan://908 gateway: 192.168.121.1 cidr: 192.168.121.0/24 mode: Dhcp network_offering_id: 17 physical_network_id: 201 data_center_id: 2 guru_name: DirectNetworkGuru state: Implemented related: 211 domain_id: 1 account_id: 1 dns1: NULL dns2: NULL guru_data: NULL set_fields: 0 acl_type: Domain network_domain: cs1cloud.internal reservation_id: f0e990b9-c85e-4ff1-baa0-189f683406e5 guest_type: Shared restart_required: 0 created: 2013-04-26 17:49:15 removed: NULL specify_ip_ranges: 1 vpc_id: NULL ip6_gateway: NULL ip6_cidr: NULL network_cidr: NULL # mysql select * from ntwk_service_map where network_id=211; ++++---+-+ | id | network_id | service| provider | created | ++++---+-+ | 25 |211 | Dhcp | VirtualRouter | 2013-04-26 17:49:15 | | 22 |211 | Dns| VirtualRouter | 2013-04-26 17:49:15 | | 21 |211 | Firewall | JuniperSRX| 2013-04-26 17:49:15 | | 27 |211 | PortForwarding | JuniperSRX| 2013-04-26 17:49:15 | | 23 |211 | SourceNat | JuniperSRX| 2013-04-26 17:49:15 | | 24 |211 | StaticNat | JuniperSRX| 2013-04-26 17:49:15 | | 26 |211 | UserData | VirtualRouter | 2013-04-26 17:49:15 | 3. Create a new domain with at least one account with user role 4. login as above user and try to create an egress rule Observations: - It fails with the following error in the logs. 2013-04-26 15:01:57,880 DEBUG [cloud.user.AccountManagerImpl] (Job-Executor-53:job-169) Access to Acct[45-dom1Acc1] granted to Acct[45-dom1Acc1] by DomainChecker_EnhancerByCloudStack_4891655 2013-04-26 15:01:57,909 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-53:job-169) Unexpected exception while executing
