date:20151220

[jira] [Created] (CLOUDSTACK-9191) ACS 4.6 Custom Offer Signature mismatch "ERROR : "unable to verify user credentials and/or request signature""

2015-12-20 Thread AssistanZ Networks Pvt (JIRA)

AssistanZ Networks Pvt created CLOUDSTACK-9191:
--

 Summary: ACS 4.6 Custom Offer Signature mismatch "ERROR : "unable 
to verify user credentials and/or request signature""
 Key: CLOUDSTACK-9191
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9191
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: API
Affects Versions: 4.6.0
 Environment: ACS 4.6 with KVM hypervisors
Reporter: AssistanZ Networks Pvt
Priority: Minor


ERROR : "unable to verify user credentials and/or request signature"

Request to CloudStack without custom offering through application :

apiKey=lGMCRQI6maiFCDsKuZAHI63u1upxCrUnNrWbXAnUZZE_qyEv7ozK_yNzYvNfXgX5x5mRcedIKynzSyLA5hf8yg=deployVirtualMachine=admin=true=3776269a-949d-11e5-b907-e06995a35804=us=priya=7efa5852-7e1f-4a26-9351-00f9d863aa3e=527ebed8-23f6-4c9f-9ee0-05926b035b1e=json=cb9fe060-1870-4bd0-8c0e-3980107acce6=96e753af-5e1a-4bf9-a28a-9f609ee06202=af3ed220-7e36-4459-a6ea-9587a18246c0=FU4xL%2FdGsYoihfWdvT%2FPrwwzthQ%3D
This is working fine.

Request to CloudStack with custom offering through application :

apiKey=lGMCRQI6maiFCDsKuZAHI63u1upxCrUnNrWbXAnUZZE_qyEv7ozK_yNzYvNfXgX5x5mRcedIKynzSyLA5hf8yg=deployVirtualMachine%5B0%5D.cpuNumber=3%5B0%5D.cpuSpeed=1500%5B0%5D.memory=512=KVM%5B0%5D.networkid=7efa5852-7e1f-4a26-9351-00f9d863aa3e=json=a1613485-8cdf-4d84-8b97-8c2695128a2f=37acb430-949d-11e5-b907-e06995a35804=af3ed220-7e36-4459-a6ea-9587a18246c0=FU4xL%2FdGsYoihfWdvT%2FPrwwzthQ%3D

ERROR : "unable to verify user credentials and/or request signature"

Values are mapped same as CloudStack command string formation.
It is generating same signature for both. Noticed difference in CloudStack is 
cpuSpeed and cpuNumber. In both Speed and Number, first letter in upper case. 
During signature generation we will convert all the values to lower case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing

2015-12-20 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066129#comment-15066129
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9192:


GitHub user nitin-maharana opened a pull request:

https://github.com/apache/cloudstack/pull/1264

CLOUDSTACK-9192: UpdateVpnCustomerGateway is failing

Reproducible Steps:

1.Create a customer gateway for a VPC.
2.Edit it using UI(API call is UpdateVpnCustomerGateway).
3.When we try to update the customer vpn gateway with connection state is 
not in "Error", we see the API error but that won't be reflected to the user in 
UI.

Actual Behaviour:
==
The API throws error. But UI doesn't show it to user.

Expected Behaviour:
=
The UI should show the error to user.

Fix:
===
TypeError: json.updatecustomergatewayresponse is undefined
The response name was wrong so corrected it.
It should be json.updatevpncustomergatewayresponse.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nitin-maharana/CloudStack CloudStack-Nitin10

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1264.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1264


commit 3022dd3094d45d6574c4d68d3a0b4e6ffde6ad11
Author: Nitin Kumar Maharana 
Date:   2015-12-21T07:37:33Z

CLOUDSTACK-9192: UpdateVpnCustomerGateway is failing

The response name was wrong so corrected it.




> UpdateVpnCustomerGateway is failing
> ---
>
> Key: CLOUDSTACK-9192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9192
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitin Kumar Maharana
>
> Reproducible Steps:
> 
> 1.Create a customer gateway for a VPC.
> 2.Edit it using UI(API call is UpdateVpnCustomerGateway).
> 3.When we try to update the customer vpn gateway with connection state is not 
> in "Error", we see the API error but that won't be reflected to the user in 
> UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9186) Root admin cannot see VPC created by Domain admin user

