- Infra - oVirt List Archives

[CQ]: 97767, 1 (ovirt-vmconsole) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Feb '19

14 Feb '19

A system test invoked by the "ovirt-4.2" change queue including change 97767,1 (ovirt-vmconsole) failed. However, this change seems not to be the root cause for this failure. Change 97704,6 (ovirt-vmconsole) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97704,6 (ovirt-vmconsole) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/97767/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97704/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3879/

1 0

[CQ]: 97704,6 (ovirt-vmconsole) failed "ovirt-master" system tests
by oVirt Jenkins 14 Feb '19

14 Feb '19

Change 97704,6 (ovirt-vmconsole) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97704/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12884/

1 0

[JENKINS] Failed to setup proejct ovirt-provider-ovn_standard-on-merge
by jenkins＠jenkins.phx.ovirt.org 14 Feb '19

14 Feb '19

Failed to run project_setup.sh for: #239 ovirt-provider-ovn [check-merged]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0094.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-provider-ovn_standard-on-merge
by jenkins＠jenkins.phx.ovirt.org 14 Feb '19

14 Feb '19

Failed to run project_setup.sh for: #239 ovirt-provider-ovn [check-merged]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0086.workers-phx.ovirt.org.

1 0

[CQ]: 97704,6 (ovirt-vmconsole) failed "ovirt-4.2" system tests
by oVirt Jenkins 14 Feb '19

14 Feb '19

Change 97704,6 (ovirt-vmconsole) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97704/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3875/

2 1

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 14 Feb '19

14 Feb '19

Failed to run project_setup.sh for: #3581 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-rszzn.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 14 Feb '19

14 Feb '19

Failed to run project_setup.sh for: #3581 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-6l0vp.

1 0

[CQ]: 97721,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 14 Feb '19

14 Feb '19

Change 97721,2 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97721/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12880/

2 1

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 14 Feb '19

14 Feb '19

Failed to run project_setup.sh for: #3578 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-m06pr.

1 0

[JIRA] (OVIRT-2617) Allow rerunning only failed test lanes
by Roman Mohr (oVirt JIRA) 14 Feb '19

14 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2617?page=com.atlassian.jira.… ] Roman Mohr commented on OVIRT-2617: ----------------------------------- So think about sprint ends. Many people have PRs, they produce load. Things are already a little bit more unstable than usual, which will increase the amount of failed lanes. So people will hit "retest this please" more often ... > Allow rerunning only failed test lanes > -------------------------------------- > > Key: OVIRT-2617 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2617 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Roman Mohr > Assignee: infra > > Hi, > In KubeVirt we run a lot of differnent test lanes. Even if our tests are > written in a good way and if the underlying CI infra is stable and fast, > there will always be cases where for-whatever reason one or two tests can > fail out of hundreds in a lane. > It would be very helpful if we could have a /retest command or something > similar where only failed lanes are re-run. That would be similar to how it > is handled in Kubernetes. > Right now it is an all-or-nothing thing. > What I would expect, is that it is still possible to see the test history > somewhere then (e.g. the first two attempts where it failed and then the > third one where it succeeds). > Best Regards, > Roman -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2617) Allow rerunning only failed test lanes
by Roman Mohr (oVirt JIRA) 14 Feb '19

14 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2617?page=com.atlassian.jira.… ] Roman Mohr commented on OVIRT-2617: ----------------------------------- Well if one suspicious lane fails, we write "retest this please". This runs everything again. > Allow rerunning only failed test lanes > -------------------------------------- > > Key: OVIRT-2617 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2617 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Roman Mohr > Assignee: infra > > Hi, > In KubeVirt we run a lot of differnent test lanes. Even if our tests are > written in a good way and if the underlying CI infra is stable and fast, > there will always be cases where for-whatever reason one or two tests can > fail out of hundreds in a lane. > It would be very helpful if we could have a /retest command or something > similar where only failed lanes are re-run. That would be similar to how it > is handled in Kubernetes. > Right now it is an all-or-nothing thing. > What I would expect, is that it is still possible to see the test history > somewhere then (e.g. the first two attempts where it failed and then the > third one where it succeeds). > Best Regards, > Roman -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2590) Cache Docker images in the datacenter
by Roman Mohr (oVirt JIRA) 14 Feb '19

