[JIRA] (OVIRT-2813) EL8 builds fail to mount loop device - kernel too old?

2019-10-09 Thread Yuval Turgeman (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39898#comment-39898
 ] 

Yuval Turgeman commented on OVIRT-2813:
---

You may be running out of loop devices, if that's the case, you need to
manually mknod them, see
https://github.com/oVirt/ovirt-node-ng-image/blob/56a2797b5ef84bd56ab95fdb0cbfb908b4bc8ec1/automation/build-artifacts.sh#L24

On Thursday, October 10, 2019, Nir Soffer  wrote:

> On Wed, Oct 9, 2019 at 11:56 PM Nir Soffer  wrote:
>
>> I'm trying to run imageio tests on el8 mock, and the tests fail early
>> when trying to create storage
>> for testing:
>>
>> [userstorage] INFOCreating filesystem 
>> /var/tmp/imageio-storage/file-512-ext4-mount
>> Suggestion: Use Linux kernel >= 3.18 for improved stability of the metadata 
>> and journal checksum features.
>> [userstorage] INFOCreating file 
>> /var/tmp/imageio-storage/file-512-ext4-mount/file
>> [userstorage] INFOCreating backing file 
>> /var/tmp/imageio-storage/file-512-xfs-backing
>> [userstorage] INFOCreating loop device 
>> /var/tmp/imageio-storage/file-512-xfs-loop
>> [userstorage] INFOCreating filesystem 
>> /var/tmp/imageio-storage/file-512-xfs-mount
>> mount: /var/tmp/imageio-storage/file-512-xfs-mount: wrong fs type, bad 
>> option, bad superblock on /dev/loop4, missing codepage or helper program, or 
>> other error.
>> Traceback (most recent call last):
>>   File "/usr/local/bin/userstorage", line 10, in 
>> sys.exit(main())
>>   File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", 
>> line 42, in main
>> create(cfg)
>>   File "/usr/local/lib/python3.6/site-packages/userstorage/__main__.py", 
>> line 52, in create
>> b.create()
>>   File "/usr/local/lib/python3.6/site-packages/userstorage/file.py", line 
>> 47, in create
>> self._mount.create()
>>   File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", line 
>> 53, in create
>> self._mount_loop()
>>   File "/usr/local/lib/python3.6/site-packages/userstorage/mount.py", line 
>> 94, in _mount_loop
>> ["sudo", "mount", "-t", self.fstype, self._loop.path, self.path])
>>   File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call
>> raise CalledProcessError(retcode, cmd)
>> subprocess.CalledProcessError: Command '['sudo', 'mount', '-t', 'xfs', 
>> '/var/tmp/imageio-storage/file-512-xfs-loop', 
>> '/var/tmp/imageio-storage/file-512-xfs-mount']' returned non-zero exit 
>> status 32.
>>
>> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-
>> patch/1593//artifact/check-patch.el8.ppc64le/mock_logs/
>> script/stdout_stderr.log
>>
>>
>> Same code runs fine in Travis:
>> https://travis-ci.org/nirs/ovirt-imageio/jobs/595794863
>>
>>
>> And also locally on Fedora 29:
>> $ ../jenkins/mock_configs/mock_runner.sh -C ../jenkins/mock_configs -p
>> el8
>> ...
>> ## Wed Oct  9 23:37:22 IDT 2019 Finished env: el8:epel-8-x86_64
>> ##  took 85 seconds
>> ##  rc = 0
>>
>>
>> My guess is that we run el8 jobs on el7 hosts with old kernels
>> (Suggestion: Use Linux kernel >= 3.18 for improved stability of the
>> metadata and journal checksum features.)
>>
>
> Here is info from failed builds:
>
> DEBUG buildroot.py:503: kernel version == 3.10.0-693.11.6.el7.ppc64le
> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-
> patch/1593/artifact/check-patch.el8.ppc64le/mock_logs/init/root.log
>
> DEBUG buildroot.py:503:  kernel version == 3.10.0-957.12.1.el7.x86_64
> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-
> patch/1593/artifact/check-patch.el8.x86_64/mock_logs/init/root.log
>
> and successful builds:
>
> DEBUG buildroot.py:503:  kernel version == 5.1.18-200.fc29.x86_64
> My laptop
>
> Runtime kernel version: 4.15.0-1032-gcp
> https://travis-ci.org/nirs/ovirt-imageio/jobs/595794863
>
>
> This issue will affects vdsm, using similar code to create storage for
>> testing.
>>
>> For vdsm the issue is more tricky, since it requires same host/distro:
>>
>>  49 - tests-py37:
>>  50 runtime-requirements:
>>  51   host-distro: same
>>
>> So I think we need:
>> - make slaves with newer kernel (fc29? fc30?) with the el8 mock env
>> - add el8 slaves for running el8 mock with "host-distro: same"
>>
>> If we don't have a solution we need to disable el8 tests, or continue
>> testing without
>> storage, which will skip about 200 tests.
>>
>> Nir
>>
>>

