I had a similar issue.
for me, taking the password from
/etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-grafana-database.conf
(GRAFANA_DB_PASSWORD)
and set that password in postgres for the
user ovirt_engine_history_grafana did the trick.
Best
Mo
On 7/14/22 16:28, Andrei Verovski wr
On 7/14/22 16:37, Moritz Baumann wrote:
I had a similar issue.
for me, taking the password from
/etc/ovirt-engine-dwh/ovirt-engine-dwhd.conf.d/10-setup-grafana-database.conf
(GRAFANA_DB_PASSWORD)
and set that password in postgres for the
user ovirt_engine_history_grafana did the trick
forgot to mention
ovirt is 4.5.1 on centos8-stream, nodes are ovirt-node-4.5.1
It's an old installation originating from 3.6 initially.
On 7/14/22 08:18, Moritz Baumann wrote:
Hi
I have removed the iso domain of an existing data center, and now I am
unable to create a new iso d
Hi
I have removed the iso domain of an existing data center, and now I am
unable to create a new iso domain
/var/log/ovirt-engine/engine.log shows:
2022-07-14 08:04:40,684+02 INFO
[org.ovirt.engine.core.bll.storage.connection.AddStorageServerConnectionCommand]
(default task-34) [8db814e3-43
Hi
after upgrade from ovirt-4.4 -> ovirt 4.5
We had to face the jdbc problem and that we had old database enties
which prohibited an upgrade.
I had dropped all dbs and restored from engine backup but now
I get the following error when I want to upgrade again
[root@ovirt-engine ~]# engine-set
Thank you Simone,
that worked.
On 19.02.19 12:40, Simone Tiraboschi wrote:
On Tue, Feb 19, 2019 at 12:18 PM Moritz Baumann
mailto:moritz.baum...@inf.ethz.ch>> wrote:
After upgrading from 4.2 -> 4.3 I cannot start a vm anymore.
I try to start the vm with run once on a
After upgrading from 4.2 -> 4.3 I cannot start a vm anymore.
I try to start the vm with run once on a specific node (ovirt-node04)
and this is the output of /var/log/vdsm/vdsm.log
2019-02-19 12:08:33,626+0100 INFO (jsonrpc/6) [api.host] START
getAllVmStats() from=:::129.132.17.194,33924
After installing a RHEL7.5 server and adding the host via ovirt-engine
it initially works, but afterwards it findes the followgin upgrades
which break e.g. yum:
-> Running transaction check
---> Package pyOpenSSL.x86_64 0:0.13.1-3.el7 will be obsoleted
---> Package python-dateutil.noarch 0:1.5
Hi Neil,
I had similar errors ('Sanlock lockspace add failure' and SPM problems,
...) in the log files and my problem was that I added the "-g" option
to mountd (months ago without restarting the service) in
/etc/sysconfig/nfs under RPCMOUNTDOPTS.
I had to either remove the "-g" option or a
On 19.06.2017 11:51, Markus Stockhausen wrote:
Maybe NFS Mounts with Version 4.2 and on Server side no SELinux nfs_t
rule defined?
Both (nfs-server and ovirt host) are in selinux permissive mode.
___
Users mailing list
Users@ovirt.org
http://lists.
Is there a way to "reinitialize" the lockspace so one node can become
SPM again and we can run VMS.
errors in /var/log/sanlock.log look like this:
2017-06-19 10:57:00+0200 1617673 [126217]: open error -13
/rhev/data-center/mnt/scratch-inf.inf.ethz.ch:_export_scratch_ovirt_data/c17d9d7f-e578-4
Hi,
I'm still strugling to get our ovirt 4.1.2 back to life.
The data domain is nfs and the nfs mount works fine. However it appears
that the sanlock does not work anymore.
Is there a way to "reinitialize" the lockspace so one node can become
SPM again and we can run VMS.
Best,
Mo
_
Hi Adam,
Just an idea, but could this be related to stale mounts from when you
rebooted the storage? Please try the following:
1. Place all nodes into maintenance mode
2. Disable the ovirt NFS exports
1. Comment out lines in /etc/exports
2. exportfs -r
3. Reboot your nodes
4. Re
I found some info on how to import an abandomed export domain
https://www.ovirt.org/documentation/how-to/storage/clear-the-storage-domain-pool-config-of-an-exported-nfs-domain/
would the same (empty POOL_UUID and SHA_CKSUM in metadata) allow me to
import the data domain as a new one (and keep t
it is nfs3 based and I did an upgrade from RHEL 6.8 -> 6.9 and rebooted
the storage. I paused all running vms but forgot to put the storage
domains into maintenance.
scratch-inf[0]:/export/scratch/ovirt# ls -lr *
iso:
total 0
-rwxr-xr-x. 1 36 kvm 0 29. Mai 18:02 __DIRECT_IO_TEST__
drwxr-xr-x.
Hi,
after an upgrade I get the following errors in the web gui:
VDSM ovirt-node01 command SpmStatusVDS failed: (13, 'Sanlock resource
read failure', 'Permission denied')
VDSM ovirt-node03 command HSMGetAllTasksStatusesVDS failed: Not SPM
These messages happen from all nodes.
I can sto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I don't see any users in ovirt after running
engine-manage-domains add --domain=EXAMPLE.ORG --provider=ipa \
- --user=baumadm --add-permissions
only the user baum...@example.org is shown with an enabled=False.
Ipa appears to be setup correct sin
17 matches
Mail list logo
