[jira] [Updated] (CLOUDSTACK-7700) Volume Snapshot Async Job returns Success for a failed operation

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-7700: - Description: Setup : Single zone , two clusters , one host in each cluster , have clu

[jira] [Created] (CLOUDSTACK-7989) [Automation]:test_ldap script execution is failing with cloudstackapi exception "

sadhu suresh created CLOUDSTACK-7989: Summary: [Automation]:test_ldap script execution is failing with cloudstackapi exception " Key: CLOUDSTACK-7989 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7989

[jira] [Closed] (CLOUDSTACK-7989) [Automation]:test_ldap script execution is failing with cloudstackapi exception "

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-7989. Tested with latest master and now tests are passing > [Automation]:test_ldap script execut

[jira] [Commented] (CLOUDSTACK-7989) [Automation]:test_ldap script execution is failing with cloudstackapi exception "

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248173#comment-14248173 ] sadhu suresh commented on CLOUDSTACK-7989: -- This test configures LDAP and at

[jira] [Commented] (CLOUDSTACK-8151) Global config and periodic thread to cleanup cloud_usage table

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275481#comment-14275481 ] sadhu suresh commented on CLOUDSTACK-8151: -- Rohit, thanks for taking the in

[jira] [Created] (CLOUDSTACK-8218) LDAP:automation:adding missing scenrios and additional checks for better debugging

sadhu suresh created CLOUDSTACK-8218: Summary: LDAP:automation:adding missing scenrios and additional checks for better debugging Key: CLOUDSTACK-8218 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8218

[jira] [Updated] (CLOUDSTACK-8218) LDAP:automation:adding missing scenrios and additional checks for better debugging

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-8218: - Fix Version/s: (was: 4.5.0) > LDAP:automation:adding missing scenrios and additio