2015-12-20 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065712#comment-15065712
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9186:


Github user nitin-maharana commented on the pull request:

https://github.com/apache/cloudstack/pull/1258#issuecomment-166109722
  
cc @remibergsma @kishankavala 


> Root admin cannot see VPC created by Domain admin user
> --
>
> Key: CLOUDSTACK-9186
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9186
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitin Kumar Maharana
>
> Issue:
> =
> Root admin cannot see LB rules and Public LB IP addresses created by 
> domain-admin in UI therefore root admin cannot manage those.
> Reproducible Steps: 
>  
> 1.Log in as a Domain-Admin account and create a VPC with vpc virtual 
> router as public load balancer provider 
> 2.click on the newly created VPC -> click on the VPC tier -> click 
> internal LB 
> 3.Add internal LB, 
> 4.Logoff domain-admin and login as root admin 
> 5.Navigate the VPC created previously and click internal LB, internal lb 
> is not showing up.
> Same steps for Public LB IP addresses except select the correct Network 
> offering while creating a tier.
> Expected Behaviour: 
> = 
> Root admin should be able to manage VPC created by Domain admin user .
> Actual Behaviour:
> == 
> Root admin cannot see VPC created by Domain admin user and hence not able to 
> manage it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8302) Cleanup snapshot on KVM with RBD

2015-12-20 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065689#comment-15065689
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8302:


Github user wido commented on the pull request:

https://github.com/apache/cloudstack/pull/1230#issuecomment-166100502
  
Last code review is LGTM to me, but didn't have the time to test it yet. I 
*think* it works, but need to verify first.


> Cleanup snapshot on KVM with RBD
> 
>
> Key: CLOUDSTACK-8302
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8302
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot, Storage Controller
>Affects Versions: 4.4.0, 4.4.1, 4.4.2
> Environment: CloudStack 4.4.2 + KVM on CentOS 6.6 + Ceph/RBD 0.80.8
>Reporter: Star Guo
>Assignee: Wido den Hollander
>Priority: Critical
>
> I just build a lab with CloudStack 4.4.2 + CentOS 6.6 KVM + Ceph/RBD 0.80.8.
> I deploy an instance on RBD and I create the ROOT volume snapshots. When 
> delete a snapshot the UI show OK, but the snapshot of the volume in the RBD 
> pool is still exist.
> And I find the code in 
> com/cloud/hypervisor/kvm/storage/KVMStorageProcessor.java: 
> …
> @Override
> public Answer deleteSnapshot(DeleteCommand cmd) {
> return new Answer(cmd);
> }
> …
> deleteSnapshot() does not be implememented. And I also find the code:
> ...
> @Override
> public Answer createTemplateFromSnapshot(CopyCommand cmd) {
> return null;  //To change body of implemented methods use File | 
> Settings | File Templates.
> }
> ...
> So does createTenokateFromSnapshot(). I just look for it in MASTER branch but 
> not do that yet. Will CloudStack Dev Team plan to do that ? Thanks .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9186) Root admin cannot see VPC created by Domain admin user

2015-12-20 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065724#comment-15065724
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9186:


Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1258#issuecomment-166112617
  
@nitin-maharana Thanks. Are there any other api calls that have the same 
issue?


> Root admin cannot see VPC created by Domain admin user
> --
>
> Key: CLOUDSTACK-9186
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9186
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitin Kumar Maharana
>
> Issue:
> =
> Root admin cannot see LB rules and Public LB IP addresses created by 
> domain-admin in UI therefore root admin cannot manage those.
> Reproducible Steps: 
>  
> 1.Log in as a Domain-Admin account and create a VPC with vpc virtual 
> router as public load balancer provider 
> 2.click on the newly created VPC -> click on the VPC tier -> click 
> internal LB 
> 3.Add internal LB, 
> 4.Logoff domain-admin and login as root admin 
> 5.Navigate the VPC created previously and click internal LB, internal lb 
> is not showing up.
> Same steps for Public LB IP addresses except select the correct Network 
> offering while creating a tier.
> Expected Behaviour: 
> = 
> Root admin should be able to manage VPC created by Domain admin user .
> Actual Behaviour:
> == 
> Root admin cannot see VPC created by Domain admin user and hence not able to 
> manage it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9186) Root admin cannot see VPC created by Domain admin user

