- Devel - oVirt List Archives

[ANN] oVirt 4.4.6 Fourth Release Candidate is now available for testing
by Sandro Bonazzola 15 Apr '21

15 Apr '21

oVirt 4.4.6 Fourth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.6 Fourth Release Candidate for testing, as of April 15th, 2021. This update is the sixth in a series of stabilization updates to the 4.4 series. Rebase on CentOS Stream Starting with oVirt 4.4.6 RC4 both oVirt Node and oVirt Engine Appliance are based on CentOS Stream. You can still install oVirt 4.4.6 on Red Hat Enterprise Linux, CentOS Linux or equivalent. Please note that when 4.4.6 will be released as generally available, existing oVirt Nodes updating to 4.4.6 will automatically be based on CentOS Stream. Help testing this release candidate will help ensuring a smooth experience for your main installation. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.6 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.6 (redeploy in case of already being on 4.4.6). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Known issues: - Bug 1946095 <https://bugzilla.redhat.com/show_bug.cgi?id=1946095> - "No valid network interface has been found" when starting HE deployment via cockpit - For testing purposes you can use the command line <https://ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_us…> Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.3 or newer * CentOS 8 Stream * CentOS Linux (or similar) 8.3 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS 8 Stream * CentOS Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS 8 Stream (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available based on CentOS 8 Stream - oVirt Node NG is already available based on CentOS 8 Stream Additional Resources: * Read more about the oVirt 4.4.6 release highlights: http://www.ovirt.org/release/4.4.6/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.6/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

ovirt-engine has been tagged (ovirt-engine-4.4.6.4)
by Tal Nisan 14 Apr '21

14 Apr '21

1 0

DB error during engine upgrade in dev environment
by Vojtech Juranek 12 Apr '21

12 Apr '21

