Hi, did you get the log file I attached? any advice?
Thank you
On 5/18/2020 4:59 PM, Sergey Levitskiy wrote:
Plz share full management-server.log since your snippet doesn't have relevant
lines.
Thanks,
Sergey
On 5/18/20, 1:25 PM, "Luis Martinez" wrote:
This is the error I see in
Hello,
I want to start with cloudstack, with two hosts servers (from OVH), and of
course 1 management server (that can be in OVH or in another dedicated server
or VPS provider).
Must be all 3 servers linked with the feature that OVH name "vlink"? (RISE
server, the cheapest, do now have such
Thank you Sina,
But I did a mistake, I wanted to write Cloudstack and I write Openstack
by error.
Thanks,
Augusto
On 20/05/2020 0:17, Sina Kashipazha wrote:
Dear Augosto,
Here is the Cloudstack mailing list, not Openstack. Cloudstack and Openstack
are doing the same thing but in a
Just for feedback, we are 4.11.3 and run KVM on CentOS 7. Our 4.11.3 template
is set to Debian GNU/Linux 8 (64-bit). Our lspci is shown below:
root@r-281-VM:~# lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3
Are you using NFS?
Yea, we implmented locking because of that problem:
https://libvirt.org/locking-lockd.html
echo lock_manager = \"lockd\" >> /etc/libvirt/qemu.conf
-Original Message-
From: Andrija Panic
Sent: Wednesday, October 30, 2019 6:55 AM
To: dev
Cc: users
Subject: Re:
Dear Augosto,
Here is the Cloudstack mailing list, not Openstack. Cloudstack and Openstack
are doing the same thing but in a completely different way. You can see them as
Android and iOS. It is better to ask your question in the Openstack mailing
list.
Kind Regards,
Sina
> On 19 May 2020, at
Sorry, Cloudstack :-)
On 19/05/2020 22:44, Andrija Panic wrote:
If you want to start with OpenStack, then you are on the wrong mailing list
:)
On Tue, 19 May 2020, 22:06 , wrote:
Hello,
I want to start with openstack with 2 hosts/nodes, from OVH and of
course 1 management server/master.
If you want to start with OpenStack, then you are on the wrong mailing list
:)
On Tue, 19 May 2020, 22:06 , wrote:
>
> Hello,
>
> I want to start with openstack with 2 hosts/nodes, from OVH and of
> course 1 management server/master.
>
> Must be all 3 servers linked with the product that OVH
Hello,
I want to start with openstack with 2 hosts/nodes, from OVH and of
course 1 management server/master.
Must be all 3 servers linked with the product that OVH naed as "vlink"?.
Can I for example have the master in one datacenter (in a hetzner VPS
for example), one host in OVH USA, and
Hi David,
0. Good :) (needless to say, always drop the messed-up DBs, and then import
the backup in, don't just try to import over the existing/messed-up DBs)
1. You are right, you HAVE TO use the **exact** name as it's stated in the
upgrade notes (ACS code base is searching for a template with
Hi all,
In my humble opinion, we should release 4.14 as it is (considering we have
enough votes), but we'll further investigate the actual/behind-the-scene
root-cause for the vSphere 6.7 harakiri (considering 6.0 and 6.5 are not
affected) - this is possibly a VMware bug and we'll certainly try to
Reporting in, I was able to roll-back the cloudstack packages and reload the
backup of the cloud database and get the UI going again.
So that's good, but a couple questions on this page (and registering the
template in the UI):
-
Thank you Bobby and Daan for the update. However I have not encountered such
issue while doing dev test with Vmware 5.5 & 6.5.
Regards,
Pavan Aravapalli.
From: Daan Hoogland
Sent: 19 May 2020 20:56
To: users
Cc: d...@cloudstack.apache.org
Subject: Re:
Thanks Bobby,
All, I've been closely working with Bobby and seen the same things. Does
anybody see any issues releasing 4.14 based on this code? I can confirm
that it is not Pavernalli's UEFI PR and we should not create a new PR to
revert it.
thanks for all of your patience,
(this is me giving a
Hi guys,
I've done more testing around this and I can now confirm it has nothing to do
with cloudstack code.
I've tested it with rc3, reverted UEFI PR and 4.13.1 (which does not happen to
have the feature at all). Also I've used a matrix of VMware version of 6.0u2,
6.5u2 and 6.7u3.
The bug
Indeed it is severe, but please note it's a corner case which was unearthed
almost by accident. It falls down to using a new feature of selecting a boot
protocol and the template must be corrupted. So with already existing templates
I would not expect to encounter it.
As for recovery, we've
16 matches
Mail list logo