14 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2590?page=com.atlassian.jira.… ] Roman Mohr commented on OVIRT-2590: ----------------------------------- Thinking about our CI images it can avoid peaks on the network consumption. Right now you need all of our lanes to have run on each bare-metal machine until all nodes have a cache for each image. They have up to 8gb. It is another measure to reduce the amount of failing tests because of networking issues. Setting it up should be pretty simple. The mirror needs then just to be injected before starting docker. > Cache Docker images in the datacenter > ------------------------------------- > > Key: OVIRT-2590 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2590 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Roman Mohr > Assignee: infra > > What? > As a user, I expect that I don't have to care about caching to speed up > builds for the good of the CI system itself. > Right now there exists a whitelist for docker images, which will not be > remove from the build slot after the build. Instead of that I expect a > clean build environment and that in general all images which I regularly > use are cached in the cluster via e.g. a pull-through-cache [1]. > Why? > 1) Caching in a build slot is not very effective. CI runs do really-a-lot > of almost identical things in a small time-window (e.g. days). If caching > happens in the build-slot and many slots are present, then the cache > utilization will be very low. > 2) Whitelisting docker images extra for a slot where the registry runs in, > is very error prone and since it is not cached across the cluster it is > also very intransparent what the clear benefit for the user is. Especially > when thinking about scaling a CI system, that seems to leak internal > optimizations to the user. Fast builds are twice as important for the CI > system than they are for the users (by default faster and lower utilization > is always better than asking people to optimize on their side). > [1] https://docs.docker.com/registry/recipes/mirror/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 97578, 9 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 14 Feb '19

14 Feb '19

Change 97578,9 (ovirt-provider-ovn) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97578/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12879/

1 0

[CQ]: 97694, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Feb '19

14 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97694,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97726,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97726,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/97694/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97726/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12876/

3 2

[CQ]: 97733, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Feb '19

14 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97733,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97726,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97726,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/97733/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97726/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12877/

2 1

[CQ]: 97726,5 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 14 Feb '19

14 Feb '19

Change 97726,5 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97726/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12875/

1 0

oVirt infra daily report - unstable production jobs - 735
by jenkins＠jenkins.phx.ovirt.org 14 Feb '19

14 Feb '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/735//artifact/exported-a… Cheers, Jenkins

1 0

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 13-02-2019 ] [ 001_initialize_engine.initialize_engine ]
by Dafna Ron 13 Feb '19

13 Feb '19

Hi, we are failing on project ovirt-engine in master branch on initialize engine Change suspected: https://gerrit.ovirt.org/#/c/95743/8 - core: Remove unused field VdsStatic.vdsStrength setup log is here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12864/artifa… full logs are here: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12864/artifa… Can you please check the issue? Thanks, Dafna <error> INSERT INTO gluster_config_master(config_key, config_description, minimum_supported_cluster, config_possible_values, config_feature) values('use_meta_volume', 'Meta volume for the geo-replication session', '3.5', 'false;true', 'geo_replication'); ************************** INSERT 0 1 2019-02-13 09:03:04,406-0500 Saving custom users permissions on database objects... ********* QUERY ********** copy ( select count(*) from pg_available_extensions where name = 'uuid-ossp' and installed_version IS NOT NULL ) to stdout with delimiter as '|'; ************************** 2019-02-13 09:03:04,906-0500 dbfunc_psql_die --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_00_0000_set_version.sql ********* QUERY ********** select 4000000; ************************** 4000000 2019-02-13 09:03:05,534-0500 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.executeRaw:863 execute-result: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s', 'localhost', '-p', '5432', '-u', 'engine', '-d', 'engine', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20190213090242-msviji.log', '-c', 'apply'], rc=1 2019-02-13 09:03:05,534-0500 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.execute:921 execute-output: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s', 'localhost', '-p', '5432', '-u', 'engine', '-d', 'engine', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20190213090242-msviji.log', '-c', 'apply'] stdout: 2019-02-13 09:03:05,535-0500 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema plugin.execute:926 execute-output: ['/usr/share/ovirt-engine/dbscripts/schema.sh', '-s', 'localhost', '-p', '5432', '-u', 'engine', '-d', 'engine', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20190213090242-msviji.log', '-c', 'apply'] stderr: FATAL: Operation aborted, found duplicate version: 04030790 2019-02-13 09:03:05,535-0500 ERROR otopi.plugins.ovirt_engine_setup.ovirt_engine.db.schema schema._misc:435 schema.sh: FATAL: Operation aborted, found duplicate version: 04030790 2019-02-13 09:03:05,535-0500 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/db/schema.py", line 437, in _misc raise RuntimeError(_('Engine schema refresh failed')) RuntimeError: Engine schema refresh failed 2019-02-13 09:03:05,536-0500 ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Misc configuration': Engine schema refresh failed 2019-02-13 09:03:05,562-0500 DEBUG otopi.plugins.otopi.debug.debug_failure.debug_failure debug_failure._notification:100 tcp connections: id uid local foreign state pid exe <error>