> EL8 builds fail to mount loop device - kernel too old?
> --
>
> Key: OVIRT-2813
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2813
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> I'm trying to run imageio tests on el8 mock, and the tests fail early when
> trying to create storage
> for testing:
> [

[JIRA] (OVIRT-2779) New ovirt project

2019-08-22 Thread Yuval Turgeman (oVirt JIRA) 
Yuval Turgeman created OVIRT-2779:
-

 Summary: New ovirt project
 Key: OVIRT-2779
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2779
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yuval Turgeman
Assignee: infra


Hi,

Can you please create a new project in gerrit: ovirt-node-coreos ?

Thanks !



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100107)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/NOBOXRWE4YDK3NNBSFYQDKB7Q3RKRH2W/

[JIRA] (OVIRT-2703) oVirt Node build fails due to CPU stuck

2019-03-18 Thread Yuval Turgeman (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39181#comment-39181
 ] 

Yuval Turgeman commented on OVIRT-2703:
---

If we have BMs, that would be best...

> oVirt Node build fails due to CPU stuck
> ---
>
> Key: OVIRT-2703
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2703
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> *CPU is getting stuck for the VM running on the slave.*
> *Error is:*
> *https://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc28-x86_64/240/console
> *
> *10:44:14* 09:44:13,825 WARNING kernel:ata2: lost interrupt (Status
> 0x58)*10:44:14* 09:44:13,834 DEBUG kernel:ata2: drained 65536 bytes to
> clear DRQ*10:44:14* 09:44:13,835 EMERG kernel:watchdog: BUG: soft
> lockup - CPU#0 stuck for 32s! [scsi_eh_1:85]*10:44:14* 09:44:13,835
> WARNING kernel:Modules linked in: xfs fcoe libfcoe libfc
> scsi_transport_fc zram scsi_dh_rdac scsi_dh_emc scsi_dh_alua
> parport_pc i2c_piix4 parport joydev loop nls_utf8 isofs 8021q garp mrp
> stp llc virtio_console serio_raw qemu_fw_cfg virtio_pci e1000
> bochs_drm drm_kms_helper ttm drm ata_generic pata_acpi sunrpc mcryptd
> sha256_ssse3 dm_crypt dm_round_robin dm_multipath linear raid10
> raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
> raid6_pq libcrc32c raid1 raid0 iscsi_ibft iscsi_boot_sysfs floppy
> iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi squashfs
> zstd_decompress xxhash cramfs edd virtio_rng virtio_ring
> virtio*10:44:14* 09:44:13,844 WARNING kernel:CPU: 0 PID: 85 Comm:
> scsi_eh_1 Not tainted 4.16.3-301.fc28.x86_64 #1*10:44:14* 09:44:13,844
> WARNING kernel:Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
> BIOS ?-20180531_142017-buildhw-08.phx2.fedoraproject.org-1.fc28
> 04/01/2014*10:44:21* 09:44:13,845 WARNING kernel:RIP:
> 0010:_raw_spin_unlock_irqrestore+0xd/0x20*10:44:21* 09:44:13,846
> WARNING kernel:RSP: 0018:a31e804cfdf0 EFLAGS: 0202 ORIG_RAX:
> ff12*10:44:21* 09:44:13,855 WARNING kernel:RAX:
>  RBX: 9654e8c5c000 RCX: *10:44:21*
> 09:44:13,856 WARNING kernel:RDX:  RSI:
> 0202 RDI: 0202*10:44:21* 09:44:13,856 WARNING
> kernel:RBP: bd60bd20 R08: 0038 R09:
> 02a4*10:44:21* 09:44:13,857 WARNING kernel:R10:
>  R11: 0001 R12: bd60b050*10:44:21*
> 09:44:13,857 WARNING kernel:R13: 9654e8c5c130 R14:
> 0202 R15: *10:44:21* 09:44:13,858 WARNING
> kernel:FS:  () GS:9654fbc0()
> knlGS:*10:44:21* 09:44:13,865 WARNING kernel:CS:  0010
> DS:  ES:  CR0: 80050033*10:44:21* 09:44:14,008 WARNING
> kernel:CR2: 7fece8177000 CR3: 69c18000 CR4:
> 06f0*10:44:21* 09:44:14,008 WARNING kernel:Call
> Trace:*10:44:21* 09:44:14,008 WARNING kernel:
> ata_sff_error_handler+0x83/0xe0*10:44:21* 09:44:14,009 WARNING kernel:
> ata_scsi_port_error_handler+0x354/0x770*10:44:21* 09:44:14,009 WARNING
> kernel: ? scsi_try_target_reset+0x90/0x90*10:44:21* 09:44:14,009
> WARNING kernel: ? scsi_eh_get_sense+0x220/0x220*10:44:21* 09:44:14,010
> WARNING kernel: ata_scsi_error+0x91/0xc0*10:44:21* 09:44:14,010
> WARNING kernel: scsi_error_handler+0xd0/0x5b0*10:44:21* 09:44:14,010
> WARNING kernel: ? scsi_eh_get_sense+0x220/0x220*10:44:21* 09:44:14,010
> WARNING kernel: kthread+0x112/0x130*10:44:21* 09:44:14,011 WARNING
> kernel: ? kthread_create_worker_on_cpu+0x70/0x70*10:44:21*
> 09:44:14,026 WARNING kernel: ?
> kthread_create_worker_on_cpu+0x70/0x70*10:44:21* 09:44:14,026 WARNING
> kernel: ret_from_fork+0x35/0x40*10:44:21* 09:44:14,026 WARNING
> kernel:Code: a8 08 74 0b 65 81 25 6f 2c 76 42 ff ff ff 7f 89 d0 c3 90
> 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 c6 07 00 48 89 f7 57
> 9d <0f> 1f 44 00 00 c3 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f
> *10:44:21* 09:44:14,027 ERR kernel:ata2.00: exception Emask 0x0 SAct
> 0x0 SErr 0x0 action 0x6 frozen*10:44:21* 09:44:14,027 ERR
> kernel:ata2.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio
> 16392 in#012 Get event status notification 4a 01 00 00 10 00
> 00 00 08 00res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4
> (timeout)*10:44:21* 09:44:14,028 ERR kernel:ata2.00: status: { DRDY
> }*10:44:21* 09:44:14,028 INFO kernel:ata2: soft resetting
> link*10:44:21* 09:44:19,296 WARNING kernel:ata2.00: qc timeout (cmd
> 0xa1)*10:44:21* 09:44:19,305 WARNING kernel:ata2.00: failed to
> IDENTIFY (I/O error, err_mask=0x4)*10:44:21* 09:44:19,305 ERR
> kernel:ata2.00: revalidation failed (e

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days

2018-12-30 Thread Yuval Turgeman (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38709#comment-38709
 ] 

Yuval Turgeman commented on OVIRT-2638:
---

Looks like livemedia-creator installed the VM correctly, but failed to
build the final image file for some reason (disk issues?).  Stdci failed
the job on timeout, but probably can't kill the hanging process.  Is it
possible to take a look at the slave somehow ?

On Sun, Dec 30, 2018, 19:57 Nir Soffer  Started 2 days 11 hr ago
> Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or
> 
>
>
> https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64/39/
>
>
> ___
> Devel mailing list -- de...@ovirt.org
> To unsubscribe send an email to devel-le...@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/de...@ovirt.org/message/FXGWNLV3ZLZSNC4MEXGBAMFP5GBAP7IY/
>

> ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
> 
>
> Key: OVIRT-2638
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> Started 2 days 11 hr ago
> Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or
> 
> https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64/39/



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100096)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/TMMW2I7ODIOINIRSZU7Z3YS5G5VYC7PT/

