[JIRA] (OVIRT-1980) CI test never reported back to Gerrit?
Yaniv Kaul created OVIRT-1980: - Summary: CI test never reported back to Gerrit? Key: OVIRT-1980 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1980 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yaniv Kaul Assignee: infra Please see https://gerrit.ovirt.org/#/c/90570/ - the Jenkins job started yesterday. Y. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35926#comment-35926 ] Yaniv Kaul commented on OST-99: --- I think it'd be easier to start with running those tests from the Engine VM, though I really like the containers idea - if it works well, we can probably use container for other areas as well (storage !). I would not start with the container just because it'll offset us from our main goal of getting the UI automation in. > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > -- > > Key: OST-99 > URL: https://ovirt-jira.atlassian.net/browse/OST-99 > Project: oVirt system tests > Issue Type: Improvement >Reporter: Greg Sheremeta >Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open > headless firefox and actually open the UI, perform a login, make sure things > look good, make sure there are no ui.log errors, etc. I'll also eventually > add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test > machine, along with chromium. There are also some binary components required, > geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, > /opt/chromium62, etc. on the machine running the suite. So I think it makes > sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want > to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1911) RFE: Add relevant git commit messages as comments in the relevant Bugzillas
Yaniv Kaul created OVIRT-1911: - Summary: RFE: Add relevant git commit messages as comments in the relevant Bugzillas Key: OVIRT-1911 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Gerrit/git Reporter: Yaniv Kaul Assignee: infra When a bug moves to MODIFIED, can we add the relevant commit message(s) to the bug? I see it happening in RHEL from time to time, and I think it's easier (for us and QE) then clicking on the link to Gerrit. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1911) RFE: Add relevant git commit messages as comments in the relevant Bugzillas
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-1911: -- Epic Link: OVIRT-411 > RFE: Add relevant git commit messages as comments in the relevant Bugzillas > --- > > Key: OVIRT-1911 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1911 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git >Reporter: Yaniv Kaul >Assignee: infra > > When a bug moves to MODIFIED, can we add the relevant commit message(s) to > the bug? > I see it happening in RHEL from time to time, and I think it's easier (for us > and QE) then clicking on the link to Gerrit. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100080) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1910) Strange Lago CI test failure
Yaniv Kaul created OVIRT-1910:
-
Summary: Strange Lago CI test failure
Key: OVIRT-1910
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1910
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Yaniv Kaul
Assignee: infra
My patch[1] is failing, but I'm not sure why.
See [2] for the job - the issues seems to be with the pusher - see its
log[3]:
2018-02-23 12:42:16,222:DEBUG:__main__:Executing command: 'git log -1
--pretty=format:%H'
2018-02-23 12:42:16,230:DEBUG:__main__:Git exited with status: 0
2018-02-23 12:42:16,230:DEBUG:__main__: stderr
2018-02-23 12:42:16,230:DEBUG:__main__: stdout
2018-02-23 12:42:16,230:DEBUG:__main__:
c26adc01449d97899aac18406298374de0e7dd73
2018-02-23 12:42:16,231:DEBUG:__main__:Executing command: 'git
rev-parse jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}'
2018-02-23 12:42:16,237:DEBUG:__main__:Git exited with status: 128
2018-02-23 12:42:16,237:DEBUG:__main__: stderr
2018-02-23 12:42:16,237:DEBUG:__main__:fatal: ambiguous argument
'jenkins-lago_master_github_check-patch-el7-x86_64-711^{commit}':
unknown revision or path not in the working tree.
Any ideas?
TIA,
Y.
[1] https://github.com/lago-project/lago/pull/695
[2]
http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/
[3]
http://jenkins.ovirt.org/job/lago_master_github_check-patch-el7-x86_64/711/artifact/exported-artifacts/pusher_logs/push_lago.log
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100080)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1829) link in 'Build successful' message is showing 'http' and not 'https' (to Jenkins)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35608#comment-35608 ] Yaniv Kaul commented on OVIRT-1829: --- Ah, my mistake. We actually don't use HTTPS... Please close the ticket. > link in 'Build successful' message is showing 'http' and not 'https' (to > Jenkins) > - > > Key: OVIRT-1829 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1829 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git >Reporter: Yaniv Kaul >Assignee: infra >Priority: Lowest > > Example: > Build Successful > http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_master_check-patch-fc26-x86_64/546/ > : SUCCESS > http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_master_check-patch-el7-x86_64/1237/ > : SUCCESS > http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_master_check-patch-fc25-x86_64/629/ > : SUCCESS > To view, visit change 86010. To unsubscribe, visit settings. > The links are actually https://... -- 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-1829) link in 'Build successful' message is showing 'http' and not 'https' (to Jenkins)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-1829: -- Epic Link: OVIRT-403 > link in 'Build successful' message is showing 'http' and not 'https' (to > Jenkins) > - > > Key: OVIRT-1829 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1829 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git >Reporter: Yaniv Kaul >Assignee: infra >Priority: Lowest > > Example: > Build Successful > http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_master_check-patch-fc26-x86_64/546/ > : SUCCESS > http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_master_check-patch-el7-x86_64/1237/ > : SUCCESS > http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_master_check-patch-fc25-x86_64/629/ > : SUCCESS > To view, visit change 86010. To unsubscribe, visit settings. > The links are actually https://... -- 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-1829) link in 'Build successful' message is showing 'http' and not 'https' (to Jenkins)
Yaniv Kaul created OVIRT-1829: - Summary: link in 'Build successful' message is showing 'http' and not 'https' (to Jenkins) Key: OVIRT-1829 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1829 Project: oVirt - virtualization made easy Issue Type: Bug Components: Gerrit/git Reporter: Yaniv Kaul Assignee: infra Priority: Lowest Example: Build Successful http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_master_check-patch-fc26-x86_64/546/ : SUCCESS http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_master_check-patch-el7-x86_64/1237/ : SUCCESS http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_master_check-patch-fc25-x86_64/629/ : SUCCESS To view, visit change 86010. To unsubscribe, visit settings. The links are actually https://... -- 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-1763) Increase entropy for hosts
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35369#comment-35369 ] Yaniv Kaul commented on OVIRT-1763: --- [~dron] - the above looks like vm_run failed - took more than 3m. It has nothing to do with entropy? > Increase entropy for hosts > -- > > Key: OVIRT-1763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1763 > Project: oVirt - virtualization made easy > Issue Type: Bug >Reporter: Dafna Ron >Assignee: infra > > we had a failure in ost that was really hard to debug: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3795/ > There are no failures in the logs and the test itself was terminated by a > timeout. > It took the vms a long time to download packages and install and didi seems > to think that this is due to limited entropy on the physical host. > we need to review this issue and increase the entropy on the hosts. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100072) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1763) Increase entropy for hosts
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35341#comment-35341 ] Yaniv Kaul commented on OVIRT-1763: --- How? We have virtio-rng. What else would you like to add? rngd? > Increase entropy for hosts > -- > > Key: OVIRT-1763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1763 > Project: oVirt - virtualization made easy > Issue Type: Bug >Reporter: Dafna Ron >Assignee: infra > > we had a failure in ost that was really hard to debug: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3795/ > There are no failures in the logs and the test itself was terminated by a > timeout. > It took the vms a long time to download packages and install and didi seems > to think that this is due to limited entropy on the physical host. > we need to review this issue and increase the entropy on the hosts. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1509) Please upload CirrOS 0.3.5 to Glance
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-1509: -- Epic Link: OVIRT-400 > Please upload CirrOS 0.3.5 to Glance > > > Key: OVIRT-1509 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1509 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: oVirt Infra >Reporter: Yaniv Kaul >Assignee: infra > > Please upload CirrOS VM v0.3.5 (I believe it's > http://download.cirros-cloud.net/0.3.5/cirros-0.3.5-x86_64-disk.img ) to > glance.ovirt.org. -- This message was sent by Atlassian JIRA (v1000.1110.1#100054) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1509) Please upload CirrOS 0.3.5 to Glance
Yaniv Kaul created OVIRT-1509: - Summary: Please upload CirrOS 0.3.5 to Glance Key: OVIRT-1509 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1509 Project: oVirt - virtualization made easy Issue Type: Task Components: oVirt Infra Reporter: Yaniv Kaul Assignee: infra Please upload CirrOS VM v0.3.5 (I believe it's http://download.cirros-cloud.net/0.3.5/cirros-0.3.5-x86_64-disk.img ) to glance.ovirt.org. -- This message was sent by Atlassian JIRA (v1000.1110.1#100054) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1459) Strange OST checkpatch failure: mv: cannot stat ���*__logs���: No such file or directory
Yaniv Kaul created OVIRT-1459: - Summary: Strange OST checkpatch failure: mv: cannot stat ���*__logs���: No such file or directory Key: OVIRT-1459 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1459 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Yaniv Kaul Assignee: infra See http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/972/console : 06:40:34 + mkdir logs 06:40:34 + mv '*__logs' logs 06:40:34 mv: cannot stat ���*__logs���: No such file or directory 06:40:34 Took 0 seconds 06:40:34 === 06:40:34 logout 06:40:34 Finish: shell 06:40:34 @@ 06:40:34 @@ Tue Jun 20 06:40:34 UTC 2017 automation/check-patch.sh chroot finished 06:40:34 @@ took 14 seconds 06:40:34 @@ rc = 1 06:40:34 @@ -- This message was sent by Atlassian JIRA (v1000.1074.0#100051) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1459) Strange OST checkpatch failure: mv: cannot stat ���*__logs���: No such file or directory
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-1459: -- Epic Link: OVIRT-400 > Strange OST checkpatch failure: mv: cannot stat ���*__logs���: No such file > or directory > > > Key: OVIRT-1459 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1459 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST >Reporter: Yaniv Kaul >Assignee: infra > > See > http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/972/console > : > 06:40:34 + mkdir logs > 06:40:34 + mv '*__logs' logs > 06:40:34 mv: cannot stat ���*__logs���: No such file or directory > 06:40:34 Took 0 seconds > 06:40:34 === > 06:40:34 logout > 06:40:34 Finish: shell > 06:40:34 @@ > 06:40:34 @@ Tue Jun 20 06:40:34 UTC 2017 automation/check-patch.sh chroot > finished > 06:40:34 @@ took 14 seconds > 06:40:34 @@ rc = 1 > 06:40:34 @@ -- This message was sent by Atlassian JIRA (v1000.1074.0#100051) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1367) Please add latest CirrOS to glance.ovirt.org
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30304#comment-30304 ] Yaniv Kaul commented on OVIRT-1367: --- [~eedri] - we are quite explicit taking 0.3.4 (downloading it from Glance). We'll need to change once the new version is uploaded. I've tried to use Fedora, the name was too long and I was too lazy to battle with it. Also, it's ~200MB, which is too much to download. > Please add latest CirrOS to glance.ovirt.org > > > Key: OVIRT-1367 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1367 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Hosting >Reporter: Yaniv Kaul >Assignee: infra > > v 0.3.5 provides virtio-scsi (see > https://git.launchpad.net/cirros/commit/?id=6752f081363a0d38b1dd41593b47ac60b0caab52 > ) which would be great to use in ovirt-system-tests. > I think the correct link is > http://download.cirros-cloud.net/0.3.5/cirros-0.3.5-x86_64-disk.img > It's also a bit smaller than 0.3.4, but nothing substantial. -- This message was sent by Atlassian JIRA (v1000.929.2#100040) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1367) Please add latest CirrOS to glance.ovirt.org
Yaniv Kaul created OVIRT-1367: - Summary: Please add latest CirrOS to glance.ovirt.org Key: OVIRT-1367 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1367 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Hosting Reporter: Yaniv Kaul Assignee: infra v 0.3.5 provides virtio-scsi (see https://git.launchpad.net/cirros/commit/?id=6752f081363a0d38b1dd41593b47ac60b0caab52 ) which would be great to use in ovirt-system-tests. I think the correct link is http://download.cirros-cloud.net/0.3.5/cirros-0.3.5-x86_64-disk.img It's also a bit smaller than 0.3.4, but nothing substantial. -- This message was sent by Atlassian JIRA (v1000.929.2#100040) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1367) Please add latest CirrOS to glance.ovirt.org
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-1367: -- Epic Link: OVIRT-400 > Please add latest CirrOS to glance.ovirt.org > > > Key: OVIRT-1367 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1367 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Hosting >Reporter: Yaniv Kaul >Assignee: infra > > v 0.3.5 provides virtio-scsi (see > https://git.launchpad.net/cirros/commit/?id=6752f081363a0d38b1dd41593b47ac60b0caab52 > ) which would be great to use in ovirt-system-tests. > I think the correct link is > http://download.cirros-cloud.net/0.3.5/cirros-0.3.5-x86_64-disk.img > It's also a bit smaller than 0.3.4, but nothing substantial. -- This message was sent by Atlassian JIRA (v1000.929.2#100040) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29503#comment-29503 ] Yaniv Kaul commented on OVIRT-1295: --- I think we need to see how many of those we have - and how many have CR+1 and V+1 and can go through the same process as well - on lower priority (say, on 3AM in the morning). What about running o-s-t on the first batch? > Add job to auto-rebase patches that are ready to be merged > --- > > Key: OVIRT-1295 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295 > Project: oVirt - virtualization made easy > Issue Type: Improvement >Reporter: eyal edri [Administrator] >Assignee: infra > > We want to help stable branch maintainers to minimize the time needed for > merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the > chance of merge conflicts. > A suggestion was made to create a job which will detect patches ready to be > merged with the flags CR +2 and V +1 set and will auto rebase them, so when a > maintainer is ready to submit a patch, hopefully the patch won't need a > rebase and can be merged without further waiting for rebase or CI. > This approach might introduce challenges when working on patches that are > dependent on other patches and a specific logic might be required to handle > special cases. > [~tni...@redhat.com][~ykaul][~dfediuck] I hope this conveys the need and > requirement, please comment or add thoughts if I missed anything. > Initially we'll try enabling it for ovirt-engine on 4.1 branch. -- This message was sent by Atlassian JIRA (v1000.870.5#100039) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1195) Unexplained failure in CI job
Yaniv Kaul created OVIRT-1195: - Summary: Unexplained failure in CI job Key: OVIRT-1195 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1195 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Yaniv Kaul Assignee: infra Priority: High See http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/197/console I'm not sure what the failure is. All I see is: 18:50:23 Start: yum install 18:50:37 ERROR: Command failed. See logs for output. -- This message was sent by Atlassian JIRA (v1000.784.1#100032) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1195) Unexplained failure in CI job
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-1195: -- Epic Link: OVIRT-400 > Unexplained failure in CI job > - > > Key: OVIRT-1195 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1195 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins >Reporter: Yaniv Kaul >Assignee: infra >Priority: High > > See > http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/197/console > > I'm not sure what the failure is. All I see is: > 18:50:23 Start: yum install > 18:50:37 ERROR: Command failed. See logs for output. -- This message was sent by Atlassian JIRA (v1000.784.1#100032) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1164) Remove most of the images from glance.ovirt.org
Yaniv Kaul created OVIRT-1164: - Summary: Remove most of the images from glance.ovirt.org Key: OVIRT-1164 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1164 Project: oVirt - virtualization made easy Issue Type: Task Components: General Reporter: Yaniv Kaul Assignee: infra I'd like to make sure people are not abusing and downloading images from Glance that are not directly related to oVirt. Providing it as a service for download is not our aim. Currently, it has a lot of different images, multiple versions of them, etc. Specifically, multiple versions of Ubuntu, and older versions of Atomic, CentOS, Fedora should be removed. -- This message was sent by Atlassian JIRA (v1000.769.1#100032) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1164) Remove most of the images from glance.ovirt.org
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-1164: -- Epic Link: OVIRT-403 > Remove most of the images from glance.ovirt.org > --- > > Key: OVIRT-1164 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1164 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General >Reporter: Yaniv Kaul >Assignee: infra > > I'd like to make sure people are not abusing and downloading images from > Glance that are not directly related to oVirt. Providing it as a service for > download is not our aim. > Currently, it has a lot of different images, multiple versions of them, etc. > Specifically, multiple versions of Ubuntu, and older versions of Atomic, > CentOS, Fedora should be removed. -- This message was sent by Atlassian JIRA (v1000.769.1#100032) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1133) CI fails on "java.io.IOException: Remote call on ovirt-srv24.phx.ovirt.org failed"
Yaniv Kaul created OVIRT-1133:
-
Summary: CI fails on "java.io.IOException: Remote call on
ovirt-srv24.phx.ovirt.org failed"
Key: OVIRT-1133
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1133
Project: oVirt - virtualization made easy
Issue Type: Outage
Components: Jenkins
Reporter: Yaniv Kaul
Assignee: infra
Priority: Highest
>From :
18:48:48 > git rev-parse FETCH_HEAD^{commit} # timeout=10
18:48:50 java.io.IOException: Remote call on ovirt-srv24.phx.ovirt.org failed
18:48:50at hudson.remoting.Channel.call(Channel.java:830)
18:48:50at
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256)
18:48:50at com.sun.proxy.$Proxy70.withRepository(Unknown Source)
--
This message was sent by Atlassian JIRA
(v1000.747.1#100028)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes
[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26430#comment-26430 ] Yaniv Kaul commented on OST-39: --- 0. I think it's time to understand if we want to use Lago for Kubevirt or not. I prefer vagrant - it's more common, works out of the box on both Ubuntu and possibly other operating systems (does it have nested virt on Mac or Windows?). I would like to believe that moving to vagrant is actually a good opportunity to start afresh. Lago is not killed by it, and will remain relevant for OST. 1. Ansible is supported today in vagrant. I believe a fair start of support exists in Lago as well - but as Barak pointed out, probably need a bit of Cloud-Init work too perhaps - not sure. Engine is not containerized for real yet. Once it does, we'll probably deploy it via standard Pod deployment options (saw today ansible-containers, for example - sounds neat). > Run OST against vdsm+Engine on kubernetes > - > > Key: OST-39 > URL: https://ovirt-jira.atlassian.net/browse/OST-39 > Project: oVirt system tests > Issue Type: New Feature >Reporter: Fabian Deutsch >Assignee: infra >Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.718.3#100026) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes
[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26428#comment-26428 ] Yaniv Kaul commented on OST-39: --- [~eedri] - too many items there, I think. We should probably document it in KubeVirt's trello and not here. 0. Do we use Lago as is, or vagrant? Unclear to me, and I do see a nice advantage for the community using vagrant. 1. Ansible installing K8S - makes sense to me. This is quite integrated into vagrant and is easy to do (though requires Ansible on Host L0) in Lago. Do we have Ansible to install Engine? Quite possibly from QCI - we should utilize that - but it's not within a Container - Engine is not yet containerized (production-ready, at least) 3. Good point about Add Host. Donno yet... 4. ACK 5. ACK. > Run OST against vdsm+Engine on kubernetes > - > > Key: OST-39 > URL: https://ovirt-jira.atlassian.net/browse/OST-39 > Project: oVirt system tests > Issue Type: New Feature >Reporter: Fabian Deutsch >Assignee: infra >Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.718.3#100026) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1048) Run OST against vdsm+Engine on kubernetes
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26402#comment-26402 ] Yaniv Kaul commented on OVIRT-1048: --- [~eedri] - I strongly agree. I think lago has just gained good support for providing the Ansible hosts list (via https://github.com/lago-project/lago/pull/428 ). The provides the basic infrastructure needed from the host (L0) to do things via Ansible. I'd argue though that we need to use Ansible from L1, not from L0. So I rather we copy the relevant Ansible, scripts, what not, and execute it from L1. I'm not sure I'd use Atomic right away, though I agree it's a goal. > Run OST against vdsm+Engine on kubernetes > - > > Key: OVIRT-1048 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1048 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins, Lago >Reporter: Fabian Deutsch >Assignee: infra >Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.718.3#100026) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1028) Configure experimental job with ANSI output - so it'd be easier to look at
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25714#comment-25714 ] Yaniv Kaul commented on OVIRT-1028: --- Others (http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86_64/815/consoleFull ) for example work fine. > Configure experimental job with ANSI output - so it'd be easier to look at > -- > > Key: OVIRT-1028 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1028 > Project: oVirt - virtualization made easy > Issue Type: Improvement >Reporter: Yaniv Kaul >Assignee: infra > Labels: experimental, jenkins, system-tests > > O-S-T uses ANSI colors for easier output. For some reason, some jobs aren't > configured with it. > http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_experimental_master/4739/console > is such an example. -- This message was sent by Atlassian JIRA (v1000.695.1#100025) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-933) Fix repoproxy service and logging mess
[
https://ovirt-jira.atlassian.net/browse/OVIRT-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24228#comment-24228
]
Yaniv Kaul commented on OVIRT-933:
--
Moving priority to High, based on 'will cause it to crash' statement above.
> Fix repoproxy service and logging mess
> --
>
> Key: OVIRT-933
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-933
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
>Reporter: Barak Korren
>Assignee: infra
>Priority: High
>
> There are a couple of issues with the way repoproxy runs right now, these
> issues probably cause it to be less stable then it can:
> # repoproxy is can currently be invoked only from puppet, because a lot of
> the data on how to run it is stored right now in puppet and nowhere else. We
> should make puppet create a systemd unit file to run repoproxy instead of
> running it itself. This way we can get rid of the cron job that runs puppet
> every 2 minutes on the proxy.
> # repoproxy is configured to run as the '{{squid}}' user and log to
> '{{/var/log/repoproxy.log}}'. That file is pre-created with the right
> permissions bu Puppet so repoproxy can write to it. However, the Python
> logger in repoproxy is configured to try and rotate the log when it becomes
> too big. That, in turn, will cause it to crash because the '{{squid}}' user
> cannot rename file in '{{/var/log}}'. We should move repoproxy logs somewhere
> else.
--
This message was sent by Atlassian JIRA
(v1000.620.0#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-933) Fix repoproxy service and logging mess
[
https://ovirt-jira.atlassian.net/browse/OVIRT-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yaniv Kaul updated OVIRT-933:
-
Priority: High (was: Medium)
> Fix repoproxy service and logging mess
> --
>
> Key: OVIRT-933
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-933
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
>Reporter: Barak Korren
>Assignee: infra
>Priority: High
>
> There are a couple of issues with the way repoproxy runs right now, these
> issues probably cause it to be less stable then it can:
> # repoproxy is can currently be invoked only from puppet, because a lot of
> the data on how to run it is stored right now in puppet and nowhere else. We
> should make puppet create a systemd unit file to run repoproxy instead of
> running it itself. This way we can get rid of the cron job that runs puppet
> every 2 minutes on the proxy.
> # repoproxy is configured to run as the '{{squid}}' user and log to
> '{{/var/log/repoproxy.log}}'. That file is pre-created with the right
> permissions bu Puppet so repoproxy can write to it. However, the Python
> logger in repoproxy is configured to try and rotate the log when it becomes
> too big. That, in turn, will cause it to crash because the '{{squid}}' user
> cannot rename file in '{{/var/log}}'. We should move repoproxy logs somewhere
> else.
--
This message was sent by Atlassian JIRA
(v1000.620.0#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-932) Wrong Lago version used in CI
Yaniv Kaul created OVIRT-932: Summary: Wrong Lago version used in CI Key: OVIRT-932 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-932 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Yaniv Kaul Assignee: infra Priority: High See http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86_64/324/console : Error: package lago-ovirt-0.23.0-1.fc24.noarch requires python-lago-ovirt = 0.23.0, but none of the providers can be installed It should use v0.28. -- This message was sent by Atlassian JIRA (v1000.620.0#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-932) Wrong Lago version used in CI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yaniv Kaul updated OVIRT-932: - Epic Link: OVIRT-400 > Wrong Lago version used in CI > - > > Key: OVIRT-932 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-932 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins >Reporter: Yaniv Kaul >Assignee: infra >Priority: High > > See > http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86_64/324/console > : > Error: package lago-ovirt-0.23.0-1.fc24.noarch requires python-lago-ovirt = > 0.23.0, but none of the providers can be installed > It should use v0.28. -- This message was sent by Atlassian JIRA (v1000.620.0#100023) ___ Infra mailing list Infra@ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-902) Speed up mock_runner.sh setup time by using caches.
[ https://ovirt-jira.atlassian.net/browse/OVIRT-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23804#comment-23804 ] Yaniv Kaul commented on OVIRT-902: -- 1. I'm not sure if it's here or requires a different ticket, but this is SLOW (taken from http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5101/consoleFull ): *00:01:28.338* INFO: installing package(s): autoconf automake gdb git libguestfs-tools-c libselinux-python3 libvirt-python3 m2crypto make mom openvswitch policycoreutils-python PyYAML python-blivet python-coverage python2-decorator python-devel python-inotify python-ioprocess python-mock python-netaddr python-pthreading python-setuptools python-six python-requests python3-decorator python3-netaddr python3-nose python3-six python3-yaml rpm-build sanlock-python sudo yum yum-utils *00:03:48.999* INFO: None 2:20 to install packages, is VERY slow. 2. Then there are the pip stuff - which probably are also going somewhere off to the 'net: 00:03:52.839 + easy_install pip ... 00:03:53.401 + pip install -U tox==2.1.1 ... 00:03:55.843 Downloading pluggy-0.3.1-py2.py3-none-any.whl 00:03:55.868 Installing collected packages: virtualenv, py, pluggy, tox 00:03:56.223 Successfully installed pluggy-0.3.1 py-1.4.31 tox-2.1.1 virtualenv-15.1.0 So only 4 seconds, but probably not needed at all. 3. Why not set locale? 00:03:56.670 + ./autogen.sh --system --enable-hooks --enable-vhostmd 00:03:56.678 perl: warning: Setting locale failed. 00:03:56.678 perl: warning: Please check that your locale settings: 00:03:56.679LANGUAGE = (unset), 00:03:56.679LC_ALL = (unset), 00:03:56.679LANG = "en_US.UTF-8" 4. The 5 seconds here are probably due to slow storage! 00:04:05.096 client/Makefile.am:23: installing 'build-aux/py-compile' 00:04:10.239 Running ./configure with --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=/usr/lib64 --enable-hooks --enable-vhostmd 5. This is also going out to the Internet? 00:04:14.989 + debuginfo-install -y python ... 00:04:30.879 glibc-debuginfo-common.x86_64 0:2.23.1-11.fc24 6. Again some more deps: 00:05:23.621 tox -e tests 00:05:23.912 tests create: /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/.tox/tests 00:05:29.991 tests installdeps: nose==1.3.7 7. it's not clear if the nose tests are running in parallel. Is that supported by VDSM tests? 8. Not sure what is going on here: 00:09:34.017 + coverage html -d /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/exported-artifacts/htmlcov 00:09:49.213 + popd 00:09:49.213 ~ 00:09:49.213 + shopt -s extglob 00:09:49.213 + git diff-tree --no-commit-id --name-only -r HEAD 00:09:49.213 + egrep --quiet 'vdsm.spec.in|Makefile.am' 00:19:07.994 Took 915 seconds > Speed up mock_runner.sh setup time by using caches. > --- > > Key: OVIRT-902 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-902 > Project: oVirt - virtualization made easy > Issue Type: Improvement >Reporter: Barak Korren >Assignee: infra >Priority: High > Labels: mock, mock_runner.sh, standard-ci > > We've already known that setting up mock takes a while, but mock has some > built-in caching features that should allow us to speed this up. > We need to ensure those features are enabled by mock_runner.sh. The mock > options to look at are: > * root_cache_enable > * yum_cache_enable > Both these options should be set to true in the mock chroot config file. > We've been using these option downstream in minimead and the vdsm build > scripts, so they should be safe to use. -- This message was sent by Atlassian JIRA (v1000.610.2#100023) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-459) create ovirt-system-tests feature page on ovirt.org
[ https://ovirt-jira.atlassian.net/browse/OVIRT-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14210#comment-14210 ] Yaniv Kaul commented on OVIRT-459: -- Ideally, yes. I'd separate the test plan (which I hope QE would add a bit) and a simple positive test case to see if we can test this functionality in ovirt-system-tests. > create ovirt-system-tests feature page on ovirt.org > > > Key: OVIRT-459 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-459 > Project: oVirt - virtualization made easy > Issue Type: Task >Reporter: eyal edri [Administrator] >Assignee: infra > > We need to have a single page on ovirt.org to concentrate all > ovirt-system-tests docs and plans per ovirt version. > Ideally we'll want a test plan attached to each feature page in oVirt 4.0 to > start with. > [~ykaul] what do you think? -- This message was sent by Atlassian JIRA (v7.2.0-OD-04-029#72002) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-95) [jenkins] add job to run upgrade vdsm from version X to version Y
[ https://ovirt-jira.atlassian.net/browse/OVIRT-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907#comment-13907 ] Yaniv Kaul commented on OVIRT-95: - Theoretically, of course. Practically, I'm not sure Lago is ready yet for upgrade tests (you need to add that upgrade tests to the previous version or something). Interesting topic to tackle actually - upgrade from 3.6 to master. Let me think about it a bit (especially concerned with the new repos and how we add them intelligently). > [jenkins] add job to run upgrade vdsm from version X to version Y > - > > Key: OVIRT-95 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-95 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins >Affects Versions: Test >Reporter: eyal edri [Administrator] >Assignee: infra > Labels: infra,vdsm,jenkins > > vdsm upgrade should be tested. (following on bug that was found). > suggested flow: > 1. install vdsm version X (e.g from 3.2) > 2. build latest vdsm version (3.3 or master) > 3. yum update vdsm > 4. check if service is up and running. -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
