[jira] [Updated] (CLOUDSTACK-6808) Need to add Database Information to Alter table statements in a commit to schema-430to440.sql
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-6808: Status: Reviewable (was: In Progress) > Need to add Database Information to Alter table statements in a commit to > schema-430to440.sql > -- > > Key: CLOUDSTACK-6808 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6808 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.0 >Reporter: Chandan Purushothama >Assignee: Rajani Karuturi >Priority: Critical > Fix For: 4.4.0 > > > Database Information is missing in the commit shown below > diff --git a/setup/db/db/schema-430to440.sql b/setup/db/db/schema-430to440.sql > index 3b525c4..2262608 100644 (file) > --- a/setup/db/db/schema-430to440.sql > +++ b/setup/db/db/schema-430to440.sql > @@ -1676,3 +1676,12 @@ CREATE TABLE `cloud`.`network_acl_item_cidrs` ( > ALTER TABLE `cloud`.`load_balancer_healthcheck_policies` ADD COLUMN `display` > tinyint(1) NOT NULL DEFAULT '1' COMMENT 'True if the policy can be displayed > to the end user'; > ALTER TABLE `cloud`.`load_balancer_stickiness_policies` ADD COLUMN `display` > tinyint(1) NOT NULL DEFAULT '1' COMMENT 'True if the policy can be displayed > to the end user'; > + > +alter table user_ip_address add column removed datetime DEFAULT NULL COMMENT > 'date removed'; > +alter table user_ip_address add column created datetime NULL COMMENT 'date > created'; > + > +alter table vlan add column removed datetime DEFAULT NULL COMMENT 'date > removed'; > +alter table vlan add column created datetime NULL COMMENT 'date created'; > + > +alter table user_ip_address drop key public_ip_address; > +alter table user_ip_address add UNIQUE KEY public_ip_address > (public_ip_address,source_network_id, removed); > \ No newline at end of file -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6808) Need to add Database Information to Alter table statements in a commit to schema-430to440.sql
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013358#comment-14013358 ] Rajani Karuturi commented on CLOUDSTACK-6808: - patch on review board https://reviews.apache.org/r/22075/ > Need to add Database Information to Alter table statements in a commit to > schema-430to440.sql > -- > > Key: CLOUDSTACK-6808 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6808 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.0 >Reporter: Chandan Purushothama >Assignee: Rajani Karuturi >Priority: Critical > Fix For: 4.4.0 > > > Database Information is missing in the commit shown below > diff --git a/setup/db/db/schema-430to440.sql b/setup/db/db/schema-430to440.sql > index 3b525c4..2262608 100644 (file) > --- a/setup/db/db/schema-430to440.sql > +++ b/setup/db/db/schema-430to440.sql > @@ -1676,3 +1676,12 @@ CREATE TABLE `cloud`.`network_acl_item_cidrs` ( > ALTER TABLE `cloud`.`load_balancer_healthcheck_policies` ADD COLUMN `display` > tinyint(1) NOT NULL DEFAULT '1' COMMENT 'True if the policy can be displayed > to the end user'; > ALTER TABLE `cloud`.`load_balancer_stickiness_policies` ADD COLUMN `display` > tinyint(1) NOT NULL DEFAULT '1' COMMENT 'True if the policy can be displayed > to the end user'; > + > +alter table user_ip_address add column removed datetime DEFAULT NULL COMMENT > 'date removed'; > +alter table user_ip_address add column created datetime NULL COMMENT 'date > created'; > + > +alter table vlan add column removed datetime DEFAULT NULL COMMENT 'date > removed'; > +alter table vlan add column created datetime NULL COMMENT 'date created'; > + > +alter table user_ip_address drop key public_ip_address; > +alter table user_ip_address add UNIQUE KEY public_ip_address > (public_ip_address,source_network_id, removed); > \ No newline at end of file -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6669) Support volume resize in usage server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-6669: Status: Reviewable (was: In Progress) > Support volume resize in usage server > - > > Key: CLOUDSTACK-6669 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6669 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kishan Kavala >Assignee: Rajani Karuturi > > volume resize events are generated in usgae_events tables. > Support to process them and update the usage records has to be added to usage > server -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6669) Support volume resize in usage server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013354#comment-14013354 ] Rajani Karuturi commented on CLOUDSTACK-6669: - patch on review board https://reviews.apache.org/r/22077/ > Support volume resize in usage server > - > > Key: CLOUDSTACK-6669 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6669 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kishan Kavala >Assignee: Rajani Karuturi > > volume resize events are generated in usgae_events tables. > Support to process them and update the usage records has to be added to usage > server -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6809) listStoragePoolsForMigration doesn't list the zone wide primary storages if the volume is on cluster-wide storage, and doesn't list cwps if volume is on zwps
Abhinav Roy created CLOUDSTACK-6809: --- Summary: listStoragePoolsForMigration doesn't list the zone wide primary storages if the volume is on cluster-wide storage, and doesn't list cwps if volume is on zwps Key: CLOUDSTACK-6809 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6809 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, Storage Controller Affects Versions: 4.4.0 Environment: HyperV Advanced zone setup with cluster wide, zone wide and local storages. Reporter: Abhinav Roy Priority: Critical Fix For: 4.4.0 Steps : == 1. Deploy a advanced zone hyperv setup with 2 clusters. 2. Have 2 primary storages in each of the clusters and 2 zone wide primary storages. 3. Deploy a VM v1 on cluster wide primary storage in cluster1/2 4. Deply a VM v2 on zone wide primary storage in cluster1/2. 5. Now do a listStoragePoolsForMigration for ROOT volumes of v1 and v2 Expected behavior : = All zone wide primary storage and cluster wide primary storages available should be listed Observed behavior : = 1. list for v1 doesn't show any zone wide primary storage. monkey# find storagepoolsformigration id=31 count = 1 storagepool: name = p2 id = b3fcb49c-b870-33e6-86f2-bb1eb72cceef clusterid = 5e649bb3-b2a8-49f9-9db0-ab50546d306a clustername = cluster1 created = 2014-05-26T11:27:01+0530 disksizeallocated = 1073741824 disksizetotal = 998772830208 disksizeused = 157359783936 ipaddress = SMB19 jobstatus = 0 overprovisionfactor = 2.0 path = /hyperv-share/abhinav-ps2?user=abhinavroy&domain=BLR podid = f36ada26-ecf2-4869-ba4f-d844ec23531a podname = hyperv scope = CLUSTER state = Up suitableformigration = False type = SMB zoneid = 242c701a-43e8-4790-84f3-9112ca0b5db7 zonename = hyperv 2. list for v2 doesn't show any cluster wide primary storage monkey# find storagepoolsformigration id=30 count = 1 storagepool: name = zwps id = 3f754d4f-365c-3bd1-93d1-c3c9947fb3cc created = 2014-05-30T11:57:02+0530 disksizeallocated = 0 disksizetotal = 998772830208 hypervisor = Hyperv ipaddress = SMB19 jobstatus = 0 overprovisionfactor = 2.0 path = /hyperv-share/abhinav-ps6?user=abhinavroy&domain=BLR scope = ZONE state = Up suitableformigration = False type = SMB zoneid = 242c701a-43e8-4790-84f3-9112ca0b5db7 zonename = hyperv NOTE : Even though the pools are not listed, if the migration is attemped using the API and passing these storage pool ids, migration succeeds from zwps to cwps and vice-versa -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6809) listStoragePoolsForMigration doesn't list the zone wide primary storages if the volume is on cluster-wide storage, and doesn't list cwps if volume is on zwps
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinav Roy updated CLOUDSTACK-6809: Description: Steps : == 1. Deploy a advanced zone hyperv setup with 2 clusters. 2. Have 2 primary storages in each of the clusters and 2 zone wide primary storages. 3. Deploy a VM v1 on cluster wide primary storage in cluster1/2 4. Deply a VM v2 on zone wide primary storage in cluster1/2. 5. Now do a listStoragePoolsForMigration for ROOT volumes of v1 and v2 Expected behavior : = All zone wide primary storage and cluster wide primary storages available should be listed Observed behavior : = 1. list for v1 doesn't show any zone wide primary storage. monkey# find storagepoolsformigration id=31 count = 1 storagepool: name = p2 id = b3fcb49c-b870-33e6-86f2-bb1eb72cceef clusterid = 5e649bb3-b2a8-49f9-9db0-ab50546d306a clustername = cluster1 created = 2014-05-26T11:27:01+0530 disksizeallocated = 1073741824 disksizetotal = 998772830208 disksizeused = 157359783936 ipaddress = SMB19 jobstatus = 0 overprovisionfactor = 2.0 path = /hyperv-share/abhinav-ps2?user=abhinavroy&domain=BLR podid = f36ada26-ecf2-4869-ba4f-d844ec23531a podname = hyperv scope = CLUSTER state = Up suitableformigration = False type = SMB zoneid = 242c701a-43e8-4790-84f3-9112ca0b5db7 zonename = hyperv 2. list for v2 doesn't show any cluster wide primary storage monkey# find storagepoolsformigration id=30 count = 1 storagepool: name = zwps id = 3f754d4f-365c-3bd1-93d1-c3c9947fb3cc created = 2014-05-30T11:57:02+0530 disksizeallocated = 0 disksizetotal = 998772830208 hypervisor = Hyperv ipaddress = SMB19 jobstatus = 0 overprovisionfactor = 2.0 path = /hyperv-share/abhinav-ps6?user=abhinavroy&domain=BLR scope = ZONE state = Up suitableformigration = False type = SMB zoneid = 242c701a-43e8-4790-84f3-9112ca0b5db7 zonename = hyperv NOTE : Even though the pools are not listed, if the migration is attempted using the API and passing these storage pool ids, migration succeeds from zwps to cwps and vice-versa was: Steps : == 1. Deploy a advanced zone hyperv setup with 2 clusters. 2. Have 2 primary storages in each of the clusters and 2 zone wide primary storages. 3. Deploy a VM v1 on cluster wide primary storage in cluster1/2 4. Deply a VM v2 on zone wide primary storage in cluster1/2. 5. Now do a listStoragePoolsForMigration for ROOT volumes of v1 and v2 Expected behavior : = All zone wide primary storage and cluster wide primary storages available should be listed Observed behavior : = 1. list for v1 doesn't show any zone wide primary storage. monkey# find storagepoolsformigration id=31 count = 1 storagepool: name = p2 id = b3fcb49c-b870-33e6-86f2-bb1eb72cceef clusterid = 5e649bb3-b2a8-49f9-9db0-ab50546d306a clustername = cluster1 created = 2014-05-26T11:27:01+0530 disksizeallocated = 1073741824 disksizetotal = 998772830208 disksizeused = 157359783936 ipaddress = SMB19 jobstatus = 0 overprovisionfactor = 2.0 path = /hyperv-share/abhinav-ps2?user=abhinavroy&domain=BLR podid = f36ada26-ecf2-4869-ba4f-d844ec23531a podname = hyperv scope = CLUSTER state = Up suitableformigration = False type = SMB zoneid = 242c701a-43e8-4790-84f3-9112ca0b5db7 zonename = hyperv 2. list for v2 doesn't show any cluster wide primary storage monkey# find storagepoolsformigration id=30 count = 1 storagepool: name = zwps id = 3f754d4f-365c-3bd1-93d1-c3c9947fb3cc created = 2014-05-30T11:57:02+0530 disksizeallocated = 0 disksizetotal = 998772830208 hypervisor = Hyperv ipaddress = SMB19 jobstatus = 0 overprovisionfactor = 2.0 path = /hyperv-share/abhinav-ps6?user=abhinavroy&domain=BLR scope = ZONE state = Up suitableformigration = False type = SMB zoneid = 242c701a-43e8-4790-84f3-9112ca0b5db7 zonename = hyperv NOTE : Even though the pools are not listed, if the migration is attemped using the API and passing these storage pool ids, migration succeeds from zwps to cwps and vice-versa > listStoragePoolsForMigration doesn't list the zone wide primary storages if > the volume is on cluster-wide storage, and doesn't list cwps if volume is on > zwps > -- > > Key: CLOUDSTACK-6809 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6809 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Storage Controller >Affects Versions: 4.4.0 > Environment: HyperV Advanced zone setup with cluster wide, zone wide > and local storages. >Reporter: Abhinav Roy >Priority: Critical >
[jira] [Closed] (CLOUDSTACK-6754) SSVM not responding with S3 secondary sotre
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavan Kumar Bandarupally closed CLOUDSTACK-6754. Closing the bug as it is invalid. Will open a new one for seed URL change. > SSVM not responding with S3 secondary sotre > --- > > Key: CLOUDSTACK-6754 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6754 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Storage Controller, SystemVM, Template >Affects Versions: 4.4.0 > Environment: Host: Xenserver > Secondary Store: Image store with S3 as provider >Reporter: Pavan Kumar Bandarupally >Assignee: Min Chen >Priority: Blocker > Fix For: 4.4.0 > > Attachments: cloud.log, cloudoutfile.zip, management-server.log > > > A new zone is created and systemVMs are up. The systemvm template is > downloaded to S3 bucket. Once the SSVMs are up, the default BUILTIN centos > template or any other template that we try to register manually are not > getting downloaded to SSVM. There is no exception generated as well. > The registerTemplate API call is just listed in the MS traces and no further > action happens. Attaching the MS logs and SSVM log. There is no trace of any > exception in SSVM log as well. Attaching the /var/log/cloud/cloud.out , which > is the only file that has some exception listed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6808) Need to add Database Information to Alter table statements in a commit to schema-430to440.sql
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi reassigned CLOUDSTACK-6808: --- Assignee: Rajani Karuturi > Need to add Database Information to Alter table statements in a commit to > schema-430to440.sql > -- > > Key: CLOUDSTACK-6808 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6808 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.0 >Reporter: Chandan Purushothama >Assignee: Rajani Karuturi >Priority: Critical > Fix For: 4.4.0 > > > Database Information is missing in the commit shown below > diff --git a/setup/db/db/schema-430to440.sql b/setup/db/db/schema-430to440.sql > index 3b525c4..2262608 100644 (file) > --- a/setup/db/db/schema-430to440.sql > +++ b/setup/db/db/schema-430to440.sql > @@ -1676,3 +1676,12 @@ CREATE TABLE `cloud`.`network_acl_item_cidrs` ( > ALTER TABLE `cloud`.`load_balancer_healthcheck_policies` ADD COLUMN `display` > tinyint(1) NOT NULL DEFAULT '1' COMMENT 'True if the policy can be displayed > to the end user'; > ALTER TABLE `cloud`.`load_balancer_stickiness_policies` ADD COLUMN `display` > tinyint(1) NOT NULL DEFAULT '1' COMMENT 'True if the policy can be displayed > to the end user'; > + > +alter table user_ip_address add column removed datetime DEFAULT NULL COMMENT > 'date removed'; > +alter table user_ip_address add column created datetime NULL COMMENT 'date > created'; > + > +alter table vlan add column removed datetime DEFAULT NULL COMMENT 'date > removed'; > +alter table vlan add column created datetime NULL COMMENT 'date created'; > + > +alter table user_ip_address drop key public_ip_address; > +alter table user_ip_address add UNIQUE KEY public_ip_address > (public_ip_address,source_network_id, removed); > \ No newline at end of file -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6808) Need to add Database Information to Alter table statements in a commit to schema-430to440.sql
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-6808: Priority: Critical (was: Major) > Need to add Database Information to Alter table statements in a commit to > schema-430to440.sql > -- > > Key: CLOUDSTACK-6808 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6808 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.4.0 >Reporter: Chandan Purushothama >Priority: Critical > Fix For: 4.4.0 > > > Database Information is missing in the commit shown below > diff --git a/setup/db/db/schema-430to440.sql b/setup/db/db/schema-430to440.sql > index 3b525c4..2262608 100644 (file) > --- a/setup/db/db/schema-430to440.sql > +++ b/setup/db/db/schema-430to440.sql > @@ -1676,3 +1676,12 @@ CREATE TABLE `cloud`.`network_acl_item_cidrs` ( > ALTER TABLE `cloud`.`load_balancer_healthcheck_policies` ADD COLUMN `display` > tinyint(1) NOT NULL DEFAULT '1' COMMENT 'True if the policy can be displayed > to the end user'; > ALTER TABLE `cloud`.`load_balancer_stickiness_policies` ADD COLUMN `display` > tinyint(1) NOT NULL DEFAULT '1' COMMENT 'True if the policy can be displayed > to the end user'; > + > +alter table user_ip_address add column removed datetime DEFAULT NULL COMMENT > 'date removed'; > +alter table user_ip_address add column created datetime NULL COMMENT 'date > created'; > + > +alter table vlan add column removed datetime DEFAULT NULL COMMENT 'date > removed'; > +alter table vlan add column created datetime NULL COMMENT 'date created'; > + > +alter table user_ip_address drop key public_ip_address; > +alter table user_ip_address add UNIQUE KEY public_ip_address > (public_ip_address,source_network_id, removed); > \ No newline at end of file -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6807) [HyperV] [Doc] Hyper-v requires all virtual switch names should be same across the entire cluster for live migration of VM to succeed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar updated CLOUDSTACK-6807: --- Description: In setup process we have to mention one more step that Hyper-v requires all virtual switch names should be same across the entire cluster for live migration of VM to succeed as mentioned @http://technet.microsoft.com/en-us/library/ff715313%28v=ws.10%29.aspx#BKMK_switchname. was: Hyper-v requires all virtual switch names should be same across the entire cluster for live migration of VM to succeed as mentioned @http://technet.microsoft.com/en-us/library/ff715313%28v=ws.10%29.aspx#BKMK_switchname. > [HyperV] [Doc] Hyper-v requires all virtual switch names should be same > across the entire cluster for live migration of VM to succeed > - > > Key: CLOUDSTACK-6807 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6807 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Anshul Gangwar >Priority: Critical > Labels: docs, hyper-V,, hyper-v > > In setup process we have to mention one more step that Hyper-v requires all > virtual switch names should be same across the entire cluster for live > migration of VM to succeed as mentioned > @http://technet.microsoft.com/en-us/library/ff715313%28v=ws.10%29.aspx#BKMK_switchname. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6807) [HyperV] Storage motion/migration is failing if the Hosts are having different vswitch names
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar updated CLOUDSTACK-6807: --- Description: Hyper-v requires all virtual switch names should be same across the entire cluster for live migration of VM to succeed as mentioned @http://technet.microsoft.com/en-us/library/ff715313%28v=ws.10%29.aspx#BKMK_switchname. > [HyperV] Storage motion/migration is failing if the Hosts are having > different vswitch names > > > Key: CLOUDSTACK-6807 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6807 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Anshul Gangwar >Priority: Critical > Labels: docs, hyper-V,, hyper-v > > Hyper-v requires all virtual switch names should be same across the entire > cluster for live migration of VM to succeed as mentioned > @http://technet.microsoft.com/en-us/library/ff715313%28v=ws.10%29.aspx#BKMK_switchname. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6808) Need to add Database Information to Alter table statements in a commit to schema-430to440.sql
Chandan Purushothama created CLOUDSTACK-6808: Summary: Need to add Database Information to Alter table statements in a commit to schema-430to440.sql Key: CLOUDSTACK-6808 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6808 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Reporter: Chandan Purushothama Fix For: 4.4.0 Database Information is missing in the commit shown below diff --git a/setup/db/db/schema-430to440.sql b/setup/db/db/schema-430to440.sql index 3b525c4..2262608 100644 (file) --- a/setup/db/db/schema-430to440.sql +++ b/setup/db/db/schema-430to440.sql @@ -1676,3 +1676,12 @@ CREATE TABLE `cloud`.`network_acl_item_cidrs` ( ALTER TABLE `cloud`.`load_balancer_healthcheck_policies` ADD COLUMN `display` tinyint(1) NOT NULL DEFAULT '1' COMMENT 'True if the policy can be displayed to the end user'; ALTER TABLE `cloud`.`load_balancer_stickiness_policies` ADD COLUMN `display` tinyint(1) NOT NULL DEFAULT '1' COMMENT 'True if the policy can be displayed to the end user'; + +alter table user_ip_address add column removed datetime DEFAULT NULL COMMENT 'date removed'; +alter table user_ip_address add column created datetime NULL COMMENT 'date created'; + +alter table vlan add column removed datetime DEFAULT NULL COMMENT 'date removed'; +alter table vlan add column created datetime NULL COMMENT 'date created'; + +alter table user_ip_address drop key public_ip_address; +alter table user_ip_address add UNIQUE KEY public_ip_address (public_ip_address,source_network_id, removed); \ No newline at end of file -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6807) [HyperV] [Doc] VM migration is failing if the Hosts are having different vswitch names
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar updated CLOUDSTACK-6807: --- Summary: [HyperV] [Doc] VM migration is failing if the Hosts are having different vswitch names (was: [HyperV] Storage motion/migration is failing if the Hosts are having different vswitch names) > [HyperV] [Doc] VM migration is failing if the Hosts are having different > vswitch names > -- > > Key: CLOUDSTACK-6807 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6807 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Anshul Gangwar >Priority: Critical > Labels: docs, hyper-V,, hyper-v > > Hyper-v requires all virtual switch names should be same across the entire > cluster for live migration of VM to succeed as mentioned > @http://technet.microsoft.com/en-us/library/ff715313%28v=ws.10%29.aspx#BKMK_switchname. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6807) [HyperV] [Doc] Hyper-v requires all virtual switch names should be same across the entire cluster for live migration of VM to succeed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anshul Gangwar updated CLOUDSTACK-6807: --- Summary: [HyperV] [Doc] Hyper-v requires all virtual switch names should be same across the entire cluster for live migration of VM to succeed (was: [HyperV] [Doc] VM migration is failing if the Hosts are having different vswitch names) > [HyperV] [Doc] Hyper-v requires all virtual switch names should be same > across the entire cluster for live migration of VM to succeed > - > > Key: CLOUDSTACK-6807 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6807 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc >Reporter: Anshul Gangwar >Priority: Critical > Labels: docs, hyper-V,, hyper-v > > Hyper-v requires all virtual switch names should be same across the entire > cluster for live migration of VM to succeed as mentioned > @http://technet.microsoft.com/en-us/library/ff715313%28v=ws.10%29.aspx#BKMK_switchname. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6807) [HyperV] Storage motion/migration is failing if the Hosts are having different vswitch names
Anshul Gangwar created CLOUDSTACK-6807: -- Summary: [HyperV] Storage motion/migration is failing if the Hosts are having different vswitch names Key: CLOUDSTACK-6807 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6807 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Doc Reporter: Anshul Gangwar Priority: Critical -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6778) [HyperV] Storage motion/migration is failing if the Hosts are having different NIC names
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshul Gangwar resolved CLOUDSTACK-6778.
Resolution: Won't Fix
> [HyperV] Storage motion/migration is failing if the Hosts are having
> different NIC names
>
>
> Key: CLOUDSTACK-6778
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6778
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller, Management Server
>Affects Versions: 4.4.0
>Reporter: Abhinav Roy
>Assignee: Anshul Gangwar
>Priority: Critical
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.4.0
>
>
> Steps :
> ==
> 1. Deploy a CS advanced zone setup with HyperV having 2 clusters.
> 2. cl1 has 2 hosts h1 and h2, cl2 has 1 host h3,
> 3. Deploy a VM on cl1 and the migrate that VM2 to h3.
> Here the NIC names of h1 and h3 are different :
> h1 : Broadcom BCM5716C NetXtreme II GigE (NDIS VBD Client) #38 - Virtual
>Switch
> h3 : Broadcom BCM5716C NetXtreme II GigE (NDIS VBD Client) #39 - Virtual
> Switch
> Expected behavior :
> ===
> The migration of VM with storage should succeed.
> Observed behavior :
> ===
> Migration fails with the following error :
> 2014-05-27 14:29:09,072 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-434:ctx-960ed94b) POST response is
> [{"com.cloud.agent.api.MigrateWithStorageAnswer":{"result":false,"volumeTos":[{"id":9,"name":"ROOT-7","path":"f2c8aa38-288f-4477-afd7-b2c23f5fd848","size":5368709120,"type":"ROOT","storagePoolType":"SMB","storagePoolUuid":"38aee7de-07f1-3f23-8f8d-6a772fb9811d","deviceId":0}],"details":"com.cloud.agent.api.MigrateWithStorageCommand
> failed due to Hyper-V Job failed, Error Code:32784, Description: Virtual
> machine migration operation for 'i-2-7-VM' failed at migration destination
> 'HYPERV20.blr.cloudstack.org'. (Virtual machine ID
> FF9CAE31-3CD1-4F19-886B-8FBE58E669F7)
> The virtual machine 'i-2-7-VM' is not compatible with physical computer
> 'HYPERV20'. (Virtual machine ID FF9CAE31-3CD1-4F19-886B-8FBE58E669F7)
> Could not find Ethernet switch 'Broadcom BCM5716C NetXtreme II GigE (NDIS VBD
> Client) #39 - Virtual Switch'.","contextMap":{}}}]
> 2014-05-27 14:29:09,073 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-434:ctx-960ed94b) executeRequest received response
> [Lcom.cloud.agent.api.Answer;@3ab8553b
> 2014-05-27 14:29:09,073 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-434:ctx-960ed94b) Seq 5-2135832123280457911: Response Received:
> 2014-05-27 14:29:09,073 DEBUG [c.c.a.t.Request]
> (DirectAgent-434:ctx-960ed94b) Seq 5-2135832123280457911: Processing: { Ans:
> , MgmtId: 213737702773493, via: 5, Ver: v1, Flags: 110,
> [{"com.cloud.agent.api.MigrateWithStorageAnswer":{"volumeTos":[{"name":"ROOT-7","size":5368709120,"path":"f2c8aa38-288f-4477-afd7-b2c23f5fd848","accountId":0,"id":9,"deviceId":0}],"result":false,"details":"com.cloud.agent.api.MigrateWithStorageCommand
> failed due to Hyper-V Job failed, Error Code:32784, Description: Virtual
> machine migration operation for 'i-2-7-VM' failed at migration destination
> 'HYPERV20.blr.cloudstack.org'. (Virtual machine ID
> FF9CAE31-3CD1-4F19-886B-8FBE58E669F7)\n\nThe virtual machine 'i-2-7-VM' is
> not compatible with physical computer 'HYPERV20'. (Virtual machine ID
> FF9CAE31-3CD1-4F19-886B-8FBE58E669F7)\n\nCould not find Ethernet switch
> 'Broadcom BCM5716C NetXtreme II GigE (NDIS VBD Client) #39 - Virtual
> Switch'.","wait":0}}] }
> 2014-05-27 14:29:09,074 DEBUG [c.c.a.t.Request]
> (Work-Job-Executor-5:ctx-083e8c2f job-45/job-46 ctx-966940f6) Seq
> 5-2135832123280457911: Received: { Ans: , MgmtId: 213737702773493, via: 5,
> Ver: v1, Flags: 110, { MigrateWithStorageAnswer } }
> 2014-05-27 14:29:09,077 DEBUG [c.c.a.m.AgentAttache]
> (DirectAgent-434:ctx-960ed94b) Seq 5-2135832123280457911: No more commands
> found
> 2014-05-27 14:29:09,074 ERROR [o.a.c.s.m.HypervStorageMotionStrategy]
> (Work-Job-Executor-5:ctx-083e8c2f job-45/job-46 ctx-966940f6) Migration with
> storage of vm VM[User|i-2-7-VM] failed. Details:
> com.cloud.agent.api.MigrateWithStorageCommand failed due to Hyper-V Job
> failed, Error Code:32784, Description: Virtual machine migration operation
> for 'i-2-7-VM' failed at migration destination 'HYPERV20.blr.cloudstack.org'.
> (Virtual machine ID FF9CAE31-3CD1-4F19-886B-8FBE58E669F7)
> The virtual machine 'i-2-7-VM' is not compatible with physical computer
> 'HYPERV20'. (Virtual machine ID FF9CAE31-3CD1-4F19-886B-8FBE58E669F7)
> Could not find Ethernet switch 'Broadcom BCM5716
[jira] [Commented] (CLOUDSTACK-6778) [HyperV] Storage motion/migration is failing if the Hosts are having different NIC names
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013315#comment-14013315
]
Anshul Gangwar commented on CLOUDSTACK-6778:
This is setup issue as hyper-v requires all virtual switch names should be same
across the entire cluster as mentioned
@http://technet.microsoft.com/en-us/library/ff715313%28v=ws.10%29.aspx#BKMK_switchname.
We have to mention this in docs in setup process. Creating doc bug for this.
> [HyperV] Storage motion/migration is failing if the Hosts are having
> different NIC names
>
>
> Key: CLOUDSTACK-6778
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6778
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller, Management Server
>Affects Versions: 4.4.0
>Reporter: Abhinav Roy
>Assignee: Anshul Gangwar
>Priority: Critical
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.4.0
>
>
> Steps :
> ==
> 1. Deploy a CS advanced zone setup with HyperV having 2 clusters.
> 2. cl1 has 2 hosts h1 and h2, cl2 has 1 host h3,
> 3. Deploy a VM on cl1 and the migrate that VM2 to h3.
> Here the NIC names of h1 and h3 are different :
> h1 : Broadcom BCM5716C NetXtreme II GigE (NDIS VBD Client) #38 - Virtual
>Switch
> h3 : Broadcom BCM5716C NetXtreme II GigE (NDIS VBD Client) #39 - Virtual
> Switch
> Expected behavior :
> ===
> The migration of VM with storage should succeed.
> Observed behavior :
> ===
> Migration fails with the following error :
> 2014-05-27 14:29:09,072 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-434:ctx-960ed94b) POST response is
> [{"com.cloud.agent.api.MigrateWithStorageAnswer":{"result":false,"volumeTos":[{"id":9,"name":"ROOT-7","path":"f2c8aa38-288f-4477-afd7-b2c23f5fd848","size":5368709120,"type":"ROOT","storagePoolType":"SMB","storagePoolUuid":"38aee7de-07f1-3f23-8f8d-6a772fb9811d","deviceId":0}],"details":"com.cloud.agent.api.MigrateWithStorageCommand
> failed due to Hyper-V Job failed, Error Code:32784, Description: Virtual
> machine migration operation for 'i-2-7-VM' failed at migration destination
> 'HYPERV20.blr.cloudstack.org'. (Virtual machine ID
> FF9CAE31-3CD1-4F19-886B-8FBE58E669F7)
> The virtual machine 'i-2-7-VM' is not compatible with physical computer
> 'HYPERV20'. (Virtual machine ID FF9CAE31-3CD1-4F19-886B-8FBE58E669F7)
> Could not find Ethernet switch 'Broadcom BCM5716C NetXtreme II GigE (NDIS VBD
> Client) #39 - Virtual Switch'.","contextMap":{}}}]
> 2014-05-27 14:29:09,073 DEBUG [c.c.h.h.r.HypervDirectConnectResource]
> (DirectAgent-434:ctx-960ed94b) executeRequest received response
> [Lcom.cloud.agent.api.Answer;@3ab8553b
> 2014-05-27 14:29:09,073 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-434:ctx-960ed94b) Seq 5-2135832123280457911: Response Received:
> 2014-05-27 14:29:09,073 DEBUG [c.c.a.t.Request]
> (DirectAgent-434:ctx-960ed94b) Seq 5-2135832123280457911: Processing: { Ans:
> , MgmtId: 213737702773493, via: 5, Ver: v1, Flags: 110,
> [{"com.cloud.agent.api.MigrateWithStorageAnswer":{"volumeTos":[{"name":"ROOT-7","size":5368709120,"path":"f2c8aa38-288f-4477-afd7-b2c23f5fd848","accountId":0,"id":9,"deviceId":0}],"result":false,"details":"com.cloud.agent.api.MigrateWithStorageCommand
> failed due to Hyper-V Job failed, Error Code:32784, Description: Virtual
> machine migration operation for 'i-2-7-VM' failed at migration destination
> 'HYPERV20.blr.cloudstack.org'. (Virtual machine ID
> FF9CAE31-3CD1-4F19-886B-8FBE58E669F7)\n\nThe virtual machine 'i-2-7-VM' is
> not compatible with physical computer 'HYPERV20'. (Virtual machine ID
> FF9CAE31-3CD1-4F19-886B-8FBE58E669F7)\n\nCould not find Ethernet switch
> 'Broadcom BCM5716C NetXtreme II GigE (NDIS VBD Client) #39 - Virtual
> Switch'.","wait":0}}] }
> 2014-05-27 14:29:09,074 DEBUG [c.c.a.t.Request]
> (Work-Job-Executor-5:ctx-083e8c2f job-45/job-46 ctx-966940f6) Seq
> 5-2135832123280457911: Received: { Ans: , MgmtId: 213737702773493, via: 5,
> Ver: v1, Flags: 110, { MigrateWithStorageAnswer } }
> 2014-05-27 14:29:09,077 DEBUG [c.c.a.m.AgentAttache]
> (DirectAgent-434:ctx-960ed94b) Seq 5-2135832123280457911: No more commands
> found
> 2014-05-27 14:29:09,074 ERROR [o.a.c.s.m.HypervStorageMotionStrategy]
> (Work-Job-Executor-5:ctx-083e8c2f job-45/job-46 ctx-966940f6) Migration with
> storage of vm VM[User|i-2-7-VM] failed. Details:
> com.cloud.agent.api.MigrateWithStorageCommand failed due to Hyper-V Job
> failed, Error Code:32784, Description: Virtual machine migration operation
> for 'i-2-7-VM' faile
[jira] [Closed] (CLOUDSTACK-6794) [Automation]: test_iso suite is failing because of no path to iso retrieval
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Kumar closed CLOUDSTACK-6794.
Resolution: Fixed
> [Automation]: test_iso suite is failing because of no path to iso retrieval
> ---
>
> Key: CLOUDSTACK-6794
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6794
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Reporter: Santhosh Kumar Edukulla
>Assignee: Bharat Kumar
>
> From the environment, where bvt is running, the path to download iso was not
> reachable, below url "http://people.apache.org/~tsp/dummy.iso";, was used for
> downloading iso and the setup either need to have access to the this url or
> url path for local share has to be used, still otherwise these suites will
> fail.
> "iso": {
> "displaytext": "Test ISO",
> "name": "ISO",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "bootable": False,
> "ispublic": False,
> "ostype": "CentOS 5.6 (64-bit)",
> },
> "iso1": {
> "displaytext": "Test ISO 1",
> "name": "ISO 1",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "isextractable": True,
> "isfeatured": True,
> "ispublic": True,
> "ostype": "CentOS 5.6 (64-bit)",
> },
> "iso2": {
> "displaytext": "Test ISO 2",
> "name": "ISO 2",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "isextractable": True,
> "isfeatured": True,
> "ispublic": True,
> "ostype": "CentOS 5.6 (64-bit)",
> "mode": 'HTTP_DOWNLOAD',
> Test Suite Exception Trace:
> File
> "/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/suite.py",
> line 208, in run
> self.setUp()
> File
> "/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/suite.py",
> line 291, in setUp
> self.setupContext(ancestor)
> File
> "/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/suite.py",
> line 314, in setupContext
> try_run(context, names)
> File
> "/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/util.py",
> line 470, in try_run
> return func()
> File
> "/automation/virtenv/00-16-3e-5d-4a-0e/306/test/integration/smoke/test_iso.py",
> line 188, in setUpClass
> % (cls.iso_1.id, e))
> 'Exception while downloading ISO d64c0284-8a03-42a1-8ce6-e6d2c53724ea: Error
> In Downloading ISO: ISO Status - No route to host\n >>
> begin captured stdout << -\n=== TestName: None | Status :
> EXCEPTION ===\n\n
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6794) [Automation]: test_iso suite is failing because of no path to iso retrieval
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013308#comment-14013308
]
Bharat Kumar commented on CLOUDSTACK-6794:
--
Hi ,
This fix is environment specific. This requires changing the test_data.py.
pushing this change into the repo might break tests running in some other env.
Currently we have fixed the issue by reading from a local copy of test_data.py.
> [Automation]: test_iso suite is failing because of no path to iso retrieval
> ---
>
> Key: CLOUDSTACK-6794
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6794
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Reporter: Santhosh Kumar Edukulla
>Assignee: Bharat Kumar
>
> From the environment, where bvt is running, the path to download iso was not
> reachable, below url "http://people.apache.org/~tsp/dummy.iso";, was used for
> downloading iso and the setup either need to have access to the this url or
> url path for local share has to be used, still otherwise these suites will
> fail.
> "iso": {
> "displaytext": "Test ISO",
> "name": "ISO",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "bootable": False,
> "ispublic": False,
> "ostype": "CentOS 5.6 (64-bit)",
> },
> "iso1": {
> "displaytext": "Test ISO 1",
> "name": "ISO 1",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "isextractable": True,
> "isfeatured": True,
> "ispublic": True,
> "ostype": "CentOS 5.6 (64-bit)",
> },
> "iso2": {
> "displaytext": "Test ISO 2",
> "name": "ISO 2",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "isextractable": True,
> "isfeatured": True,
> "ispublic": True,
> "ostype": "CentOS 5.6 (64-bit)",
> "mode": 'HTTP_DOWNLOAD',
> Test Suite Exception Trace:
> File
> "/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/suite.py",
> line 208, in run
> self.setUp()
> File
> "/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/suite.py",
> line 291, in setUp
> self.setupContext(ancestor)
> File
> "/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/suite.py",
> line 314, in setupContext
> try_run(context, names)
> File
> "/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/util.py",
> line 470, in try_run
> return func()
> File
> "/automation/virtenv/00-16-3e-5d-4a-0e/306/test/integration/smoke/test_iso.py",
> line 188, in setUpClass
> % (cls.iso_1.id, e))
> 'Exception while downloading ISO d64c0284-8a03-42a1-8ce6-e6d2c53724ea: Error
> In Downloading ISO: ISO Status - No route to host\n >>
> begin captured stdout << -\n=== TestName: None | Status :
> EXCEPTION ===\n\n
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6794) [Automation]: test_iso suite is failing because of no path to iso retrieval
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek updated CLOUDSTACK-6794:
---
Assignee: Bharat Kumar (was: Abhinandan Prateek)
> [Automation]: test_iso suite is failing because of no path to iso retrieval
> ---
>
> Key: CLOUDSTACK-6794
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6794
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Automation
>Reporter: Santhosh Kumar Edukulla
>Assignee: Bharat Kumar
>
> From the environment, where bvt is running, the path to download iso was not
> reachable, below url "http://people.apache.org/~tsp/dummy.iso";, was used for
> downloading iso and the setup either need to have access to the this url or
> url path for local share has to be used, still otherwise these suites will
> fail.
> "iso": {
> "displaytext": "Test ISO",
> "name": "ISO",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "bootable": False,
> "ispublic": False,
> "ostype": "CentOS 5.6 (64-bit)",
> },
> "iso1": {
> "displaytext": "Test ISO 1",
> "name": "ISO 1",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "isextractable": True,
> "isfeatured": True,
> "ispublic": True,
> "ostype": "CentOS 5.6 (64-bit)",
> },
> "iso2": {
> "displaytext": "Test ISO 2",
> "name": "ISO 2",
> "url": "http://people.apache.org/~tsp/dummy.iso";,
> "isextractable": True,
> "isfeatured": True,
> "ispublic": True,
> "ostype": "CentOS 5.6 (64-bit)",
> "mode": 'HTTP_DOWNLOAD',
> Test Suite Exception Trace:
> File
> "/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/suite.py",
> line 208, in run
> self.setUp()
> File
> "/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/suite.py",
> line 291, in setUp
> self.setupContext(ancestor)
> File
> "/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/suite.py",
> line 314, in setupContext
> try_run(context, names)
> File
> "/automation/virtenv/00-16-3e-5d-4a-0e/306/testenv/lib/python2.7/site-packages/nose/util.py",
> line 470, in try_run
> return func()
> File
> "/automation/virtenv/00-16-3e-5d-4a-0e/306/test/integration/smoke/test_iso.py",
> line 188, in setUpClass
> % (cls.iso_1.id, e))
> 'Exception while downloading ISO d64c0284-8a03-42a1-8ce6-e6d2c53724ea: Error
> In Downloading ISO: ISO Status - No route to host\n >>
> begin captured stdout << -\n=== TestName: None | Status :
> EXCEPTION ===\n\n
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CLOUDSTACK-6806) UI:API: If VM start is performed when createTemplate from Volume is in progress, user should be notified
Parth Jagirdar created CLOUDSTACK-6806: -- Summary: UI:API: If VM start is performed when createTemplate from Volume is in progress, user should be notified Key: CLOUDSTACK-6806 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6806 Project: CloudStack Issue Type: Improvement Security Level: Public (Anyone can view this level - this is the default.) Components: API, UI Affects Versions: 4.4.0 Reporter: Parth Jagirdar Perform following, create a VM, Create a Template from volume. (The pre-req is VM must be in stopped state) Verify that the newly listed template is listed on UI. click on template and check that ready=no. (Template creation still in progress) While status Ready=no is true, attempt to start the VM. Observe that upon VM start the template is no longer listed on UI and DB entry for this template is removed. (DB entry is entirely removed from table instead of marking removed field; this is by design) Proposal is to:: Notify user upon VM start when Template creation is in progress Instead of removing/deleting template without notifying. If volume is big enough createTemplate can take a while and its very likely that user may attempt to start VM. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-6805) UI - Unable to create an account when the password field contains ‘#’ charactrer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012798#comment-14012798 ] Jessica Wang edited comment on CLOUDSTACK-6805 at 5/29/14 8:01 PM: --- http://bugs-ccp.citrix.com/i#browse/CS-20110 http://bugs-ccp.citrix.com/i#browse/CS-20109 was (Author: jessicawang): http://bugs-ccp.citrix.com/i#browse/CS-20110 > UI - Unable to create an account when the password field contains ‘#’ > charactrer > - > > Key: CLOUDSTACK-6805 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6805 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6805) UI - Unable to create an account when the password field contains ‘#’ charactrer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang closed CLOUDSTACK-6805. > UI - Unable to create an account when the password field contains ‘#’ > charactrer > - > > Key: CLOUDSTACK-6805 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6805 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6805) UI - Unable to create an account when the password field contains ‘#’ charactrer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-6805. -- Resolution: Fixed > UI - Unable to create an account when the password field contains ‘#’ > charactrer > - > > Key: CLOUDSTACK-6805 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6805 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6805) UI - Unable to create an account when the password field contains ‘#’ charactrer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012797#comment-14012797 ] ASF subversion and git services commented on CLOUDSTACK-6805: - Commit 9f4d4646408d12d4ce7a55aa89d6e8a6914b108e in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9f4d464 ] CLOUDSTACK-6805: UI > create account > fix a bug that account creation failed when password contains # character. > UI - Unable to create an account when the password field contains ‘#’ > charactrer > - > > Key: CLOUDSTACK-6805 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6805 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6805) UI - Unable to create an account when the password field contains ‘#’ charactrer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012798#comment-14012798 ] Jessica Wang commented on CLOUDSTACK-6805: -- http://bugs-ccp.citrix.com/i#browse/CS-20110 > UI - Unable to create an account when the password field contains ‘#’ > charactrer > - > > Key: CLOUDSTACK-6805 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6805 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6805) UI - Unable to create an account when the password field contains ‘#’ charactrer
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012717#comment-14012717 ] ASF subversion and git services commented on CLOUDSTACK-6805: - Commit 76c71c7bc1fc0368e7d86c63107e269f34787c23 in cloudstack's branch refs/heads/4.4-forward from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=76c71c7 ] CLOUDSTACK-6805: UI > create account > fix a bug that account creation failed when password contains # character. > UI - Unable to create an account when the password field contains ‘#’ > charactrer > - > > Key: CLOUDSTACK-6805 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6805 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Jessica Wang >Assignee: Jessica Wang > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6805) UI - Unable to create an account when the password field contains ‘#’ charactrer
Jessica Wang created CLOUDSTACK-6805: Summary: UI - Unable to create an account when the password field contains ‘#’ charactrer Key: CLOUDSTACK-6805 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6805 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6804) [Automation] Add host fails in KVM
Rayees Namathponnan created CLOUDSTACK-6804: --- Summary: [Automation] Add host fails in KVM Key: CLOUDSTACK-6804 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6804 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: KVM Affects Versions: 4.4.0 Environment: RHEL 6.3 Reporter: Rayees Namathponnan Priority: Blocker Fix For: 4.4.0 Add host failing in in KVM with RHEL 6.3 2014-05-29 11:09:24,951 INFO [c.c.r.ResourceManagerImpl] (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Trying to add a new host at http://10.223.250.194 in data center 1 2014-05-29 11:09:25,211 DEBUG [c.c.u.s.SSHCmdHelper] (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Executing cmd: lsmod|grep kvm 2014-05-29 11:09:26,454 DEBUG [c.c.u.s.SSHCmdHelper] (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Executing cmd: lsmod|grep kvm 2014-05-29 11:09:27,512 DEBUG [c.c.u.s.SSHCmdHelper] (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Executing cmd: lsmod|grep kvm 2014-05-29 11:09:28,568 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer] (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) It's not a KVM enabled machine 2014-05-29 11:09:28,571 WARN [c.c.r.ResourceManagerImpl] (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Unable to find the server resources at http://10.223.250.194 2014-05-29 11:09:28,574 INFO [c.c.u.e.CSExceptionErrorCode] (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2014-05-29 11:09:28,574 WARN [o.a.c.a.c.a.h.AddHostCmd] (catalina-exec-24:ctx-5e2c748e ctx-937164b5 ctx-8e5deda3) Exception: com.cloud.exception.DiscoveryException: Unable to add the host at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:791) at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:586) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy146.discoverHosts(Unknown Source) at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:141) at com.cloud.api.ApiServer.queueCommand(ApiServer.java:683) at com.cloud.api.ApiServer.handleRequest(ApiServer.java:506) at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:330) at com.cloud.api.ApiServlet.access$000(ApiServlet.java:54) at com.cloud.api.ApiServlet$1.run(ApiServlet.java:118) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:115) at com.cloud.api.ApiServlet.doGet(ApiServlet.java:77) 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:10
[jira] [Updated] (CLOUDSTACK-6803) UI:QuickView: Unable to render Quick view overlay on VM snapshots
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Jagirdar updated CLOUDSTACK-6803: --- Priority: Critical (was: Major) > UI:QuickView: Unable to render Quick view overlay on VM snapshots > - > > Key: CLOUDSTACK-6803 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6803 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.4.0 >Reporter: Parth Jagirdar >Priority: Critical > Attachments: qv_overlay.jpg > > > Create a VM, > Take a Snapshot, > Click on this Snapshot, > Hover mouse over Quick View icon, > Observer Quick View doesn't get rendered. > *** Click on the snapshot, observe that user is presented with a black > screen. (Due to this behavior, raising bug severity to Critical, As this > prevents user to perform operations on VM snapshot from the UI)) > Screen attached. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6803) UI:QuickView: Unable to render Quick view overlay on VM snapshots
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Jagirdar updated CLOUDSTACK-6803: --- Description: Create a VM, Take a Snapshot, Click on this Snapshot, Hover mouse over Quick View icon, Observer Quick View doesn't get rendered. *** Click on the snapshot, observe that user is presented with a black screen. (Due to this behavior, raising bug severity to Critical, As this prevents user to perform operations on VM snapshot from the UI)) Screen attached. was: Create a VM, Take a Snapshot, Click on this Snapshot, Hover mouse over Quick View icon, Observer Quick View doesn't get rendered. Screen attached. > UI:QuickView: Unable to render Quick view overlay on VM snapshots > - > > Key: CLOUDSTACK-6803 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6803 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.4.0 >Reporter: Parth Jagirdar > Attachments: qv_overlay.jpg > > > Create a VM, > Take a Snapshot, > Click on this Snapshot, > Hover mouse over Quick View icon, > Observer Quick View doesn't get rendered. > *** Click on the snapshot, observe that user is presented with a black > screen. (Due to this behavior, raising bug severity to Critical, As this > prevents user to perform operations on VM snapshot from the UI)) > Screen attached. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6803) UI:QuickView: Unable to render Quick view overlay on VM snapshots
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Jagirdar updated CLOUDSTACK-6803: --- Attachment: qv_overlay.jpg > UI:QuickView: Unable to render Quick view overlay on VM snapshots > - > > Key: CLOUDSTACK-6803 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6803 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Affects Versions: 4.4.0 >Reporter: Parth Jagirdar > Attachments: qv_overlay.jpg > > > Create a VM, > Take a Snapshot, > Click on this Snapshot, > Hover mouse over Quick View icon, > Observer Quick View doesn't get rendered. > Screen attached. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6803) UI:QuickView: Unable to render Quick view overlay on VM snapshots
Parth Jagirdar created CLOUDSTACK-6803: -- Summary: UI:QuickView: Unable to render Quick view overlay on VM snapshots Key: CLOUDSTACK-6803 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6803 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Parth Jagirdar Create a VM, Take a Snapshot, Click on this Snapshot, Hover mouse over Quick View icon, Observer Quick View doesn't get rendered. Screen attached. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6658) Unknown parameters... seen in the logs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012565#comment-14012565 ] Nitin Mehta commented on CLOUDSTACK-6658: - ParamGenericValidationWorker checks whether the params passed for the api are an exact match (nothing more nothing less) to the params we expect and if not throws only a warning as seen below.I dont think this adds any value and decreases the performance for production systems I believe. It is an eye sore in the logs as well. > Unknown parameters... seen in the logs > -- > > Key: CLOUDSTACK-6658 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6658 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.0 >Reporter: Nitin Mehta >Priority: Critical > Fix For: 4.4.0 > > > Log messages show me the following. Add ctxdetails in defaultParamNames in > ParamGenericValidationWorker to get rid of following log messages. > Received unknown parameters for command updateNetworkServiceProvider. Unknown > parameters : ctxdetails -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6658) Unknown parameters... seen in the logs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-6658: Assignee: (was: Nitin Mehta) > Unknown parameters... seen in the logs > -- > > Key: CLOUDSTACK-6658 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6658 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.0 >Reporter: Nitin Mehta >Priority: Critical > Fix For: 4.4.0 > > > Log messages show me the following. Add ctxdetails in defaultParamNames in > ParamGenericValidationWorker to get rid of following log messages. > Received unknown parameters for command updateNetworkServiceProvider. Unknown > parameters : ctxdetails -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6658) Unknown parameters... seen in the logs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-6658: Priority: Critical (was: Major) > Unknown parameters... seen in the logs > -- > > Key: CLOUDSTACK-6658 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6658 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.0 >Reporter: Nitin Mehta >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.4.0 > > > Log messages show me the following. Add ctxdetails in defaultParamNames in > ParamGenericValidationWorker to get rid of following log messages. > Received unknown parameters for command updateNetworkServiceProvider. Unknown > parameters : ctxdetails -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6658) Unknown parameters... seen in the logs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-6658: Summary: Unknown parameters... seen in the logs (was: Add ctxdetails in defaultParamNames in ParamGenericValidationWorker) > Unknown parameters... seen in the logs > -- > > Key: CLOUDSTACK-6658 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6658 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.4.0 >Reporter: Nitin Mehta >Assignee: Nitin Mehta > Fix For: 4.4.0 > > > Log messages show me the following. Add ctxdetails in defaultParamNames in > ParamGenericValidationWorker to get rid of following log messages. > Received unknown parameters for command updateNetworkServiceProvider. Unknown > parameters : ctxdetails -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6282) [Automation]: Adding new Testcases
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012321#comment-14012321 ] ASF subversion and git services commented on CLOUDSTACK-6282: - Commit cdf4047ce823edcdd73f9a1562abc9c27f473557 in cloudstack's branch refs/heads/master from monism [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=cdf4047 ] CLOUDSTACK-6282-Added Autometed test for network APIs after incorporating review comments > [Automation]: Adding new Testcases > -- > > Key: CLOUDSTACK-6282 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6282 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Vinay Vegesna >Assignee: Santhosh Kumar Edukulla > > [Automation]: Adding below new Test cases for test_escalations.py > test_01_list_volumes_pagination > test_02_list_volume_byid > test_03_data_volume_resize > test_04_custom_volume > test_05_volume_snapshot > test_06_volume_snapshot_policy > test_07_volume_snapshots_pagination > test_08_volume_extract > test_09_volume_upload -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6802) Attaching a data disk created on local storage to a VM is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012302#comment-14012302
]
Devdeep Singh commented on CLOUDSTACK-6802:
---
Issue is with the local storage pool allocators. They way it is listing pools
needs to be fixed. The query does a join on the details table even when no tags
are present which ends up returning an empty list.
> Attaching a data disk created on local storage to a VM is failing
> -
>
> Key: CLOUDSTACK-6802
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6802
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Storage Controller
>Affects Versions: 4.4.0
>Reporter: Abhinav Roy
>Assignee: Devdeep Singh
>Priority: Critical
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.4.0
>
>
> Steps :
> =
> 1. Deploy a CS advanced zone setup with both local storage and shared storage
> enabled.
> 2. Deploy VMs. ( both on shared and local storage)
> 3. create a disk offering with local storage
> 4. Create a data disk with local storage disk offering.
> 5. attach the datadisk created on step 4 to VM created on step 2
> Expected result :
> ===
> Volume should be attached successfully.
> Observed result :
> ==
> volume attach fails with following error.
> 2014-05-29 13:02:45,410 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-16:ctx-87ef4f22) ===START=== 10.101.254.225 -- GET
> command=createVolume&response=json&sessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3D&name=data-local2&zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7&diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24&_=1401348494217
> 2014-05-29 13:02:45,466 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-16:ctx-87ef4f22 ctx-bf1bb5b6) submit async job-64, details:
> AsyncJobVO {id:64, userId: 2, accountId: 2, instanceType: Volume, instanceId:
> 18, cmd:
> org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
> cmdInfo:
> {"id":"18","response":"json","sessionkey":"YYidBdJcBJV64kdZ8c+KOeSqY14\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":18,\"Volume\":\"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\",\"com.cloud.dc.DataCenter\":1,\"com.cloud.offering.DiskOffering\":14}","cmdEventType":"VOLUME.CREATE","ctxUserId":"2","name":"data-local2","diskOfferingId":"8cf4d614-08b8-455c-a99f-814f4b109d24","httpmethod":"GET","_":"1401348494217","uuid":"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d","ctxAccountId":"2","ctxStartEventId":"125","zoneId":"242c701a-43e8-4790-84f3-9112ca0b5db7"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-29 13:02:45,467 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-16:ctx-87ef4f22 ctx-bf1bb5b6) ===END=== 10.101.254.225 -- GET
>
> command=createVolume&response=json&sessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3D&name=data-local2&zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7&diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24&_=1401348494217
> 2014-05-29 13:02:45,470 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-14:ctx-23711cb3 job-64) Add job-64 into job monitoring
> 2014-05-29 13:02:45,470 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-14:ctx-23711cb3 job-64) Executing AsyncJobVO {id:64,
> userId: 2, accountId: 2, instanceType: Volume, instanceId: 18, cmd:
> org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
> cmdInfo:
> {"id":"18","response":"json","sessionkey":"YYidBdJcBJV64kdZ8c+KOeSqY14\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":18,\"Volume\":\"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\",\"com.cloud.dc.DataCenter\":1,\"com.cloud.offering.DiskOffering\":14}","cmdEventType":"VOLUME.CREATE","ctxUserId":"2","name":"data-local2","diskOfferingId":"8cf4d614-08b8-455c-a99f-814f4b109d24","httpmethod":"GET","_":"1401348494217","uuid":"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d","ctxAccountId":"2","ctxStartEventId":"125","zoneId":"242c701a-43e8-4790-84f3-9112ca0b5db7"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-29 13:02:45,475 WARN [c.c.a.d.ParamGenericValidationWorker]
> (API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Received unknown
> parameters for command createVolume. Unknown parameters : ctxdetails
> 2014-05-29 13:02:45,501 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Complete async job-64,
> jobStatus: SUCC
[jira] [Updated] (CLOUDSTACK-6802) Attaching a data disk created on local storage to a VM is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh updated CLOUDSTACK-6802:
--
Summary: Attaching a data disk created on local storage to a VM is failing
(was: [HyperV] Attaching a data disk created on local storage to a VM is
failing)
> Attaching a data disk created on local storage to a VM is failing
> -
>
> Key: CLOUDSTACK-6802
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6802
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Storage Controller
>Affects Versions: 4.4.0
>Reporter: Abhinav Roy
>Assignee: Devdeep Singh
>Priority: Critical
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.4.0
>
>
> Steps :
> =
> 1. Deploy a CS advanced zone setup with both local storage and shared storage
> enabled.
> 2. Deploy VMs. ( both on shared and local storage)
> 3. create a disk offering with local storage
> 4. Create a data disk with local storage disk offering.
> 5. attach the datadisk created on step 4 to VM created on step 2
> Expected result :
> ===
> Volume should be attached successfully.
> Observed result :
> ==
> volume attach fails with following error.
> 2014-05-29 13:02:45,410 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-16:ctx-87ef4f22) ===START=== 10.101.254.225 -- GET
> command=createVolume&response=json&sessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3D&name=data-local2&zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7&diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24&_=1401348494217
> 2014-05-29 13:02:45,466 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-16:ctx-87ef4f22 ctx-bf1bb5b6) submit async job-64, details:
> AsyncJobVO {id:64, userId: 2, accountId: 2, instanceType: Volume, instanceId:
> 18, cmd:
> org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
> cmdInfo:
> {"id":"18","response":"json","sessionkey":"YYidBdJcBJV64kdZ8c+KOeSqY14\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":18,\"Volume\":\"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\",\"com.cloud.dc.DataCenter\":1,\"com.cloud.offering.DiskOffering\":14}","cmdEventType":"VOLUME.CREATE","ctxUserId":"2","name":"data-local2","diskOfferingId":"8cf4d614-08b8-455c-a99f-814f4b109d24","httpmethod":"GET","_":"1401348494217","uuid":"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d","ctxAccountId":"2","ctxStartEventId":"125","zoneId":"242c701a-43e8-4790-84f3-9112ca0b5db7"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-29 13:02:45,467 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-16:ctx-87ef4f22 ctx-bf1bb5b6) ===END=== 10.101.254.225 -- GET
>
> command=createVolume&response=json&sessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3D&name=data-local2&zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7&diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24&_=1401348494217
> 2014-05-29 13:02:45,470 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-14:ctx-23711cb3 job-64) Add job-64 into job monitoring
> 2014-05-29 13:02:45,470 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-14:ctx-23711cb3 job-64) Executing AsyncJobVO {id:64,
> userId: 2, accountId: 2, instanceType: Volume, instanceId: 18, cmd:
> org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
> cmdInfo:
> {"id":"18","response":"json","sessionkey":"YYidBdJcBJV64kdZ8c+KOeSqY14\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":18,\"Volume\":\"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\",\"com.cloud.dc.DataCenter\":1,\"com.cloud.offering.DiskOffering\":14}","cmdEventType":"VOLUME.CREATE","ctxUserId":"2","name":"data-local2","diskOfferingId":"8cf4d614-08b8-455c-a99f-814f4b109d24","httpmethod":"GET","_":"1401348494217","uuid":"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d","ctxAccountId":"2","ctxStartEventId":"125","zoneId":"242c701a-43e8-4790-84f3-9112ca0b5db7"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-29 13:02:45,475 WARN [c.c.a.d.ParamGenericValidationWorker]
> (API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Received unknown
> parameters for command createVolume. Unknown parameters : ctxdetails
> 2014-05-29 13:02:45,501 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Complete async job-64,
> jobStatus: SUCCEEDED, resultCode: 0, result:
> org.apache.cloudstack.api.response.VolumeResponse/volume/{"id":"dd5d8d3
[jira] [Resolved] (CLOUDSTACK-6223) removeNicFromVirtualMachine fails if another instance in another domain has a nic with the same ip and a forwarding rule configured on it
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
upendra moturi resolved CLOUDSTACK-6223.
Resolution: Fixed
Fix Version/s: 4.4.0
https://reviews.apache.org/r/19902/
> removeNicFromVirtualMachine fails if another instance in another domain has a
> nic with the same ip and a forwarding rule configured on it
> -
>
> Key: CLOUDSTACK-6223
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6223
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.2.1
>Reporter: Joris van Lieshout
>Assignee: upendra moturi
>Priority: Blocker
> Fix For: 4.4.0
>
>
> When removeNicFromVirtualMachine is called for a nic on an instance the code
> below is evaluated. This piece of code searches for portforwarding rules
> across all domains. If another instance exists that has a nic with the same
> ip and a forwarding rule the search returns >1 and the
> removeNicFromVirtualMachine call failed.
> server/src/com/cloud/network/rules/RulesManagerImpl.java
> @Override
> public List listAssociatedRulesForGuestNic(Nic nic){
> List result = new ArrayList();
> // add PF rules
>
> result.addAll(_portForwardingDao.listByDestIpAddr(nic.getIp4Address()));
> // add static NAT rules
> Stack trace:
> 2014-03-11 15:24:04,944 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-102:job-193607 = [ 30e81de3-2a00-49f2-8d80-545a765e4c1e ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.RemoveNicFromVMCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to remove nic from
> VM[User|zzz1] in Ntwk[994|Guest|14], nic has associated Port forwarding or
> Load balancer or Static NAT rules.
> at
> com.cloud.vm.VirtualMachineManagerImpl.removeNicFromVm(VirtualMachineManagerImpl.java:3058)
> at
> com.cloud.vm.UserVmManagerImpl.removeNicFromVirtualMachine(UserVmManagerImpl.java:1031)
> at
> org.apache.cloudstack.api.command.user.vm.RemoveNicFromVMCmd.execute(RemoveNicFromVMCmd.java:103)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> 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)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6223) removeNicFromVirtualMachine fails if another instance in another domain has a nic with the same ip and a forwarding rule configured on it
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012198#comment-14012198
]
ASF subversion and git services commented on CLOUDSTACK-6223:
-
Commit e9af5f44ae080da3f191cba57b55747801c3100e in cloudstack's branch
refs/heads/master from [~Upendra]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e9af5f4 ]
CLOUDSTACK-6223. removeNicFromVirtualMachine fails if another instance in
another domain has a nic with the same ip and a forwarding rule configured on it
Signed-off-by: Daan Hoogland
> removeNicFromVirtualMachine fails if another instance in another domain has a
> nic with the same ip and a forwarding rule configured on it
> -
>
> Key: CLOUDSTACK-6223
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6223
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.2.1
>Reporter: Joris van Lieshout
>Assignee: upendra moturi
>Priority: Blocker
>
> When removeNicFromVirtualMachine is called for a nic on an instance the code
> below is evaluated. This piece of code searches for portforwarding rules
> across all domains. If another instance exists that has a nic with the same
> ip and a forwarding rule the search returns >1 and the
> removeNicFromVirtualMachine call failed.
> server/src/com/cloud/network/rules/RulesManagerImpl.java
> @Override
> public List listAssociatedRulesForGuestNic(Nic nic){
> List result = new ArrayList();
> // add PF rules
>
> result.addAll(_portForwardingDao.listByDestIpAddr(nic.getIp4Address()));
> // add static NAT rules
> Stack trace:
> 2014-03-11 15:24:04,944 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-102:job-193607 = [ 30e81de3-2a00-49f2-8d80-545a765e4c1e ])
> Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.RemoveNicFromVMCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to remove nic from
> VM[User|zzz1] in Ntwk[994|Guest|14], nic has associated Port forwarding or
> Load balancer or Static NAT rules.
> at
> com.cloud.vm.VirtualMachineManagerImpl.removeNicFromVm(VirtualMachineManagerImpl.java:3058)
> at
> com.cloud.vm.UserVmManagerImpl.removeNicFromVirtualMachine(UserVmManagerImpl.java:1031)
> at
> org.apache.cloudstack.api.command.user.vm.RemoveNicFromVMCmd.execute(RemoveNicFromVMCmd.java:103)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> 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)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6801) Public IP not assigned to eth1 on VR in VPC
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012178#comment-14012178 ] Andrija Panic commented on CLOUDSTACK-6801: --- Hi Jayapal, Will try this, but this was not the problem for last few ACS versions I have used. Yes, Public vlan is untagged, I will try this as a workarround - not sure it is possible to change existing Public IP vlan from untagged to tagged ? Regards Andrija > Public IP not assigned to eth1 on VR in VPC > --- > > Key: CLOUDSTACK-6801 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6801 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Virtual Router >Affects Versions: 4.3.0 > Environment: CentOS, KVM. >Reporter: Andrija Panic >Priority: Blocker > Labels: publicip, virtualrouter, vpc > > Hi, > after upgrade from 4.2.1 to 4.3.0, Public IP on eth1 is missing on VR when > creating new (and on existing) VPCs, although eth1 seems present per > /proc/net/dev. > Mangement logs are fine, eth1 plugged in correct bridge, etc. > Manually adding IP on eth1 and starting eth1 does work. > From /var/log/messages inside VR: > May 28 18:27:36 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 0 seconds > May 28 18:27:37 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 1 seconds > May 28 18:27:38 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 2 seconds > May 28 18:27:39 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 3 seconds > May 28 18:27:40 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 4 seconds > May 28 18:27:41 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 5 seconds > May 28 18:27:42 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 6 seconds > May 28 18:27:43 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 7 seconds > May 28 18:27:44 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 8 seconds > May 28 18:27:45 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 9 seconds > May 28 18:27:46 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 10 seconds > May 28 18:27:47 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 11 seconds > May 28 18:27:48 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 12 seconds > May 28 18:27:49 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 13 seconds > May 28 18:27:50 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 14 seconds > May 28 18:27:51 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 15 seconds > May 28 18:27:52 r-799-VM cloud: vpc_ipassoc.sh:Waiting for interface ethnull > to appear, 16 seconds > May 28 18:27:53 r-799-VM cloud: vpc_ipassoc.sh:interface ethnull never > appeared > May 28 18:27:53 r-799-VM cloud: vpc_ipassoc.sh:Adding ip 46.232.x.246 on > interface ethnull > May 28 18:27:53 r-799-VM cloud: vpc_ipassoc.sh:Add routing 46.232.x.246 on > interface ethnull > May 28 18:27:53 r-799-VM cloud: vpc_privateGateway.sh:Added SourceNAT > 46.232.x.246 on interface ethnull > May 28 18:27:53 r-799-VM cloud: vpc_snat.sh:Added SourceNAT 46.232.x.246 on > interface eth1 > May 28 18:27:54 r-799-VM cloud: vpc_guestnw.sh: Create network on interface > eth2, gateway 10.0.1.1, network 10.0.1.1/24 > May 28 18:27:59 r-799-VM cloud: Setting up apache web server for eth2 > May 28 18:27:59 r-799-VM cloud: Setting up password service for network > 10.0.1.1/24, eth eth2 > May 28 18:27:59 r-799-VM cloud: vpc_guestnw.sh: Create network on interface > eth3, gateway 10.0.3.1, network 10.0.3.1/24 > May 28 18:28:04 r-799-VM cloud: Setting up apache web server for eth3 > May 28 18:28:06 r-799-VM cloud: Setting up password service for network > 10.0.3.1/24, eth eth3 > May 28 18:28:06 r-799-VM cloud: vpc_guestnw.sh: Create network on interface > eth4, gateway 10.0.4.1, network 10.0.4.1/24 > May 28 18:28:11 r-799-VM cloud: Setting up apache web server for eth4 > May 28 18:28:12 r-799-VM cloud: Setting up password service for network > 10.0.4.1/24, eth eth4 > May 28 18:28:13 r-799-VM cloud: vpc_guestnw.sh: Create network on interface > eth5, gateway 10.0.6.1, network 10.0.6.1/24 > May 28 18:28:18 r-799-VM cloud: Setting up apache web server for eth5 > May 28 18:28:19 r-799-VM cloud: Setting up password service for network > 10.0.6.1/24, eth eth5 > Nothing else usefull in other logs... -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6802) [HyperV] Attaching a data disk created on local storage to a VM is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012173#comment-14012173
]
Abhinav Roy commented on CLOUDSTACK-6802:
-
Error is seen even when we try to Deploy a VM with a data disk of local storage
type.
Deploy VM succeeds when we create a VM only with ROOT disk on local storage and
no data disk.
> [HyperV] Attaching a data disk created on local storage to a VM is failing
> --
>
> Key: CLOUDSTACK-6802
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6802
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Storage Controller
>Affects Versions: 4.4.0
>Reporter: Abhinav Roy
>Assignee: Devdeep Singh
>Priority: Critical
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.4.0
>
>
> Steps :
> =
> 1. Deploy a CS advanced zone setup with both local storage and shared storage
> enabled.
> 2. Deploy VMs. ( both on shared and local storage)
> 3. create a disk offering with local storage
> 4. Create a data disk with local storage disk offering.
> 5. attach the datadisk created on step 4 to VM created on step 2
> Expected result :
> ===
> Volume should be attached successfully.
> Observed result :
> ==
> volume attach fails with following error.
> 2014-05-29 13:02:45,410 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-16:ctx-87ef4f22) ===START=== 10.101.254.225 -- GET
> command=createVolume&response=json&sessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3D&name=data-local2&zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7&diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24&_=1401348494217
> 2014-05-29 13:02:45,466 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-16:ctx-87ef4f22 ctx-bf1bb5b6) submit async job-64, details:
> AsyncJobVO {id:64, userId: 2, accountId: 2, instanceType: Volume, instanceId:
> 18, cmd:
> org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
> cmdInfo:
> {"id":"18","response":"json","sessionkey":"YYidBdJcBJV64kdZ8c+KOeSqY14\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":18,\"Volume\":\"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\",\"com.cloud.dc.DataCenter\":1,\"com.cloud.offering.DiskOffering\":14}","cmdEventType":"VOLUME.CREATE","ctxUserId":"2","name":"data-local2","diskOfferingId":"8cf4d614-08b8-455c-a99f-814f4b109d24","httpmethod":"GET","_":"1401348494217","uuid":"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d","ctxAccountId":"2","ctxStartEventId":"125","zoneId":"242c701a-43e8-4790-84f3-9112ca0b5db7"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-29 13:02:45,467 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-16:ctx-87ef4f22 ctx-bf1bb5b6) ===END=== 10.101.254.225 -- GET
>
> command=createVolume&response=json&sessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3D&name=data-local2&zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7&diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24&_=1401348494217
> 2014-05-29 13:02:45,470 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-14:ctx-23711cb3 job-64) Add job-64 into job monitoring
> 2014-05-29 13:02:45,470 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-14:ctx-23711cb3 job-64) Executing AsyncJobVO {id:64,
> userId: 2, accountId: 2, instanceType: Volume, instanceId: 18, cmd:
> org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
> cmdInfo:
> {"id":"18","response":"json","sessionkey":"YYidBdJcBJV64kdZ8c+KOeSqY14\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":18,\"Volume\":\"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\",\"com.cloud.dc.DataCenter\":1,\"com.cloud.offering.DiskOffering\":14}","cmdEventType":"VOLUME.CREATE","ctxUserId":"2","name":"data-local2","diskOfferingId":"8cf4d614-08b8-455c-a99f-814f4b109d24","httpmethod":"GET","_":"1401348494217","uuid":"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d","ctxAccountId":"2","ctxStartEventId":"125","zoneId":"242c701a-43e8-4790-84f3-9112ca0b5db7"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-29 13:02:45,475 WARN [c.c.a.d.ParamGenericValidationWorker]
> (API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Received unknown
> parameters for command createVolume. Unknown parameters : ctxdetails
> 2014-05-29 13:02:45,501 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Complete async job-64,
> jobStatus: SUCCEEDED, resultCo
[jira] [Assigned] (CLOUDSTACK-6802) [HyperV] Attaching a data disk created on local storage to a VM is failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devdeep Singh reassigned CLOUDSTACK-6802:
-
Assignee: Devdeep Singh
> [HyperV] Attaching a data disk created on local storage to a VM is failing
> --
>
> Key: CLOUDSTACK-6802
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6802
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Storage Controller
>Affects Versions: 4.4.0
>Reporter: Abhinav Roy
>Assignee: Devdeep Singh
>Priority: Critical
> Labels: hyper-V,, hyper-v, hyperv
> Fix For: 4.4.0
>
>
> Steps :
> =
> 1. Deploy a CS advanced zone setup with both local storage and shared storage
> enabled.
> 2. Deploy VMs. ( both on shared and local storage)
> 3. create a disk offering with local storage
> 4. Create a data disk with local storage disk offering.
> 5. attach the datadisk created on step 4 to VM created on step 2
> Expected result :
> ===
> Volume should be attached successfully.
> Observed result :
> ==
> volume attach fails with following error.
> 2014-05-29 13:02:45,410 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-16:ctx-87ef4f22) ===START=== 10.101.254.225 -- GET
> command=createVolume&response=json&sessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3D&name=data-local2&zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7&diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24&_=1401348494217
> 2014-05-29 13:02:45,466 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (catalina-exec-16:ctx-87ef4f22 ctx-bf1bb5b6) submit async job-64, details:
> AsyncJobVO {id:64, userId: 2, accountId: 2, instanceType: Volume, instanceId:
> 18, cmd:
> org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
> cmdInfo:
> {"id":"18","response":"json","sessionkey":"YYidBdJcBJV64kdZ8c+KOeSqY14\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":18,\"Volume\":\"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\",\"com.cloud.dc.DataCenter\":1,\"com.cloud.offering.DiskOffering\":14}","cmdEventType":"VOLUME.CREATE","ctxUserId":"2","name":"data-local2","diskOfferingId":"8cf4d614-08b8-455c-a99f-814f4b109d24","httpmethod":"GET","_":"1401348494217","uuid":"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d","ctxAccountId":"2","ctxStartEventId":"125","zoneId":"242c701a-43e8-4790-84f3-9112ca0b5db7"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-29 13:02:45,467 DEBUG [c.c.a.ApiServlet]
> (catalina-exec-16:ctx-87ef4f22 ctx-bf1bb5b6) ===END=== 10.101.254.225 -- GET
>
> command=createVolume&response=json&sessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3D&name=data-local2&zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7&diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24&_=1401348494217
> 2014-05-29 13:02:45,470 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (API-Job-Executor-14:ctx-23711cb3 job-64) Add job-64 into job monitoring
> 2014-05-29 13:02:45,470 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-14:ctx-23711cb3 job-64) Executing AsyncJobVO {id:64,
> userId: 2, accountId: 2, instanceType: Volume, instanceId: 18, cmd:
> org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
> cmdInfo:
> {"id":"18","response":"json","sessionkey":"YYidBdJcBJV64kdZ8c+KOeSqY14\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":18,\"Volume\":\"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\",\"com.cloud.dc.DataCenter\":1,\"com.cloud.offering.DiskOffering\":14}","cmdEventType":"VOLUME.CREATE","ctxUserId":"2","name":"data-local2","diskOfferingId":"8cf4d614-08b8-455c-a99f-814f4b109d24","httpmethod":"GET","_":"1401348494217","uuid":"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d","ctxAccountId":"2","ctxStartEventId":"125","zoneId":"242c701a-43e8-4790-84f3-9112ca0b5db7"},
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
> null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
> lastPolled: null, created: null}
> 2014-05-29 13:02:45,475 WARN [c.c.a.d.ParamGenericValidationWorker]
> (API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Received unknown
> parameters for command createVolume. Unknown parameters : ctxdetails
> 2014-05-29 13:02:45,501 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Complete async job-64,
> jobStatus: SUCCEEDED, resultCode: 0, result:
> org.apache.cloudstack.api.response.VolumeResponse/volume/{"id":"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d","name":"data-local2","zoneid":"242c701a-43e8-4790-84f3-9112ca0b5db7","zonename":"
[jira] [Created] (CLOUDSTACK-6802) [HyperV] Attaching a data disk created on local storage to a VM is failing
Abhinav Roy created CLOUDSTACK-6802:
---
Summary: [HyperV] Attaching a data disk created on local storage
to a VM is failing
Key: CLOUDSTACK-6802
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6802
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server, Storage Controller
Affects Versions: 4.4.0
Reporter: Abhinav Roy
Priority: Critical
Fix For: 4.4.0
Steps :
=
1. Deploy a CS advanced zone setup with both local storage and shared storage
enabled.
2. Deploy VMs. ( both on shared and local storage)
3. create a disk offering with local storage
4. Create a data disk with local storage disk offering.
5. attach the datadisk created on step 4 to VM created on step 2
Expected result :
===
Volume should be attached successfully.
Observed result :
==
volume attach fails with following error.
2014-05-29 13:02:45,410 DEBUG [c.c.a.ApiServlet]
(catalina-exec-16:ctx-87ef4f22) ===START=== 10.101.254.225 -- GET
command=createVolume&response=json&sessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3D&name=data-local2&zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7&diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24&_=1401348494217
2014-05-29 13:02:45,466 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-16:ctx-87ef4f22 ctx-bf1bb5b6) submit async job-64, details:
AsyncJobVO {id:64, userId: 2, accountId: 2, instanceType: Volume, instanceId:
18, cmd: org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin,
cmdInfo:
{"id":"18","response":"json","sessionkey":"YYidBdJcBJV64kdZ8c+KOeSqY14\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":18,\"Volume\":\"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\",\"com.cloud.dc.DataCenter\":1,\"com.cloud.offering.DiskOffering\":14}","cmdEventType":"VOLUME.CREATE","ctxUserId":"2","name":"data-local2","diskOfferingId":"8cf4d614-08b8-455c-a99f-814f4b109d24","httpmethod":"GET","_":"1401348494217","uuid":"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d","ctxAccountId":"2","ctxStartEventId":"125","zoneId":"242c701a-43e8-4790-84f3-9112ca0b5db7"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-29 13:02:45,467 DEBUG [c.c.a.ApiServlet] (catalina-exec-16:ctx-87ef4f22
ctx-bf1bb5b6) ===END=== 10.101.254.225 -- GET
command=createVolume&response=json&sessionkey=YYidBdJcBJV64kdZ8c%2BKOeSqY14%3D&name=data-local2&zoneId=242c701a-43e8-4790-84f3-9112ca0b5db7&diskOfferingId=8cf4d614-08b8-455c-a99f-814f4b109d24&_=1401348494217
2014-05-29 13:02:45,470 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-14:ctx-23711cb3 job-64) Add job-64 into job monitoring
2014-05-29 13:02:45,470 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-14:ctx-23711cb3 job-64) Executing AsyncJobVO {id:64, userId:
2, accountId: 2, instanceType: Volume, instanceId: 18, cmd:
org.apache.cloudstack.api.command.admin.volume.CreateVolumeCmdByAdmin, cmdInfo:
{"id":"18","response":"json","sessionkey":"YYidBdJcBJV64kdZ8c+KOeSqY14\u003d","ctxDetails":"{\"com.cloud.storage.Volume\":18,\"Volume\":\"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d\",\"com.cloud.dc.DataCenter\":1,\"com.cloud.offering.DiskOffering\":14}","cmdEventType":"VOLUME.CREATE","ctxUserId":"2","name":"data-local2","diskOfferingId":"8cf4d614-08b8-455c-a99f-814f4b109d24","httpmethod":"GET","_":"1401348494217","uuid":"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d","ctxAccountId":"2","ctxStartEventId":"125","zoneId":"242c701a-43e8-4790-84f3-9112ca0b5db7"},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, initMsid: 213737702773493, completeMsid: null, lastUpdated: null,
lastPolled: null, created: null}
2014-05-29 13:02:45,475 WARN [c.c.a.d.ParamGenericValidationWorker]
(API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Received unknown
parameters for command createVolume. Unknown parameters : ctxdetails
2014-05-29 13:02:45,501 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-14:ctx-23711cb3 job-64 ctx-5e5a2bf1) Complete async job-64,
jobStatus: SUCCEEDED, resultCode: 0, result:
org.apache.cloudstack.api.response.VolumeResponse/volume/{"id":"dd5d8d32-03b4-4afd-80ca-58586c7c9e8d","name":"data-local2","zoneid":"242c701a-43e8-4790-84f3-9112ca0b5db7","zonename":"hyperv","type":"DATADISK","size":3221225472,"created":"2014-05-29T13:02:45+0530","state":"Allocated","account":"admin","domainid":"c190bda2-e497-11e3-8557-c264afd952f5","domain":"ROOT","storagetype":"local","hypervisor":"None","diskofferingid":"8cf4d614-08b8-455c-a99f-814f4b109d24","diskofferingname":"local","diskofferingdisplaytext":"local","destroyed":false,"isextractable":true,"tags":[],"displayvolume":true,"quiescev