[jira] [Closed] (CLOUDSTACK-7979) [Automation] Fix the script "test_security_groups.py" - Zone Network Type Information should to be passed to VirtualMachine create method

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-7979. Resolution: Fixed its already addressed in CLOUDSTACK-7980 [ so closing this issue. >

[jira] [Closed] (CLOUDSTACK-8218) LDAP:automation:adding missing scenrios and additional checks for better debugging

[ https://issues.apache.org/jira/browse/CLOUDSTACK-8218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-8218. Resolution: Fixed addressed in https://github.com/apache/cloudstack/pull/135 so closing

[jira] [Closed] (CLOUDSTACK-6464) [KVM:basic zone- upgrade to 4.3],after any vm restart,all the nics are plugged to default bridge even though trafiic labels are being used

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-6464. closing the issue as original issue addressed. > [KVM:basic zone- upgrade to 4.3],after

[jira] [Closed] (CLOUDSTACK-5646) ConsoleProxyLoadReportCommand failed after upgrade from 3.0.7patchD to 4.3

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-5646. Not seen this issue in recent builds so closing the issue. > ConsoleProxyLoadReportCommand

[jira] [Closed] (CLOUDSTACK-7169) VR_Rolling_Upgarde: command execution order changed when we restart the network

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-7169. closing this as its working as per design. "Not a problem because without aggregation comma

[jira] [Closed] (CLOUDSTACK-7068) addIpToNic not BaseAsyncCreate but creates an entity

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-7068. working as per fix not addipTonic (add secondary IP to VM)is now async call and observed

[jira] [Created] (CLOUDSTACK-6719) OVS:VPC:UI wizard allowing to add non OVS enabled network to distributed VPC

sadhu suresh created CLOUDSTACK-6719: Summary: OVS:VPC:UI wizard allowing to add non OVS enabled network to distributed VPC Key: CLOUDSTACK-6719 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6719

[jira] [Updated] (CLOUDSTACK-6719) OVS:VPC:UI wizard allowing to add non OVS enabled network to distributed VPC

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-6719: - Component/s: Management Server Description: problem:OVS:VPC:UI: Add new tier wiz

[jira] [Closed] (CLOUDSTACK-6603) [Upgrade]DB Exception while Autoscale monitoring after upgrading from 4.3 to 4.4

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-6603. upgrade form 4.3 to 4.4 successful.not seen any issue as mentioned in the issue so closin

[jira] [Closed] (CLOUDSTACK-6604) [Upgrade]"Failed to find any private zone for Resource domain admin" message when admin logs in after upgrading from 4.3 to 4.4

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-6604. Not seen this problem .upgrade successful from 4.3 to 4.4.so closing this issue. mysql> s

[jira] [Commented] (CLOUDSTACK-7043) Management server fails to load due to DB Decryption failure

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052267#comment-14052267 ] sadhu suresh commented on CLOUDSTACK-7043: -- In my case CPVM is in alert stat

[jira] [Commented] (CLOUDSTACK-7079) 'update:Exception:Invalid cluster session detected' error thrown after MS restart

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057396#comment-14057396 ] sadhu suresh commented on CLOUDSTACK-7079: -- Still i am hitting this issse i

[jira] [Commented] (CLOUDSTACK-7079) 'update:Exception:Invalid cluster session detected' error thrown after MS restart

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057397#comment-14057397 ] sadhu suresh commented on CLOUDSTACK-7079: -- current.ThreadPoolExecutor$Worke

[jira] [Commented] (CLOUDSTACK-7070) Continuous Error messages" Invalid cluster session detected" in MS logs after starting the management server

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057410#comment-14057410 ] sadhu suresh commented on CLOUDSTACK-7070: -- Bug still noticed in below comm

[jira] [Updated] (CLOUDSTACK-7070) Continuous Error messages" Invalid cluster session detected" in MS logs after starting the management server

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-7070: - Priority: Blocker (was: Critical) > Continuous Error messages" Invalid cluster sess

[jira] [Commented] (CLOUDSTACK-7070) Continuous Error messages" Invalid cluster session detected" in MS logs after starting the management server

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058355#comment-14058355 ] sadhu suresh commented on CLOUDSTACK-7070: -- CS system vms are not coming i

[jira] [Commented] (CLOUDSTACK-7070) Continuous Error messages" Invalid cluster session detected" in MS logs after starting the management server

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058385#comment-14058385 ] sadhu suresh commented on CLOUDSTACK-7070: -- I just updated the side effect o

[jira] [Commented] (CLOUDSTACK-7070) Continuous Error messages" Invalid cluster session detected" in MS logs after starting the management server

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058402#comment-14058402 ] sadhu suresh commented on CLOUDSTACK-7070: -- Please update the bug with commi

[jira] [Comment Edited] (CLOUDSTACK-7043) Management server fails to load due to DB Decryption failure

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061734#comment-14061734 ] sadhu suresh edited comment on CLOUDSTACK-7043 at 7/15/14 6:09 AM:

[jira] [Commented] (CLOUDSTACK-7043) Management server fails to load due to DB Decryption failure

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14061734#comment-14061734 ] sadhu suresh commented on CLOUDSTACK-7043: -- I still noticed the same behavio

[jira] [Updated] (CLOUDSTACK-7043) Management server fails to load due to DB Decryption failure

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-7043: - Priority: Critical (was: Blocker) > Management server fails to load due to DB Decry

[jira] [Updated] (CLOUDSTACK-7043) CPVM in alert state due to Decryption failure

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-7043: - Summary: CPVM in alert state due to Decryption failure (was: Management server fai

[jira] [Closed] (CLOUDSTACK-7070) Continuous Error messages" Invalid cluster session detected" in MS logs after starting the management server

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-7070. NOt noticed the issue in the latest build ,so closing this issue. > Continuous Error mes

[jira] [Created] (CLOUDSTACK-7131) RVR: router's reduandant state shown as unknown(CheckRouterCommand is failing)

sadhu suresh created CLOUDSTACK-7131: Summary: RVR: router's reduandant state shown as unknown(CheckRouterCommand is failing) Key: CLOUDSTACK-7131 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7131

[jira] [Updated] (CLOUDSTACK-7131) RVR: router's reduandant state shown as unknown(CheckRouterCommand is failing)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-7131: - Attachment: management-server.rar management log > RVR: router's reduandant state s

[jira] [Updated] (CLOUDSTACK-7131) RVR: router's reduandant state shown as unknown(CheckRouterCommand is failing)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-7131: - Attachment: messages-20140717.rar message log > RVR: router's reduandant state sho

[jira] [Commented] (CLOUDSTACK-6498) [Automation] unable to start management server after restart

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068231#comment-14068231 ] sadhu suresh commented on CLOUDSTACK-6498: -- Its reproduced on my setup and

[jira] [Commented] (CLOUDSTACK-6498) [Automation] unable to start management server after restart

[ https://issues.apache.org/jira/browse/CLOUDSTACK-6498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068392#comment-14068392 ] sadhu suresh commented on CLOUDSTACK-6498: -- my MS is up now by following th

[jira] [Created] (CLOUDSTACK-7169) VR_Rolling_Upgarde: command execution order changed when we restart the network

sadhu suresh created CLOUDSTACK-7169: Summary: VR_Rolling_Upgarde: command execution order changed when we restart the network Key: CLOUDSTACK-7169 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7169

[jira] [Created] (CLOUDSTACK-7176) vmware:default route is wrongly configured when deploy a vm with multiple networks

sadhu suresh created CLOUDSTACK-7176: Summary: vmware:default route is wrongly configured when deploy a vm with multiple networks Key: CLOUDSTACK-7176 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7176

[jira] [Commented] (CLOUDSTACK-5870) API support for retrieving UserData

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14073140#comment-14073140 ] sadhu suresh commented on CLOUDSTACK-5870: -- retrieved user data through getV

[jira] [Created] (CLOUDSTACK-5363) kvm:vmsync:vm state still show running even after host is poweredoff

sadhu suresh created CLOUDSTACK-5363: Summary: kvm:vmsync:vm state still show running even after host is poweredoff Key: CLOUDSTACK-5363 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5363

[jira] [Created] (CLOUDSTACK-5375) ldap:ldapconfig and ldapRemove api's are not working

sadhu suresh created CLOUDSTACK-5375: Summary: ldap:ldapconfig and ldapRemove api's are not working Key: CLOUDSTACK-5375 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5375 Project: CloudSta

[jira] [Updated] (CLOUDSTACK-5375) ldap:ldapconfig and ldapRemove api's are not working

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-5375: - Priority: Critical (was: Major) Fix Version/s: 4.3.0 Fut

[jira] [Created] (CLOUDSTACK-5488) KVM:agent is still in stopped state even after host recovered from sudddent power failures(powered off/powered on the kvm host)

sadhu suresh created CLOUDSTACK-5488: Summary: KVM:agent is still in stopped state even after host recovered from sudddent power failures(powered off/powered on the kvm host) Key: CLOUDSTACK-5488 URL: https://

[jira] [Closed] (CLOUDSTACK-5300) applying VPN users fails but notifications says success

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-5300. verifed this issue on upgarde env. before upgrade router try to create a vpn user and it

[jira] [Created] (CLOUDSTACK-5646) ConsoleProxyLoadReportCommand failed after upgrade from 3.0.7patchD to 4.3

sadhu suresh created CLOUDSTACK-5646: Summary: ConsoleProxyLoadReportCommand failed after upgrade from 3.0.7patchD to 4.3 Key: CLOUDSTACK-5646 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5646

[jira] [Updated] (CLOUDSTACK-5646) ConsoleProxyLoadReportCommand failed after upgrade from 3.0.7patchD to 4.3

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-5646: - Attachment: management-server.rar management log > ConsoleProxyLoadReportCommand fa

[jira] [Updated] (CLOUDSTACK-5646) ConsoleProxyLoadReportCommand failed after upgrade from 3.0.7patchD to 4.3

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-5646: - Description: Steps: Created a 3.0.7 setup Registered new system vm templates Stop t

[jira] [Updated] (CLOUDSTACK-5646) ConsoleProxyLoadReportCommand failed after upgrade from 3.0.7patchD to 4.3

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-5646: - Attachment: clouddbdumpfiles.rar db dump files before and after upgrade > ConsolePr

[jira] [Closed] (CLOUDSTACK-5208) upgrade from 3.0.6 to 4.3 is not throwing any exception if new System VM template is not registered with proper name

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-5208. verified the issue and now its showing the proper exception(MS status is running) on the

[jira] [Updated] (CLOUDSTACK-5646) ConsoleProxyLoadReportCommand failed after upgrade from 3.0.7patchD to 4.3

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-5646: - Component/s: Upgrade Priority: Blocker (was: Critical) > ConsoleProxyLoadRep

[jira] [Commented] (CLOUDSTACK-5646) ConsoleProxyLoadReportCommand failed after upgrade from 3.0.7patchD to 4.3

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856813#comment-13856813 ] sadhu suresh commented on CLOUDSTACK-5646: -- after upgarde host goes to disco

[jira] [Commented] (CLOUDSTACK-5393) [Automation] Failed to create snapshot from ROOT volume in KVM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858705#comment-13858705 ] sadhu suresh commented on CLOUDSTACK-5393: -- not seen this issue in 4.3 recen

[jira] [Commented] (CLOUDSTACK-5393) [Automation] Failed to create snapshot from ROOT volume in KVM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859469#comment-13859469 ] sadhu suresh commented on CLOUDSTACK-5393: -- not able to reproduce the issue

[jira] [Created] (CLOUDSTACK-5713) kvm:NPE when agentmanager tries to update the stopped vm state during vmsync

sadhu suresh created CLOUDSTACK-5713: Summary: kvm:NPE when agentmanager tries to update the stopped vm state during vmsync Key: CLOUDSTACK-5713 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5713

[jira] [Updated] (CLOUDSTACK-5713) kvm:NPE when agentmanager tries to update the destroyed vm state during vmsync

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-5713: - Description: env:4.3,kvm steps: 1. create a advanced zone and add a host 2. deploy

[jira] [Updated] (CLOUDSTACK-5713) kvm:NPE when agentmanager tries to update the destroyed vm state during vmsync

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-5713: - Attachment: management-server.rar management log > kvm:NPE when agentmanager tries

[jira] [Updated] (CLOUDSTACK-5713) kvm:vmsync:NPE when agentmanager tries to update the destroyed vm state during vmsync

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-5713: - Summary: kvm:vmsync:NPE when agentmanager tries to update the destroyed vm state du

[jira] [Reopened] (CLOUDSTACK-3344) ldap:UI:sending wrong query filter(converting &symbol to "amp&")during ldapconfig through UI[due to this ldap users fail to login]

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh reopened CLOUDSTACK-3344: -- Now amp was decoded properly but fail to login using ldap credentials firefox respo

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

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-2386. verified this issue(SRX/F5 env) and able to configure the firewall on ICMP rule.so closi

[jira] [Closed] (CLOUDSTACK-2450) SRX:F5:guestvm deployement with userdata failed with exception

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-2450. verified this issue and found to be OK.after url-encoding the base64 userdata deployment

[jira] [Closed] (CLOUDSTACK-2442) VR:F5:deployVM failed due to multiple generic soure NAT IPs provided for network

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-2442. Not able to reproduce the issue in the current build so i am closing this issue.

[jira] [Reopened] (CLOUDSTACK-3482) primary:iscsi:detachvolume is failed when we attach voulme on stopped vm and try to detach volume when VM is running state

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh reopened CLOUDSTACK-3482: -- Its default centos template and i hope pv drivers will come by default.can you please

[jira] [Created] (CLOUDSTACK-4148) usage:usage stats are not triggered for shared network

sadhu suresh created CLOUDSTACK-4148: Summary: usage:usage stats are not triggered for shared network Key: CLOUDSTACK-4148 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4148 Project: CloudS

[jira] [Updated] (CLOUDSTACK-4148) usage:usage stats are not triggered for shared network

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-4148: - Attachment: management-server.rar management log > usage:usage stat

[jira] [Closed] (CLOUDSTACK-3344) ldap:UI:sending wrong query filter(converting &symbol to "amp&")during ldapconfig through UI[due to this ldap users fail to login]

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-3344. verified the issue in the new build and working fine.so closing this issue.

[jira] [Closed] (CLOUDSTACK-3478) primary:iscsi:cleanupvolumes fail with runtime exception

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh closed CLOUDSTACK-3478. destroyed VM expunged successfully.tested with vmware and openfiler iscsi as primary.

[jira] [Created] (CLOUDSTACK-4217) ceph:addprimary storage is failed with exception

sadhu suresh created CLOUDSTACK-4217: Summary: ceph:addprimary storage is failed with exception Key: CLOUDSTACK-4217 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4217 Project: CloudStack

[jira] [Updated] (CLOUDSTACK-4217) ceph:addprimary storage is failed with exception

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-4217: - Priority: Major (was: Critical) > ceph:addprimary storage is failed with except

[jira] [Updated] (CLOUDSTACK-4217) ceph:addprimary storage is failed with exception(documentation is not clear)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-4217: - Component/s: Doc Priority: Minor (was: Major) Summary: ceph:addprimar

[jira] [Comment Edited] (CLOUDSTACK-4217) ceph:addprimary storage is failed with exception(documentation is not clear)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13736353#comment-13736353 ] sadhu suresh edited comment on CLOUDSTACK-4217 at 8/11/13 5:41 PM:

[jira] [Created] (CLOUDSTACK-4240) ceph:unable to attach a rbd datadisk to a ceph instance

sadhu suresh created CLOUDSTACK-4240: Summary: ceph:unable to attach a rbd datadisk to a ceph instance Key: CLOUDSTACK-4240 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4240 Project: Cloud

[jira] [Updated] (CLOUDSTACK-4240) ceph:unable to attach a rbd datadisk to a ceph instance

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-4240: - Fix Version/s: 4.2.0 > ceph:unable to attach a rbd datadisk to a ceph instance >

[jira] [Updated] (CLOUDSTACK-4240) ceph:unable to attach a rbd datadisk to a ceph instance

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-4240: - Attachment: management-server.rar > ceph:unable to attach a rbd datadisk to a ce

[jira] [Resolved] (CLOUDSTACK-4240) ceph:unable to attach a rbd datadisk to a ceph instance

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh resolved CLOUDSTACK-4240. -- Resolution: Invalid Fix Version/s: (was: 4.2.0) > ceph:unable to at

[jira] [Updated] (CLOUDSTACK-4249) ceph:showing wrong template size 755.64 TB(template created from snapshot)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-4249: - Fix Version/s: 4.2.0 > ceph:showing wrong template size 755.64 TB(template creat

[jira] [Created] (CLOUDSTACK-4249) ceph:showing wrong template size 755.64 TB(template created from snapshot)

sadhu suresh created CLOUDSTACK-4249: Summary: ceph:showing wrong template size 755.64 TB(template created from snapshot) Key: CLOUDSTACK-4249 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4249

[jira] [Updated] (CLOUDSTACK-4249) ceph:showing wrong template size 755.64 TB(template created from snapshot)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-4249: - Attachment: management-server.rar > ceph:showing wrong template size 755.64 TB(t

[jira] [Updated] (CLOUDSTACK-410) KVM:Ubuntu:vnc_listen not configured in qemu.conf for Ubuntu KVM host(unable to view the console)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-410: Component/s: Doc Priority: Critical (was: Major) Summary: KVM:Ubuntu:vnc

[jira] [Created] (CLOUDSTACK-4278) ceph:volumeresize failed with Internal error(Nullpointer exception)

sadhu suresh created CLOUDSTACK-4278: Summary: ceph:volumeresize failed with Internal error(Nullpointer exception) Key: CLOUDSTACK-4278 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4278 P

[jira] [Updated] (CLOUDSTACK-4278) ceph:volumeresize failed with Internal error(Nullpointer exception)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-4278: - Component/s: Doc > ceph:volumeresize failed with Internal error(Nullpointer exce

[jira] [Updated] (CLOUDSTACK-4278) ceph:volumeresize failed with Internal error(Nullpointer exception)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-4278: - Fix Version/s: 4.2.0 > ceph:volumeresize failed with Internal error(Nullpointer

[jira] [Commented] (CLOUDSTACK-4217) ceph:addprimary storage is failed with exception(documentation is not clear)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738062#comment-13738062 ] sadhu suresh commented on CLOUDSTACK-4217: -- wido, every time when i use clie

[jira] [Created] (CLOUDSTACK-4292) ceph:destroyedvm failed with ArrayIndexexception while expunging

sadhu suresh created CLOUDSTACK-4292: Summary: ceph:destroyedvm failed with ArrayIndexexception while expunging Key: CLOUDSTACK-4292 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4292 Proj

[jira] [Created] (CLOUDSTACK-4297) ceph:request to add support for zonewide prmary storage.

sadhu suresh created CLOUDSTACK-4297: Summary: ceph:request to add support for zonewide prmary storage. Key: CLOUDSTACK-4297 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4297 Project: Clou

[jira] [Commented] (CLOUDSTACK-4292) ceph:destroyedvm failed with ArrayIndexexception while expunging

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738148#comment-13738148 ] sadhu suresh commented on CLOUDSTACK-4292: -- asyn job shows destroyVM success

[jira] [Updated] (CLOUDSTACK-4292) ceph:destroyedvm failed with ArrayIndexexception while expunging

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-4292: - Attachment: management-server.rar management log > ceph:destroyedvm

[jira] [Created] (CLOUDSTACK-4301) ceph:KVM:create volume from snapshot failing with Runtime exception

sadhu suresh created CLOUDSTACK-4301: Summary: ceph:KVM:create volume from snapshot failing with Runtime exception Key: CLOUDSTACK-4301 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4301 P

[jira] [Created] (CLOUDSTACK-4304) ceph:fail to attach a volume created from snapshot to same Instance

sadhu suresh created CLOUDSTACK-4304: Summary: ceph:fail to attach a volume created from snapshot to same Instance Key: CLOUDSTACK-4304 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4304 P

[jira] [Commented] (CLOUDSTACK-4304) ceph:fail to attach a volume created from snapshot to same Instance

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738691#comment-13738691 ] sadhu suresh commented on CLOUDSTACK-4304: -- mysql> select * from snapshots

[jira] [Updated] (CLOUDSTACK-4304) ceph:nfsfail to attach a volume created from snapshot to same Instance

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-4304: - Summary: ceph:nfsfail to attach a volume created from snapshot to same Instance (wa

[jira] [Created] (CLOUDSTACK-4373) vpn:fai to connect to vpnserver after restartnetwork with cleanup option

sadhu suresh created CLOUDSTACK-4373: Summary: vpn:fai to connect to vpnserver after restartnetwork with cleanup option Key: CLOUDSTACK-4373 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4373

[jira] [Updated] (CLOUDSTACK-4373) vpn:fai to connect to vpnserver after restartnetwork with cleanup option

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-4373: - Attachment: management-server.rar management log > vpn:fai to conne

[jira] [Commented] (CLOUDSTACK-4301) ceph:KVM:create volume from snapshot failing with Runtime exception

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745928#comment-13745928 ] sadhu suresh commented on CLOUDSTACK-4301: -- Tested in the latest build and f

[jira] [Commented] (CLOUDSTACK-4249) [KVM]ceph:showing wrong template size 755.64 TB(template created from snapshot)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745970#comment-13745970 ] sadhu suresh commented on CLOUDSTACK-4249: -- properties of template created f

[jira] [Created] (CLOUDSTACK-4423) ceph:migrate instance form one primary to another primary failing

sadhu suresh created CLOUDSTACK-4423: Summary: ceph:migrate instance form one primary to another primary failing Key: CLOUDSTACK-4423 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4423 Pr

[jira] [Updated] (CLOUDSTACK-4423) ceph:migrate instance form one primary to another primary failing

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-4423: - Attachment: management-server.rar management log > ceph:migrate ins

[jira] [Created] (CLOUDSTACK-4424) ceph:kvm:download volume created from snapshot failed with runtime exception

sadhu suresh created CLOUDSTACK-4424: Summary: ceph:kvm:download volume created from snapshot failed with runtime exception Key: CLOUDSTACK-4424 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4424

[jira] [Updated] (CLOUDSTACK-4424) ceph:kvm:download volume created from snapshot failed with runtime exception

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-4424: - Affects Version/s: 4.2.0 Fix Version/s: 4.2.0 > ceph:kvm:download volume

[jira] [Updated] (CLOUDSTACK-4424) ceph:kvm:download volume created from snapshot failed with runtime exception

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sadhu suresh updated CLOUDSTACK-4424: - Attachment: management-server_1.rar management log > ceph:kvm:downl

[jira] [Commented] (CLOUDSTACK-4249) [KVM]ceph:showing wrong template size 755.64 TB(template created from snapshot)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746027#comment-13746027 ] sadhu suresh commented on CLOUDSTACK-4249: -- I have tried on normal kVM's NFS

[jira] [Comment Edited] (CLOUDSTACK-4249) [KVM]ceph:showing wrong template size 755.64 TB(template created from snapshot)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746027#comment-13746027 ] sadhu suresh edited comment on CLOUDSTACK-4249 at 8/21/13 1:16 PM:

  1   2   3   >