2015-12-20 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065731#comment-15065731
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9186:


Github user rafaelweingartner commented on the pull request:

https://github.com/apache/cloudstack/pull/1258#issuecomment-166114305
  
@nitin-maharana shouldn't we use the "recursive" parameter set to "true" 
too?


> Root admin cannot see VPC created by Domain admin user
> --
>
> Key: CLOUDSTACK-9186
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9186
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitin Kumar Maharana
>
> Issue:
> =
> Root admin cannot see LB rules and Public LB IP addresses created by 
> domain-admin in UI therefore root admin cannot manage those.
> Reproducible Steps: 
>  
> 1.Log in as a Domain-Admin account and create a VPC with vpc virtual 
> router as public load balancer provider 
> 2.click on the newly created VPC -> click on the VPC tier -> click 
> internal LB 
> 3.Add internal LB, 
> 4.Logoff domain-admin and login as root admin 
> 5.Navigate the VPC created previously and click internal LB, internal lb 
> is not showing up.
> Same steps for Public LB IP addresses except select the correct Network 
> offering while creating a tier.
> Expected Behaviour: 
> = 
> Root admin should be able to manage VPC created by Domain admin user .
> Actual Behaviour:
> == 
> Root admin cannot see VPC created by Domain admin user and hence not able to 
> manage it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8302) Cleanup snapshot on KVM with RBD

2015-12-20 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065687#comment-15065687
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8302:


Github user wido commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1230#discussion_r48101631
  
--- Diff: 
plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/storage/KVMStorageProcessor.java
 ---