Hi, I'm trying to upgrade my engine dev environment to latest master, but during $HOME/ovirt-engine/bin/engine-setup I'm getting error bellow even when I run with full DB vacuum. Any idea how to fix it? Thanks Vojta 2021-04-12 08:45:41,395-0400 DEBUG otopi.context context._executeMethod:145 method exception Traceback (most recent call last): File "/usr/lib/python3.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/home/**FILTERED**/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/bin/../plugins/ovirt-**FILTERED**-setup/ovirt-**FILTERED**/config/public_glance_repository.py", line 69, in _misc storage_domain_id="072fbaa1-08f3-4a40-9f34-a5ca22dd1d74" File "/home/**FILTERED**/ovirt-**FILTERED**/share/ovirt-**FILTERED**/setup/ovirt_**FILTERED**_setup/**FILTERED**_common/database.py", line 258, in execute args, psycopg2.ProgrammingError: function inst_add_glance_provider(unknown, unknown, unknown, unknown, unknown) does not exist LINE 2: select inst_add_glance_provider( ^ HINT: No function matches the given name and argument types. You might need to add explicit type casts. 2021-04-12 08:45:41,396-0400 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Misc configuration': function inst_add_glance_provider(unknown, unknown, unknown, unknown, unknown) does not exist LINE 2: select inst_add_glance_provider( ^ HINT: No function matches the given name and argument types. You might need to add explicit type casts.

3 3

Merge rights changes in the oVirt Engine project
by Tal Nisan 09 Apr '21

09 Apr '21

Hi everyone, As you probably know we are now in a mode in which we develop our next zstream version on the master branch as opposed to how we worked before where the master version was dedicated for the next major version. This makes the rapid changes in master to be delivered to customers in a much higher cadence thus affecting stability. Due to that we think it's best that from now on merges in the master branch will be done only by stable branch maintainers after inspecting those closely. What you need to do in order to get your patch merged: - Have it pass Jenkins - Have it get code review +2 - Have it mark verified +1 - It's always encourage to have it tested by OST, for bigger changes it's a must Once you have all those covered, please add me as a reviewer and I'll examine it and merge if everything seems right, if I haven't done it in a timely manner feel free to ping me.

3 4

Thank you from an oVirt user
by Scott Sobotka 08 Apr '21

08 Apr '21

Dear oVirt developers, I just wanted to drop you all a note to thank you for the great work you've done with oVirt. I've been using it for several years and am vastly impressed with your robust and stable solution to what is, frankly, a very complex set of problems. Thank you so much. Your efforts are greatly appreciated. Thanks and have a great day, --Scott Sobotka

2 1

planned Jenkins restart
by Evgheni Dereveanchin 08 Apr '21

08 Apr '21

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new CI jobs will be scheduled during this maintenance period. I will inform you once it is back online. -- Regards, Evgheni Dereveanchin

1 1

ovirt-engine has been tagged (ovirt-engine-4.4.6.3)
by Tal Nisan 07 Apr '21

07 Apr '21

1 0

Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 1974 - Still Failing!
by Yedidyah Bar David 07 Apr '21

07 Apr '21

On Mon, Apr 5, 2021 at 5:53 AM <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1974/ FYI: This failed twice in a row (1973 and 1974), for the same reason. I reproduced locally, looked a bit, failed to find the root cause. When I connected to host-1's console, it was stuck in emergency after reboot. I checked a bit, there was some error about kdump failing to read the kernel image ( /boot/vmlinuz-4.18.0-240.15.1.el8_3.x86_64 ), when I tried manually as root I did manage to read it. I rebooted, and the VM came up fine. I decided to try OST again, cleaned up and ran it, and opened a 'lago console' on the vm after it was up, but OST passed. Tried again, passed again. Then I manually ran in CI 1975 and it passed, and also the nightly 1976 passed. So I am going to ignore for now. I think we need a patch to make lago/OST log consoles of all the VMs. I might try to work on this. Best regards, -- Didi

2 5

OST failed during test_003_00_metrics_bootstrap
by Eyal Shenitzky 07 Apr '21

07 Apr '21

Hi all, OST failed to run due to the following error in test_003_00_metrics_bootstrap - ost_utils.ansible.module_mappers.AnsibleExecutionError: Error running ansible: rc=2, stdout=/usr/lib/python3.6/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.26.4) or chardet (3.0.4) doesn't match a supported version! RequestsDependencyWarning) lago-basic-suite-master-engine | FAILED | rc=1 >> This command will collect system configuration and diagnostic information from this system. The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Use the -h option to see usage. DEBUG: Configuration: DEBUG: command: collect DEBUG: Traceback (most recent call last): DEBUG: File "/usr/lib/python3.6/site-packages/ovirt_log_collector/__main__.py", line 2067, in <module> DEBUG: '%s directory is not empty.' % (conf["local_tmp_dir"]) DEBUG: Exception: /dev/shm/iSX3ZN directory is not empty.ERROR: /dev/shm/iSX3ZN directory is not empty.non-zero return code Stacktrace ansible_engine = <ost_utils.ansible.module_mappers.ModuleMapper object at 0x7f67b85bb048> ansible_hosts = <ost_utils.ansible.module_mappers.ModuleMapper object at 0x7f67b85bbb38> def test_metrics_and_log_collector(ansible_engine, ansible_hosts): vt = utils.VectorThread( [ functools.partial(configure_metrics, ansible_engine, ansible_hosts), functools.partial(run_log_collector, ansible_engine), ], ) vt.start_all() > vt.join_all() basic-suite-master/test-scenarios/test_003_00_metrics_bootstrap.py:96: Logs can be found in - https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/16188… Can someone have a look? -- Regards, Eyal Shenitzky

2 1

lago project locations/home
by Yedidyah Bar David 06 Apr '21

06 Apr '21

Hi all, Can we please somehow have a single location one can check when searching where its source code is, etc., and update all the others to point there? We currently have at least: https://github.com/lago-project/lago http://lago.readthedocs.io/ https://www.ovirt.org/develop/infra/testing/lago/ https://gerrit.ovirt.org/admin/repos/lago https://gerrit.ovirt.org/admin/repos/lago-ost It seems like the last one is the current "source of truth", but I didn't see this announced anywhere. Also, coming to the next point, its name is confusing with "lago-ost-plugin". In addition to above, we also have these, for lago-ost-plugin: https://github.com/lago-project/lago-ost-plugin https://lago-ost-plugin.readthedocs.io/ It's not clear if we still need it or not. It would be nice to mention this in such a home page, even after we do not need it anymore (just the fact that it's not needed, to clear potential confusion for people still finding it). For all of above git repos that are not in use anymore, it would also be nice to push a patch adding a short note to their README saying they are not used anymore and linking at a home page. Last but not least, I do support the new name "lago-ost" - "lago" itself appears in far too many other unrelated places on the net. Thanks and best regards, -- Didi

1 0