September 2019 - Devel - Ovirt List Archives

[oVirt] [CQ weekly status] [07-09-2019]

by Dusan Fodor

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: NOT RELEVANT This CQ is not followed anymore, since it's about to be decommissioned. *CQ-4.3*: YELLOW (#1) Last failure was on 06-09 for vdsm in host installation. It was caused by missing package and solved soon after. *CQ-Master:* YELLOW (#1) Last failure was on 05-09 was random one-time failure on adding storage domain. Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.2_change-queue-tester/ [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.3_change-queue-tester/ [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -master_change-queue-tester/ Have a nice week! Dusan ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3) _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt .org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt .org/message/YCNCKRK3G4EJXA3OCYAUS4VMKRDA67F4/

4 years, 7 months

3
2
0 / 0

Error running engine-setup in dev-env on FC29

by Martin Perina

Hi, has anyone seen below error when running engine-setup in dev env on FC29? [ INFO ] Generating post install configuration file '/home/mperina/ovirt-engine/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf' [ ERROR ] Failed to execute stage 'Misc configuration': a bytes-like object is required, not 'str' [ INFO ] Rolling back database schema [ INFO ] Clearing Engine database engine [ INFO ] Stage: Clean up Log file is located at /home/mperina/ovirt-engine/var/log/ovirt-engine/setup/ovirt-engine-setup-20190909105257-dh2le0.log [ INFO ] Generating answer file '/home/mperina/ovirt-engine/var/lib/ovirt-engine/setup/answers/20190909105355-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed Following exception is raised in the setup log: 2019-09-09 10:53:49,357+0200 DEBUG otopi.context context._executeMethod:127 Stage misc METHOD otopi.plugins.ovirt_engine_common.base.core.postinstall.Plugin._misc 2019-09-09 10:53:49,357+0200 INFO otopi.plugins.ovirt_engine_common.base.core.postinstall postinstall._misc:60 Generating post install configuration file '/home/mperina/ovirt-engine/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf' 2019-09-09 10:53:49,358+0200 DEBUG otopi.transaction transaction._prepare:61 preparing 'File transaction for '/home/mperina/ovirt-engine/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf'' 2019-09-09 10:53:49,358+0200 DEBUG otopi.filetransaction filetransaction.prepare:184 file '/home/mperina/ovirt-engine/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf' missing 2019-09-09 10:53:49,358+0200 DEBUG otopi.transaction transaction._prepare:66 exception during prepare phase FATAL Internal error (main): a bytes-like object is required, not 'str' Traceback (most recent call last): File "/usr/lib/python3.7/site-packages/otopi/__main__.py", line 83, in main installer.execute() File "/usr/lib/python3.7/site-packages/otopi/main.py", line 151, in execute self.context.runSequence() File "/usr/lib/python3.7/site-packages/otopi/context.py", line 643, in runSequence util.raiseExceptionInformation(infos[0]) File "/usr/lib/python3.7/site-packages/otopi/util.py", line 84, in raiseExceptionInformation raise info[1].with_traceback(info[2]) File "/usr/lib/python3.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/home/mperina/ovirt-engine/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/base/core/postinstall.py", line 98, in _misc otopicons.CoreEnv.MODIFIED_FILES File "/usr/lib/python3.7/site-packages/otopi/transaction.py", line 106, in append self._prepare(element=element) File "/usr/lib/python3.7/site-packages/otopi/transaction.py", line 62, in _prepare element.prepare() File "/usr/lib/python3.7/site-packages/otopi/filetransaction.py", line 253, in prepare os.write(fd, self._content) TypeError: a bytes-like object is required, not 'str' It's latest master, all packages updated in the morning. Thanks, M. -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

4 years, 7 months

3
5
0 / 0

chanking mkIsoFs path

by Dan Kenigsberg

I bumped by accident on https://gerrit.ovirt.org/#/c/102698/ py3: mkimage: Remove md5 part in getFileName and I don't think it is right: if a VM is created in a 4.3 cluster and then migrated to a 4.4 cluster, qemu would not find the ISO image where it expects it, and it would break. I don't recall WHY we had md5 included into the path. It may well has been a mistake. I just do not see a (easy) backward-compatible way to drop it now.

4 years, 7 months

3
2
0 / 0

OST is broken since this morning - looks like infra issue

by Nir Soffer