@@ -1274,7 +1274,46 @@ public Answer createVolumeFromSnapshot(final 
CopyCommand cmd) {
 
 @Override
 public Answer deleteSnapshot(final DeleteCommand cmd) {
-return new Answer(cmd);
+try {
+SnapshotObjectTO snapshotTO = (SnapshotObjectTO) cmd.getData();
+PrimaryDataStoreTO primaryStore = (PrimaryDataStoreTO) 
snapshotTO.getDataStore();
+VolumeObjectTO volume = snapshotTO.getVolume();
+String snapshotFullPath = snapshotTO.getPath();
+String snapshotName = 
snapshotFullPath.substring(snapshotFullPath.lastIndexOf("/") + 1);
+KVMStoragePool primaryPool = 
storagePoolMgr.getStoragePool(primaryStore.getPoolType(), 
primaryStore.getUuid());
+KVMPhysicalDisk disk = 
storagePoolMgr.getPhysicalDisk(primaryStore.getPoolType(), 
primaryStore.getUuid(), volume.getPath());
+if (primaryPool.getType() == StoragePoolType.RBD) {
+Rados r = new Rados(primaryPool.getAuthUserName());
+r.confSet("mon_host", primaryPool.getSourceHost() + ":" + 
primaryPool.getSourcePort());
+r.confSet("key", primaryPool.getAuthSecret());
+r.confSet("client_mount_timeout", "30");
+r.connect();
+s_logger.debug("Succesfully connected to Ceph cluster at " 
+ r.confGet("mon_host"));
+IoCTX io = r.ioCtxCreate(primaryPool.getSourceDir());
+Rbd rbd = new Rbd(io);
+RbdImage image = rbd.open(disk.getName());
+try {
+s_logger.info("Attempting to remove RBD snapshot " + 
disk.getName() + "@" + snapshotName);
+if (image.snapIsProtected(snapshotName)) {
+s_logger.debug("Unprotecting RBD snapshot " + 
snapshotFullPath);
+image.snapUnprotect(snapshotName);
+}
+image.snapRemove(snapshotName);
+s_logger.info("Snapshot " + snapshotFullPath + " 
successfully removed from " +
+primaryPool.getType().toString() + "  pool.");
+} finally {
+rbd.close(image);
+r.ioCtxDestroy(io);
+}
+} else {
+s_logger.warn("Operation not implemented for storage pool 
type of " + primaryPool.getType().toString());
+throw new InternalErrorException("Operation not 
implemented for storage pool type of " + primaryPool.getType().toString());
+}
+return new Answer(cmd, true, "Snapshot removed successfully.");
+} catch (Exception e) {
+s_logger.error(e.getMessage());
+return new Answer(cmd, false, "Failed to remove snapshot!");
--- End diff --

Same here. Tell which snapshot couldn't be removed


> Cleanup snapshot on KVM with RBD
> 
>
> Key: CLOUDSTACK-8302
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8302
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot, Storage Controller
>Affects Versions: 4.4.0, 4.4.1, 4.4.2
> Environment: CloudStack 4.4.2 + KVM on CentOS 6.6 + Ceph/RBD 0.80.8
>Reporter: Star Guo
>Assignee: Wido den Hollander
>Priority: Critical
>
> I just build a lab with CloudStack 4.4.2 + CentOS 6.6 KVM + Ceph/RBD 0.80.8.
> I deploy an instance on RBD and I create the ROOT volume snapshots. When 
> delete a snapshot the UI show OK, but the snapshot of the volume in the RBD 
> pool is still exist.
> And I find the code in 
> com/cloud/hypervisor/kvm/storage/KVMStorageProcessor.java: 
> …
> @Override
> public Answer deleteSnapshot(DeleteCommand cmd) {
> return new Answer(cmd);
> }
> …
> deleteSnapshot() does not be implememented. And I also find the code:
> ...
> @Override
> public Answer createTemplateFromSnapshot(CopyCommand cmd) {
> return null;  //To change body of implemented methods use File | 
> Settings | File Templates.
> }
> ...
> So does createTenokateFromSnapshot(). I just look for it in MASTER

[jira] [Commented] (CLOUDSTACK-8302) Cleanup snapshot on KVM with RBD

2015-12-20 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065686#comment-15065686
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8302:


Github user wido commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1230#discussion_r48101628
  
--- Diff: 
plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/storage/KVMStorageProcessor.java
 ---
@@ -1274,7 +1274,46 @@ public Answer createVolumeFromSnapshot(final 
CopyCommand cmd) {
 
 @Override
 public Answer deleteSnapshot(final DeleteCommand cmd) {
-return new Answer(cmd);
+try {
+SnapshotObjectTO snapshotTO = (SnapshotObjectTO) cmd.getData();
+PrimaryDataStoreTO primaryStore = (PrimaryDataStoreTO) 
snapshotTO.getDataStore();
+VolumeObjectTO volume = snapshotTO.getVolume();
+String snapshotFullPath = snapshotTO.getPath();
+String snapshotName = 
snapshotFullPath.substring(snapshotFullPath.lastIndexOf("/") + 1);
+KVMStoragePool primaryPool = 
storagePoolMgr.getStoragePool(primaryStore.getPoolType(), 
primaryStore.getUuid());
+KVMPhysicalDisk disk = 
storagePoolMgr.getPhysicalDisk(primaryStore.getPoolType(), 
primaryStore.getUuid(), volume.getPath());
+if (primaryPool.getType() == StoragePoolType.RBD) {
+Rados r = new Rados(primaryPool.getAuthUserName());
+r.confSet("mon_host", primaryPool.getSourceHost() + ":" + 
primaryPool.getSourcePort());
+r.confSet("key", primaryPool.getAuthSecret());
+r.confSet("client_mount_timeout", "30");
+r.connect();
+s_logger.debug("Succesfully connected to Ceph cluster at " 
+ r.confGet("mon_host"));
+IoCTX io = r.ioCtxCreate(primaryPool.getSourceDir());
+Rbd rbd = new Rbd(io);
+RbdImage image = rbd.open(disk.getName());
+try {
+s_logger.info("Attempting to remove RBD snapshot " + 
disk.getName() + "@" + snapshotName);
+if (image.snapIsProtected(snapshotName)) {
+s_logger.debug("Unprotecting RBD snapshot " + 
snapshotFullPath);
+image.snapUnprotect(snapshotName);
+}
+image.snapRemove(snapshotName);
+s_logger.info("Snapshot " + snapshotFullPath + " 
successfully removed from " +
+primaryPool.getType().toString() + "  pool.");
+} finally {
+rbd.close(image);
+r.ioCtxDestroy(io);
+}
+} else {
+s_logger.warn("Operation not implemented for storage pool 
type of " + primaryPool.getType().toString());
+throw new InternalErrorException("Operation not 
implemented for storage pool type of " + primaryPool.getType().toString());
+}
+return new Answer(cmd, true, "Snapshot removed successfully.");
--- End diff --

I would add the path of the snapshot here: pool/image@snap. Logs should be 
easy to consume


> Cleanup snapshot on KVM with RBD
> 
>
> Key: CLOUDSTACK-8302
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8302
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot, Storage Controller
>Affects Versions: 4.4.0, 4.4.1, 4.4.2
> Environment: CloudStack 4.4.2 + KVM on CentOS 6.6 + Ceph/RBD 0.80.8
>Reporter: Star Guo
>Assignee: Wido den Hollander
>Priority: Critical
>
> I just build a lab with CloudStack 4.4.2 + CentOS 6.6 KVM + Ceph/RBD 0.80.8.
> I deploy an instance on RBD and I create the ROOT volume snapshots. When 
> delete a snapshot the UI show OK, but the snapshot of the volume in the RBD 
> pool is still exist.
> And I find the code in 
> com/cloud/hypervisor/kvm/storage/KVMStorageProcessor.java: 
> …
> @Override
> public Answer deleteSnapshot(DeleteCommand cmd) {
> return new Answer(cmd);
> }
> …
> deleteSnapshot() does not be implememented. And I also find the code:
> ...
> @Override
> public Answer createTemplateFromSnapshot(CopyCommand cmd) {
> return null;  //To change body of implemented methods use File | 
> Settings | File Templates.
> }
> ...
> So does createTenokateFromSnapshot(). I just look for it in MASTER branch but 
> not do that yet. Will CloudStack Dev Team plan to do that ? Thanks .



--
This message was sent by Atlassian

[jira] [Created] (CLOUDSTACK-9190) ACs is falling to identify the version of pure Xen hypervisor + XAPI hosts.

2015-12-20 Thread Rafael Weingartner (JIRA)

Rafael Weingartner created CLOUDSTACK-9190:
--

 Summary: ACs is falling to identify the version of pure Xen 
hypervisor + XAPI hosts.
 Key: CLOUDSTACK-9190
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9190
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: XCP, Xen, XenServer
Affects Versions: 4.7.0
 Environment: Xen hypervisor + XAPI + (any OS as the base for the 
system)
Reporter: Rafael Weingartner
Priority: Critical
 Fix For: Future


The problem is the following:
In environments in which we use pure Xen hypervisor + XAPI, ACS is not loading 
the Hypervisor version properly. That happens because when you use pure Xen 
Hypervisor + XAPI, it does not have that “product_version_text_short” entry. In 
those Environments, the version that we have to retrieve comes from 
“platform_version” entry.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-8302) Cleanup snapshot on KVM with RBD

2015-12-20 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15065665#comment-15065665
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8302:


Github user remibergsma commented on the pull request:

https://github.com/apache/cloudstack/pull/1230#issuecomment-166087210
  
@andrijapanic Merge without testing and LGTMs? Really?


> Cleanup snapshot on KVM with RBD
> 
>
> Key: CLOUDSTACK-8302
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8302
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot, Storage Controller
>Affects Versions: 4.4.0, 4.4.1, 4.4.2
> Environment: CloudStack 4.4.2 + KVM on CentOS 6.6 + Ceph/RBD 0.80.8
>Reporter: Star Guo
>Assignee: Wido den Hollander
>Priority: Critical
>
> I just build a lab with CloudStack 4.4.2 + CentOS 6.6 KVM + Ceph/RBD 0.80.8.
> I deploy an instance on RBD and I create the ROOT volume snapshots. When 
> delete a snapshot the UI show OK, but the snapshot of the volume in the RBD 
> pool is still exist.
> And I find the code in 
> com/cloud/hypervisor/kvm/storage/KVMStorageProcessor.java: 
> …
> @Override
> public Answer deleteSnapshot(DeleteCommand cmd) {
> return new Answer(cmd);
> }
> …
> deleteSnapshot() does not be implememented. And I also find the code:
> ...
> @Override
> public Answer createTemplateFromSnapshot(CopyCommand cmd) {
> return null;  //To change body of implemented methods use File | 
> Settings | File Templates.
> }
> ...
> So does createTenokateFromSnapshot(). I just look for it in MASTER branch but 
> not do that yet. Will CloudStack Dev Team plan to do that ? Thanks .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing

2015-12-20 Thread Nitin Kumar Maharana (JIRA)

Nitin Kumar Maharana created CLOUDSTACK-9192:


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


Reproducible Steps:

1.Create a customer gateway for a VPC.
2.Edit it using UI(API call is UpdateVpnCustomerGateway).
3.When we try to update the customer vpn gateway with connection state is not 
in "Error", we see the API error but that won't be reflected to the user in UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing

2015-12-20 Thread Wei Zhou (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066124#comment-15066124
 ] 

Wei Zhou commented on CLOUDSTACK-9192:
--

I met this issue last week and fixed it. 
 the fix is simple. Do you need me to create a PR for it?

> UpdateVpnCustomerGateway is failing
> ---
>
> Key: CLOUDSTACK-9192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9192
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitin Kumar Maharana
>
> Reproducible Steps:
> 
> 1.Create a customer gateway for a VPC.
> 2.Edit it using UI(API call is UpdateVpnCustomerGateway).
> 3.When we try to update the customer vpn gateway with connection state is not 
> in "Error", we see the API error but that won't be reflected to the user in 
> UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing

2015-12-20 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066135#comment-15066135
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9192:


Github user ustcweizhou commented on the pull request:

https://github.com/apache/cloudstack/pull/1264#issuecomment-166223301
  
@nitin-maharana 
I am not sure if it is necessary to add the following change after success, 
but I added it in my fix, basides your change.

```
error: function(json) {

args.response.error(parseXMLHttpResponse(json));
 }
```


> UpdateVpnCustomerGateway is failing
> ---
>
> Key: CLOUDSTACK-9192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9192
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitin Kumar Maharana
>
> Reproducible Steps:
> 
> 1.Create a customer gateway for a VPC.
> 2.Edit it using UI(API call is UpdateVpnCustomerGateway).
> 3.When we try to update the customer vpn gateway with connection state is not 
> in "Error", we see the API error but that won't be reflected to the user in 
> UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing

2015-12-20 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15066133#comment-15066133
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9192:


Github user nitin-maharana commented on the pull request:

https://github.com/apache/cloudstack/pull/1264#issuecomment-166223258
  
cc @JayapalUradi 


> UpdateVpnCustomerGateway is failing
> ---
>
> Key: CLOUDSTACK-9192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9192
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitin Kumar Maharana
>
> Reproducible Steps:
> 
> 1.Create a customer gateway for a VPC.
> 2.Edit it using UI(API call is UpdateVpnCustomerGateway).
> 3.When we try to update the customer vpn gateway with connection state is not 
> in "Error", we see the API error but that won't be reflected to the user in 
> UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (CLOUDSTACK-9191) ACS 4.6 Custom Offer Signature mismatch "ERROR : "unable to verify user credentials and/or request signature""

[jira] [Commented] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing

[jira] [Commented] (CLOUDSTACK-9186) Root admin cannot see VPC created by Domain admin user

[jira] [Commented] (CLOUDSTACK-8302) Cleanup snapshot on KVM with RBD

[jira] [Commented] (CLOUDSTACK-9186) Root admin cannot see VPC created by Domain admin user

[jira] [Commented] (CLOUDSTACK-9186) Root admin cannot see VPC created by Domain admin user

[jira] [Commented] (CLOUDSTACK-8302) Cleanup snapshot on KVM with RBD

[jira] [Commented] (CLOUDSTACK-8302) Cleanup snapshot on KVM with RBD

[jira] [Created] (CLOUDSTACK-9190) ACs is falling to identify the version of pure Xen hypervisor + XAPI hosts.

[jira] [Commented] (CLOUDSTACK-8302) Cleanup snapshot on KVM with RBD

[jira] [Created] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing

[jira] [Commented] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing

[jira] [Commented] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing

[jira] [Commented] (CLOUDSTACK-9192) UpdateVpnCustomerGateway is failing

14 matches

Site Navigation

Mail list logo

Footer information