Hello All - I'm trying to upgrade a Data Center in ovirt 3.6.4 from 3.4 to 3.6
but I'm getting this error when I tried:
May 7, 2018 3:07:55 PM VDSM command failed: Upgrading a pool while an upgrade
is in process is unsupported
(pool: `9667c5e8-97b1-4e09-be44-2696a69f8959`)
Please note that all
First restart the engine. Then try to change the required network to be
non-required and click on RefreshCapabilities on the host.
It should move the host to active state without the need to remove it.
If it doesn't help, please attach your full engine.log and server.log.
Anyway please update
Hi,
currently I'm evaluating oVirt and I have three hosts installed within
nested KVM. They're sharing a gluster environment which has been
configured using the oVirt Node Wizards.
It seems to work quite well, but after some hours I get many status
update mails from the ovirt engine which are
Hi Samuli,
Let's first make sure the configuration is correct.
How did you configure the env? Did you use the automatic engine-setup
configuration?
Can you please send me the output of the following:
on engine:
ovn-sbctl show
ovn-nbctl show
on hosts:
ip addr
ovs-vsctl show
The
On Mon, May 7, 2018 at 11:50 AM, Bernhard Dick wrote:
> Hi,
>
> currently I'm evaluating oVirt and I have three hosts installed within
> nested KVM. They're sharing a gluster environment which has been configured
> using the oVirt Node Wizards.
> It seems to work quite well,
Good morning,
vdsm-client StorageDomain getInfo storagedomainID= :
{
"uuid": "6e5cce71-3438-4045-9d54-607123e0557e",
"type": "ISCSI",
"vguuid": "7JOYDc-iQgm-11Pk-2czh-S8k0-Qc5U-f1npF1",
"metadataDevice": "36005076300810a4db802",
"state": "OK",
"version": "4",
Hi,
after upgrade ovirt from 4.2.2 to 4.2.3.5-1.el7.centos I cannot login
into admin portal because
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to
find valid certification path to requested target
I am
Randy this flaky layer two problem reeks of a possible MTU situation between
your oVirt switches and your physical switches.
> On May 7, 2018, at 3:59 PM, Dominik Holler wrote:
>
> On Mon, 7 May 2018 11:43:51 -0700
> "Rue, Randy" wrote:
>
>> I've sort
You should query the network to team for sure.
You should also use use the ping command (from the VM) to troubleshoot possible
MTU problems getting to your infrastructure DNS servers and gateway.
# ping -M do -s 1472 xxx.xxx.xxx.xxx
Starting at 1472 and “walking” the -s up and down will help
Hello Ovirt users,
i'm trying to install ovirt node on a Dell server using a bootable usb.
After i click install ovirt, the following message is displayed on the
screen;
/*dracut-initqueue[488]: Warning: Could not boot*. / I tried different
version of Ovirt node without success, can anyone
>Was the bond created before adding the hosts to oVirt, or after adding the
>hosts via oVirt web UI?
>If the switch requires configuration for the bond, is this applied?
>Can you check if the VM can ping the getaway, if you use a simple Ethernet
>connection instead of the >bond?
Should any of
There must be more error messages than that?
From: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] On Behalf Of
Abdelkarim ZANNI
Sent: Monday, May 7, 2018 8:50 AM
To: Users@ovirt.org
Subject: [ovirt-users] dracut-initqueue[488]: Warning: Could not boot.
Hello Ovirt users,
i'm
Dear Mr. Zanni:
I have had what I believe to be similar issues. I am in no way an expert
or even knowledgeable, but from experience I have found this to work:
dd if=/tmp/ovirt-node-ng-installer-ovirt-4.2-2018050417.iso of=/dev/sdb
This command assumes that you are on CentOS or similar; assumes
On Mon, 7 May 2018 11:43:51 -0700
"Rue, Randy" wrote:
> I've sort of had some progress. On Friday I went to the dentist and
> when I returned, my VM could ping google.
>
> I don't believe I changed anything Friday morning but I confess I've
> been flailing on this for so
I installed the ovirt node to standalone interfaces, then created the
bond via the ovirt-node webui at port 9090, before adding the node to
the cluster.
The DHCP server happens to be in the same subnet but no, I can't ping it
as I can't ping anything beyond the physical interfaces of the
Looks like the physical interface on the host and the virtual interface
on the VM are both at the default 1500 MTU.
How can I determine the MTU setting for the physical switches without
admin access to them? Or do I need to ask the network team?
On 5/7/2018 2:03 PM, Clint Boggio wrote:
I forgot to cross-post to other lists. Please read announcement below.
On 05/08/2018 12:45 PM, Marc Dequènes (Duck) wrote:
> Quack,
>
> On 04/28/2018 09:34 AM, Marc Dequènes (Duck) wrote:
>
>> A few months ago we had to rollback the migration because of a nasty
>> bug. This is fixed in recent
I've sort of had some progress. On Friday I went to the dentist and when
I returned, my VM could ping google.
I don't believe I changed anything Friday morning but I confess I've
been flailing on this for so long I'm not keeping detailed notes on what
I change. And as I'm evaluating oVirt as
> On 3 May 2018, at 11:40, Simon Coter wrote:
>
> Hi,
>
> I'm new to this ML.
> I started to play a bit with oVirt and I saw that you actually support RH and
> CentOS.
> Is there any plan to also support Oracle Linux ?
nope
why would you want to use OL? Supposing you
Hi Marcin,
Thank you for your response.
I used engine-setup to do the configuration. Only exception is that I
had to run "vdsm-tool ovn-config engine-ip local-ip" (ie. vdsm-tool
ovn-config 10.0.1.101 10.0.1.21) on hypervisors.
Here is the output of requested commands:
[root@oe ~]#
20 matches
Mail list logo