[JIRA] (OVIRT-2628) Unable to use virt-install in mock

2018-12-18 Thread Yuval Turgeman (oVirt JIRA) 
Yuval Turgeman created OVIRT-2628:
-

 Summary: Unable to use virt-install in mock
 Key: OVIRT-2628
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2628
 Project: oVirt - virtualization made easy
  Issue Type: Bug
Reporter: Yuval Turgeman
Assignee: infra


Some jenkins jobs that run virt-install (node-ng, appliance) randomly fail on  
"ERRORHost does not support any virtualization options".



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100096)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/YTYG5OQATPQORM744ZE62T52DW4ZL6TT/

[JIRA] (OVIRT-2534) imgbased master is failing on build-artifacts of fc28 due to missing deps

2018-10-11 Thread Yuval Turgeman (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yuval Turgeman reassigned OVIRT-2534:
-

Assignee: Yuval Turgeman  (was: infra)

> imgbased master is failing on build-artifacts of fc28 due to missing deps
> -
>
> Key: OVIRT-2534
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2534
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Dafna Ron
>Assignee: Yuval Turgeman
>  Labels: ost_build-arifacts, ost_failures
>
> https://pastebin.com/DrKqnrJx
>  http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10567/
>  http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10564/
> changes:  
> https://gerrit.ovirt.org/#/c/94844/2
> https://gerrit.ovirt.org/#/c/94500/3
> https://jenkins.ovirt.org/job/imgbased_standard-on-merge/96/consoleFull



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100094)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/DLDEVVW7F5AOA4G5JGRBZ5OLWCWPOOS2/

