[jira] [Created] (CLOUDSTACK-5642) KVM - LibvirtDomainXMLParser did not support

howie yu created CLOUDSTACK-5642: Summary: KVM - LibvirtDomainXMLParser did not support Key: CLOUDSTACK-5642 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5642 Project: CloudStack Is

[jira] [Commented] (CLOUDSTACK-5144) [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when there is no ingress rule defined for the security group

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856519#comment-13856519 ] Jayapal Reddy commented on CLOUDSTACK-5144: --- In 4.3, basic zone with KVM th

[jira] [Commented] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856438#comment-13856438 ] Nitin Mehta commented on CLOUDSTACK-5641: - This is because in the storage poo

[jira] [Created] (CLOUDSTACK-5641) Local disk usage on host don't show up in the admin's webui

Nitin Mehta created CLOUDSTACK-5641: --- Summary: Local disk usage on host don't show up in the admin's webui Key: CLOUDSTACK-5641 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5641 Project: Cl

[jira] [Commented] (CLOUDSTACK-5613) CloudStack 4.2.0 - Usage server is running but tables remain empty

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856389#comment-13856389 ] Guy Beaupré commented on CLOUDSTACK-5613: - I confirm that both files exist an

[jira] [Updated] (CLOUDSTACK-5640) [Automation] sequence item 0: expected string, NoneType found

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5640: - Description: Creating this bug as a place holder for the fol

[jira] [Commented] (CLOUDSTACK-5144) [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when there is no ingress rule defined for the security group

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856327#comment-13856327 ] Wei Zhou commented on CLOUDSTACK-5144: -- Jayapal, I checked our 4.2.1 platform

[jira] [Created] (CLOUDSTACK-5640) [Automation] sequence item 0: expected string, NoneType found

Srikanteswararao Talluri created CLOUDSTACK-5640: Summary: [Automation] sequence item 0: expected string, NoneType found Key: CLOUDSTACK-5640 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5

[jira] [Updated] (CLOUDSTACK-5639) [Hyper-v] cold storage migration does not work in hyperv

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjeev N updated CLOUDSTACK-5639: -- Attachment: management-server.rar Attached MS log file. > [Hyper-v] cold storage migratio

[jira] [Created] (CLOUDSTACK-5639) [Hyper-v] cold storage does not work in hyperv

Sanjeev N created CLOUDSTACK-5639: - Summary: [Hyper-v] cold storage does not work in hyperv Key: CLOUDSTACK-5639 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5639 Project: CloudStack

[jira] [Updated] (CLOUDSTACK-5639) [Hyper-v] cold storage migration does not work in hyperv

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjeev N updated CLOUDSTACK-5639: -- Summary: [Hyper-v] cold storage migration does not work in hyperv (was: [Hyper-v] cold st

[jira] [Updated] (CLOUDSTACK-5637) [Automation] test_09_stop_vm_migrate_vol failed due to Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext : u'Volume needs to be detached from VM'}

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5637: - Description: Creating this bug as a place holder for the fol

[jira] [Created] (CLOUDSTACK-5638) [Automation] test_02_NetworkGarbageCollection failed because it could not Check list router response for router state

Srikanteswararao Talluri created CLOUDSTACK-5638: Summary: [Automation] test_02_NetworkGarbageCollection failed because it could not Check list router response for router state Key: CLOUDSTACK-5638

[jira] [Updated] (CLOUDSTACK-5638) [Automation] test_02_NetworkGarbageCollection failed because it could not Check list router response for router state

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5638: - Description: Creating this bug as a place holder for the fol

[jira] [Created] (CLOUDSTACK-5637) [Automation] test_09_stop_vm_migrate_vol failed due to Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext : u'Volume needs to be detached from VM'}

Srikanteswararao Talluri created CLOUDSTACK-5637: Summary: [Automation] test_09_stop_vm_migrate_vol failed due to Execute cmd: asyncquery failed, due to: {errorcode : 530, errortext : u'Volume needs to be detached from VM'}

[jira] [Created] (CLOUDSTACK-5635) [Automation]Max volumes has been exceeded for domain during test

Srikanteswararao Talluri created CLOUDSTACK-5635: Summary: [Automation]Max volumes has been exceeded for domain during test Key: CLOUDSTACK-5635 URL: https://issues.apache.org/jira/browse/CLOUDSTAC

[jira] [Updated] (CLOUDSTACK-5636) [Automation]Failed to upgrade network offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5636: - Description: Creating this bug as a place holder for the fol

[jira] [Updated] (CLOUDSTACK-5635) [Automation]Max volumes has been exceeded for domain during test

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5635: - Description: Creating this bug as a place holder for the fol

[jira] [Created] (CLOUDSTACK-5636) [Automation]Failed to upgrade network offering

Srikanteswararao Talluri created CLOUDSTACK-5636: Summary: [Automation]Failed to upgrade network offering Key: CLOUDSTACK-5636 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5636

[jira] [Created] (CLOUDSTACK-5634) [Automation]Host is becoming unreachable during tests

Srikanteswararao Talluri created CLOUDSTACK-5634: Summary: [Automation]Host is becoming unreachable during tests Key: CLOUDSTACK-5634 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5634

[jira] [Updated] (CLOUDSTACK-5634) [Automation]Host is becoming unreachable during tests

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5634: - Description: Creating this bug as a place holder for the fol

[jira] [Updated] (CLOUDSTACK-5633) [Automation]cleanup failed due to network deletion failed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5633: - Summary: [Automation]cleanup failed due to network deletion f

[jira] [Updated] (CLOUDSTACK-5633) [Automation]cleanup failed due to network deletion failed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5633: - Description: Creating this bug as a place holder for the fol

[jira] [Updated] (CLOUDSTACK-5633) [Automation]cleanup failed due to network doesn't exist

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5633: - Description: Creating this bug as a place holder for the fol

[jira] [Created] (CLOUDSTACK-5633) [Automation]cleanup failed due to network doesn't exist

Srikanteswararao Talluri created CLOUDSTACK-5633: Summary: [Automation]cleanup failed due to network doesn't exist Key: CLOUDSTACK-5633 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5633

[jira] [Updated] (CLOUDSTACK-5631) [Automation]setup related failures in tests

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5631: - Description: Creating this bug as a place holder for the fol

[jira] [Updated] (CLOUDSTACK-5632) [Automation]template deletion failed because teardown is not waiting for it to download

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5632: - Description: Creating this bug as a place holder for the fol

[jira] [Created] (CLOUDSTACK-5632) [Automation]template deletion failed because teardown is not waiting for it to download

Srikanteswararao Talluri created CLOUDSTACK-5632: Summary: [Automation]template deletion failed because teardown is not waiting for it to download Key: CLOUDSTACK-5632 URL: https://issues.apache.or

[jira] [Updated] (CLOUDSTACK-5630) [Automation]snapshot tests are failing

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5630: - Summary: [Automation]snapshot tests are failing (was: CLONE

[jira] [Created] (CLOUDSTACK-5631) [Automation]setup related failures in tests

Srikanteswararao Talluri created CLOUDSTACK-5631: Summary: [Automation]setup related failures in tests Key: CLOUDSTACK-5631 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5631 Pr

[jira] [Updated] (CLOUDSTACK-5630) CLONE - [Automation]snapshot tests are failing

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5630: - Description: Creating this bug as a place holder for the fol

[jira] [Created] (CLOUDSTACK-5630) CLONE - [Automation]snapshot tests are failing

Srikanteswararao Talluri created CLOUDSTACK-5630: Summary: CLONE - [Automation]snapshot tests are failing Key: CLOUDSTACK-5630 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5630

[jira] [Updated] (CLOUDSTACK-5629) [Automation] ssh access failed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5629: - Description: Creating this bug as a place holder for the fol

[jira] [Updated] (CLOUDSTACK-5629) [Automation] ssh access failed

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5629: - Description: Creating this bug as a place holder for the fol

[jira] [Created] (CLOUDSTACK-5629) [Automation] ssh access failed

Srikanteswararao Talluri created CLOUDSTACK-5629: Summary: [Automation] ssh access failed Key: CLOUDSTACK-5629 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5629 Project: CloudS

[jira] [Created] (CLOUDSTACK-5628) [Automation] associateIPaddresscmd failed due to: errorCode: 431, errorText:Account has more than one Isolated network in the zone

Srikanteswararao Talluri created CLOUDSTACK-5628: Summary: [Automation] associateIPaddresscmd failed due to: errorCode: 431, errorText:Account has more than one Isolated network in the zone Key: CLOUDSTACK-5628

[jira] [Updated] (CLOUDSTACK-5628) [Automation] associateIPaddresscmd failed due to: errorCode: 431, errorText:Account has more than one Isolated network in the zone

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5628: - Description: Creating this bug as a place holder for the fol

[jira] [Created] (CLOUDSTACK-5627) [Automation] exception not raised

Srikanteswararao Talluri created CLOUDSTACK-5627: Summary: [Automation] exception not raised Key: CLOUDSTACK-5627 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5627 Project: Clo

[jira] [Updated] (CLOUDSTACK-5627) [Automation] exception not raised

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5627: - Description: Creating this bug as a place holder for the fol

[jira] [Updated] (CLOUDSTACK-5626) [Automation] migrate instance tests are failing

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5626: - Description: Creating this bug as a place holder for the fol

[jira] [Created] (CLOUDSTACK-5626) [Automation] migrate instance tests are failing

Srikanteswararao Talluri created CLOUDSTACK-5626: Summary: [Automation] migrate instance tests are failing Key: CLOUDSTACK-5626 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5626

[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] [Updated] (CLOUDSTACK-5625) [Automation] ldap configuration tests are failing

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5625: - Description: Creating this bug as a place holder for the fol

[jira] [Created] (CLOUDSTACK-5625) [Automation] ldap configuration tests are failing

Srikanteswararao Talluri created CLOUDSTACK-5625: Summary: [Automation] ldap configuration tests are failing Key: CLOUDSTACK-5625 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5625

[jira] [Updated] (CLOUDSTACK-5624) [Automation] Cleanup_resources not found

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5624: - Description: Creating this bug as a place holder for the fol

[jira] [Created] (CLOUDSTACK-5624) [Automation] Cleanup_resources not found

Srikanteswararao Talluri created CLOUDSTACK-5624: Summary: [Automation] Cleanup_resources not found Key: CLOUDSTACK-5624 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5624 Proje

[jira] [Updated] (CLOUDSTACK-5144) [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when there is no ingress rule defined for the security group

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayapal Reddy updated CLOUDSTACK-5144: -- Assignee: Wei Zhou (was: Jayapal Reddy) > [Automation]: Basic Zone Security Group

[jira] [Commented] (CLOUDSTACK-5144) [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when there is no ingress rule defined for the security group

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856305#comment-13856305 ] Jayapal Reddy commented on CLOUDSTACK-5144: --- Hi Wei zhou, I have observed

[jira] [Updated] (CLOUDSTACK-5342) Add NIC to virtual machine fails in KVM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala updated CLOUDSTACK-5342: -- Assignee: Saksham Srivastava (was: Kishan Kavala) > Add NIC to virtual machine fa

[jira] [Commented] (CLOUDSTACK-5342) Add NIC to virtual machine fails in KVM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856304#comment-13856304 ] Kishan Kavala commented on CLOUDSTACK-5342: --- Saksham, Is KVM supported for

[jira] [Updated] (CLOUDSTACK-5619) [Automation] Router is not accessible

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5619: - Description: Creating this bug as a place holder for the fo

[jira] [Updated] (CLOUDSTACK-5623) [Automation]Failed to wget from VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5623: - Description: Creating this bug as a place holder for the fol

[jira] [Created] (CLOUDSTACK-5623) [Automation]Failed to wget from VM

Srikanteswararao Talluri created CLOUDSTACK-5623: Summary: [Automation]Failed to wget from VM Key: CLOUDSTACK-5623 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5623 Project: Cl

[jira] [Updated] (CLOUDSTACK-5144) [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when there is no ingress rule defined for the security group

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye updated CLOUDSTACK-5144: --- Attachment: agent.log > [Automation]: Basic Zone Security Groups - SSH to VM is

[jira] [Updated] (CLOUDSTACK-5622) [Automation]test_forceDeleteDomain failed due to :cloudstackAPIException not raised

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5622: - Description: Creating this bug as a place holder for the fol

[jira] [Updated] (CLOUDSTACK-5621) [Automation] global name 'login' is not defined

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5621: - Description: Creating this bug as a place holder for the fo

[jira] [Created] (CLOUDSTACK-5622) [Automation]test_forceDeleteDomain failed due to :cloudstackAPIException not raised

Srikanteswararao Talluri created CLOUDSTACK-5622: Summary: [Automation]test_forceDeleteDomain failed due to :cloudstackAPIException not raised Key: CLOUDSTACK-5622 URL: https://issues.apache.org/ji

[jira] [Created] (CLOUDSTACK-5620) [Automation] test_07_1_egress_fr7 FAILED Router network failed to come up after 6 minutes. test_07_egress_fr7 FAILED Router network failed to come up after 6 minutes

Srikanteswararao Talluri created CLOUDSTACK-5620: Summary: [Automation] test_07_1_egress_fr7 FAILED Router network failed to come up after 6 minutes. test_07_egress_fr7FAILED Router network failed to come up after 6 minutes.

[jira] [Updated] (CLOUDSTACK-5620) [Automation] Router network failed to come up after 6 minutes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanteswararao Talluri updated CLOUDSTACK-5620: - Description: Creating this bug as a place holder for the f

[jira] [Created] (CLOUDSTACK-5621) [Automation] global name 'login' is not defined

Srikanteswararao Talluri created CLOUDSTACK-5621: Summary: [Automation] global name 'login' is not defined Key: CLOUDSTACK-5621 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5621

[jira] [Created] (CLOUDSTACK-5619) [Automation] Router is not accessible

Srikanteswararao Talluri created CLOUDSTACK-5619: Summary: [Automation] Router is not accessible Key: CLOUDSTACK-5619 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5619 Project:

[jira] [Commented] (CLOUDSTACK-5254) firewall command is not applied on VR after upgrade if firewall rule is set on VR when VR is on older version

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856300#comment-13856300 ] ASF subversion and git services commented on CLOUDSTACK-5254: -

[jira] [Resolved] (CLOUDSTACK-5254) firewall command is not applied on VR after upgrade if firewall rule is set on VR when VR is on older version

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala resolved CLOUDSTACK-5254. --- Resolution: Fixed > firewall command is not applied on VR after upgrade if firew

[jira] [Commented] (CLOUDSTACK-5254) firewall command is not applied on VR after upgrade if firewall rule is set on VR when VR is on older version

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856299#comment-13856299 ] ASF subversion and git services commented on CLOUDSTACK-5254: -

[jira] [Updated] (CLOUDSTACK-5144) [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when there is no ingress rule defined for the security group

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye updated CLOUDSTACK-5144: --- Attachment: ipset-L output.txt > [Automation]: Basic Zone Security Groups - SSH

[jira] [Updated] (CLOUDSTACK-5552) createPrivateGateway cmd should fail on non-upgarded VR as applying Network ACL fails.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala updated CLOUDSTACK-5552: -- Assignee: Jayapal Reddy (was: Kishan Kavala) > createPrivateGateway cmd should fa

[jira] [Updated] (CLOUDSTACK-5617) [LDAP] change password is disabled for admin user once LDAP is configured

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5617: Description: After configuring LDAP, there is no way to change the password of

[jira] [Updated] (CLOUDSTACK-3183) [AWSAPI] EC2 SOAP calls fail with NPE in a developer setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty updated CLOUDSTACK-3183: --- Fix Version/s: (was: 4.3.0) Future > [AWSAPI] EC2 SOAP ca

[jira] [Updated] (CLOUDSTACK-5144) [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when there is no ingress rule defined for the security group

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye updated CLOUDSTACK-5144: --- Attachment: iptables-rules.txt Iptable rules on the KVM host > [Automation]: Ba

[jira] [Resolved] (CLOUDSTACK-5508) Vmware - When there are multiple secondary stores , the newly added secondary store is not being selected for backing up snapshots.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Likitha Shetty resolved CLOUDSTACK-5508. Resolution: Fixed > Vmware - When there are multiple secondary stores , the ne

[jira] [Updated] (CLOUDSTACK-5144) [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when there is no ingress rule defined for the security group

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Aradhye updated CLOUDSTACK-5144: --- Attachment: MS-Log.txt Steps: 1) Created account 2) Deployed VM 3) SSH to vm (Wi

[jira] [Commented] (CLOUDSTACK-5508) Vmware - When there are multiple secondary stores , the newly added secondary store is not being selected for backing up snapshots.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856293#comment-13856293 ] ASF subversion and git services commented on CLOUDSTACK-5508: -

[jira] [Created] (CLOUDSTACK-5618) [LDAP] same LDAP user can be imported to multiple domains

Rajani Karuturi created CLOUDSTACK-5618: --- Summary: [LDAP] same LDAP user can be imported to multiple domains Key: CLOUDSTACK-5618 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5618 Projec

[jira] [Commented] (CLOUDSTACK-5144) [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when there is no ingress rule defined for the security group

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856290#comment-13856290 ] Gaurav Aradhye commented on CLOUDSTACK-5144: Hi, KVM basic zone setup is

[jira] [Commented] (CLOUDSTACK-5600) Xenserver - After HA , CPVM's disk is corrupted resulting in CPVM being stuck in "Starting" state.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856288#comment-13856288 ] Koushik Das commented on CLOUDSTACK-5600: - Sangeetha, Is the global config "e

[jira] [Updated] (CLOUDSTACK-5600) Xenserver - After HA , CPVM's disk is corrupted resulting in CPVM being stuck in "Starting" state.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-5600: Assignee: Sangeetha Hariharan > Xenserver - After HA , CPVM's disk is corrupted result

[jira] [Commented] (CLOUDSTACK-5508) Vmware - When there are multiple secondary stores , the newly added secondary store is not being selected for backing up snapshots.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856287#comment-13856287 ] ASF subversion and git services commented on CLOUDSTACK-5508: -

[jira] [Created] (CLOUDSTACK-5617) [LDAP] change password is disabled for admin user once LDAP is configured

Rajani Karuturi created CLOUDSTACK-5617: --- Summary: [LDAP] change password is disabled for admin user once LDAP is configured Key: CLOUDSTACK-5617 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5617

[jira] [Commented] (CLOUDSTACK-5600) Xenserver - After HA , CPVM's disk is corrupted resulting in CPVM being stuck in "Starting" state.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856286#comment-13856286 ] Koushik Das commented on CLOUDSTACK-5600: - Simultaneous HA jobs for CPVM v-1-

[jira] [Commented] (CLOUDSTACK-5144) [Automation]: Basic Zone Security Groups - SSH to VM is allowed even when there is no ingress rule defined for the security group

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856285#comment-13856285 ] Jayapal Reddy commented on CLOUDSTACK-5144: --- Hi Gaurav, Did you install CS

[jira] [Resolved] (CLOUDSTACK-5595) [Hyper-V] add vlan to storage nic to vnic for ssvm

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala resolved CLOUDSTACK-5595. Resolution: Fixed > [Hyper-V] add vlan to storage nic to vnic for ssvm > -

[jira] [Commented] (CLOUDSTACK-5595) [Hyper-V] add vlan to storage nic to vnic for ssvm

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856281#comment-13856281 ] ASF subversion and git services commented on CLOUDSTACK-5595: -

[jira] [Updated] (CLOUDSTACK-5595) [Hyper-V] add vlan to storage nic to vnic for ssvm

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala updated CLOUDSTACK-5595: --- Priority: Critical (was: Blocker) > [Hyper-V] add vlan to storage nic to vnic f

[jira] [Resolved] (CLOUDSTACK-5601) Created Desktop based default CentOS template for HyperV

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala resolved CLOUDSTACK-5601. Resolution: Fixed > Created Desktop based default CentOS template for HyperV >

[jira] [Resolved] (CLOUDSTACK-5585) [Automation]Unable to stop VM reported by HA Worker

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar resolved CLOUDSTACK-5585. -- Resolution: Fixed > [Automation]Unable to stop VM reported by HA Worker >

[jira] [Commented] (CLOUDSTACK-5585) [Automation]Unable to stop VM reported by HA Worker

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856261#comment-13856261 ] Bharat Kumar commented on CLOUDSTACK-5585: -- The stopVM command is successfu

[jira] [Resolved] (CLOUDSTACK-5562) management-server.log file does not get created with cloud user hence logging fails

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saksham Srivastava resolved CLOUDSTACK-5562. Resolution: Implemented > management-server.log file does not get crea

[jira] [Commented] (CLOUDSTACK-5562) management-server.log file does not get created with cloud user hence logging fails

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856260#comment-13856260 ] Saksham Srivastava commented on CLOUDSTACK-5562: Resolving the bug as

[jira] [Commented] (CLOUDSTACK-5562) management-server.log file does not get created with cloud user hence logging fails

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856259#comment-13856259 ] Sanjeev N commented on CLOUDSTACK-5562: --- It works in the latest build. > manag

[jira] [Created] (CLOUDSTACK-5616) [DBHA]:There is no way to know to which DB is the CS writing in the case of DBHA.

Kiran Koneti created CLOUDSTACK-5616: Summary: [DBHA]:There is no way to know to which DB is the CS writing in the case of DBHA. Key: CLOUDSTACK-5616 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5616

[jira] [Assigned] (CLOUDSTACK-5610) [Hyper-v] Host does not go into Alert state even though it is power-off hence vm deployment fails

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devdeep Singh reassigned CLOUDSTACK-5610: - Assignee: Devdeep Singh > [Hyper-v] Host does not go into Alert state even t

[jira] [Closed] (CLOUDSTACK-5226) CS never goes down when both M1 and M2 are down in case of DB HA enabled.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-5226. Not reproduced in the latest builds hence closing the issue. > CS never goes down when bo

[jira] [Updated] (CLOUDSTACK-5615) [UI]: ldap add account header is not i18n'd

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5615: Labels: i18n ldap (was: ldap) > [UI]: ldap add account header is not i18n'd >

[jira] [Closed] (CLOUDSTACK-5207) jdbc.exceptions are observed when both Master 1 and master 2 goes down and comes back.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Koneti closed CLOUDSTACK-5207. Closing the issue as the Design is changed that when both the DB servers are down the CS

[jira] [Updated] (CLOUDSTACK-5615) [UI]: ldap add account header is not i18n'd

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5615: Description: once ldap is configured, on clicking add account on all accounts

[jira] [Updated] (CLOUDSTACK-5615) [UI]: ldap add account header is not i18n'd

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5615: Description: once ldap is configured, on clicking add account on all accounts

[jira] [Updated] (CLOUDSTACK-5615) [UI]: ldap add account header is not i18n'd

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5615: Description: once ldap is configured, on clicking add account on all accounts

[jira] [Updated] (CLOUDSTACK-5615) [UI]: ldap add account header is not i18n'd

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5615: Description: once ldap is configured, on clicking add account on all accounts

[jira] [Updated] (CLOUDSTACK-5615) [UI]: ldap add account header is not i18n'd

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5615: Attachment: CloudStack-add-account.png > [UI]: ldap add account header is not

[jira] [Updated] (CLOUDSTACK-5615) [UI]: ldap add account header is not i18n'd

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-5615: Description: once ldap is configured, on clicking add account on all accounts

  1   2   >