2 3

[CQ]: 97356, 14 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Feb '19

13 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97356,14 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97463,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97463,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/97356/14 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97463/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12867/

1 0

[CQ]: 95743, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 13 Feb '19

13 Feb '19

A system test invoked by the "ovirt-master" change queue including change 95743,8 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97463,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97463,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/95743/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97463/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12864/

1 0

[CQ]: 97463,5 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 13 Feb '19

13 Feb '19

Change 97463,5 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97463/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12861/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 13 Feb '19

13 Feb '19

Failed to run project_setup.sh for: #3566 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-pf1nk.

1 0

[CQ]: 97599,9 (ovirt-release) failed "ovirt-master" system tests
by oVirt Jenkins 13 Feb '19

13 Feb '19

Change 97599,9 (ovirt-release) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97599/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12860/

1 0

[CQ]: 900b39f (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 13 Feb '19

13 Feb '19

Change 900b39f (ovirt-ansible-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/900b39f1f… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12858/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 13 Feb '19

13 Feb '19

Failed to run project_setup.sh for: #3562 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-7930z.

1 0

[CQ]: 900b39f (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 13 Feb '19

13 Feb '19

Change 900b39f (ovirt-ansible-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/900b39f1f… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12856/

1 0

concerns about the viability of hyperkitty
by Greg Sheremeta 13 Feb '19

13 Feb '19

Hi, After a user on the users list asked about a forum, I pointed them to our hyperkitty instance [lists.ovirt.org] which people did not know about. Maybe that was a bad idea, because a few who started looking at it commented that it was broken. This is not a good community experience. [Thank you, Marc, for opening https://gitlab.com/mailman/hyperkitty/issues/206 - but no reply for 2 months on a *major* bug like that?] While investigating the threading issue today, I found a new issue (attached screenshot). Also, one person sent the same message to the list 7 times today because he never saw his message show up in the list / UI. Perhaps hyperkitty is not well-tested nor really used by others, in which case we should not use it. There are many alternative forums, including popular (although admittedly walled off) ones like reddit [ https://www.reddit.com/r/ovirt] Please share your thoughts. Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig>

4 7

oVirt infra daily report - unstable production jobs - 734
by jenkins＠jenkins.phx.ovirt.org 13 Feb '19

13 Feb '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/734//artifact/exported-a… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2677) Fwd: [ovirt-users] Not receiving signup confirmation email
by Evgheni Dereveanchin (oVirt JIRA) 12 Feb '19

12 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2677?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2677: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Fwd: [ovirt-users] Not receiving signup confirmation email > ---------------------------------------------------------- > > Key: OVIRT-2677 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2677 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Emil Natan > Assignee: Evgheni Dereveanchin > > This will open a ticket at our Jira system. > ---------- Forwarded message --------- > From: Jonas Lindholm <jonas.lindholm(a)nasdaq.com> > Date: Sun, Feb 10, 2019 at 10:49 AM > Subject: [ovirt-users] Not receiving signup confirmation email > To: users(a)ovirt.org <users(a)ovirt.org> > Hi. I tried to signup 30 minutes ago with this email address but has still > not received the signup confirmation email. > /Jonas > *********************************************************** > CONFIDENTIALITY AND PRIVACY NOTICE: This e-mail and any attachments are for > the exclusive and confidential use of the intended recipient and may > constitute non-public information. Personal data in this email is governed > by our Privacy Policy at http://business.nasdaq.com/privacy-statement > unless explicitly excluded from it; please see the section in the policy > entitled “Situations Where This Privacy Policy Does Not Apply” for > circumstances where different privacy terms govern emailed personal data. > If you received this e-mail in error, disclosing, copying, distributing or > taking any action in reliance of this e-mail is strictly prohibited and may > be unlawful. Instead, please notify us immediately by return e-mail and > promptly delete this message and its attachments from your computer system. > We do not waive any work product or other applicable legal privilege(s) by > the transmission of this message. > *********************************************************** > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-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/users@ovirt.org/message/IG4W6JRM2MI2Z… > -- > Emil Natan > RHV/CNV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2678) Re: [ovirt-users] Not receiving signup confirmation email
by Eyal Edri (oVirt JIRA) 12 Feb '19

12 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2678?page=com.atlassian.jira.… ] Eyal Edri reassigned OVIRT-2678: -------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Re: [ovirt-users] Not receiving signup confirmation email > --------------------------------------------------------- > > Key: OVIRT-2678 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2678 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: Marc Dequènes (Duck) > > Hi, > I received this email. Sorry you are having troubles. > @Marc Dequenes <duck(a)redhat.com> can you look into this? > Greg > On Sun, Feb 10, 2019 at 3:50 AM Jonas Lindholm <jonas.lindholm(a)nasdaq.com> > wrote: > > Hi. I tried to signup 30 minutes ago with this email address but has still > > not received the signup confirmation email. > > > > /Jonas > > > > *********************************************************** > > CONFIDENTIALITY AND PRIVACY NOTICE: This e-mail and any attachments are > > for the exclusive and confidential use of the intended recipient and may > > constitute non-public information. Personal data in this email is governed > > by our Privacy Policy at http://business.nasdaq.com/privacy-statement > > unless explicitly excluded from it; please see the section in the policy > > entitled “Situations Where This Privacy Policy Does Not Apply” for > > circumstances where different privacy terms govern emailed personal data. > > If you received this e-mail in error, disclosing, copying, distributing or > > taking any action in reliance of this e-mail is strictly prohibited and may > > be unlawful. Instead, please notify us immediately by return e-mail and > > promptly delete this message and its attachments from your computer system. > > We do not waive any work product or other applicable legal privilege(s) by > > the transmission of this message. > > *********************************************************** > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org > > To unsubscribe send an email to users-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/users@ovirt.org/message/IG4W6JRM2MI2Z… > > > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc29-x86_64 #281
by jenkins＠jenkins.phx.ovirt.org 12 Feb '19

12 Feb '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc29-x86_64…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc29-x86_64…> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune # timeout=10 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 3f600edf0a902320f77ac99a769631eec564d14a (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 3f600edf0a902320f77ac99a769631eec564d14a # timeout=10 Commit message: "mock_runner: always mount ci_toolbox" > git rev-list --no-walk 3f600edf0a902320f77ac99a769631eec564d14a # timeout=10 [system-sync_mirrors-fedora-updates-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins313835014205766275.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-updates-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs fedora-updates-fc29 yum + local repo_name=fedora-updates-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-updates-fc29 /var/www/html/repos/yum/fedora-updates-fc29/base + check_yum_sync_needed fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-updates-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/fedora-updates-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-updates-fc29 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=fedora-updates-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-updates-fc29/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1022, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 700, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 695, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 632, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 875, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 821, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 897, in _getMetalink raise Errors.RepoError, msg yum.Errors.RepoError: Cannot retrieve metalink for repository: fedora-updates-fc29. Please verify its path and try again + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[CQ]: 97138,13 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 12 Feb '19

12 Feb '19

Change 97138,13 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97138/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12843/

1 0

oVirt infra daily report - unstable production jobs - 733
by jenkins＠jenkins.phx.ovirt.org 12 Feb '19

12 Feb '19

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/733//artifact/exported-a… Cheers, Jenkins

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 11 Feb '19

11 Feb '19

Failed to run project_setup.sh for: #3542 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-v5sbt.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 11 Feb '19

11 Feb '19

Failed to run project_setup.sh for: #3542 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-5f85q.

1 0

[CQ]: 65ae943 (ovirt-web-ui) failed "ovirt-master" system tests
by oVirt Jenkins 11 Feb '19

11 Feb '19

Change 65ae943 (ovirt-web-ui) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-web-ui/commit/65ae9430becd5849c48fa6767938b3… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12837/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 11 Feb '19

11 Feb '19

Failed to run project_setup.sh for: #3541 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-1j3cq.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 11 Feb '19

11 Feb '19

Failed to run project_setup.sh for: #3541 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-scbsr.

1 0

[CQ]: 97186, 20 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Feb '19

11 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97186,20 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 97501,4 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97501,4 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/97186/20 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97501/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12835/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 11 Feb '19

11 Feb '19

Failed to run project_setup.sh for: #3534 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-mxtm8.

1 0

[CQ]: 97642, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Feb '19

11 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97642,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 97501,4 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97501,4 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/97642/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97501/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12832/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 11 Feb '19

11 Feb '19

Failed to run project_setup.sh for: #3530 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-gkx0c.

1 1

[CQ]: 97509, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Feb '19

11 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97509,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 97501,4 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97501,4 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/97509/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97501/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12829/

1 0

[CQ]: 97501,4 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 11 Feb '19

11 Feb '19

Change 97501,4 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97501/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12826/

1 0

[CQ]: 97506, 10 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Feb '19

11 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97506,10 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97675,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97675,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/97506/10 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97675/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12823/

1 0

[CQ]: 97466, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Feb '19

11 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97466,8 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97675,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97675,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/97466/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97675/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12820/

1 0

[CQ]: 97394, 18 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Feb '19

11 Feb '19

A system test invoked by the "ovirt-master" change queue including change 97394,18 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97675,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97675,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/97394/18 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97675/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12818/

1 0

[CQ]: 97675,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 11 Feb '19

11 Feb '19

Change 97675,2 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97675/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12816/

2 1

[JIRA] (OVIRT-2663) Please add ManageIQ Hammer-1 to glance repository
by Evgheni Dereveanchin (oVirt JIRA) 11 Feb '19

11 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2663?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2663: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Please add ManageIQ Hammer-1 to glance repository > ------------------------------------------------- > > Key: OVIRT-2663 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2663 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > In glance latest version available is Gaprindashvili-7. > Please update with Hammer-1. > Thanks, > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2671) Re: Rename GitHub repo ovirt-ansible-v2v-conversion-host
by Evgheni Dereveanchin (oVirt JIRA) 11 Feb '19

11 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2671?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2671: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Re: Rename GitHub repo ovirt-ansible-v2v-conversion-host > -------------------------------------------------------- > > Key: OVIRT-2671 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2671 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: Evgheni Dereveanchin > > Openning a ticket. > On Tue, Feb 5, 2019 at 11:55 AM Tomáš Golembiovský <tgolembi(a)redhat.com> > wrote: > > Hi, > > > > I would like to rename the GitHub repo ovirt-ansible-v2v-conversion-host > > to v2v-conversion-host. Is there a list of things I should do before > > or after the operation? Will the automation still work? > > > > Tomas > > > > -- > > Tomáš Golembiovský <tgolembi(a)redhat.com> > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-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/infra@ovirt.org/message/WFEG3OQ3Q2DDX… > > > -- > Anton Marchukov > Team Lead - Release Management - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0