[jira] [Created] (CLOUDSTACK-1771) IPv6 - Network restart for a dual network , results in the ipv4 address of the router to be changed. After netwpork restart , name resolution of the Vms fail.

Sangeetha Hariharan created CLOUDSTACK-1771: --- Summary: IPv6 - Network restart for a dual network , results in the ipv4 address of the router to be changed. After netwpork restart , name resolution of the Vms fail. Key:

[jira] [Commented] (CLOUDSTACK-1701) ipv6 - When VM is deployed as part of 2 ipv4 networks , in /ect/resolv.conf domain -name of the non default network is programmed resulting in name resolution fail

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13609470#comment-13609470 ] Sangeetha Hariharan commented on CLOUDSTACK-1701: - Confirmed that thi

[jira] [Closed] (CLOUDSTACK-1710) AWS Regions - As part of adding a new region,default_zone_id column for the account entries should not be synced.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1710. --- Following documentation is added in FS: 7. Set default zone as null

[jira] [Closed] (CLOUDSTACK-1716) AWS Regions - listRegions(),removeRegions(),updateRegions() should accept UUID value instead of id.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1716. --- Closing this issue as per Kishan's comments. > AWS Regions

[jira] [Closed] (CLOUDSTACK-1711) AWS Regions - Include all the details of the API call made in the Events payload when changes in Admin/Account/User objects are made..

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1711. --- Closing this issue as per Murali's comments that there is no need for all th

[jira] [Closed] (CLOUDSTACK-1218) IPv6: Shared Network - After network restart with clean option , router is assigned a different address. Name resolution for the existing guest Vms in the network fai

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1218. --- Closing this issue. With latest build from 4.1 , ipv6 router is always give

[jira] [Closed] (CLOUDSTACK-1709) AWS Regions - As part of adding a new region , project related entries should not be synced from accounts table.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1709. --- Following documentation added to FS: 6. Remove project accounts after copyi

[jira] [Closed] (CLOUDSTACK-1636) AWS Regions - Remove the concept of having an owner region for domain/account/user objects.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1636. --- With latest build from 4.1: There is no region_id in domain/account/user ta

[jira] [Created] (CLOUDSTACK-1775) AWS Regions - Events Framework - Events relating to User/Domain/Account are not being published to the RabbitMQ server expect for USER-DISABLE,DOMAIN-DELETE and ACCO

Sangeetha Hariharan created CLOUDSTACK-1775: --- Summary: AWS Regions - Events Framework - Events relating to User/Domain/Account are not being published to the RabbitMQ server expect for USER-DISABLE,DOMAIN-DELETE and ACCOUNT.DISABLE even

[jira] [Commented] (CLOUDSTACK-1775) AWS Regions - Events Framework - Events relating to User/Domain/Account are not being published to the RabbitMQ server expect for USER-DISABLE,DOMAIN-DELETE and AC

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13609777#comment-13609777 ] Sangeetha Hariharan commented on CLOUDSTACK-1775: - Also for the the U

[jira] [Reopened] (CLOUDSTACK-1664) Action Events are not logged due to spring changes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan reopened CLOUDSTACK-1664: - With the latest build from 4.1 , I see the events being created in DB fo

[jira] [Updated] (CLOUDSTACK-1775) AWS Regions - Events Framework - Events relating to User/Domain/Account are not being published to the RabbitMQ server expect for USER-DISABLE,DOMAIN-DELETE and ACCO

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1775: Fix Version/s: (was: 4.1.1) 4.1.0 > AWS Reg

[jira] [Created] (CLOUDSTACK-1792) AWS Regions - RuntimeException while executing listAccounts() , when the encryption keys are set to different values between regions.

Sangeetha Hariharan created CLOUDSTACK-1792: --- Summary: AWS Regions - RuntimeException while executing listAccounts() , when the encryption keys are set to different values between regions. Key: CLOUDSTACK-1792

[jira] [Updated] (CLOUDSTACK-1792) AWS Regions - RuntimeException while executing listAccounts() , when the encryption keys are set to different values between regions.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1792: Description: Steps to reproduce the problem: Install a 1 management s

[jira] [Commented] (CLOUDSTACK-1792) AWS Regions - RuntimeException while executing listAccounts() , when the encryption keys are set to different values between regions.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611310#comment-13611310 ] Sangeetha Hariharan commented on CLOUDSTACK-1792: - The issue seems to

[jira] [Closed] (CLOUDSTACK-1553) AWS Regions-Not able to list accounts from the 2nd region after user/account/domain details have been manually synced up from first region.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1553. --- Closing this issue. FS includes the step to restart management servers after

[jira] [Closed] (CLOUDSTACK-1674) AWS Regions - Events - Account Deletion event does not include the UUID of the account deleted.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1674. --- Closing this issue . Issue mentioned in the bug is tracked part of CLOUDSTA

[jira] [Closed] (CLOUDSTACK-1663) AWS Regions - Events - There are no events being generated when a new domain is added/edited.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1663. --- Closing this issue . Issue mentioned in the bug is tracked part of CLOUDSTA

[jira] [Closed] (CLOUDSTACK-1488) Ipv6 - When Vm is deployed as part of multiple networks, one of the IPV6 address assigned to guest VM is lost.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1488. --- closing this issue as this is a guest os specific issue. >

[jira] [Closed] (CLOUDSTACK-1665) AWS Regions - Events - There are no events being generated when a new user is added/edited/enabled/deleted/password changes/api&secret keys are generated.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1665. --- Closing this issue . Issue mentioned in the bug is tracked part of CLOUDSTA

[jira] [Reopened] (CLOUDSTACK-1717) AWS Regions - Local region entry that gets added by default should not include "/api" for its end_point.Also the endpoint should have the actual hostname instead of

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan reopened CLOUDSTACK-1717: - Should we be able to use the cluster.node.IP parameter in db.properties

[jira] [Commented] (CLOUDSTACK-1717) AWS Regions - Local region entry that gets added by default should not include "/api" for its end_point.Also the endpoint should have the actual hostname instead o

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611359#comment-13611359 ] Sangeetha Hariharan commented on CLOUDSTACK-1717: - Tested with latest

[jira] [Closed] (CLOUDSTACK-1139) After the Vm is "Expunged" we see the entry still being present in the router in /etc/dhcphosts.txt

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1139. --- Closing this issue as per Sheng's comments. > After the Vm

[jira] [Closed] (CLOUDSTACK-1094) Ipv6 - hostname/hostname --fqdn does not return the name of the VM. But i am able to reach the Vm using their names.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1094. --- closing this issue as this is guest os specific issue. > Ip

[jira] [Closed] (CLOUDSTACK-1688) AWS Regions - Domain admin user is not able to use getUser() command to fetch user details.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1688. --- Closing this issue as per the comments from Kishan. > AWS R

[jira] [Closed] (CLOUDSTACK-1671) AWS Regions - Events - Domain Delete event does not include the UUID of the domain that was deleted.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1671. --- Closing this issue. I will verify the use cases mentioned in this bug as pa

[jira] [Closed] (CLOUDSTACK-1464) IPV6 - Multi nic - Ubuntu 1210 -When Vm is stopped and started/ rebooted , i get multiple global IPV6 addresses being allocated for one of the nics.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1464. --- Closing this issue as this is a guest os specific issue. >

[jira] [Closed] (CLOUDSTACK-1463) IPV6 - Ubuntu 12.10 - Multiple Nic - IPV6 address is assigned automatically for 1 nic only. Need to do a manual dhclient request to get the ipv6 for other nic.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1463. --- Closing this issue as this is a guest os specific issue. >

[jira] [Closed] (CLOUDSTACK-1583) AWS Regions - RabbitMQ Server did not recieve any event notification during account creation.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1583. --- Closing this issue. We are able to see events being published to RabbitMQ s

