Re: Can't join new mon - lossy channel, failing
by Konstantin Shalygin
Hi,
> On 4 Oct 2021, at 16:37, Vladimir Bashkirtsev <vladimir(a)bashkirtsev.com> wrote:
>
> And just for clarity: you do not attempt to join mixed 32/64 bit cluster? There's a known bug in src/msg/async/frames_v2.h causing frame size mismatch on mixed clusters leading to the same error messages.
All hardware is x86_64
k
2 years, 6 months
qemu-guest-agent not reporting IP address on boot?
by c.schreuders＠leedsbeckett.ac.uk
Hi folks,
Kali Linux repos (based on Debian) no longer ship ovirt-guest-agent, and instead package qemu-guest-agent. However, since this upgrade VMs based on Kali no longer report their IP address to oVirt (and therefore timeout during provisioning). If I interact with the VM console, the VM does have an IP address, and the agent is running, yet oVirt reports N/A IP address. I've tried restarting the agent, but that does not help. If I load the console and use the VM it seems to increase the chances the IP address will eventually makes it's way to oVirt, although I can't seem to reproduce an update, or get it to provide the IP address on boot so that provisioning works reliably.
Any suggestions would be really appreciated.
Thank you.
Cheers,
Cliffe.
2 years, 6 months
Re: Upgrading from 4.3 to 4.4.8
by Gianluca Cecchi
On Mon, Oct 4, 2021 at 12:32 AM Jason Harris <jasonmicron(a)gmail.com> wrote:
> Engine is updated to the latest 4.3 release and rebooted. Still getting
> this after re-enabling the 4.4 repo:
>
>
oVirt 4.4 requires engine and hosts based on RH EL / CentOS 8, while your
current env in 4.3 has them based on RH EL 7 / CentOS 7. You have to
reinstall the node that you isolated with the engine.
So after taing the engine at its latest 4.3.x level and rebooting the 4.3
engine OS, you have to follow the steps described in 6.5: stop the
ovirt-engine service, take a backup and copy the generated file outside of
the env, scratch the engine and related node and reinstall it with 4.4
ovirt node and then on the host, now in 4.4, run the command
hosted-engine --deploy --restore-from-file=backup.bck
and so on...
Gianluca
2 years, 6 months
Re: oVirt 4.3 DWH with Grafana
by Tommy Sway
Thank you!
I tried it, and I can import the json after replace the 4.4 with 4.3, but still have some errors like this:
pq: column "count_threads_as_cores" does not exist
Object
status:400
statusText:"Bad Request"
data:Object
results:Object
message:"pq: column "count_threads_as_cores" does not exist"
message:"pq: column "count_threads_as_cores" does not exist"
Many of the other reports worked fine, with only a few similar errors.
Is this caused by version incompatibility?
After all, 4.4 in the original document was replaced with 4.3 before the import.
From: Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com>
Sent: Wednesday, September 15, 2021 3:28 AM
To: Tommy Sway <sz_cuitao(a)163.com>; 'Michal Gutowski' <michal.gutowski(a)oracle.com>; 'Vrgotic, Marko' <M.Vrgotic(a)activevideo.com>
Cc: users(a)ovirt.org
Subject: RE: [ovirt-users] Re: oVirt 4.3 DWH with Grafana
The instructions to modify the json files are missing. (Using find and sed to change all instances of v4_4_ to v4_3_ before importing them into Grafana)
This is from an Oracle Blog on the doing this with OLVM 4.3 (which is basically a repackaged oVirt 4.3)
Build Grafana Dashboard for Oracle Linux Virtualization Manager 4.3 <https://blogs.oracle.com/scoter/post/build-grafana-dashboard-for-oracle-l...>
From: Tommy Sway <sz_cuitao(a)163.com <mailto:sz_cuitao@163.com> >
Sent: Tuesday, September 14, 2021 3:01 AM
To: 'Michal Gutowski' <michal.gutowski(a)oracle.com <mailto:michal.gutowski@oracle.com> >; 'Vrgotic, Marko' <M.Vrgotic(a)activevideo.com <mailto:M.Vrgotic@activevideo.com> >
Cc: users(a)ovirt.org <mailto:users@ovirt.org>
Subject: [ovirt-users] Re: oVirt 4.3 DWH with Grafana
The oVirt version I'm using is 4.3, and I get an error when I import JSON.
pq: relation"v4_4_latest_configuration_datacenters" does not exist.
From: users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org> <users-bounces(a)ovirt.org <mailto:users-bounces@ovirt.org> > On Behalf Of Michal Gutowski
Sent: Wednesday, November 25, 2020 12:26 AM
To: Vrgotic, Marko <M.Vrgotic(a)activevideo.com <mailto:M.Vrgotic@activevideo.com> >
Cc: users(a)ovirt.org <mailto:users@ovirt.org>
Subject: [ovirt-users] Re: oVirt 4.3 DWH with Grafana
Hi Marko,
I've tested this myself as I like playing with various Grafana use-cases and following steps allow you to set up Grafana Monitoring for your oVirt 4.3 environment and re-use all Grafana Dashboards from latest oVirt 4.4 on a previous release.
1. Allowing Grafana to connect to oVirt DWH database (Data Warehouse)
Login to the oVirt engine 4.3 and create a user "grafana" with password "grafana" that will get a read-only access to the ovirt_engine_history database and will be able to use public schema
# su - postgres -c 'scl enable rh-postgresql10 bash'
# psql -U postgres -c "CREATE ROLE grafana WITH LOGIN ENCRYPTED PASSWORD 'grafana';" -d ovirt_engine_history
# psql -U postgres -c "GRANT CONNECT ON DATABASE ovirt_engine_history TO grafana;"
# psql -U postgres -c "GRANT USAGE ON SCHEMA public TO grafana;" ovirt_engine_history
Generate the rest of the permissions that will be granted to the newly created user and save them to a file:
# psql -U postgres -c "SELECT 'GRANT SELECT ON ' || relname || ' TO grafana;' FROM pg_class JOIN pg_namespace ON pg_namespace.oid = pg_class.relnamespace WHERE nspname = 'public' AND relkind IN ('r', 'v');" --pset=tuples_only=on ovirt_engine_history > grant.sql
Use the file you created in the previous step to grant permissions to the newly created user:
# psql -U postgres -f grant.sql ovirt_engine_history
Remove the file you used to grant permissions:
# rm grant.sql
Exit the postgres user shell by pressing Ctrl+d
Add the following lines for the newly created user to /var/opt/rh/rh-postgresql10/lib/pgsql/data/pg_hba.conf preceding the line beginning local all all
host ovirt_engine_history grafana 0.0.0.0/0 md5
host ovirt_engine_history grafana ::0/0 md5
Reload postgres service
# systemctl reload rh-postgresql10-postgresql
2. Installing Grafana
You can install Grafana directly on the oVirt Engine machine (this is how it's done in oVirt 4.4) or on a separate machine. Following steps shows how you can install Grafana on a Oracle Linux 7 server. Note: Oracle provides Grafana in the OLCNE yum repository - you only need to install the repository definition package to pickup Grafana and it's dependencies.
# yum install oraclelinux-release-el7
# yum install oracle-olcne-release-el7
# yum-config-manager --enable ol7_optional_latest ol7_olcne11
# yum install grafana
# systemctl enable --now grafana-server
3. Adding oVirt DWH database as Data Source in Grafana
Login to Grafana (default port 3000) and navigate to Configuration -> DataSources and click on Add Data Source button.
Select PostgreSQL source and use the following settings (adjust the Host IP address to match your oVirt Engine IP but do not change the Name):
Name: oVirt DWH
Host: your-engine-ip-address:5432
user: grafana
pass: grafana
SSL mode: disable
4. Importing Dashboards from oVirt 4.4
Download Grafana Dashboards from oVirt 4.4 repository: https://github.com/oVirt/ovirt-dwh/tree/master/packaging/conf/grafana-das...
You can now import them in Grafana by navigating to Create -> Import and clicking on Upload .json file or by simply pasting JSON content.
I've tested this on my OLVM/oVirt 4.3 and works perfectly well.
Have fun!
Michal
Michał Gutowski
Principal Solutions Engineer, EMEA
+48 665 222 979
Oracle Open Cloud Infrastructure Software - Linux & Virtualization
On 24 Nov 2020, at 11:53, Vrgotic, Marko <M.Vrgotic(a)activevideo.com <mailto:M.Vrgotic@activevideo.com> > wrote:
Dear oVirt folks,
Thank you all for suggestions.
I will give it a go and see how far I get.
-----
kind regards/met vriendelijke groeten
Marko Vrgotic
Sr. System Engineer @ System Administration
ActiveVideo
o: +31 (35) 6774131
m: +31 (65) 5734174
e: <mailto:m.vrgotic@activevideo.com> m.vrgotic(a)activevideo.com
w: <https://urldefense.com/v3/__http:/www.activevideo.com__;!!GqivPVa7Brio!MN...> www.activevideo.com
ActiveVideo Networks BV. Mediacentrum 3745 Joop van den Endeplein 1.1217 WJ Hilversum, The Netherlands. The information contained in this message may be legally privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or ActiveVideo Networks, LLC by telephone at +1 408.931.9200 and delete or destroy any copy of this message.
From: Yedidyah Bar David <didi(a)redhat.com <mailto:didi@redhat.com> >
Date: Sunday, 22 November 2020 at 08:39
To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com <mailto:M.Vrgotic@activevideo.com> >
Cc: "users(a)ovirt.org <mailto:users@ovirt.org> " <users(a)ovirt.org <mailto:users@ovirt.org> >
Subject: Re: [ovirt-users] oVirt 4.3 DWH with Grafana
***CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender!!!***
On Fri, Nov 20, 2020 at 8:45 AM Vrgotic, Marko <M.Vrgotic(a)activevideo.com <mailto:M.Vrgotic@activevideo.com> > wrote:
Dear oVirt,
We are currently running oVirt 4.3 and upgrade/migration to 4.4 won’t be possible for few more months.
I am looking into guidelines, how to, for setting up Grafana using DataWarehouse as data source.
Did anyone already did this, and would be willing to share the steps?
AFAIU this is definitely not tested/recommended/supported, but the current (4.4) dashboards use only 4.3 dwh compatibility views. So in theory, 4.4 grafana setup can work against your 4.3 engine/dwh without problems. So you can try something like:
1. Install el8 on some machine
2. Install ovirt-release (4.4!)
3. Install ovirt-engine-dwh-grafana-integration-setup. I *think*, didn't try, that it would carry with it all the dependencies it needs.
4. Run engine-setup. When prompted, only accept "Configure grafana?", and reply "No" to everything else
5. Follow the other prompts as applicable
This should be enough.
Not sure about the commands to add SSO on the engine machine. Perhaps better verify this first against a test engine (can be on another el7/ovirt4.3 VM with no hosts).
But, repeating: this isn't recommended.
Did you consider upgrading only your engine, and keep your hosts 4.3 until you can upgrade them later?
Best regards,
--
Didi
_______________________________________________
Users mailing list -- <mailto:users@ovirt.org> users(a)ovirt.org
To unsubscribe send an email to <mailto:users-leave@ovirt.org> users-leave(a)ovirt.org
Privacy Statement: <https://urldefense.com/v3/__https:/www.ovirt.org/privacy-policy.html__;!!...> https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!...
oVirt Code of Conduct: <https://urldefense.com/v3/__https:/www.ovirt.org/community/about/communit...> https://urldefense.com/v3/__https://www.ovirt.org/community/about/communi...
List Archives: <https://urldefense.com/v3/__https:/lists.ovirt.org/archives/list/users@ov...> https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@o...
2 years, 6 months
Live domain migration breaks Windows (UEFI) vitrual machine
by Patrick Lomakin
Greetings! I've already mentioned the problem of live disk migration between different storage domains, but yesterday I found the same problem in a new oVirt installation.
My actions after deploying oVirt are:
1) Created a storage domain (iSCSI and Gluster);
2) Created a virtual machine with Windows 10 (UEFI);
3) Placed the virtual machine on the Gluster domain;
4) Started the virtual machine and started moving the disk from the Gluster storage domain to iSCSI.
The disk move process was successful and error free and the virtual machine worked. However, after a reboot, the machine no longer started. The boot goes into recovery mode. All attempts to restore the machine to work were unsuccessful. I want to note that this does not happen if the machine was turned off during the disk move. In this case, it starts up without any problems. The type of domain from or to which the disk is migrated does not important. In case of live migration the Windows (UEFI) VM crashes in any case.
2 years, 6 months
Upgrading from 4.3 to 4.4.8
by jasonmicron＠gmail.com
You guys scare me. Seriously.
I'm trying to update from oVirt 4.3 to 4.4 using a self-hosted engine. All VMs on the host are migrated off, other than the hosted engine, from the first host I intend to update to EL 8.4, per the documentation.
I installed the RPM from here: https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
I'm configuring the Engine following the upgrade document located here:
https://www.ovirt.org/documentation/upgrade_guide/index.html#SHE_Upgradin...
Step 6.4, after installing the oVirt 4.4 RPM on the engine:
engine-upgrade-check - I get this response:
[root@labmanager yum.repos.d]# engine-upgrade-check
VERB: queue package ovirt-engine-setup for update
VERB: Downloading: ovirt-4.3-epel/x86_64/metalink (0%)
VERB: Downloading: ovirt-4.3-epel/x86_64/metalink 10 k(100%)
FAIL: Cannot queue package ovirt-engine-setup: Cannot find a valid baseurl for repo: ovirt-4.4/7
OK: Performing yum transaction rollback
Error: Cannot find a valid baseurl for repo: ovirt-4.4/7
Doing a 'yum update' to just validate yum is working correctly, after installing the 44 RPM, I get this:
Cannot find a valid baseurl for repo: ovirt-4.4/7
Any advice? Is the repo just not valid at the moment? Did someone forget to run a 'createrepo' after updating the YUM/DNF repo?
2 years, 6 months
Reinstall without dataloss
by hans＠jiflin.nl
Hi all,
I am new here, been searching the mailing list on a regular base when I encountered problems and till now I always was able to keep the system up & running.
As said... till now...
I have oVirt at home, and I have about 7 vm's running on it. Lately I have had some troubles with my electricity, which results in a complete power outage on a irregular base.
Yesterday I had a power outage which left the system unbootable with the following errors:
error: ../../grub-core/loader/i386/pc/linux.c:170:invalid magic number.
error: ../../grub-core/loader/i386/pc/linux.c:1418:you need to load the kernel first.
Press any key to continue
Normally this can be solved following https://access.redhat.com/solutions/5829141, but his time also the files in /boot had a size of 0 bytes. So basically i did not have a working kernel on the system anymore.
https://www.thegeekdiary.com/centos-rhel-7-how-to-install-kernel-from-res... does work for CentOS 8 also, but the ovirt 4.8 iso does not have the same directory structure. Using CentOS 8 installs a kernel, but not a bootable system.
Is there a way i can start the installer in troubleshooting mode so I can reinstall just the kernel on the system?
2 years, 6 months
gluster 5834 Unsynced entries present
by Dominique D
yesterday I had a glich and my second ovnode2 server restarted
here are some errors in the events :
VDSM ovnode3.telecom.lan command SpmStatusVDS failed: Connection timeout for host 'ovnode3.telecom.lan', last response arrived 2455 ms ago.
Host ovnode3.telecom.lan is not responding. It will stay in Connecting state for a grace period of 86 seconds and after that an attempt to fence the host will be issued.
Invalid status on Data Center Default. Setting Data Center status to Non Responsive (On host ovnode3.telecom.lan, Error: Network error during communication with the Host.).
Executing power management status on Host ovnode3.telecom.lan using Proxy Host ovnode1.telecom.lan and Fence Agent ipmilan:10.5.1.16.
Now my 3 bricks have errors from my gluster volume
[root@ovnode2 ~]# gluster volume status
Status of volume: datassd
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
Brick ovnode1s.telecom.lan:/gluster_bricks/
datassd/datassd 49152 0 Y 4027
Brick ovnode2s.telecom.lan:/gluster_bricks/
datassd/datassd 49153 0 Y 2393
Brick ovnode3s.telecom.lan:/gluster_bricks/
datassd/datassd 49152 0 Y 2347
Self-heal Daemon on localhost N/A N/A Y 2405
Self-heal Daemon on ovnode3s.telecom.lan N/A N/A Y 2366
Self-heal Daemon on 172.16.70.91 N/A N/A Y 4043
Task Status of Volume datassd
------------------------------------------------------------------------------
There are no active volume tasks
gluster volume heal datassd info | grep -i "Number of entries:" | grep -v "entries: 0"
Number of entries: 5759
in the webadmin all the bricks are green with comments for two :
ovnode1 Up, 5834 Unsynced entries present
ovnode2 Up,
ovnode3 Up, 5820 Unsynced entries present
I tried this without success
gluster volume heal datassd
Launching heal operation to perform index self heal on volume datassd has been unsuccessful:
Glusterd Syncop Mgmt brick op 'Heal' failed. Please check glustershd log file for details.
What are the next steps ?
Thank you
2 years, 6 months
about the expiration time of the oVirt certs
by Tommy Sway
As you know, there are many kinds of certificates in Ovirt, used for
communication, authentication and so on.
However, in practice, there is a security risk related to the above
certificates.
That is, you need to generate a new certificate after the certificate
expires. Otherwise, a problem will occur.
In addition, different certificates expire at different times, which brings
a lot of management trouble to users.
Especially in the production system, a huge virtualization cluster may run
thousands of VMS. If a cluster certificate has a problem, the impact is very
serious.
So I felt there was an urgent need for a technical tool that could help
users quickly locate certificates, identify their expiration dates, and
rebuild them.
Even if there is no tool, there should be a way to solve the problems caused
by partial certificate expiration. I think it should include the following
points:
First, how to list the certificate in detail
Second, how to check the certificate expiration time
Third, how to rebuild the certificate
Does anyone else have this kind of confusion? What's a good solution?
Thanks.
2 years, 6 months