The last successful build was today at 08:10: Since then all builds fail very early with the error below - which is not related to oVirt. Removing image: sha256:f8e5aa8e979155e074411bfef9adade6cdcdf3a5a2eb1d5ad2dbf0288d585ffa, force=True Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 222, in _raise_for_status response.raise_for_status() File "/usr/lib/python3.6/site-packages/requests/models.py", line 893, in raise_for_status raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http+docker://localunixsocket/v1.30/images/sha256:f8e5aa8e979155e074411bfef9adade6cdcdf3a5a2eb1d5ad2dbf0288d585ffa?force=True&noprune=False During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py", line 349, in <module> main() File "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py", line 37, in main safe_image_cleanup(client, whitelisted_repos) File "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py", line 107, in safe_image_cleanup _safe_rm(client, parent) File "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py", line 329, in _safe_rm client.images.remove(image_id, force=force) File "/usr/lib/python3.6/site-packages/docker/models/images.py", line 288, in remove self.client.api.remove_image(*args, **kwargs) File "/usr/lib/python3.6/site-packages/docker/utils/decorators.py", line 19, in wrapped return f(self, resource_id, *args, **kwargs) File "/usr/lib/python3.6/site-packages/docker/api/image.py", line 481, in remove_image return self._result(res, True) File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 228, in _result self._raise_for_status(response) File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 224, in _raise_for_status raise create_api_error_from_http_exception(e) File "/usr/lib/python3.6/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception raise cls(e, response=response, explanation=explanation) docker.errors.NotFound: 404 Client Error: Not Found ("reference does not exist") Aborting. Build step 'Execute shell' marked build as failure x [image: Failed > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5542/console> #5542 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5542/> Sep 5, 2019 3:02 PM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5542/> [image: Failed > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5541/console> #5541 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5541/> Sep 5, 2019 3:02 PM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5541/> [image: Failed > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5540/console> #5540 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5540/> Sep 5, 2019 3:01 PM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5540/> [image: Failed > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5539/console> #5539 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5539/> Sep 5, 2019 2:13 PM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5539/> [image: Failed > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5538/console> #5538 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5538/> Sep 5, 2019 1:58 PM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5538/> [image: Failed > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5537/console> #5537 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5537/> Sep 5, 2019 1:50 PM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5537/> [image: Failed > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5536/console> #5536 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5536/> Sep 5, 2019 10:21 AM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5536/> [image: x] <http://jenkins.ovirt.org/job/ovirt-system-tests_manual/jobConfigHistory/s...> [image: Success > Console Output] <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5535/console> #5535 <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5535/> Sep 5, 2019 8:10 AM <https://jenkins.ovirt.org/job/ovirt-system-tests_manual/5535/>

4 years, 7 months

1
0
0 / 0

'Misc configuration' failed in engine-setup

by Shmuel Melamud

Hi! I've tried several minutes ago to perform engine-setup on the latest master and it failed with the message: [ INFO ] Stage: Misc configuration [ ERROR ] Failed to execute stage 'Misc configuration': [Errno 2] No such file or directory: '/etc/ovirt-provider-ovn/conf.d/10-setup-ovirt-provider-ovn.conf' Anybody knows what may cause the error? Shmuel

4 years, 7 months

3
4
0 / 0

OST fails in verify_backup_snapshot_removed

by Yedidyah Bar David

Hi all, OST manual job failed for me a few times recently in 004_basic_sanity.verify_backup_snapshot_removed , last two (both with what I think are unrelated changes) are: 1. https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te... with the copyright notices patches to the engine: https://gerrit.ovirt.org/97698 2. https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te... with the unicode patches to the engine and to otopi: https://gerrit.ovirt.org/102936 https://gerrit.ovirt.org/102938 In job console, you can see that remove_backup_vm_and_backup_snapshot finished successfully, and several minutes latee verify_backup_snapshot_removed fails with a timeout. In between, engine.log has several ERRORs, e.g.: https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te... 2019-09-04 11:05:31,271-04 ERROR [org.ovirt.engine.core.bll.storage.disk.image.DestroyImageCommand] (EE-ManagedThreadFactory-engine-Thread-354) [e55e5d43-c168-42b4-9b80-e0cd2b8405bb] Ending command 'org.ovirt.engine.core.bll.storage.disk.image.DestroyImageCommand' with failure. No idea if that's related, didn't dig deeper. Any clue? Is this a known issue? Thanks and best regards, -- Didi

4 years, 7 months

2
1
0 / 0

Detach Storage Domain

by scott.fitzgerald＠oracle.com

Hi, I'm looking to use the SDK to detach a Non Master Storage Domain from a given Data Centre, without removing it from the system, ie it goes to Unattached mode. I have set the Domain to Maintenance, but can't see an obvious option for detaching it, except for removing it from the system entirely. Any advice is appreciated.

4 years, 7 months

2
2
1 / 0

ovirt-engine has been tagged (ovirt-engine-4.3.6.5)

by Tal Nisan

4 years, 7 months

1
0
0 / 0

the virtual machine crushed and I cant shutdown the vm successfully

by zhouhao＠vip.friendtimes.net

Dear ovirt developers: The trouble bothered me for a long time;Some times my vm will crush and I cant shutdown it,I had to reboot the ovirt-node to slove it; the vm's error below The ovirt-node's error below The vm's threading on the ovirt-node, the IO ratio is 100% and the vm's process change to defunct I can not kill it,every time I had to shutdown the ovirt-node on the engine website ,the vm's status always in the way to shutdown ,even if I wait for it for hours; It either failed or is shutting down and the "power off" cant shutdown the vm too. ---------------------------------------------------------------- The other infomation about my ovirt-node node-version： node hardware zhouhao(a)vip.friendtimes.net

4 years, 7 months

1
0
0 / 0

the virtual machine crushed and I cant shutdown the vm successfully

by zhouhao＠vip.friendtimes.net

Dear ovirt developers: The trouble bothered me for a long time;Some times my vm will crush and I cant shutdown it,I had to reboot the ovirt-node to slove it; the vm's error below The ovirt-node's error below The vm's threading on the ovirt-node, the IO ratio is 100% and the vm's process change to defunct I can not kill it,every time I had to shutdown the ovirt-node on the engine website ,the vm's status always in the way to shutdown ,even if I wait for it for hours; It either failed or is shutting down and the "power off" cant shutdown the vm too. ---------------------------------------------------------------- The other infomation about my ovirt-node node-version： node hardware zhouhao(a)vip.friendtimes.net

4 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Devel September 2019