Gregor,
can you confirm if you followed the steps exactly in regards to template
flags and more importantly the actual name - I believe in the code, during
upgrading, it will search for specific template name (i.e.
systemvm-vmware-4.11.3) and update it's DB values so it becomes a "SYSTEM"
instead
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
Hi,
I already added a question related to this a few days ago but i already
solved the first issue i had with it. So i thought to create a new one with
the new trouble i had on it
I installed Cloudstack 4.11.2.0 on Ubuntu 16.04
This is my environment:
- 1 Zone
- 1 Pod
- 2 Clusters (LXC and
Dear Apache Enthusiast,
(You’re receiving this message because you’re subscribed to one or more
Apache Software Foundation project user mailing lists.)
We’re thrilled to announce the schedule for our upcoming conference,
ApacheCon North America 2019, in Las Vegas, Nevada. See it now at
Dear Apache Enthusiast,
(You’re receiving this message because you’re subscribed to one or more
Apache Software Foundation project user mailing lists.)
We’re thrilled to announce the schedule for our upcoming conference,
ApacheCon North America 2019, in Las Vegas, Nevada. See it now at
Hi Paul,
> The release notes are still work-in-progress, but the systemvm
> template upgrade section has been updated. You may refer the
> following for systemvm template upgrade testing:
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/index.html
Thanks!
We're
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
Hello everyone
I am having running snapshot issues on large volumes. The hypervisor is KVM and
the storage backend is Ceph (rbd). Here is my issue:
I've got several vms with 3-6 volumes of 2TB each. I have a recurring schedule
setup to take a snapshot of each volume once a month. It takes a