[JIRA] (OVIRT-2534) imgbased master is failing on build-artifacts of fc28 due to missing deps

2018-10-11 Thread Yuval Turgeman (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38202#comment-38202
 ] 

Yuval Turgeman commented on OVIRT-2534:
---

and here also https://gerrit.ovirt.org/#/c/94875/ :)

> imgbased master is failing on build-artifacts of fc28 due to missing deps
> -
>
> Key: OVIRT-2534
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2534
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Dafna Ron
>Assignee: infra
>  Labels: ost_build-arifacts, ost_failures
>
> https://pastebin.com/DrKqnrJx
>  http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10567/
>  http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10564/
> changes:  
> https://gerrit.ovirt.org/#/c/94844/2
> https://gerrit.ovirt.org/#/c/94500/3
> https://jenkins.ovirt.org/job/imgbased_standard-on-merge/96/consoleFull



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100094)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/WLHQPMFNLOUPZJRZXOF3LHBYWIEWXDR4/

[JIRA] (OVIRT-2534) imgbased master is failing on build-artifacts of fc28 due to missing deps

2018-10-11 Thread Yuval Turgeman (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38199#comment-38199
 ] 

Yuval Turgeman commented on OVIRT-2534:
---

I posted a patch that should solve this - https://gerrit.ovirt.org/#/c/94860/

> imgbased master is failing on build-artifacts of fc28 due to missing deps
> -
>
> Key: OVIRT-2534
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2534
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Dafna Ron
>Assignee: infra
>  Labels: ost_build-arifacts, ost_failures
>
> https://pastebin.com/DrKqnrJx
>  http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10567/
>  http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10564/
> changes:  
> https://gerrit.ovirt.org/#/c/94844/2
> https://gerrit.ovirt.org/#/c/94500/3
> https://jenkins.ovirt.org/job/imgbased_standard-on-merge/96/consoleFull



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100094)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/JT6A34ABIIDFFFGVD35PUZCDXBCIYXD3/

[JIRA] (OVIRT-2389) libvirt issues on ovirt-srv17

2018-08-02 Thread Yuval Turgeman (oVirt JIRA) 
Yuval Turgeman created OVIRT-2389:
-

 Summary: libvirt issues on ovirt-srv17
 Key: OVIRT-2389
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2389
 Project: oVirt - virtualization made easy
  Issue Type: Bug
  Components: Jenkins Slaves
Reporter: Yuval Turgeman
Assignee: infra


Recently, jobs that run on ovirt-srv17 and use libvirt to install a vm, fail 
because the vms do not receive an ip from libvirt/dnsmasq.  Some examples:

https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64/64/
https://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el7-x86_64/

Thanks.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/WQGSQVKWKJCCD5EGHSTZT5NMDFHXQQBQ/

[JIRA] (OVIRT-2287) ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs

2018-07-10 Thread Yuval Turgeman (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37421#comment-37421
 ] 

Yuval Turgeman commented on OVIRT-2287:
---

Gal took care of this already - https://gerrit.ovirt.org/#/c/92902/ :)

On Tue, Jul 10, 2018, 18:59 Dafna Ron  wrote:

> host memory is 4720 for both hosts. since one is running the engine should
> we increase it?
>
> {%- for i in range(hostCount) %}
>   lago-{{ env.suite_name }}-host-{{ i }}:
> vm-type: ovirt-host
> distro: el7
> service_provider: systemd
> memory: 4720
>
>
>
> On Sun, Jul 8, 2018 at 7:38 AM, Barak Korren  wrote:
>
>>
>>
>> On 6 July 2018 at 11:57, Sandro Bonazzola  wrote:
>>
>>>
>>>
>>> https://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/165/testReport/(root)/004_basic_sanity/vm_run/
>>>
>>> Cannot run VM. There is no host that satisfies current scheduling
>>> constraints. See below for details:, The host
>>> lago-he-node-ng-suite-master-host-0 did not satisfy internal filter Memory
>>> because its available memory is too low (656 MB) to run the VM.
>>>
>>>
>>
>> this sounds like something that needs to be fixed in the suit's
>> LagoInitFile.
>>
>>
>>
>>> --
>>>
>>> SANDRO BONAZZOLA
>>>
>>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>>>
>>> Red Hat EMEA 
>>>
>>> sbona...@redhat.com
>>> 
>>>
>>> ___
>>> Devel mailing list -- de...@ovirt.org
>>> To unsubscribe send an email to devel-le...@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/de...@ovirt.org/message/TDKLML6YDBATFHS232GFJF7QVRTWUH74/
>>>
>>>
>>
>>
>> --
>> Barak Korren
>> RHV DevOps team , RHCE, RHCi
>> Red Hat EMEA
>> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
>>
>> ___
>> Devel mailing list -- de...@ovirt.org
>> To unsubscribe send an email to devel-le...@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/de...@ovirt.org/message/S6F3JGB3C5OSKNWMM3THXMIR2XYYUOGO/
>>
>>
> ___
> Devel mailing list -- de...@ovirt.org
> To unsubscribe send an email to devel-le...@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/de...@ovirt.org/message/CUT2OW3NUPU26NOLNYMFPQHANC4AYOU2/
>

> ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to 
> run VMs
> -
>
> Key: OVIRT-2287
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2287
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: sbonazzo
>Assignee: infra
>Priority: Highest
>  Labels: ost_failures, ost_lago
> Attachments: srv.log
>
>
> https://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/165/testReport/(root)/004_basic_sanity/vm_run/
> Cannot run VM. There is no host that satisfies current scheduling
> constraints. See below for details:, The host
> lago-he-node-ng-suite-master-host-0 did not satisfy internal filter Memory
> because its available memory is too low (656 MB) to run the VM.
> -- 
> SANDRO BONAZZOLA
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
> Red Hat EMEA 
> sbona...@redhat.com
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100088)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/W6SDLYPNHMWRTMMMQXOSJ3G7XFS22FMO/

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches

2018-07-10 Thread Yuval Turgeman (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37400#comment-37400
 ] 

Yuval Turgeman commented on OVIRT-2201:
---

For ovirt-node-ng, we generate a latest-installation-iso.html in 
build-artifacts, and the download page[1] points to the last successful build 
per ovirt version.  It looks like we can't do it in V2 today.

[1] https://www.ovirt.org/node/

> [regression] STDCI v2 doesn't distinguish jobs for different branches
> -
>
> Key: OVIRT-2201
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Standard CI (Pipelines)
>Reporter: sbonazzo
>Assignee: infra
>
> In V1 we had jobs with different name based on branches they were building.
> In V2 we have single job building all branches.
> As an example for imgbased:
> https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBuild/artifact/
> will contain randomly 4.2 or master builds.
> This won't allow to filter jenkins to see which branches are failing to
> build, forcing developers to check manually.
> This also won't allow to check if latest build landed in tested repo
> because thee build may be targeted to a different branch than the one under
> check.
> To me this is a regression that will make me rethink about the switching to
> v2 and considering reverting to v1.
> -- 
> SANDRO BONAZZOLA
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
> Red Hat EMEA 
> sbona...@redhat.com
> 



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100088)
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/PUP4ALCGSZXWEQZBETRPPUGDAFA6DNQA/

