olas Vazquez
>
> De: Alejandro Ruiz Bermejo
> Enviado: sábado, 15 de junio 16:15
> Asunto: Re: launch instance error
> Para: users@cloudstack.apache.org
>
>
> Hi,
> I made a fresh install of the CoudStack environment with 2 nodes:
> management and server. The primary an
a disks unless you add a Ceph storage
> pool.
>
> References:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/LXC+Enhancements
> https://issues.apache.org/jira/browse/CLOUDSTACK-8574
>
> Regards,
> Nicolas Vazquez
>
> De: Alejandro Ruiz Bermejo
> Enviado:
: sábado, 15 de junio 16:15
Asunto: Re: launch instance error
Para: users@cloudstack.apache.org
Hi,
I made a fresh install of the CoudStack environment with 2 nodes:
management and server. The primary and secondary storage inside the
management server, both using NFS.
1 Zone
1 Pod
1 Cluster
1 Host
Hi,
I made a fresh install of the CoudStack environment with 2 nodes:
management and server. The primary and secondary storage inside the
management server, both using NFS.
1 Zone
1 Pod
1 Cluster
1 Host (LXC)
The secondary and console proxy VMs where created successfully and i
created an LXC temp
I would go with 2nd aproach - I don't expect "same" issues actually - you
can either add a new pod/cluster or just new cluster in same pod.
On Fri, 14 Jun 2019 at 21:25, Alejandro Ruiz Bermejo <
arbermejo0...@gmail.com> wrote:
> I created a new zone, pod and cluster and added the LXC host to the
I created a new zone, pod and cluster and added the LXC host to the new
cluster. CloudStack did everything for me. Since i am in a test environment
i used the same subnet for both zones.
I can do 2 things:
1. I will wipe the host and do a fresh install(only on the compute host),
but i will probabl
I'm not sure how you moved the host to another Zone ? (Please describe)
But anyway, I would wipe that host (perhaps some settings are kept locally,
etc), and add it as a fresh host to a new cluster (could be in same Pod as
well, ot a new one).i.e. start from scratch please - since your setup seems
Yes trying to find solutions i did create a new zone pod and cluster and
moved the lxc host to it, but i had the same errors. So i moved it back to
my original LXC cluster into my original zone. I guess thats why it shows
those records.
I made all the movements using the UI, it seems like the valu
So, there are a couple of problems I see, based on your storage pool DB
records:
your storage (for LXC) is CLUSTER wide, so back to first SQL I share, as
following:
SELECT storage_pool.id, storage_pool.name, storage_pool.uuid,
storage_pool.pool_type, storage_pool.created, storage_pool.removed,
sto
this was the ouputs
mysql> SELECT storage_pool.id, storage_pool.name, storage_pool.uuid,
-> storage_pool.pool_type, storage_pool.created, storage_pool.removed,
-> storage_pool.update_time, storage_pool.data_center_id,
storage_pool.pod_id,
-> storage_pool.used_bytes, storage_pool.capaci
right... based on logs, it used different sql to search for ZONE-wide
storage, execute this one please:
SELECT storage_pool.id, storage_pool.name, storage_pool.uuid,
storage_pool.pool_type, storage_pool.created, storage_pool.removed,
storage_pool.update_time, storage_pool.data_center_id, storage_p
Hi and thanks again for your help,
So i run the query with both level scopes of storage
with storage_pool.scope = 'CLUSTER'
output:
Empty set (0.00 sec)
with storage_pool.scope = 'ZONE'
++-+--+---+-+-+-
Execute this one (from logs) against your DB - does it return/finds a
storage pool ?
SELECT storage_pool.id, storage_pool.name, storage_pool.uuid,
storage_pool.pool_type, storage_pool.created, storage_pool.removed,
storage_pool.update_time, storage_pool.data_center_id, storage_pool.pod_id,
storage
Hi,
I really need to get LXC working, I'm very interested on using CS and i
need to move LXC instances to the new cloud. Thats's why i'm insisting on
it. So please if you see any errors or can help me i will appreciate it.
1. I haven't used any Tag till now (should i?)
2. Already set the TRACE lo
Well, this one still doesn't provide any usefull info.
1. Can you confirm if you have tags set on LXC Compute Offerings or any
storage used by LXC cluster?
2. Consider change logging level for management-server.log to TRACE mode,
which will show also all SQL queries executed, so perhaps we can see
Hi this is the full log for one instance cretion with the same error (
https://pastebin.com/HHKnHi36)
On Tue, Jun 11, 2019 at 5:10 PM Andrija Panic
wrote:
> Alejandro,
>
> Please send the whole log on pastebin or similar, this one doesn't provide
> enough information... (beside the " Found pools
Alejandro,
Please send the whole log on pastebin or similar, this one doesn't provide
enough information... (beside the " Found pools matching tags: [] ")
On Tue, 11 Jun 2019 at 17:57, Alejandro Ruiz Bermejo <
arbermejo0...@gmail.com> wrote:
> ok, so i registered a new template and unset-ed the
ok, so i registered a new template and unset-ed the HVM option and launched
a new instance using this themplate.
Now the planner can find the host inside the LXC cluster but it seems like
it can't find now a propper storage pool. I already have everything
configured as it appears on the installatio
Interesting lines being:
FirstFitRoutingAllocator) (logid:0a0b5a30) FirstFitAllocator has 1 hosts to
check for allocation: [Host[-4-Routing]]
2019-06-10 13:40:11,373 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
(API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7
FirstFitRoutingAllocator) (logid:0a0b5a3
i don't know if its ok sending files over here. In case it is here is the
content of the previous fail i sended
root@cloudstack-manager:/home/team# grep -i "job-41"
/var/log/cloudstack/management/management-server.log
2019-06-10 13:40:11,238 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-14
Hi, thanks for your answer, as an update of mi issue i've keep digging on
it and found this the log for the job. It seems like the allocation server
can't find my LXC host inside the LXC cluster. I don't know anymore if my
trouble is because the checksum. I attach here the file with the log output
Hi Alejandro,
Can you verify if the expected checksum is the correct and i that case update
the checksum column on vm_template table fot that template and restart
management server?
Regards,
Nicolas Vazquez
From: Alejandro Ruiz Bermejo
Sent: Monday, June 10, 2
22 matches
Mail list logo
