This was one of my fears regarding the IBM acquisition. I guess we
can't complain too much, it's not like anybody *pays* for CentOS. :)
On 12/8/2020 3:14 PM, Strahil Nikolov via Users wrote:
> Yeah,
> the main problem is that Stream won't be as stable as RHEL (which also
> has tons of bugs) and
Thanks for the response. The issue was that I had to run engine-setup
after running yum updates. The rpms do not appear to do this or tell
you that you need to run the command. :)
On 7/10/2020 3:22 AM, Martin Perina wrote:
>
>
> On Thu, Jul 9, 2020 at 7:07 PM Strahil Nikolov via Users
>
After installing updates on our ovirt-engine running CentOS 7.8 the
administration portal will no longer load. The engine.log shows an
error as follows.
2020-07-09 11:26:27,094-04 ERROR
[org.ovirt.engine.core.bll.GetConfigurationValuesQuery] (default task-2)
IMO forums are worse than mailing lists. Email lists are decentralized,
can be searched offline, and don't require singing up for yet another
web site.
Of course I wouldn't even mind going back to usenet...
On 1/13/20 11:16 AM, Strahil wrote:
> I can admit that I also struggle with the search.
For what it's worth there *is* an ovirt subreddit.
https://www.reddit.com/r/ovirt/
On 1/14/20 12:51 PM, m.skrzetu...@gmail.com wrote:
> Sure but it's like building a web frontend for parsing and displaying CSV
> files.
>
>> there is a web frontend for the mailing list at
>>
I need to migrate running VMs from one host in our cluster to another
however the task keeps failing any time I start a migration. The engine
logs show a few different errors as follows.
2019-07-10 09:53:19,440-04 ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
Same here. Our engine is configured to use iptables and works fine. I
really wish RedHat would stop trying to force firewalld on everything.
It isn't needed and causes issues with environments using the
puppetlabs-firewall module.
On 7/4/19 3:17 PM, Darrell Budic wrote:
> I’m in the same boat,
change..
>
> On Thu, May 16, 2019 at 7:14 AM Michael Watters <mailto:watte...@watters.ws>> wrote:
>
> Had the same message on our cluster. The solution was to click
> edit on each host and refetch the ssh host key. I'm not sure why
> this is nec
Had the same message on our cluster. The solution was to click edit on
each host and refetch the ssh host key. I'm not sure why this is
necessary in the first place however.
On 5/14/19 3:15 PM, Andrew DeMaria wrote:
> Hi,
>
> I am running ovirt 4.3 and have found the following action item
>
> 2018-09-13 12:59:02,171+03 INFOProfile='ldap23.exalt.ps'
> authn='ldap23.exalt.ps-authn' authz='ldap23.exalt.ps-authz' mapping='null'
2018-09-13 12:59:02,171+03 INFOAPI:
-->Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS profile='ldap23.exalt.ps'
user='user002'
using "System" but that does not work despite our
internal CA being installed as a trusted certificate authority.
On 09/11/2018 10:07 AM, Michael Watters wrote:
> I've just upgraded our ovirt engine server to ovirt 4.6 and it appears
> that LDAP logins no longer work. When I attempt to
I've just upgraded our ovirt engine server to ovirt 4.6 and it appears
that LDAP logins no longer work. When I attempt to log in using an AD
account the following errors are shown in the engine log.
2018-09-11 10:03:44,610-04 ERROR
[org.ovirt.engine.core.sso.servlets.InteractiveAuthServlet]
On 06/28/2018 02:18 AM, Michal Skrivanek wrote:
>
>> On 27 Jun 2018, at 16:47, Michael Watters wrote:
>>
>> Having the same issue after upgrading from ovirt 4.1 to 4.2.4.
>> Attempting to migrate any VM results in an immediate failure. The
>> engine log shows a
On 06/28/2018 02:18 AM, Michal Skrivanek wrote:
>
>> On 27 Jun 2018, at 16:47, Michael Watters wrote:
>>
>> Having the same issue after upgrading from ovirt 4.1 to 4.2.4.
>> Attempting to migrate any VM results in an immediate failure. The
>> engine log shows a
After upgrading our ovirt hosts to the 4.2.4 release two nodes are
unable to run VMs. The vdsm.log shows a failure which appears to be
related to firewalld.
2018-06-27 10:58:08,340-0400 ERROR (vm/5a42e1ed) [virt.vm]
(vmId='5a42e1ed-7b9f-42f2-b1c3-403276cf1cd9') The vm start process failed
Having the same issue after upgrading from ovirt 4.1 to 4.2.4.
Attempting to migrate any VM results in an immediate failure. The
engine log shows an error as follows.
2018-06-27 10:43:59,815-04 ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
(ForkJoinPool-1-worker-3) [] Migration
You should be able to use bonded interfaces with an IP on each VLAN
Interface for the ovirt hosts and the engine. For example, here is the
IP configuration for one of our VLANs.
10: bond3: mtu 1500 qdisc
noqueue state UP group default qlen 1000
link/ether 00:1b:21:5c:80:39 brd
don't have any role assigned to your user.
>
> Please check following documentation:
>
>
> https://www.ovirt.org/documentation/admin-guide/chap-Users_and_Roles/#user-authorization
>
>
> to understand permission model of oVirt.
>
> On 06/14/2018 02:39 PM, Michael Watters
correct for example by running the ldapsearch command with it.
>
> On 06/13/2018 05:33 PM, Michael Watters wrote:
>> I've ran the ovirt-engine-extension-aaa-ldap-setup command to configure
>> LDAP authentication using Active Directory however I am unable to
>> authenticate using
I've ran the ovirt-engine-extension-aaa-ldap-setup command to configure
LDAP authentication using Active Directory however I am unable to
authenticate using valid credentials. Here is the output show while
testing the login flow.
[ INFO ] Executing login sequence...
Login output:
No problem. I was able to work around the issue but it's something that
should be looked at.
On 06/12/2018 02:36 PM, Greg Sheremeta wrote:
> Please open a bug
> [https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-engine]
> and include your ui.log and the specific old and new ovirt
I am having an issue getting users to authenticate using the Active
Directory backend. I've installed the
ovirt-engine-extension-aaa-ldap-setup package and ran
ovirt-engine-extension-aaa-ldap-setup to configure everything however
users are unable to authenticate. Testing using my own account
After upgrading my engine to the 4.2 release I'm receiving an uncaught
exception error when I attempt to create a new cluster.
Uncaught exception occurred. Please try reloading the page. Details:
(TypeError) : Cannot read property 'b' of null
Please have your administrator check the UI logs
The
I actually managed to fix it. The ovirt-engine package was still on
version 4.1, after running yum update to upgrade everything to version
4.2 the engine-setup script was able to upgrade postgresql.
On 06/11/2018 11:31 AM, Simone Tiraboschi wrote:
>
>
> On Mon, Jun 11, 2018 at 4:31 PM
After installing the ovirt 4.2 repository and running engine-setup the
upgrade script fails with an error as shown below.
[ ERROR ] Postgresql client version is '9.5.9', whereas the version on
'localhost' is '9.2.23'. Please use a PostgreSQL server of version '9.5.9'.
Please note the
I am attempting to upgrade from ovirt-engine 4.1 to 4.2 however yum
updates are failing due to dependency conflicts.
[root@ovirt-engine yum.repos.d]# yum update "ovirt-*-setup*"
Loaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
* ovirt-4.2: mirrors.rit.edu
*
On 05/31/2018 06:43 AM, Ondra Machacek wrote:
> That's very strange, can you please share the upgrade log if you still
> have it?
>
Here's a copy of the upgrade log. The file is pretty large.
https://paste.fedoraproject.org/paste/I3WapJfAnzk81gEgKeeIDg/
> Also can you please share the output
, Alex K wrote:
> Are you using engine IP to login? Perhaps the sso default file was
> overwritten?
>
> Alex
>
> On Tue, May 29, 2018, 20:32 Michael Watters <mailto:watte...@watters.ws>> wrote:
>
> I recently upgraded one of our ovirt engines from 4.1 to the
I recently upgraded one of our ovirt engines from 4.1 to the 4.2.3
release and the admin account is no longer able to login. After
entering the user name and password I receive a message that states "The
user admin@internal is not authorized to perform login".
Is there a way to resolve this?
On 05/17/2018 09:06 AM, Yaniv Kaul wrote:
>
>
> On Wed, May 16, 2018 at 7:26 PM, Michael Watters <watte...@watters.ws
> <mailto:watte...@watters.ws>> wrote:
>
> Is it possible to have multiple engines with different versions of
> ovirt
> runnin
Is it possible to have multiple engines with different versions of ovirt
running in the same cluster? I am working on a plan to upgrade our
ovirt cluster to the 4.2 release however we would like to have a
rollback plan in case there are issues with the new engine.
We run Dell Poweredge R720s and R730s with 32 GB of RAM and quad Xeon
processors. Storage is provided by Dell MD3800i and Promise arrays
using iSCSI. The network is all 10 gigabit interfaces using 802.3ad
bonds. We actually just upgraded from 1 gigabit NICs since there were
some performance
rina
>
>
> On Thu, Oct 5, 2017 at 9:08 PM, Michael Watters <watte...@watters.ws> wrote:
>
>> I'm having some issues granting permissions to AD users in ovirt-engine
>> 4.1. Users can log in but receive an error as below.
>> The user u...@example.com@example.com
I'm having some issues granting permissions to AD users in ovirt-engine
4.1. Users can log in but receive an error as below.
The user u...@example.com@example.com is not authorized to perform login
I am also not able to grant this user any permissions through the admin
console. Entering a user
On Thu, 2017-05-04 at 14:56 +0200, Sandro Bonazzola wrote:
>
>
> On Thu, May 4, 2017 at 2:53 PM, Sandro Bonazzola
> Due to an issue with the publishing of the website, looks like the
> release notes are not yet published.
> Source for the release notes is available
> on
Is there a way to disable the guest agent needs to be installed warnings
in ovirt? I have guest VMs which cannot be updated due to having older
operating systems installed.
___
Users mailing list
Users@ovirt.org
On 05/03/2017 12:16 PM, Michal Skrivanek wrote:
>
>> On 3 May 2017, at 18:10, Michael Watters <watte...@watters.ws
>> <mailto:watte...@watters.ws>> wrote:
>>
>> I have a cluster of hosts that have just been upgraded to oVirt 4.1
>> however I am rece
I have a cluster of hosts that have just been upgraded to oVirt 4.1
however I am receiving an error from the engine when I attempt to
upgrade the cluster compatibility level.
Error while executing action: Cannot edit Cluster if some of the
specified custom properties are not configured by the
I've noticed the same issue on 4.0. Clicking OK *does* start the
upgrade but the dialog box doesn't update properly to notify you that it
is working. The issue happens in Chrome and Opera no matter what OS I
login from.
On 04/21/2017 12:50 PM, Nelson Lameiras wrote:
> Hello,
>
> Since
I have an ovirt host running ovirt 4.0 which keeps putting the VMs
running on that host into an unknown state. I checked the vdsm logs and
there are several errors similar to below.
Mar 20 10:16:11 ovirt-node-production3.example.com vdsm[17123]: vdsm root ERROR
Unhandled exception
Traceback
You can manually delete the domain from the database. Run a backup
first though.
On 03/07/2017 12:14 PM, Simon Vincent wrote:
> I have setup a small cluster running a hosted engine using iSCSI. I
> tried to add a new iSCSI storage domain but this failed as not all
> hosts could access the
Can you configure a *new* cluster and migrate the engine to that? You
should be able to import your existing storage domains and logical
networks under the new cluster which can then be used as a migration
target for any running VMs. Your other option would be to build a new
engine using 4.0 and
On 02/23/2017 10:28 AM, Francesco Romani wrote:
>
> The load/save state errors are most often found when the two sides of
> the migration have different and incompatible version of QEMU.
> In turn, this is quite often a bug, because forward migrations (e.g.
> from 2.3.0 to 2.4.0) are always
On 02/23/2017 10:28 AM, Francesco Romani wrote:
> On 02/23/2017 04:20 PM, Michael Watters wrote:
>> I have an ovirt cluster running ovirt 4.0 and I am seeing several errors
>> when I attempt to put one of our nodes into maintenance mode. The logs
>> on the source server s
I have an ovirt cluster running ovirt 4.0 and I am seeing several errors
when I attempt to put one of our nodes into maintenance mode. The logs
on the source server show errors as follows.
Feb 23 10:15:08 ovirt-node-production3.example.com libvirtd[18800]: operation
aborted: migration job:
On 02/21/2017 03:09 AM, Dan Kenigsberg wrote:
> On Mon, Feb 20, 2017 at 6:00 PM, Michael Watters <watte...@watters.ws> wrote:
>> I am building a new ovirt host running Ovirt 4.0 however I am receiving
>> UI errors when I attempt to define the host networks in the engine. Th
Thanks. I managed to get it working after changing the bonding options
in the /etc/sysconfig/network-scripts/bond0 file.
On 02/20/2017 11:31 AM, Yaniv Kaul wrote:
>
>
> On Mon, Feb 20, 2017 at 6:00 PM, Michael Watters <watte...@watters.ws
> <mailto:watte...@watters.ws>
I am building a new ovirt host running Ovirt 4.0 however I am receiving
UI errors when I attempt to define the host networks in the engine. The
engine logs show errors as follows.
2017-02-20 10:53:44,478 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
(default
Looks like the issue was caused by having my iscsi targeted hosted on an
LVM volume. I changed the target to use a raw disk (/dev/sdb) and disk
moves between pools are working now.
On 02/07/2017 03:23 PM, Michael Watters wrote:
> I have set up a new iSCSI storage pool in ovirt and attemp
I have set up a new iSCSI storage pool in ovirt and attempted to move a
disk from another iSCSI pool however the operation fails with the
following error.
* User admin@internal have failed to move disk centos7_template_Disk1 to
domain TempPool.
* VDSM mdct-ovirt-node-production1 command failed:
Thanks. I guess we'll just have to ignore these errors until the host
nodes get upgraded.
On Thu, 2017-02-02 at 17:38 +0100, Martin Perina wrote:
> Hi,
>
> unfortunately you have found a bug [1]. The workaround is to upgrade
> 3.6 host to 4.0, for 4.0+ package lists for "Check for upgrades"
My intention was to upgrade the ovirt-engine to 4.0 first and then the
host nodes when we can get to them.
On Thu, 2017-02-02 at 10:50 +0200, Yedidyah Bar David wrote:
> On Wed, Feb 1, 2017 at 10:45 PM, Victor Jose Acosta om> wrote:
> > So, that's the problem, engine is
I'm also seeing this error using a Dell MD3800i array. The multipath
errors shown in our logs are different however.
Feb 1 15:11:58 ovirt-node-production2 kernel: dd: sending ioctl
80306d02 to a partition!
Feb 1 15:21:01 ovirt-node-production2 multipathd: dm-31: remove map
(uevent)
Feb 1
The engine is 4.0, the host nodes are running 3.6 with VDSM 4.17.35.
On 02/01/2017 02:41 PM, Victor Jose Acosta wrote:
> Hello
>
> ovirt-imageio-daemon is part of ovirt 4 repository, is your engine
> version 4 or 3.6?
___
Users mailing list
I don't think IPv6 is the cause. When the engine checks for updates
there is a yum error shown in the debug logs as follows.
2017-02-01 10:38:39 INFO otopi.plugins.ovirt_host_mgmt.packages.update
update.info:98 Yum: Performing yum transaction rollback
2017-02-01 10:38:39 DEBUG otopi.context
I have ovirt-engine 3.6 set up on a dedicated host which is managing two
ovirt hosts. I am seeing errors when the engine attempts to check for
updates as follows.
Failed to check for available updates on host ovirt-node-production2 with
message 'Command returned failure code 1 during SSH
he nodes via /proc etc. Storing this into RRD databases and
> doing a little LAMP scripting you get the attached result.
>
> Best regards.
>
> Markus
>
>
> Von: users-boun...@ovirt.org [users-boun...@ovirt.org] im Auftrag von
&g
Does ovirt have any way to monitor disk I/O for each VM or disk in a
storage pool? I am receiving disk latency warnings and would like to
know which VMs are causing the most disk I/O.
___
Users mailing list
Users@ovirt.org
urious what to expect.
>
> On Thu, Jan 19, 2017 at 10:42 AM, Michael Watters
> <michael.watt...@dart.biz <mailto:michael.watt...@dart.biz>> wrote:
>
> You can upgrade vdsm without upgrading to ovirt 4. I went through the
> same issue on our cluster a fe
Looks like Office 365 likes to mangle hyperlinks. The correct URL for
the git repo should be github.com/oVirt/vdsm.git.
On Thu, 2017-01-19 at 17:42 +, Michael Watters wrote:
> You can upgrade vdsm without upgrading to ovirt 4. I went through
> the
> same issue on our cluster a
You can upgrade vdsm without upgrading to ovirt 4. I went through the
same issue on our cluster a few weeks ago and the process was pretty
simple.
You'll need to do this on each of your hosts.
yum --enablerepo=extras install -y epel-release git
git clone https://github.com/oVirt/vdsm.git
cd
I'm getting yum errors when I try to update the ovirt-release40 package
on our engine.
>ovirt-release40-4.0.6-1.noarch FAILED
http://mirror.isoc.org.il/pub/ovirt/ovirt-4.0/rpm/el7/noarch/ovirt-release40-4.0.6-1.noarch.rpm:
[Errno -1] Package does not
Thank you. That appears to have fixed it.
On Mon, 2017-01-09 at 15:02 -0500, Robert Story wrote:
> On Mon, 9 Jan 2017 19:35:13 + Michael wrote:
> MW> After upgrading to ovirt-engine 4 some of our users are receiving
> a
> MW> message as follows.
> MW>
> MW> > The client is not authorized
gt; # yum --enablerepo=extras install centos-release-qemu-ev
>
> -Original Message-
> From: Michael Watters <michael.watt...@dart.biz>
> Date: Monday 9 January 2017 at 19:19
> To: "Users@ovirt.org" <Users@ovirt.org>, Pavel Gashev <p...@acronis.co
> m>
After upgrading to ovirt-engine 4 some of our users are receiving a
message as follows.
> The client is not authorized to request an authorization. It's required to
> access the system using FQDN.
Is there a way to direct ovirt login requests to the server's FQDN
using mod_rewrite? I placed
Thanks, that's kind of what I'm discovering. Is it possible for an
ovirt 4 host to join a 3.6 cluster? Do I need to upgrade my engine
first? We are running ovirt-engine 3.6 on a dedicated server which
manages two ovirt nodes right now.
On Sat, 2017-01-07 at 09:30 +, Pavel Gashev wrote:
>
t; # yum --enablerepo=extras install -y epel-release git
> # git clone https://github.com/oVirt/vdsm.git
> # cd vdsm
> # git checkout v4.17.35
> # yum install -y `cat ./automation/build-artifacts.packages`
> # ./automation/build-artifacts.sh
>
> -Original Message-
Is there a way to upgrade vdsm without upgrading everything else?
On Sat, 2017-01-07 at 09:36 +, Pavel Gashev wrote:
> The same is here. Upgrade vdsm to 4.17.35.
>
> -Original Message-
> From: <users-boun...@ovirt.org> on behalf of Michael Watters .watt..
I am receiving several LVM errors when attempting to move a disk from
one storage domain to another.
> VDSM ovirt-node-production2 command failed: Logical Volume extend
failed
vdsm.log shows a failure message as follows.
> d6d4529e-db0d-49ac-a0c3-ee9d2e8cc9bb::ERROR::2017-01-06
Hello,
I have two hosts in a cluster running ovirt 3.6 and I keep seeing
errors in the event log as follows.
Jan 5, 2017 2:34:01 PM

Host ovirt-node-production2 power management was verified successfully.

Jan 5, 2017 2:34:01 PM

Status of host ovirt-node-production2 was set to Up.

I am running ovirt 3.6 on our cluster and VM migration is failing. The
VDSM logs show an error as follows.
jsonrpc.Executor/7::ERROR::2016-12-16
08:41:04,398::vm::4714::virt.vm::(_updateDevicesDomxmlCache)
vmId=`dc419d2b-522a-4e96-b06a-243ec8ede44e`::Alias not found for device type
redir
I have two brand new ovirt hosts running ovirt 3.6 which are giving a
warning message whenever the host is activated.
>Kdump integration is enabled for host ovirt-node-production1, but
kdump is not configured properly on host.
The server does have the kdump package installed and the service is
72 matches
Mail list logo