[JIRA] (OVIRT-1846) New gerrit project - ovirt-node-ng-image

2018-01-14 Thread Yuval Turgeman (oVirt JIRA) 
Yuval Turgeman created OVIRT-1846:
-

 Summary: New gerrit project - ovirt-node-ng-image
 Key: OVIRT-1846
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1846
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yuval Turgeman
Assignee: infra


Hi,

We would like to split the squashfs+installer creation from the current
ovirt-node-ng project, leaving it to build its current rpms only (nodectl,
docs, tools etc) according to [1].

For this we would like to have a new gerrit project `ovirt-node-ng-image`.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1527120

Thanks,
Yuval.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1607) Failed ovirt-system-tests_master_check-patch-el7-x86_64

2017-08-29 Thread Yuval Turgeman (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34809#comment-34809
 ] 

Yuval Turgeman commented on OVIRT-1607:
---

+1 good call

> Failed ovirt-system-tests_master_check-patch-el7-x86_64
> ---
>
> Key: OVIRT-1607
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1607
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yedidyah Bar David
>Assignee: infra
>
> I want to verify [1]. It (expectedly) failed in the past, needed [2].
> [2] was merged yesterday and [1] still fails. I retriggered it several
> times, and it failed due to different reasons. Last was [3]:
> 08:11:38 + find /dev/shm/ost/deployment-image-ng-suite-master -type f
> '(' -iname 'nose*.xml' -o -iname '*.junit.xml' ')' -exec mv '{}'
> exported-artifacts/ ';'
> 08:11:38 find: ���/dev/shm/ost/deployment-image-ng-suite-master���: No
> such file or directory
> Please have a look. Thanks,
> [1] https://gerrit.ovirt.org/80820
> [2] https://gerrit.ovirt.org/79345
> [3] 
> http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/1467/
> -- 
> Didi



--
This message was sent by Atlassian JIRA
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1607) Failed ovirt-system-tests_master_check-patch-el7-x86_64

2017-08-29 Thread Yuval Turgeman (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34807#comment-34807
 ] 

Yuval Turgeman commented on OVIRT-1607:
---

Didn't see it happening anymore, perhaps a glitch in the jenkins api didn't 
return buildNumber ?

> Failed ovirt-system-tests_master_check-patch-el7-x86_64
> ---
>
> Key: OVIRT-1607
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1607
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yedidyah Bar David
>Assignee: infra
>
> I want to verify [1]. It (expectedly) failed in the past, needed [2].
> [2] was merged yesterday and [1] still fails. I retriggered it several
> times, and it failed due to different reasons. Last was [3]:
> 08:11:38 + find /dev/shm/ost/deployment-image-ng-suite-master -type f
> '(' -iname 'nose*.xml' -o -iname '*.junit.xml' ')' -exec mv '{}'
> exported-artifacts/ ';'
> 08:11:38 find: ���/dev/shm/ost/deployment-image-ng-suite-master���: No
> such file or directory
> Please have a look. Thanks,
> [1] https://gerrit.ovirt.org/80820
> [2] https://gerrit.ovirt.org/79345
> [3] 
> http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/1467/
> -- 
> Didi



--
This message was sent by Atlassian JIRA
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1607) Failed ovirt-system-tests_master_check-patch-el7-x86_64

2017-08-23 Thread Yuval Turgeman (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34765#comment-34765
 ] 

Yuval Turgeman commented on OVIRT-1607:
---

It still uses lastSuccessful, but you are right [~ngol...@redhat.com], I added 
a call to buildNumber to see which images we're fetching.  Since buildNumber is 
empty in this case, it produces a wrong download link.  Question is, how can 
buildNumber be empty ?

