[jira] [Updated] (CLOUDSTACK-7857) CitrixResourceBase wrongly calculates total memory on hosts with a lot of memory and large Dom0
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daan Hoogland updated CLOUDSTACK-7857:
--
Priority: Critical (was: Blocker)
CitrixResourceBase wrongly calculates total memory on hosts with a lot of
memory and large Dom0
---
Key: CLOUDSTACK-7857
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7857
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: Future, 4.3.0, 4.4.0, 4.5.0, 4.3.1, 4.4.1, 4.6.0
Reporter: Joris van Lieshout
Priority: Critical
We have hosts with 256GB memory and 4GB dom0. During startup ACS calculates
available memory using this formula:
CitrixResourceBase.java
protected void fillHostInfo
ram = (long) ((ram - dom0Ram - _xs_memory_used) *
_xs_virtualization_factor);
In our situation:
ram = 274841497600
dom0Ram = 4269801472
_xs_memory_used = 128 * 1024 * 1024L = 134217728
_xs_virtualization_factor = 63.0/64.0 = 0,984375
(274841497600 - 4269801472 - 134217728) * 0,984375 = 266211892800
This is in fact not the actual amount of memory available for instances. The
difference in our situation is a little less then 1GB. On this particular
hypervisor Dom0+Xen uses about 9GB.
As the comment above the definition of XsMemoryUsed allready stated it's time
to review this logic.
//Hypervisor specific params with generic value, may need to be overridden
for specific versions
The effect of this bug is that when you put a hypervisor in maintenance it
might try to move instances (usually small instances (1GB)) to a host that
in fact does not have enought free memory.
This exception is thrown:
ERROR [c.c.h.HighAvailabilityManagerImpl] (HA-Worker-3:ctx-09aca6e9
work-8981) Terminating HAWork[8981-Migration-4482-Running-Migrating]
com.cloud.utils.exception.CloudRuntimeException: Unable to migrate due to
Catch Exception com.cloud.utils.exception.CloudRuntimeException: Migration
failed due to com.cloud.utils.exception.CloudRuntim
eException: Unable to migrate VM(r-4482-VM) from
host(6805d06c-4d5b-4438-a245-7915e93041d9) due to Task failed! Task record:
uuid: 645b63c8-1426-b412-7b6a-13d61ee7ab2e
nameLabel: Async.VM.pool_migrate
nameDescription:
allowedOperations: []
currentOperations: {}
created: Thu Nov 06 13:44:14 CET 2014
finished: Thu Nov 06 13:44:14 CET 2014
status: failure
residentOn: com.xensource.xenapi.Host@b42882c6
progress: 1.0
type: none/
result:
errorInfo: [HOST_NOT_ENOUGH_FREE_MEMORY, 272629760, 263131136]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at
com.cloud.vm.VirtualMachineManagerImpl.migrate(VirtualMachineManagerImpl.java:1840)
at
com.cloud.vm.VirtualMachineManagerImpl.migrateAway(VirtualMachineManagerImpl.java:2214)
at
com.cloud.ha.HighAvailabilityManagerImpl.migrate(HighAvailabilityManagerImpl.java:610)
at
com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.runWithContext(HighAvailabilityManagerImpl.java:865)
at
com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.access$000(HighAvailabilityManagerImpl.java:822)
at
com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread$1.run(HighAvailabilityManagerImpl.java:834)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.run(HighAvailabilityManagerImpl.java:831)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8129) [VMware] Cold migration of VM across VMware DCs leaves the VM behind in the source host.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14262916#comment-14262916 ] ASF subversion and git services commented on CLOUDSTACK-8129: - Commit 15b348632df2049347f58c87830be2c02eee3b61 in cloudstack's branch refs/heads/reporter from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=15b3486 ] CLOUDSTACK-8129. Cold migration of VM across VMware DCs leaves the VM behind in the source host. If VM has been cold migrated across different VMware DCs, then unregister the VM from source host. [VMware] Cold migration of VM across VMware DCs leaves the VM behind in the source host. Key: CLOUDSTACK-8129 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8129 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Priority: Critical Fix For: Future 1. Have an upgraded VMware setup with a legacy zone (Legacy zone is a zone where a CS zone has clusters that are spread across different VMware DCs). So ensure there are two clusters say C1 and C2 that belong to VMware DCs D1 and D2 respectively. 2. Deploy a VM. Say it is in C1. 3. Stop the VM. 3. Migrate the VM to a storage in a C2. 4. Start the VM. Observations - VM will be be successfully started in a host in C2. But a stale entry of the VM will be left in C1. And whenever VM sync kicks in it stops ans start the VM repeatedly because there are two VMs by the same name in vCenter. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8134) [VMware] Worker VMs don't have MS id set in vCenter annotation 'cloud.vm.workertag'.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14262918#comment-14262918 ] ASF subversion and git services commented on CLOUDSTACK-8134: - Commit 13bdc1cef4ee0fae2f263777317c170302c49689 in cloudstack's branch refs/heads/reporter from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=13bdc1c ] CLOUDSTACK-8134. Worker VMs don't have MS id set in vCenter annotation 'cloud.vm.workertag'. Correctly register node info for a newly created VMware context. [VMware] Worker VMs don't have MS id set in vCenter annotation 'cloud.vm.workertag'. Key: CLOUDSTACK-8134 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8134 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: VMware Affects Versions: 4.5.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Fix For: Future +Steps to reproduce+ 1. Deploy a VMware setup. 2. Perform an operation that requires SSVM to create a worker VM. For e.g. - Take a volume snapshot. 3. Check the worker VM's annotation _'cloud.vm.workertag'_ in vCenter +Observation+ Annotation is in the following format _'1403328707521-null'_. +Expected behavior+ Annotation is expected to be in the following format _'1403328707521-345050805373-1403229668525'_ where the second string in the worker VM tag is the MS id. This annotation is used in the cleanup of worker VMs and hence needs to be correctly set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-6920) Support listing of LBHealthcheck policy with LBHealthcheck policy ID
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14262917#comment-14262917 ] ASF subversion and git services commented on CLOUDSTACK-6920: - Commit c7b23d0a10fa6fc55820f298cce658bff0b8125c in cloudstack's branch refs/heads/reporter from [~rajesh_battala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c7b23d0 ] CLOUDSTACK-6920 Support listing of LBHealthcheck policy with LBHealthcheck policy ID Support listing of LBHealthcheck policy with LBHealthcheck policy ID Key: CLOUDSTACK-6920 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6920 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.4.0 Reporter: Rajesh Battala Assignee: Rajesh Battala Fix For: 4.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8136) [VMware] Create VM snapshot fails if a previous attempt to take the snapshot failed.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14262919#comment-14262919 ] ASF subversion and git services commented on CLOUDSTACK-8136: - Commit 25a4f0dc530951e87fe357313dc983cb75aa8972 in cloudstack's branch refs/heads/reporter from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=25a4f0d ] CLOUDSTACK-8136. [VMware] Create VM snapshot fails if a previous attempt to take the snapshot failed. While looking for an ongoing VM snapshot task, check the task status to identify if the task is still running. [VMware] Create VM snapshot fails if a previous attempt to take the snapshot failed. Key: CLOUDSTACK-8136 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8136 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.5.0 Reporter: Likitha Shetty Assignee: Likitha Shetty Fix For: Future +Steps to reproduce+ 1. Deploy a VM. 2. Take a failed VM snapshot. - Stop the VM. - Migrate VM's ROOT disk to another primary storage. - Try to take a VM snapshot - Expected failure (fails because CS expects the VM to be started after it has been cold migration before performing any further operations on the VM). 3. Start the VM. 4. Immediately take another VM snapshot - Fails. 5. Try taking a snapshot after 10 mins when the VMs 'Recent Tasks' in vCenter are all cleared - Succeeds. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7399) broadcast_uri and possibly isolation_uri is not set correctly with Basic Network
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudha Ponnaganti updated CLOUDSTACK-7399: - Fix Version/s: (was: 4.1.1) 4.4.1 broadcast_uri and possibly isolation_uri is not set correctly with Basic Network Key: CLOUDSTACK-7399 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7399 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: CentOS Linux 6.5 64Bit, KVM, Basic Network Reporter: Thomas Moroder Fix For: 4.4.1 Since updating to version 4.4.0 of Cloudstack I have noticed problems when starting new VMs and also System-VMs. After analyzing the database changes it seems that broadcast_uri and possibly isolation_uri do not get set and/or do not get set correctly for new VM instances in the nics table. E.g.: mysql select * from nics where instance_id=457; +-+--+-+---+--+---++-+---++--+---+--+---+--+---+-+---+-+-+-+-+-+-+--+--+-+ | id | uuid | instance_id | mac_address | ip4_address | netmask | gateway| ip_type | broadcast_uri | network_id | mode | state | strategy | reserver_name | reservation_id | device_id | update_time | isolation_uri | ip6_address | default_nic | vm_type | created | removed | ip6_gateway | ip6_cidr | secondary_ip | display_nic | +-+--+-+---+--+---++-+---++--+---+--+---+--+---+-+---+-+-+-+-+-+-+--+--+-+ | 668 | ec1d8296-1bb5-4844-8485-00ada7c7a8f9 | 457 | 06:97:ae:00:00:5c | 1.2.3.4 | 255.255.255.0 | 1.2.3.1 | Ip4 | NULL |212 | Dhcp | Allocated | Start| DirectPodBasedNetworkGuru | e7b3de50-8cf0-43db-a7b2-4cc44d2d13c5 | 0 | 2014-08-22 10:12:17 | NULL | NULL| 1 | User| 2014-08-22 08:12:09 | NULL | NULL| NULL |0 | 1 | +-+--+-+---+--+---++-+---++--+---+--+---+--+---+-+---+-+-+-+-+-+-+--+--+-+ With previous versions both broadcast_uri and isolation_uri where set in the Basic Network mode to vlan://untagged and ec2://untagged. This causes failures to start the VMs with the cloudstack-agent on the single hosts giving the following error message: 2014-08-22 02:43:08,457 WARN [cloud.agent.Agent] (agentRequest-Handler-5:null) Caught: java.lang.NullPointerException at com.cloud.network.Networks$BroadcastDomainType.getSchemeValue(Networks.java:160) at com.cloud.network.Networks$BroadcastDomainType.getValue(Networks.java:214) at com.cloud.hypervisor.kvm.resource.BridgeVifDriver.plug(BridgeVifDriver.java:96) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVif(LibvirtComputingResource.java:4010) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.createVifs(LibvirtComputingResource.java:3766) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:3795) at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1333) at com.cloud.agent.Agent.processRequest(Agent.java:501) at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808) at com.cloud.utils.nio.Task.run(Task.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at
[jira] [Created] (CLOUDSTACK-8140) secstorage.service.offering in GS set to service offering ID Webui fails to start
Nuno Tavares created CLOUDSTACK-8140: Summary: secstorage.service.offering in GS set to service offering ID Webui fails to start Key: CLOUDSTACK-8140 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8140 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.1 Reporter: Nuno Tavares Hi. I'm using CS 4.2.1, and wanted to make sure that this has been corrected in next versions: It seems secstorage.service.offering setting in GS is expecting an integer ID instead of the typical GUID. According to Nitin Mehta it's a bug, and here is the bug report. I kept the subject line from the CS thread I came across: http://markmail.org/thread/jbdg544zmnye6kui#query:+page:1+mid:ifpbo3nivmpojtm3+state:results Not sure why/if it is directly related, if I set any value with update configuration set value = X where name = 'secstorage.service.offering'; the management server will not launch properly. After restarting, this is what I get: list capabilities Error: The given command:listCapabilities does not exist or it is not available for user with id:null list templates templatefilter=all Error: The given command:listTemplates does not exist or it is not available for user with id:null (mgt server logs complain about listCapabilites as well). After setting the value to NULL everything comes back well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8140) secstorage.service.offering in GS set to service offering ID Webui fails to start
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nuno Tavares updated CLOUDSTACK-8140:
-
Description:
Hi. I'm using CS 4.2.1, and wanted to make sure that this has been corrected in
next versions:
It seems secstorage.service.offering setting in GS is expecting an integer ID
instead of the typical GUID. According to Nitin Mehta it's a bug, and here is
the bug report.
I kept the subject line from the CS thread I came across:
http://markmail.org/thread/jbdg544zmnye6kui#query:+page:1+mid:ifpbo3nivmpojtm3+state:results
Not sure why/if it is directly related, if I set any value with
update configuration set value = X where name =
'secstorage.service.offering';
the management server will not launch properly. After restarting, this is what
I get:
{code}
list capabilities
Error: The given command:listCapabilities does not exist or it is not available
for user with id:null
list templates templatefilter=all
Error: The given command:listTemplates does not exist or it is not available
for user with id:null
{code]
(mgt server logs complain about listCapabilites as well).
After setting the value to NULL everything comes back well.
was:
Hi. I'm using CS 4.2.1, and wanted to make sure that this has been corrected in
next versions:
It seems secstorage.service.offering setting in GS is expecting an integer ID
instead of the typical GUID. According to Nitin Mehta it's a bug, and here is
the bug report.
I kept the subject line from the CS thread I came across:
http://markmail.org/thread/jbdg544zmnye6kui#query:+page:1+mid:ifpbo3nivmpojtm3+state:results
Not sure why/if it is directly related, if I set any value with
update configuration set value = X where name =
'secstorage.service.offering';
the management server will not launch properly. After restarting, this is what
I get:
list capabilities
Error: The given command:listCapabilities does not exist or it is not available
for user with id:null
list templates templatefilter=all
Error: The given command:listTemplates does not exist or it is not available
for user with id:null
(mgt server logs complain about listCapabilites as well).
After setting the value to NULL everything comes back well.
secstorage.service.offering in GS set to service offering ID Webui fails to
start
-
Key: CLOUDSTACK-8140
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8140
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.1
Reporter: Nuno Tavares
Hi. I'm using CS 4.2.1, and wanted to make sure that this has been corrected
in next versions:
It seems secstorage.service.offering setting in GS is expecting an integer ID
instead of the typical GUID. According to Nitin Mehta it's a bug, and here is
the bug report.
I kept the subject line from the CS thread I came across:
http://markmail.org/thread/jbdg544zmnye6kui#query:+page:1+mid:ifpbo3nivmpojtm3+state:results
Not sure why/if it is directly related, if I set any value with
update configuration set value = X where name =
'secstorage.service.offering';
the management server will not launch properly. After restarting, this is
what I get:
{code}
list capabilities
Error: The given command:listCapabilities does not exist or it is not
available for user with id:null
list templates templatefilter=all
Error: The given command:listTemplates does not exist or it is not available
for user with id:null
{code]
(mgt server logs complain about listCapabilites as well).
After setting the value to NULL everything comes back well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8140) secstorage.service.offering in GS set to service offering ID Webui fails to start
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nuno Tavares updated CLOUDSTACK-8140:
-
Description:
Hi. I'm using CS 4.2.1, and wanted to make sure that this has been corrected in
next versions:
It seems secstorage.service.offering setting in GS is expecting an integer ID
instead of the typical GUID. According to Nitin Mehta it's a bug, and here is
the bug report.
I kept the subject line from the CS thread I came across:
http://markmail.org/thread/jbdg544zmnye6kui#query:+page:1+mid:ifpbo3nivmpojtm3+state:results
Not sure why/if it is directly related, if I set any value with
update configuration set value = X where name =
'secstorage.service.offering';
the management server will not launch properly. After restarting, this is what
I get:
{code}
list capabilities
Error: The given command:listCapabilities does not exist or it is not available
for user with id:null
list templates templatefilter=all
Error: The given command:listTemplates does not exist or it is not available
for user with id:null
{code}
(mgt server logs complain about listCapabilites as well).
After setting the value to NULL everything comes back well.
was:
Hi. I'm using CS 4.2.1, and wanted to make sure that this has been corrected in
next versions:
It seems secstorage.service.offering setting in GS is expecting an integer ID
instead of the typical GUID. According to Nitin Mehta it's a bug, and here is
the bug report.
I kept the subject line from the CS thread I came across:
http://markmail.org/thread/jbdg544zmnye6kui#query:+page:1+mid:ifpbo3nivmpojtm3+state:results
Not sure why/if it is directly related, if I set any value with
update configuration set value = X where name =
'secstorage.service.offering';
the management server will not launch properly. After restarting, this is what
I get:
{code}
list capabilities
Error: The given command:listCapabilities does not exist or it is not available
for user with id:null
list templates templatefilter=all
Error: The given command:listTemplates does not exist or it is not available
for user with id:null
{code]
(mgt server logs complain about listCapabilites as well).
After setting the value to NULL everything comes back well.
secstorage.service.offering in GS set to service offering ID Webui fails to
start
-
Key: CLOUDSTACK-8140
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8140
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.1
Reporter: Nuno Tavares
Hi. I'm using CS 4.2.1, and wanted to make sure that this has been corrected
in next versions:
It seems secstorage.service.offering setting in GS is expecting an integer ID
instead of the typical GUID. According to Nitin Mehta it's a bug, and here is
the bug report.
I kept the subject line from the CS thread I came across:
http://markmail.org/thread/jbdg544zmnye6kui#query:+page:1+mid:ifpbo3nivmpojtm3+state:results
Not sure why/if it is directly related, if I set any value with
update configuration set value = X where name =
'secstorage.service.offering';
the management server will not launch properly. After restarting, this is
what I get:
{code}
list capabilities
Error: The given command:listCapabilities does not exist or it is not
available for user with id:null
list templates templatefilter=all
Error: The given command:listTemplates does not exist or it is not available
for user with id:null
{code}
(mgt server logs complain about listCapabilites as well).
After setting the value to NULL everything comes back well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8139) UI create compute offering server-side only supports one single host tag instead of multiple host tags. So, change UI to take in only one single host tag inste
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14263151#comment-14263151 ] ASF subversion and git services commented on CLOUDSTACK-8139: - Commit 61154b92f73ecae5f5622eae53b3f0124a6709d5 in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=61154b9 ] CLOUDSTACK-8139: UI create compute offering server-side only supports one single host tag instead of multiple host tags. So, change UI to take in only one single host tag instead of multiple host tags in create compute dialog. UI create compute offering server-side only supports one single host tag instead of multiple host tags. So, change UI to take in only one single host tag instead of multiple host tags in create compute dialog. - Key: CLOUDSTACK-8139 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8139 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8141) UI use Project view Infrastructure zone physical network Public traffic type do not pass projectId to listNetworks API.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14263166#comment-14263166 ] ASF subversion and git services commented on CLOUDSTACK-8141: - Commit b64fa34ce901f88a944f9f104310a8f53a827f0f in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b64fa34 ] CLOUDSTACK-8141: UI use Project view Infrastructure zone physical network Public traffic type do not pass projectId to listNetworks API. UI use Project view Infrastructure zone physical network Public traffic type do not pass projectId to listNetworks API. --- Key: CLOUDSTACK-8141 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8141 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8141) UI use Project view Infrastructure zone physical network Public traffic type do not pass projectId to listNetworks API.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14263165#comment-14263165 ] ASF subversion and git services commented on CLOUDSTACK-8141: - Commit 775e4d34c3236ca58749b4b6065d6b8f0b6ce555 in cloudstack's branch refs/heads/4.5 from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=775e4d3 ] CLOUDSTACK-8141: UI use Project view Infrastructure zone physical network Public traffic type do not pass projectId to listNetworks API. UI use Project view Infrastructure zone physical network Public traffic type do not pass projectId to listNetworks API. --- Key: CLOUDSTACK-8141 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8141 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8139) UI create compute offering server-side only supports one single host tag instead of multiple host tags. So, change UI to take in only one single host tag instea
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-8139. -- Resolution: Fixed UI create compute offering server-side only supports one single host tag instead of multiple host tags. So, change UI to take in only one single host tag instead of multiple host tags in create compute dialog. - Key: CLOUDSTACK-8139 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8139 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-8139) UI create compute offering server-side only supports one single host tag instead of multiple host tags. So, change UI to take in only one single host tag instead
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang closed CLOUDSTACK-8139. UI create compute offering server-side only supports one single host tag instead of multiple host tags. So, change UI to take in only one single host tag instead of multiple host tags in create compute dialog. - Key: CLOUDSTACK-8139 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8139 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-8141) UI use Project view Infrastructure zone physical network Public traffic type do not pass projectId to listNetworks API.
Jessica Wang created CLOUDSTACK-8141: Summary: UI use Project view Infrastructure zone physical network Public traffic type do not pass projectId to listNetworks API. Key: CLOUDSTACK-8141 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8141 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7857) CitrixResourceBase wrongly calculates total memory on hosts with a lot of memory and large Dom0
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14262796#comment-14262796
]
Daan Hoogland commented on CLOUDSTACK-7857:
---
Marking it as critical instead of blocker. Let's discuss on list if it needs to
be a blocker anyway.
CitrixResourceBase wrongly calculates total memory on hosts with a lot of
memory and large Dom0
---
Key: CLOUDSTACK-7857
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7857
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Affects Versions: Future, 4.3.0, 4.4.0, 4.5.0, 4.3.1, 4.4.1, 4.6.0
Reporter: Joris van Lieshout
Priority: Critical
We have hosts with 256GB memory and 4GB dom0. During startup ACS calculates
available memory using this formula:
CitrixResourceBase.java
protected void fillHostInfo
ram = (long) ((ram - dom0Ram - _xs_memory_used) *
_xs_virtualization_factor);
In our situation:
ram = 274841497600
dom0Ram = 4269801472
_xs_memory_used = 128 * 1024 * 1024L = 134217728
_xs_virtualization_factor = 63.0/64.0 = 0,984375
(274841497600 - 4269801472 - 134217728) * 0,984375 = 266211892800
This is in fact not the actual amount of memory available for instances. The
difference in our situation is a little less then 1GB. On this particular
hypervisor Dom0+Xen uses about 9GB.
As the comment above the definition of XsMemoryUsed allready stated it's time
to review this logic.
//Hypervisor specific params with generic value, may need to be overridden
for specific versions
The effect of this bug is that when you put a hypervisor in maintenance it
might try to move instances (usually small instances (1GB)) to a host that
in fact does not have enought free memory.
This exception is thrown:
ERROR [c.c.h.HighAvailabilityManagerImpl] (HA-Worker-3:ctx-09aca6e9
work-8981) Terminating HAWork[8981-Migration-4482-Running-Migrating]
com.cloud.utils.exception.CloudRuntimeException: Unable to migrate due to
Catch Exception com.cloud.utils.exception.CloudRuntimeException: Migration
failed due to com.cloud.utils.exception.CloudRuntim
eException: Unable to migrate VM(r-4482-VM) from
host(6805d06c-4d5b-4438-a245-7915e93041d9) due to Task failed! Task record:
uuid: 645b63c8-1426-b412-7b6a-13d61ee7ab2e
nameLabel: Async.VM.pool_migrate
nameDescription:
allowedOperations: []
currentOperations: {}
created: Thu Nov 06 13:44:14 CET 2014
finished: Thu Nov 06 13:44:14 CET 2014
status: failure
residentOn: com.xensource.xenapi.Host@b42882c6
progress: 1.0
type: none/
result:
errorInfo: [HOST_NOT_ENOUGH_FREE_MEMORY, 272629760, 263131136]
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
at
com.cloud.vm.VirtualMachineManagerImpl.migrate(VirtualMachineManagerImpl.java:1840)
at
com.cloud.vm.VirtualMachineManagerImpl.migrateAway(VirtualMachineManagerImpl.java:2214)
at
com.cloud.ha.HighAvailabilityManagerImpl.migrate(HighAvailabilityManagerImpl.java:610)
at
com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.runWithContext(HighAvailabilityManagerImpl.java:865)
at
com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.access$000(HighAvailabilityManagerImpl.java:822)
at
com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread$1.run(HighAvailabilityManagerImpl.java:834)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.run(HighAvailabilityManagerImpl.java:831)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8038) Create a new reusable tinylinux appliance for all hypervisors
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14263331#comment-14263331 ] Nux commented on CLOUDSTACK-8038: - Hi and happy new year, I am at a stage now where I am happy with Macchinina. It seems to boot, resize, retrieve passwords and ssh key as well as executing user data scripts. It takes 50MB (20MB compressed) of space and can run in as low as 48MB RAM. What is missing is more testing on other hypervisors (tested KVM and XS) so if you guys have the time and means, I'd appreciate it. I am still waiting for Ilya to help out with the vmdk conversion. Download from here: http://dl.openvm.eu/cloudstack/macchinina/x86_64/ Relevant links: https://github.com/NuxRo/macchinina http://jenkins.openvm.eu/job/Macchinina/ Any feedback is welcome. Create a new reusable tinylinux appliance for all hypervisors - Key: CLOUDSTACK-8038 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8038 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Rohit Yadav Assignee: Rohit Yadav Fix For: Future, 4.6.0 Using our systemvm build infra/scripts, create a tiny linux appliance (10-20 MB in size) that has the reset password/ssh-public-key scripts for testing purposes. Make this available for everyone for various hypervisors - Xen, VMWare, KVM, HyperV, OVM (LXC). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7383) [LXC][UI] dont show vm snapshot button in UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14263269#comment-14263269 ] ASF subversion and git services commented on CLOUDSTACK-7383: - Commit 744c1a1b03c5485dc51c4b85c7c22052f6e23934 in cloudstack's branch refs/heads/4.5 from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=744c1a1 ] CLOUDSTACK-7383: UI Instances menu detail view TakeSnapshot action should be hidden when VM's hypervisor is LXC. [LXC][UI] dont show vm snapshot button in UI Key: CLOUDSTACK-7383 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7383 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Jessica Wang Priority: Critical Fix For: 4.5.0 Attachments: lxc.png, vmsnap.png Repro steps: Vm snapshot is not supported in LXC so we should not show VM snapshot option in UI in instance tab , the way we do it for KVM .We dont show VM snapshot button in cae of KVM vm. Attaching snapshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7383) [LXC][UI] dont show vm snapshot button in UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14263274#comment-14263274 ] ASF subversion and git services commented on CLOUDSTACK-7383: - Commit 7fe1ed9dc81a92312cb273dc464d5f6d4259af05 in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7fe1ed9 ] CLOUDSTACK-7383: UI Instances menu detail view TakeSnapshot action should be hidden when VM's hypervisor is LXC. [LXC][UI] dont show vm snapshot button in UI Key: CLOUDSTACK-7383 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7383 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Jessica Wang Priority: Critical Fix For: 4.5.0 Attachments: lxc.png, vmsnap.png Repro steps: Vm snapshot is not supported in LXC so we should not show VM snapshot option in UI in instance tab , the way we do it for KVM .We dont show VM snapshot button in cae of KVM vm. Attaching snapshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-8141) UI use Project view Infrastructure zone physical network Public traffic type do not pass projectId to listNetworks API.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang closed CLOUDSTACK-8141. UI use Project view Infrastructure zone physical network Public traffic type do not pass projectId to listNetworks API. --- Key: CLOUDSTACK-8141 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8141 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang Priority: Critical Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-8141) UI use Project view Infrastructure zone physical network Public traffic type do not pass projectId to listNetworks API.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-8141. -- Resolution: Fixed UI use Project view Infrastructure zone physical network Public traffic type do not pass projectId to listNetworks API. --- Key: CLOUDSTACK-8141 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8141 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang Priority: Critical Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7383) [LXC][UI] dont show vm snapshot button in UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-7383. -- Resolution: Fixed [LXC][UI] dont show vm snapshot button in UI Key: CLOUDSTACK-7383 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7383 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Jessica Wang Priority: Critical Fix For: 4.5.0 Attachments: lxc.png, vmsnap.png Repro steps: Vm snapshot is not supported in LXC so we should not show VM snapshot option in UI in instance tab , the way we do it for KVM .We dont show VM snapshot button in cae of KVM vm. Attaching snapshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7383) [LXC][UI] dont show vm snapshot button in UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang closed CLOUDSTACK-7383. [LXC][UI] dont show vm snapshot button in UI Key: CLOUDSTACK-7383 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7383 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.5.0 Reporter: shweta agarwal Assignee: Jessica Wang Priority: Critical Fix For: 4.5.0 Attachments: lxc.png, vmsnap.png Repro steps: Vm snapshot is not supported in LXC so we should not show VM snapshot option in UI in instance tab , the way we do it for KVM .We dont show VM snapshot button in cae of KVM vm. Attaching snapshot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8139) UI create compute offering server-side only supports one single host tag instead of multiple host tags. So, change UI to take in only one single host tag instead
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-8139: - Fix Version/s: 4.5.0 UI create compute offering server-side only supports one single host tag instead of multiple host tags. So, change UI to take in only one single host tag instead of multiple host tags in create compute dialog. - Key: CLOUDSTACK-8139 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8139 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang Priority: Critical Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8141) UI use Project view Infrastructure zone physical network Public traffic type do not pass projectId to listNetworks API.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-8141: - Fix Version/s: 4.5.0 UI use Project view Infrastructure zone physical network Public traffic type do not pass projectId to listNetworks API. --- Key: CLOUDSTACK-8141 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8141 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang Priority: Critical Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8038) Create a new reusable tinylinux appliance for all hypervisors
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14263385#comment-14263385 ] ilya musayev commented on CLOUDSTACK-8038: -- Nux, Let me play with these early next week. I'll figure out vmware tools portion and provide details on making it work with vmware. Feel free to ping me next week if i don't respond. Regards ilya Create a new reusable tinylinux appliance for all hypervisors - Key: CLOUDSTACK-8038 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8038 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Reporter: Rohit Yadav Assignee: Rohit Yadav Fix For: Future, 4.6.0 Using our systemvm build infra/scripts, create a tiny linux appliance (10-20 MB in size) that has the reset password/ssh-public-key scripts for testing purposes. Make this available for everyone for various hypervisors - Xen, VMWare, KVM, HyperV, OVM (LXC). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
