Hi Simon,
Thanks for the reply.
>> Also run ceph health and make sure your agent can talk to your ceph
monitors.
ceph health status shows fine and also we can connect our OSD's from
monitor server. Snippets pasted below.
===
[root@mon1 ~]# ceph -s
cluster ebac75fc-e631-4c9f-a310-880cbc
Yes, I am able to explain. I am still not getting the whole picture here.
VR = virtual router
First condition:
> if (dest.getCluster() != null) {
>
- If we are forcing a VR to a specific cluster, normally this happens
when we are starting a router that was already deployed. If it is a new
I agree, agent logs would be good to look at.
You can enable kvm agent debugging by running this: sed -i 's/INFO/DEBUG/g'
/etc/cloudstack/agent/log4j-cloud.xml
Restart the agent and then tail -f /var/log/cloudstack/agent/agent.log
Also run ceph health and make sure your agent can talk to you
Yuriy,
Can you provide some background to us in addition to your logs?
What ACS version?
Hypervisor type?
Is this production or lab?
Any other info around what you're trying to do?
- Si
From: Yuriy Karpel
Sent: Tuesday, February 21, 2017 1:35 AM
To: user
Vladimir,
To answer your immediate question, I don't think you're at major risk by
staying on Centos 6 in the medium term. Centos 6 will be supported by Centos
until Nov 30th, 2020. In terms of what ACS will support, I don't think it has
been discussed on the list for a while. There will be a
Hi,
after digging into the source code I wonder if
https://github.com/apache/cloudstack/blob/master/server/src/com/cloud/network/router/NetworkHelperImpl.java
line 453
final List hypervisors =
getHypervisors(routerDeploymentDefinition);
line 458
for (final Iterator iter = hypervisors.iterato
Hi Martin,
does the volume still exist on primary storage? You can also take a look at
SMlog on XenServer.
Mit freundlichen Grüßen / With kind regards,
Swen
-Ursprüngliche Nachricht-
Von: Martin Emrich [mailto:martin.emr...@empolis.com]
Gesendet: Mittwoch, 22. Februar 2017 12:27
An:
Hi!
After shutting down a VM for resizing, it no longer starts. The GUI reports
insufficient Capacity (but there's plenty), and in the Log I see this:
2017-02-22 12:18:40,626 DEBUG [o.a.c.e.o.VolumeOrchestrator]
(Work-Job-Executor-11:ctx-c5cca7da job-70304/job-70306 ctx-a412f4b8) Checking
if w
Hi,
this behavior was caused by the following setting:
system.vm.default.hypervisor = Xenserver
After setting this global parameter to NULL we are able to deploy SystemVMs
(virtual router) on KVM.
Sad to say, we are no more able to deploy SystemVMs on Xenserver since we
changed the parameter?