> Failed ovirt-system-tests_master_check-patch-el7-x86_64
> ---
>
> Key: OVIRT-1607
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1607
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yedidyah Bar David
>Assignee: infra
>
> I want to verify [1]. It (expectedly) failed in the past, needed [2].
> [2] was merged yesterday and [1] still fails. I retriggered it several
> times, and it failed due to different reasons. Last was [3]:
> 08:11:38 + find /dev/shm/ost/deployment-image-ng-suite-master -type f
> '(' -iname 'nose*.xml' -o -iname '*.junit.xml' ')' -exec mv '{}'
> exported-artifacts/ ';'
> 08:11:38 find: ���/dev/shm/ost/deployment-image-ng-suite-master���: No
> such file or directory
> Please have a look. Thanks,
> [1] https://gerrit.ovirt.org/80820
> [2] https://gerrit.ovirt.org/79345
> [3] 
> http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/1467/
> -- 
> Didi



--
This message was sent by Atlassian JIRA
(v1001.0.0-SNAPSHOT#100059)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1544) Generating puddle composes automatically

2017-07-19 Thread Yuval Turgeman (oVirt JIRA) 
Yuval Turgeman created OVIRT-1544:
-

 Summary: Generating puddle composes automatically
 Key: OVIRT-1544
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1544
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yuval Turgeman
Assignee: infra


Hi,

We would like to generate composes on rcm-guest automatically and add this
step to the build process of rhvh and rhvm-appliance.  To do that, we
already have a user setup with a correct authorized key, and we would like
to add the private key to the downstream jenkins in order to automatically
ssh from our job to rcm-guest and build the compose there.
Is it possible ?

Thanks,
Yuval



--
This message was sent by Atlassian JIRA
(v1000.1126.1#100055)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1542) Generating puddle composes automatically

2017-07-19 Thread Yuval Turgeman (oVirt JIRA) 
Yuval Turgeman created OVIRT-1542:
-

 Summary: Generating puddle composes automatically
 Key: OVIRT-1542
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1542
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yuval Turgeman
Assignee: infra


Hi,

We would like to generate composes on rcm-guest automatically and add this
step to the build process of rhvh and rhvm-appliance.  To do that, we
already have a user setup with a correct authorized key, and we would like
to add the private key to the downstream jenkins in order to automatically
ssh from our job to rcm-guest and build the compose there.
Is it possible ?

Thanks,
Yuval



--
This message was sent by Atlassian JIRA
(v1000.1126.1#100055)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months

2017-06-26 Thread Yuval Turgeman (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32838#comment-32838
 ] 

Yuval Turgeman commented on OVIRT-1475:
---

There were more than 2 builds in the job's history after Sep 2016... why did it 
save that single job from 2016 ?

> Check why 
> http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/
>  wasn't time triggered for months
> 
>
> Key: OVIRT-1475
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: eedri
>Assignee: infra
>Priority: High
>
> The follow job 
> http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/
>  is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 
> months(!).
> We need to investigate why it didn't run and maybe find some clues in the 
> logs.
> cc [~sbona...@redhat.com]



--
This message was sent by Atlassian JIRA
(v1000.1085.0#100052)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months

2017-06-25 Thread Yuval Turgeman (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32809#comment-32809
 ] 

Yuval Turgeman commented on OVIRT-1475:
---

Yes, [~eedri] is right, I think the deletion messed up lastSuccessful, making 
it point to some old version.  However, using the rpm would mean a bigger 
change, and it would take a little more time to run (extract the rpm etc).  I 
think that the best way to fix this, is to copy the squashfs from its original 
place to the exported-artifacts dir with a timestamp, so instead of cp 
 exported-artifacts, it would be something like cp squashfs 
exported-artifacts/squashfs-, and let image-ng continue to pick up 
the squashfs by a build number.

> Check why 
> http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/
>  wasn't time triggered for months
> 
>
> Key: OVIRT-1475
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: eedri
>Assignee: infra
>Priority: High
>
> The follow job 
> http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/
>  is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 
> months(!).
> We need to investigate why it didn't run and maybe find some clues in the 
> logs.
> cc [~sbona...@redhat.com]



--
This message was sent by Atlassian JIRA
(v1000.1085.0#100052)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-956) trigger jobs on jenkins

2016-12-21 Thread Yuval Turgeman (oVirt JIRA) 
Yuval Turgeman created OVIRT-956:


 Summary: trigger jobs on jenkins
 Key: OVIRT-956
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-956
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yuval Turgeman
Assignee: infra


Hi,

Can I please get permissions to trigger jobs in jenkin ?

I need to trigger this one:
http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.0-pre_build-artifacts-el7-x86_64/56/


Thanks,
Yuval.



--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra