[jira] [Assigned] (CLOUDSTACK-5989) Trying to start a vm while 'vm snapshot' is in progress results in inconsistency

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-5989: --- Assignee: Koushik Das Trying to start a vm while 'vm snapshot' is in progress

[jira] [Created] (CLOUDSTACK-5989) Trying to start a vm while 'vm snapshot' is in progress results in inconsistency

Koushik Das created CLOUDSTACK-5989: --- Summary: Trying to start a vm while 'vm snapshot' is in progress results in inconsistency Key: CLOUDSTACK-5989 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5989

[jira] [Commented] (CLOUDSTACK-5989) Trying to start a vm while 'vm snapshot' is in progress results in inconsistency

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886431#comment-13886431 ] Koushik Das commented on CLOUDSTACK-5989: - Workaround: Don't perform

[jira] [Created] (CLOUDSTACK-5993) Cloud agent fails to start on 32-bit system vms (cpvm and ssvm) created with 4GB RAM offering

Koushik Das created CLOUDSTACK-5993: --- Summary: Cloud agent fails to start on 32-bit system vms (cpvm and ssvm) created with 4GB RAM offering Key: CLOUDSTACK-5993 URL:

[jira] [Assigned] (CLOUDSTACK-5993) Cloud agent fails to start on 32-bit system vms (cpvm and ssvm) created with 4GB RAM offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-5993: --- Assignee: Koushik Das Cloud agent fails to start on 32-bit system vms (cpvm

[jira] [Resolved] (CLOUDSTACK-5993) Cloud agent fails to start on 32-bit system vms (cpvm and ssvm) created with 4GB RAM offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-5993. - Resolution: Fixed Cloud agent fails to start on 32-bit system vms (cpvm and ssvm)

[jira] [Resolved] (CLOUDSTACK-5989) Trying to start a vm while 'vm snapshot' is in progress results in inconsistency

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-5989. - Resolution: Fixed Trying to start a vm while 'vm snapshot' is in progress results

[jira] [Updated] (CLOUDSTACK-5989) Trying to start a vm while 'vm snapshot' is in progress results in inconsistency

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-5989: Priority: Critical (was: Major) Trying to start a vm while 'vm snapshot' is in

[jira] [Updated] (CLOUDSTACK-5993) Cloud agent fails to start on 32-bit system vms (cpvm and ssvm) created with 4GB RAM offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-5993: Priority: Critical (was: Major) Cloud agent fails to start on 32-bit system vms

[jira] [Resolved] (CLOUDSTACK-5949) Remove unused field vnc_password from user_vm_view

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-5949. - Resolution: Fixed Remove unused field vnc_password from user_vm_view

[jira] [Commented] (CLOUDSTACK-5901) [Automation] Unable to start a VM due to concurrent operation

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13876206#comment-13876206 ] Koushik Das commented on CLOUDSTACK-5901: - VM deployment is failing as CS

[jira] [Closed] (CLOUDSTACK-2169) [DOC] Reset ASA 1000v appliance to factory setting as part of guest network cleanup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das closed CLOUDSTACK-2169. --- [DOC] Reset ASA 1000v appliance to factory setting as part of guest network cleanup

[jira] [Closed] (CLOUDSTACK-4856) Optimize on the # of control commands sent by MS to HV host

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das closed CLOUDSTACK-4856. --- Optimize on the # of control commands sent by MS to HV host

[jira] [Resolved] (CLOUDSTACK-5002) unable to destroy vm ;VM destroy failed in Stop i-2-59-VM Command due to You gave an invalid object reference. The object may have recently been deleted.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-5002. - Resolution: Fixed unable to destroy vm ;VM destroy failed in Stop i-2-59-VM

[jira] [Assigned] (CLOUDSTACK-5706) Multiple NPEs when host is put in maintenance after upgrading from 4.2.1 to 4.3

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-5706: --- Assignee: Koushik Das Multiple NPEs when host is put in maintenance after

[jira] [Assigned] (CLOUDSTACK-5792) All the VMs are shown as running even after the host is put in maintenance.NPE in logs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-5792: --- Assignee: Koushik Das All the VMs are shown as running even after the host is

[jira] [Resolved] (CLOUDSTACK-5706) Multiple NPEs when host is put in maintenance after upgrading from 4.2.1 to 4.3

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-5706. - Resolution: Fixed This is fixed as part of commit

[jira] [Resolved] (CLOUDSTACK-5792) All the VMs are shown as running even after the host is put in maintenance.NPE in logs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-5792. - Resolution: Fixed This should be resolved as part of commit

[jira] [Assigned] (CLOUDSTACK-5714) [upgrade]getting blank console;failed to destroy CPVM in upgraded setup ;Unable to send due to java.lang.ArrayIndexOutOfBoundsException: 0

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-5714: --- Assignee: Koushik Das [upgrade]getting blank console;failed to destroy CPVM in

[jira] [Resolved] (CLOUDSTACK-5714) [upgrade]getting blank console;failed to destroy CPVM in upgraded setup ;Unable to send due to java.lang.ArrayIndexOutOfBoundsException: 0

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-5714. - Resolution: Fixed This is fixed as part of commit

[jira] [Commented] (CLOUDSTACK-5712) [Automation] Failed to stop vm during vm destroy command, observed the error Unable to update VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13860132#comment-13860132 ] Koushik Das commented on CLOUDSTACK-5712: - What is the value for config

[jira] [Commented] (CLOUDSTACK-5712) [Automation] Failed to stop vm during vm destroy command, observed the error Unable to update VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13860133#comment-13860133 ] Koushik Das commented on CLOUDSTACK-5712: - Reducing the priority to

[jira] [Updated] (CLOUDSTACK-5712) [Automation] Failed to stop vm during vm destroy command, observed the error Unable to update VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-5712: Priority: Critical (was: Blocker) [Automation] Failed to stop vm during vm destroy

[jira] [Assigned] (CLOUDSTACK-5712) [Automation] Failed to stop vm during vm destroy command, observed the error Unable to update VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-5712: --- Assignee: Koushik Das [Automation] Failed to stop vm during vm destroy

[jira] [Assigned] (CLOUDSTACK-5002) unable to destroy vm ;VM destroy failed in Stop i-2-59-VM Command due to You gave an invalid object reference. The object may have recently been deleted.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-5002: --- Assignee: Koushik Das unable to destroy vm ;VM destroy failed in Stop

[jira] [Commented] (CLOUDSTACK-5712) [Automation] Failed to stop vm during vm destroy command, observed the error Unable to update VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13860136#comment-13860136 ] Koushik Das commented on CLOUDSTACK-5712: - Found another issue

[jira] [Resolved] (CLOUDSTACK-5712) [Automation] Failed to stop vm during vm destroy command, observed the error Unable to update VM

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-5712. - Resolution: Duplicate [Automation] Failed to stop vm during vm destroy command,

[jira] [Updated] (CLOUDSTACK-4944) Command sequence logic in agent code may lead to errors in clustered MS setup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-4944: Fix Version/s: (was: 4.3.0) Future Command sequence logic in

[jira] [Updated] (CLOUDSTACK-2540) Cisco VNMC - Cleanup vservice node that gets created on Nexus switch during network cleanup

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-2540: Fix Version/s: (was: 4.3.0) Future Cisco VNMC - Cleanup

[jira] [Resolved] (CLOUDSTACK-2414) NPE while deleting Cisco VNMC provider

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-2414. - Resolution: Cannot Reproduce Not able to repro this issue in 4.3. NPE while

[jira] [Resolved] (CLOUDSTACK-2560) Adding duplicate ASA device entity failure should be handled with API

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-2560. - Resolution: Fixed Adding duplicate ASA device entity failure should be handled

[jira] [Resolved] (CLOUDSTACK-5565) custom compute offering is not honoring Global parameter custom.diskoffering.size.max/min

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-5565. - Resolution: Invalid custom compute offering is not honoring Global parameter

[jira] [Commented] (CLOUDSTACK-5565) custom compute offering is not honoring Global parameter custom.diskoffering.size.max/min

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13856237#comment-13856237 ] Koushik Das commented on CLOUDSTACK-5565: - Memory and

[jira] [Assigned] (CLOUDSTACK-5565) custom compute offering is not honoring Global parameter custom.diskoffering.size.max/min

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-5565: --- Assignee: Koushik Das custom compute offering is not honoring Global parameter

[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-tabpanelfocusedCommentId=13856286#comment-13856286 ] Koushik Das commented on CLOUDSTACK-5600: - Simultaneous HA jobs for CPVM

[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

[jira] [Resolved] (CLOUDSTACK-5545) Xenserver - After HA , ssvm fails to start on the new host . Also not able to deploy new Vms in this host.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-5545. - Resolution: Fixed Xenserver - After HA , ssvm fails to start on the new host .

[jira] [Commented] (CLOUDSTACK-5545) Xenserver - After HA , ssvm fails to start on the new host . Also not able to deploy new Vms in this host.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13855609#comment-13855609 ] Koushik Das commented on CLOUDSTACK-5545: - HA getting scheduled twice is

[jira] [Commented] (CLOUDSTACK-5545) Xenserver - After HA , ssvm fails to start on the new host . Also not able to deploy new Vms in this host.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13852865#comment-13852865 ] Koushik Das commented on CLOUDSTACK-5545: - There are 2 sets of HA getting

[jira] [Commented] (CLOUDSTACK-5582) kvm - HA is not triggered when host is powered down since the host gets into Disconnected state.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13853645#comment-13853645 ] Koushik Das commented on CLOUDSTACK-5582: - HA gets triggered only when host

[jira] [Resolved] (CLOUDSTACK-5458) cpu speed is not getting updated in vm_instance table after service offeirngs change

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-5458. - Resolution: Fixed cpu speed is not getting updated in vm_instance table after

[jira] [Commented] (CLOUDSTACK-5458) cpu speed is not getting updated in vm_instance table after service offeirngs change

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851545#comment-13851545 ] Koushik Das commented on CLOUDSTACK-5458: - Refer to the dev list discussion

[jira] [Updated] (CLOUDSTACK-5458) cpu speed is not getting updated in vm_instance table after service offeirngs change

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-5458: Fix Version/s: 4.3.0 cpu speed is not getting updated in vm_instance table after

[jira] [Commented] (CLOUDSTACK-2428) HA - When the master host is disconnected , the host status contines to remain in Up state because of com.cloud.utils.exception.CloudRuntimeException: Unable to

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13851675#comment-13851675 ] Koushik Das commented on CLOUDSTACK-2428: - I looked at the logs and see that

[jira] [Assigned] (CLOUDSTACK-5545) Xenserver - After HA , ssvm fails to start on the new host . Also not able to deploy new Vms in this host.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-5545: --- Assignee: Koushik Das Xenserver - After HA , ssvm fails to start on the new

[jira] [Assigned] (CLOUDSTACK-5470) Xenserver - Host continues to remain in Up state when powere off due to exception - Unable to reset master of slave

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-5470: --- Assignee: Koushik Das Xenserver - Host continues to remain in Up state when

[jira] [Resolved] (CLOUDSTACK-5470) Xenserver - Host continues to remain in Up state when powere off due to exception - Unable to reset master of slave

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-5470. - Resolution: Cannot Reproduce Snapshots don't have any impact on the status of host.

[jira] [Commented] (CLOUDSTACK-5520) Script errors seen when trying to seed the 64 bit Xenserver templates.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13850323#comment-13850323 ] Koushik Das commented on CLOUDSTACK-5520: - Looks like a duplicate of

[jira] [Assigned] (CLOUDSTACK-5458) cpu speed is not getting updated in vm_instance table after service offeirngs change

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-5458: --- Assignee: Koushik Das cpu speed is not getting updated in vm_instance table

[jira] [Commented] (CLOUDSTACK-2428) HA - When the master host is disconnected , the host status contines to remain in Up state because of com.cloud.utils.exception.CloudRuntimeException: Unable to

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13849010#comment-13849010 ] Koushik Das commented on CLOUDSTACK-2428: - Sangeetha, I am not abe to repro

[jira] [Assigned] (CLOUDSTACK-2428) HA - When the master host is disconnected , the host status contines to remain in Up state because of com.cloud.utils.exception.CloudRuntimeException: Unable to r

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-2428: --- Assignee: Sangeetha Hariharan (was: Koushik Das) HA - When the master host is

[jira] [Updated] (CLOUDSTACK-2414) NPE while deleting Cisco VNMC provider

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-2414: Priority: Minor (was: Major) NPE while deleting Cisco VNMC provider

[jira] [Commented] (CLOUDSTACK-5385) Management server not able start when there ~15 snapshot policies.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845237#comment-13845237 ] Koushik Das commented on CLOUDSTACK-5385: - Did the following steps but wasn't

[jira] [Resolved] (CLOUDSTACK-5385) Management server not able start when there ~15 snapshot policies.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-5385. - Resolution: Incomplete Management server not able start when there ~15 snapshot

[jira] [Commented] (CLOUDSTACK-5385) Management server not able start when there ~15 snapshot policies.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845248#comment-13845248 ] Koushik Das commented on CLOUDSTACK-5385: - Log snippet indicating 15 snapshot

[jira] [Assigned] (CLOUDSTACK-5460) Getting error as Template 5 has not been completely downloaded to zone 1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-5460: --- Assignee: Koushik Das Getting error as Template 5 has not been completely

[jira] [Resolved] (CLOUDSTACK-5460) Getting error as Template 5 has not been completely downloaded to zone 1

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-5460. - Resolution: Not A Problem The template should be in ready state (Raedy = Yes) for

[jira] [Commented] (CLOUDSTACK-2428) HA - When the master host is disconnected , the host status contines to remain in Up state because of com.cloud.utils.exception.CloudRuntimeException: Unable to

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13844201#comment-13844201 ] Koushik Das commented on CLOUDSTACK-2428: - Tried on master with XS 6.2.

[jira] [Resolved] (CLOUDSTACK-2428) HA - When the master host is disconnected , the host status contines to remain in Up state because of com.cloud.utils.exception.CloudRuntimeException: Unable to r

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-2428. - Resolution: Cannot Reproduce HA - When the master host is disconnected , the host

[jira] [Commented] (CLOUDSTACK-2428) HA - When the master host is disconnected , the host status contines to remain in Up state because of com.cloud.utils.exception.CloudRuntimeException: Unable to

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845099#comment-13845099 ] Koushik Das commented on CLOUDSTACK-2428: - Tried on 4.3 with XS 6.2. Master

[jira] [Resolved] (CLOUDSTACK-2141) During HA process , dead lock is detected - Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLTransactionRollbackException: Deadlock found when trying to get lock; t

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-2141. - Resolution: Cannot Reproduce Tried on 4.3. During HA process , dead lock is

[jira] [Commented] (CLOUDSTACK-2428) HA - When the master host is disconnected , the host status contines to remain in Up state because of com.cloud.utils.exception.CloudRuntimeException: Unable to

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845115#comment-13845115 ] Koushik Das commented on CLOUDSTACK-2428: - I think having the host shutdown

[jira] [Resolved] (CLOUDSTACK-4371) [Performance Testing] Basic zone with 20K Hosts, management server restart leaves the hosts in disconnected state for very long time

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-4371. - Resolution: Cannot Reproduce [Performance Testing] Basic zone with 20K Hosts,

[jira] [Commented] (CLOUDSTACK-4371) [Performance Testing] Basic zone with 20K Hosts, management server restart leaves the hosts in disconnected state for very long time

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13845118#comment-13845118 ] Koushik Das commented on CLOUDSTACK-4371: - Sowmya, Please check if the

[jira] [Resolved] (CLOUDSTACK-4697) Not able to delete Primary storage when there are no hosts in the cluster.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-4697. - Resolution: Duplicate CLOUDSTACK-4402 Not able to delete Primary storage when

[jira] [Created] (CLOUDSTACK-5247) SSVM/CPVM needs to be handle the scenario of agent going to 'Disconnected' state

Koushik Das created CLOUDSTACK-5247: --- Summary: SSVM/CPVM needs to be handle the scenario of agent going to 'Disconnected' state Key: CLOUDSTACK-5247 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5247

[jira] [Updated] (CLOUDSTACK-5247) SSVM/CPVM needs to be handle the scenario of agent going to 'Disconnected' state

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-5247: Description: SSVM/CPVM needs to be handle the scenario of agent going to

[jira] [Assigned] (CLOUDSTACK-5247) SSVM/CPVM needs to be handle the scenario of agent going to 'Disconnected' state

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-5247: --- Assignee: Koushik Das SSVM/CPVM needs to be handle the scenario of agent going

[jira] [Assigned] (CLOUDSTACK-5203) Leverage native XS HA capabilities for user VMs

[ https://issues.apache.org/jira/browse/CLOUDSTACK-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-5203: --- Assignee: Koushik Das Leverage native XS HA capabilities for user VMs

[jira] [Created] (CLOUDSTACK-5203) Leverage native XS HA capabilities for user VMs

Koushik Das created CLOUDSTACK-5203: --- Summary: Leverage native XS HA capabilities for user VMs Key: CLOUDSTACK-5203 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5203 Project: CloudStack

[jira] [Resolved] (CLOUDSTACK-4855) Throttle based on the # of outstanding requests to the directly managed HV host (direct agents)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-4855. - Resolution: Fixed Throttle based on the # of outstanding requests to the directly

[jira] [Created] (CLOUDSTACK-4964) Cisco VNMC: Nexus password gets logged in MS logs during guest n/w implementation with VNMC provider

Koushik Das created CLOUDSTACK-4964: --- Summary: Cisco VNMC: Nexus password gets logged in MS logs during guest n/w implementation with VNMC provider Key: CLOUDSTACK-4964 URL:

[jira] [Resolved] (CLOUDSTACK-4964) Cisco VNMC: Nexus password gets logged in MS logs during guest n/w implementation with VNMC provider

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-4964. - Resolution: Fixed Cisco VNMC: Nexus password gets logged in MS logs during guest

[jira] [Resolved] (CLOUDSTACK-3808) Attach volume should work when root is at zone level primary store and data at cluster level or host level store

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-3808. - Resolution: Fixed Resolving as it is working fine in Vmware. For KVM, the issue is

[jira] [Commented] (CLOUDSTACK-4936) System VM's Agent goes to disconnected state but VM state still up when they are stopped manually.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13803979#comment-13803979 ] Koushik Das commented on CLOUDSTACK-4936: - Yes. Issue is same as

[jira] [Resolved] (CLOUDSTACK-4936) System VM's Agent goes to disconnected state but VM state still up when they are stopped manually.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-4936. - Resolution: Cannot Reproduce Fixed in latest build by fix for CLOUDSTACK-4937

[jira] [Created] (CLOUDSTACK-4944) Command sequence logic in agent code may lead to errors in clustered MS setup

Koushik Das created CLOUDSTACK-4944: --- Summary: Command sequence logic in agent code may lead to errors in clustered MS setup Key: CLOUDSTACK-4944 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4944

[jira] [Commented] (CLOUDSTACK-4948) DeploymentPlanner: Logic to check if cluster can be avoided, needs to consider if VM is using local storage and/or shared storage

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13804493#comment-13804493 ] Koushik Das commented on CLOUDSTACK-4948: - This should be fixed by commit

[jira] [Commented] (CLOUDSTACK-3808) Attach volume should work when root is at zone level primary store and data at cluster level or host level store

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13802691#comment-13802691 ] Koushik Das commented on CLOUDSTACK-3808: - From the error looks like a

[jira] [Resolved] (CLOUDSTACK-4681) data disk with local disk offering are geting created on shared storage .

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-4681. - Resolution: Fixed data disk with local disk offering are geting created on

[jira] [Commented] (CLOUDSTACK-4551) Migrating the data volume from NFS to local storage ,underlying disk offering is not changed.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13797647#comment-13797647 ] Koushik Das commented on CLOUDSTACK-4551: - This shouldn't be allowed. Even

[jira] [Resolved] (CLOUDSTACK-4551) Migrating the data volume from NFS to local storage ,underlying disk offering is not changed.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-4551. - Resolution: Fixed Migrating the data volume from NFS to local storage ,underlying

[jira] [Assigned] (CLOUDSTACK-3808) Attach volume should work when root is at zone level primary store and data at cluster level or host level store

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-3808: --- Assignee: Koushik Das (was: Devdeep Singh) Attach volume should work when

[jira] [Commented] (CLOUDSTACK-3808) Attach volume should work when root is at zone level primary store and data at cluster level or host level store

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796688#comment-13796688 ] Koushik Das commented on CLOUDSTACK-3808: - If the VM can access the data disk

[jira] [Resolved] (CLOUDSTACK-3808) Attach volume should work when root is at zone level primary store and data at cluster level or host level store

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-3808. - Resolution: Fixed Attach volume should work when root is at zone level primary

[jira] [Commented] (CLOUDSTACK-3808) Attach volume should work when root is at zone level primary store and data at cluster level or host level store

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796690#comment-13796690 ] Koushik Das commented on CLOUDSTACK-3808: - Fixed as part of commit

[jira] [Commented] (CLOUDSTACK-4681) data disk with local disk offering are geting created on shared storage .

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13796703#comment-13796703 ] Koushik Das commented on CLOUDSTACK-4681: - I again tried it, and was able to

[jira] [Created] (CLOUDSTACK-4855) Throttle based on the # of outstanding requests to the directly managed HV host (direct agents)

Koushik Das created CLOUDSTACK-4855: --- Summary: Throttle based on the # of outstanding requests to the directly managed HV host (direct agents) Key: CLOUDSTACK-4855 URL:

[jira] [Assigned] (CLOUDSTACK-4855) Throttle based on the # of outstanding requests to the directly managed HV host (direct agents)

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-4855: --- Assignee: Koushik Das Throttle based on the # of outstanding requests to the

[jira] [Created] (CLOUDSTACK-4856) Optimize on the # of control commands sent by MS to HV host

Koushik Das created CLOUDSTACK-4856: --- Summary: Optimize on the # of control commands sent by MS to HV host Key: CLOUDSTACK-4856 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4856 Project:

[jira] [Assigned] (CLOUDSTACK-3367) When one primary storage fails, all XenServer hosts get rebooted, killing all VMs, even those not on this primary storage.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-3367: --- Assignee: Koushik Das When one primary storage fails, all XenServer hosts get

[jira] [Resolved] (CLOUDSTACK-2428) HA - When the master host is disconnected , the host status contines to remain in Up state because of com.cloud.utils.exception.CloudRuntimeException: Unable to r

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-2428. - Resolution: Cannot Reproduce Please check if this only happens with XS 6.1.

[jira] [Commented] (CLOUDSTACK-2428) HA - When the master host is disconnected , the host status contines to remain in Up state because of com.cloud.utils.exception.CloudRuntimeException: Unable to

[ https://issues.apache.org/jira/browse/CLOUDSTACK-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770682#comment-13770682 ] Koushik Das commented on CLOUDSTACK-2428: - I tried to repro the issue on 2

[jira] [Assigned] (CLOUDSTACK-4699) Xenserver 6.1 - When a host gets added to an existing cluster with hosts , Add host succeeds but is in Alert state. Transitions to Connecting and Up state aft

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reassigned CLOUDSTACK-4699: --- Assignee: Koushik Das Xenserver 6.1 - When a host gets added to an

[jira] [Resolved] (CLOUDSTACK-4699) Xenserver 6.1 - When a host gets added to an existing cluster with hosts , Add host succeeds but is in Alert state. Transitions to Connecting and Up state aft

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das resolved CLOUDSTACK-4699. - Resolution: Not A Problem This is by design. For 1st host in a cluster it is owned

[jira] [Commented] (CLOUDSTACK-4681) data disk with local disk offering are geting created on shared storage .

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13769258#comment-13769258 ] Koushik Das commented on CLOUDSTACK-4681: - Tried this on a XS setup and not

[jira] [Commented] (CLOUDSTACK-4682) VMs are getting deployed with shared service offering and local compute offering

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13769268#comment-13769268 ] Koushik Das commented on CLOUDSTACK-4682: - I verified this on a XS setup.

[jira] [Commented] (CLOUDSTACK-3367) When one primary storage fails, all XenServer hosts get rebooted, killing all VMs, even those not on this primary storage.

[ https://issues.apache.org/jira/browse/CLOUDSTACK-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13766393#comment-13766393 ] Koushik Das commented on CLOUDSTACK-3367: - In XS 6.2 I simulated SR failure

[jira] [Reopened] (CLOUDSTACK-4617) [UI] Xenserver 6.1 - Add host succeeds but gets into Alert state due to Unable to create local link network. It remains in Alert state for a while and then gets

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das reopened CLOUDSTACK-4617: - The UI aspect also needs to be fixed. The wizard should check if at least one host in

[jira] [Updated] (CLOUDSTACK-4636) In a scaled up setup all Vm's in a cluster were stopped and/or started after management server restart

[ https://issues.apache.org/jira/browse/CLOUDSTACK-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-4636: Summary: In a scaled up setup all Vm's in a cluster were stopped and/or started after

<    1   2   3   4   5   6   7   >