[jira] [Closed] (CLOUDSTACK-1418) As regular user , we are not allowed to deploy VM on a shared network.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1418. --- Tested with latest build from 4.1. We are allowed to deploy Vms in a Shared

[jira] [Closed] (CLOUDSTACK-1417) When invalid values are passed to createNetwork() , error message does not indicate the parameter name that has invalid values.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1417. --- Tested with latest build from 4.1. We are now presented with parameter name

[jira] [Closed] (CLOUDSTACK-1718) AWS Regions - removeRegion() response returns updateregionresponse.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1718. --- Tested with latest 4.1 build. We get the following response for removeRegio

[jira] [Closed] (CLOUDSTACK-1482) IPV6 - We are not allowed to create a shared IPV6 network with a VLAN which already is associated with a IPV4 network.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1482. --- Closing this issue. I am not able to reproduce this issue on 4.1 branch. m

[jira] [Closed] (CLOUDSTACK-1078) Not able to start System Vms on Rhel 6.3 KVM host

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1078. --- Closing this issue . With latest 4.1 build , I have not seen this issue.

[jira] [Created] (CLOUDSTACK-1794) We are allowed to create Egress rules for Shared networks.

Sangeetha Hariharan created CLOUDSTACK-1794: --- Summary: We are allowed to create Egress rules for Shared networks. Key: CLOUDSTACK-1794 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1794

[jira] [Updated] (CLOUDSTACK-1794) We are allowed to create Egress rules for Shared networks.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1794: Description: We are allowed to create Egress rules for Shared networks

[jira] [Reopened] (CLOUDSTACK-1008) "Egress" tab should not be presented in the UI for Shared Networks

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan reopened CLOUDSTACK-1008: - Pranav, I am able to reproduce this issue on 4.1 branch: screenshow you

[jira] [Created] (CLOUDSTACK-1802) Upgrade 4.0 -> 4.1 - Not able to strat management server becasue of missing /etc/cloudstack/management/tomcat6.conf file.

Sangeetha Hariharan created CLOUDSTACK-1802: --- Summary: Upgrade 4.0 -> 4.1 - Not able to strat management server becasue of missing /etc/cloudstack/management/tomcat6.conf file. Key: CLOUDSTACK-1802 URL:

[jira] [Commented] (CLOUDSTACK-1776) NPE on listSecondaryStorageHostsInAllZones in Upgraded setup from 4.0 to 4.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613103#comment-13613103 ] Sangeetha Hariharan commented on CLOUDSTACK-1776: - I see the same pro

[jira] [Commented] (CLOUDSTACK-1694) Issues to start/access Management Server after upgrade from 4.0 to 4.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613128#comment-13613128 ] Sangeetha Hariharan commented on CLOUDSTACK-1694: - Tested upgrade fro

[jira] [Comment Edited] (CLOUDSTACK-1694) Issues to start/access Management Server after upgrade from 4.0 to 4.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613128#comment-13613128 ] Sangeetha Hariharan edited comment on CLOUDSTACK-1694 at 3/25/13 9:09 PM: -

[jira] [Comment Edited] (CLOUDSTACK-1694) Issues to start/access Management Server after upgrade from 4.0 to 4.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613128#comment-13613128 ] Sangeetha Hariharan edited comment on CLOUDSTACK-1694 at 3/25/13 9:18 PM: -

[jira] [Created] (CLOUDSTACK-1804) Upgrade 4.0 -> 4.1 - DB upgrade fails.

Sangeetha Hariharan created CLOUDSTACK-1804: --- Summary: Upgrade 4.0 -> 4.1 - DB upgrade fails. Key: CLOUDSTACK-1804 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1804 Project: CloudSta

[jira] [Closed] (CLOUDSTACK-1802) Upgrade 4.0 -> 4.1 - Not able to strat management server becasue of missing /etc/cloudstack/management/tomcat6.conf file.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1802. --- Closing this issue as this is being tracked as part of CLOUDSTACK-1694

[jira] [Commented] (CLOUDSTACK-1694) Issues to start/access Management Server after upgrade from 4.0 to 4.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613168#comment-13613168 ] Sangeetha Hariharan commented on CLOUDSTACK-1694: - Following 3 issues

[jira] [Updated] (CLOUDSTACK-1804) Upgrade 4.0 -> 4.1 - DB upgrade fails.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1804: Priority: Blocker (was: Major) > Upgrade 4.0 -> 4.1 - DB upgrade

[jira] [Updated] (CLOUDSTACK-1694) Issues to start/access Management Server after upgrade from 4.0 to 4.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1694: Attachment: Upgrade-4.0-4.1.rar Attaching the the DB dumps before and

[jira] [Updated] (CLOUDSTACK-1804) Upgrade 4.0 -> 4.1 - DB upgrade fails.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1804: Attachment: Upgrade-4.0-4.1.rar Attaching the the DB dumps before and

[jira] [Reopened] (CLOUDSTACK-1776) NPE on listSecondaryStorageHostsInAllZones in Upgraded setup from 4.0 to 4.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan reopened CLOUDSTACK-1776: - Reopening this issue. Will verify and close this issue once CLOUDSTACK-

[jira] [Created] (CLOUDSTACK-1805) com.mysql.jdbc.exceptions.jdbc4.CommunicationsException seen after long time of inactivity resulting in not being able to log in to thr management server.

Sangeetha Hariharan created CLOUDSTACK-1805: --- Summary: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException seen after long time of inactivity resulting in not being able to log in to thr management server. Key: CLOU

[jira] [Commented] (CLOUDSTACK-1805) com.mysql.jdbc.exceptions.jdbc4.CommunicationsException seen after long time of inactivity resulting in not being able to log in to thr management server.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613327#comment-13613327 ] Sangeetha Hariharan commented on CLOUDSTACK-1805: - apilogs showing no

[jira] [Updated] (CLOUDSTACK-1805) com.mysql.jdbc.exceptions.jdbc4.CommunicationsException seen after long time of inactivity resulting in not being able to log in to thr management server.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1805: Attachment: DBError.rar > com.mysql.jdbc.exceptions.jdbc4.Communic

[jira] [Updated] (CLOUDSTACK-1805) com.mysql.jdbc.exceptions.jdbc4.CommunicationsException seen after long time of inactivity resulting in not being able to log in to thr management server.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1805: Fix Version/s: 4.2.0 This issue is seen on the management server from

[jira] [Commented] (CLOUDSTACK-1804) Upgrade 4.0 -> 4.1 - DB upgrade fails.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614324#comment-13614324 ] Sangeetha Hariharan commented on CLOUDSTACK-1804: - Prachi/Jayapal, W

[jira] [Created] (CLOUDSTACK-1811) Upgrade 4.0->4.1 - When upgrade scripts fail , component loading continues and management server starts.

Sangeetha Hariharan created CLOUDSTACK-1811: --- Summary: Upgrade 4.0->4.1 - When upgrade scripts fail , component loading continues and management server starts. Key: CLOUDSTACK-1811 URL: https://issues.

[jira] [Updated] (CLOUDSTACK-1811) Upgrade 4.0->4.1 - When upgrade scripts fail , component loading continues and management server starts.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1811: Priority: Critical (was: Major) > Upgrade 4.0->4.1 - When upgrade

[jira] [Commented] (CLOUDSTACK-1804) Upgrade 4.0 -> 4.1 - DB upgrade fails.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614368#comment-13614368 ] Sangeetha Hariharan commented on CLOUDSTACK-1804: - >>This is another

[jira] [Updated] (CLOUDSTACK-1811) Upgrade 4.0->4.1 - When upgrade scripts fail , component loading continues and management server starts.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1811: Attachment: management-server.log.2013-03-25 > Upgrade 4.0->4.1 -

[jira] [Reopened] (CLOUDSTACK-1792) AWS Regions - RuntimeException while executing listAccounts() , when the encryption keys are set to different values between regions.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan reopened CLOUDSTACK-1792: - Reopening this issue to get the following confirmation: FS is updated f

[jira] [Created] (CLOUDSTACK-1819) Issues seen when trying to move a zone from 1 region to another.

Sangeetha Hariharan created CLOUDSTACK-1819: --- Summary: Issues seen when trying to move a zone from 1 region to another. Key: CLOUDSTACK-1819 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1819

[jira] [Updated] (CLOUDSTACK-1819) AWS Regions - Issues seen when trying to move a zone from 1 region to another.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1819: Summary: AWS Regions - Issues seen when trying to move a zone from 1 re

[jira] [Updated] (CLOUDSTACK-1819) AWS Regions - Issues seen when trying to move a zone from 1 region to another.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1819: Attachment: Region.rar Management server logs from both regions.

[jira] [Updated] (CLOUDSTACK-1819) AWS Regions - Issues seen when trying to move a zone from 1 region to another.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1819: Description: Issues seen when trying to move a zone from 1 region to a

[jira] [Reopened] (CLOUDSTACK-1811) Upgrade 4.0->4.1 - When upgrade scripts fail , component loading continues and management server starts.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan reopened CLOUDSTACK-1811: - Kelven , can you mark this bug as "Fixed" once the patch has been pushed

[jira] [Reopened] (CLOUDSTACK-1664) Action Events are not logged due to spring changes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan reopened CLOUDSTACK-1664: - Kelven , can you mark this bug as "Fixed" once the patch has been pushed

[jira] [Reopened] (CLOUDSTACK-1776) NPE on listSecondaryStorageHostsInAllZones in Upgraded setup from 4.0 to 4.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan reopened CLOUDSTACK-1776: - Kelven , can you mark this bug as "Fixed" once the patch has been pushed

[jira] [Commented] (CLOUDSTACK-1804) Upgrade 4.0 -> 4.1 - DB upgrade fails.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615383#comment-13615383 ] Sangeetha Hariharan commented on CLOUDSTACK-1804: - Issues 1,2,3 outli

[jira] [Updated] (CLOUDSTACK-1673) AWS Regions - Events - User disable / Domain Delete event does not include the UUID of the user/domain that was disabled.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1673: Description: AWS Regions - Events - User disable / Domain Delete event

[jira] [Commented] (CLOUDSTACK-1673) AWS Regions - Events - User disable / Domain Delete event does not include the UUID of the user/domain that was disabled.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615480#comment-13615480 ] Sangeetha Hariharan commented on CLOUDSTACK-1673: - Updated the bug to

[jira] [Updated] (CLOUDSTACK-1819) AWS Regions - Issues seen when trying to move a zone from 1 region to another.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1819: Description: Issues seen when trying to move a zone from 1 region to a

[jira] [Commented] (CLOUDSTACK-1664) Action Events are not logged due to spring changes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615685#comment-13615685 ] Sangeetha Hariharan commented on CLOUDSTACK-1664: - Tested with latest

[jira] [Reopened] (CLOUDSTACK-1664) Action Events are not logged due to spring changes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan reopened CLOUDSTACK-1664: - Tested with latest build form 4.1: I do see events for Create User bein

[jira] [Commented] (CLOUDSTACK-1664) Action Events are not logged due to spring changes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615770#comment-13615770 ] Sangeetha Hariharan commented on CLOUDSTACK-1664: - Thanks Kelven. An

[jira] [Closed] (CLOUDSTACK-1792) AWS Regions - RuntimeException while executing listAccounts() , when the encryption keys are set to different values between regions.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1792. --- Closing this issue. > AWS Regions - RuntimeException while

[jira] [Created] (CLOUDSTACK-1834) Events are not generated for registerUserKeys(), Enabling account and Editing account.

Sangeetha Hariharan created CLOUDSTACK-1834: --- Summary: Events are not generated for registerUserKeys(), Enabling account and Editing account. Key: CLOUDSTACK-1834 URL: https://issues.apache.org/jira/brow

[jira] [Commented] (CLOUDSTACK-1834) Events are not generated for registerUserKeys(), Enabling account and Editing account.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616435#comment-13616435 ] Sangeetha Hariharan commented on CLOUDSTACK-1834: - This bug is logged

[jira] [Commented] (CLOUDSTACK-1664) Action Events are not logged due to spring changes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616440#comment-13616440 ] Sangeetha Hariharan commented on CLOUDSTACK-1664: - Logged CLOUDSTACK-

[jira] [Closed] (CLOUDSTACK-1664) Action Events are not logged due to spring changes

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1664. --- Resolution: Fixed Closing this issue . Tarcking the remaining issues in

[jira] [Created] (CLOUDSTACK-1837) Additonal Steps ( Restart of all system Vms , copy vhd-utils) to be included in the upgrade procedure from 4.0 -> 4.1

Sangeetha Hariharan created CLOUDSTACK-1837: --- Summary: Additonal Steps ( Restart of all system Vms , copy vhd-utils) to be included in the upgrade procedure from 4.0 -> 4.1 Key: CLOUDSTACK-1837 URL: http

[jira] [Created] (CLOUDSTACK-1839) Upgrade 4.0 -> 4.1 - Upgraded DB has lot more keys and indexes for many tables compare to the fresh installed 4.1 DB.

Sangeetha Hariharan created CLOUDSTACK-1839: --- Summary: Upgrade 4.0 -> 4.1 - Upgraded DB has lot more keys and indexes for many tables compare to the fresh installed 4.1 DB. Key: CLOUDSTACK-1839 URL: http

[jira] [Updated] (CLOUDSTACK-1839) Upgrade 4.0 -> 4.1 - Upgraded DB has lot more keys and indexes for many tables compare to the fresh installed 4.1 DB.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1839: Attachment: upgrade-db-dumps.rar Attaching the Db dumps before and aft

[jira] [Created] (CLOUDSTACK-1840) Add Instance Wizard - When there are multiple zones , selecting a zone which has no templates yet results in templates from other zone being shown.

Sangeetha Hariharan created CLOUDSTACK-1840: --- Summary: Add Instance Wizard - When there are multiple zones , selecting a zone which has no templates yet results in templates from other zone being shown. Key: CLOUDSTACK

[jira] [Assigned] (CLOUDSTACK-1839) Upgrade 4.0 -> 4.1 - Upgraded DB has lot more keys and indexes for many tables compare to the fresh installed 4.1 DB.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan reassigned CLOUDSTACK-1839: --- Assignee: Rohit Yadav > Upgrade 4.0 -> 4.1 - Upgraded DB has

[jira] [Commented] (CLOUDSTACK-1839) Upgrade 4.0 -> 4.1 - Upgraded DB has lot more keys and indexes for many tables compare to the fresh installed 4.1 DB.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616863#comment-13616863 ] Sangeetha Hariharan commented on CLOUDSTACK-1839: - Seems like all the

[jira] [Created] (CLOUDSTACK-1844) Upgrade 4.0 -> 4.1 - KVM host agent.properties is not restored as part of upgrading the binaries from 4.0 to 4.1.

Sangeetha Hariharan created CLOUDSTACK-1844: --- Summary: Upgrade 4.0 -> 4.1 - KVM host agent.properties is not restored as part of upgrading the binaries from 4.0 to 4.1. Key: CLOUDSTACK-1844 URL: https://

[jira] [Commented] (CLOUDSTACK-1844) Upgrade 4.0 -> 4.1 - KVM host agent.properties is not restored as part of upgrading the binaries from 4.0 to 4.1.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616985#comment-13616985 ] Sangeetha Hariharan commented on CLOUDSTACK-1844: - Created a repo for

[jira] [Updated] (CLOUDSTACK-1844) Upgrade 4.0 -> 4.1 - KVM host agent.properties is not restored as part of upgrading the binaries from 4.0 to 4.1.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1844: Attachment: agent.properties.txt Marcus , I did the following: Crea

[jira] [Updated] (CLOUDSTACK-1844) Upgrade 4.0 -> 4.1 - KVM host agent.properties is not restored as part of upgrading the binaries from 4.0 to 4.1.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1844: Attachment: agent.properties.txt > Upgrade 4.0 -> 4.1 - KVM host a

[jira] [Closed] (CLOUDSTACK-1804) Upgrade 4.0 -> 4.1 - DB upgrade fails.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1804. --- Closing issue. DB Upgrade from 4.0->4.1 succeeds when using the lastet buil

[jira] [Commented] (CLOUDSTACK-1805) com.mysql.jdbc.exceptions.jdbc4.CommunicationsException seen after long time of inactivity resulting in not being able to log in to thr management server.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617693#comment-13617693 ] Sangeetha Hariharan commented on CLOUDSTACK-1805: - I have set the fol

[jira] [Updated] (CLOUDSTACK-1837) Additonal Steps ( Restart of all system Vms , copy vhd-utils) to be included in the upgrade procedure from 4.0 -> 4.1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1837: Description: Additonal Steps ( Restart of all system Vms , copy vhd-ut

[jira] [Created] (CLOUDSTACK-1856) Upgrade 4.0 -> 4.1 - Fresh install of 4.1 has 3 parameters missing in db.properties compared to an upgrdaed 4.0 set up.

Sangeetha Hariharan created CLOUDSTACK-1856: --- Summary: Upgrade 4.0 -> 4.1 - Fresh install of 4.1 has 3 parameters missing in db.properties compared to an upgrdaed 4.0 set up. Key: CLOUDSTACK-1856 URL:

[jira] [Resolved] (CLOUDSTACK-1248) QA - IPV6 Support in Shared Network

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan resolved CLOUDSTACK-1248. - Resolution: Fixed Closing this issue. Test plans have been posted fo

[jira] [Closed] (CLOUDSTACK-1248) QA - IPV6 Support in Shared Network

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1248. --- Closing as per my previous comments. > QA - IPV6 Support in

[jira] [Created] (CLOUDSTACK-1859) Automate test cases for IPV6 Support on Shared Network

Sangeetha Hariharan created CLOUDSTACK-1859: --- Summary: Automate test cases for IPV6 Support on Shared Network Key: CLOUDSTACK-1859 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1859 P

[jira] [Created] (CLOUDSTACK-1860) Automate test cases for AWS Style Regions.

Sangeetha Hariharan created CLOUDSTACK-1860: --- Summary: Automate test cases for AWS Style Regions. Key: CLOUDSTACK-1860 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1860 Project: Clou

[jira] [Commented] (CLOUDSTACK-843) [QA] Test VM Snapshots

[ https://issues.apache.org/jira/browse/CLOUDSTACK-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618517#comment-13618517 ] Sangeetha Hariharan commented on CLOUDSTACK-843: Test cases for this f

[jira] [Created] (CLOUDSTACK-1861) Automate test cases for VM Snapshot features

Sangeetha Hariharan created CLOUDSTACK-1861: --- Summary: Automate test cases for VM Snapshot features Key: CLOUDSTACK-1861 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1861 Project: Cl

[jira] [Closed] (CLOUDSTACK-1805) com.mysql.jdbc.exceptions.jdbc4.CommunicationsException seen after long time of inactivity resulting in not being able to log in to thr management server.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan closed CLOUDSTACK-1805. --- Closing this issue: I did not see this issue happen in 3 out of the 4 set u

[jira] [Created] (CLOUDSTACK-1874) AWS Regions - Account table in cloud_usage DB has region_id.

Sangeetha Hariharan created CLOUDSTACK-1874: --- Summary: AWS Regions - Account table in cloud_usage DB has region_id. Key: CLOUDSTACK-1874 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1874

  1   2   3   4   5   6   7   8   9   >