- Infra - oVirt List Archives

[JIRA] (OVIRT-753) ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-753?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-753: ------------------------------------------------- being verified here: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… > ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands > ----------------------------------------------------------------------------- > > Key: OVIRT-753 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-753 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > In: > http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… > After appliance shutdown: > *00:15:44.383* [[ -n "1" ]] && [[ "$(virt-sparsify --help)" =~ > --in-place ]] && ( virt-sparsify --in-place > ovirt-engine-appliance.qcow2 ; ln ovirt-engine-appliance.qcow2 > ovirt-engine-appliance.qcow2.sparse ; )*00:25:53.734* virt-sparsify: > error: libguestfs error: guestfs_launch failed.*00:25:53.735* This > usually means the libguestfs appliance failed to start or > crashed.*00:25:53.735* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:25:53.735* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:25:53.735* bug report or message to the libguestfs mailing list. > The job should have failed here. Instead, the job continues and fails in a > later stage: > *00:33:01.284* ls -shal ovirt-engine-appliance.ova*00:33:01.287* 1.4G > -rwxr-xr-x. 1 root root 1.4G Oct 6 14:13 > ovirt-engine-appliance.ova*00:33:01.288* echo "all" appliance > done*00:33:01.290* all appliance done*00:33:01.291* + make > check*00:33:01.299* make -f image-tools/build.mk > ovirt-engine-appliance-manifest-rpm*00:33:01.305* make[1]: Entering > directory `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:33:01.305* > guestfish --ro -i -a ovirt-engine-appliance.qcow2 sh 'rpm -qa | sort > -u' > ovirt-engine-appliance-manifest-rpm*00:41:58.044* libguestfs: > error: appliance closed the connection unexpectedly.*00:41:58.044* > This usually means the libguestfs appliance crashed.*00:41:58.044* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.045* > for information about how to debug libguestfs and report > bugs.*00:41:58.045* libguestfs: error: guestfs_launch > failed.*00:41:58.045* This usually means the libguestfs appliance > failed to start or crashed.*00:41:58.045* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.046* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:41:58.046* bug report or message to the libguestfs mailing > list.*00:41:58.059* make[1]: *** [ovirt-engine-appliance-manifest-rpm] > Error 1*00:41:58.059* make[1]: Leaving directory > `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:41:58.060* > make: *** [ovirt-engine-appliance-manifest-rpm] Error 2*00:41:58.065* > Took 2325 seconds > wasting 20 minutes of jenkins slave time testing something already known > broken. > While working on fixing this job, please investigate while it's failing and > open a separate issue or bugzilla for it. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-753) ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-753?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-753: -------------------------------------------- Status: In Progress (was: Blocked) > ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands > ----------------------------------------------------------------------------- > > Key: OVIRT-753 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-753 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > In: > http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… > After appliance shutdown: > *00:15:44.383* [[ -n "1" ]] && [[ "$(virt-sparsify --help)" =~ > --in-place ]] && ( virt-sparsify --in-place > ovirt-engine-appliance.qcow2 ; ln ovirt-engine-appliance.qcow2 > ovirt-engine-appliance.qcow2.sparse ; )*00:25:53.734* virt-sparsify: > error: libguestfs error: guestfs_launch failed.*00:25:53.735* This > usually means the libguestfs appliance failed to start or > crashed.*00:25:53.735* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:25:53.735* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:25:53.735* bug report or message to the libguestfs mailing list. > The job should have failed here. Instead, the job continues and fails in a > later stage: > *00:33:01.284* ls -shal ovirt-engine-appliance.ova*00:33:01.287* 1.4G > -rwxr-xr-x. 1 root root 1.4G Oct 6 14:13 > ovirt-engine-appliance.ova*00:33:01.288* echo "all" appliance > done*00:33:01.290* all appliance done*00:33:01.291* + make > check*00:33:01.299* make -f image-tools/build.mk > ovirt-engine-appliance-manifest-rpm*00:33:01.305* make[1]: Entering > directory `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:33:01.305* > guestfish --ro -i -a ovirt-engine-appliance.qcow2 sh 'rpm -qa | sort > -u' > ovirt-engine-appliance-manifest-rpm*00:41:58.044* libguestfs: > error: appliance closed the connection unexpectedly.*00:41:58.044* > This usually means the libguestfs appliance crashed.*00:41:58.044* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.045* > for information about how to debug libguestfs and report > bugs.*00:41:58.045* libguestfs: error: guestfs_launch > failed.*00:41:58.045* This usually means the libguestfs appliance > failed to start or crashed.*00:41:58.045* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.046* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:41:58.046* bug report or message to the libguestfs mailing > list.*00:41:58.059* make[1]: *** [ovirt-engine-appliance-manifest-rpm] > Error 1*00:41:58.059* make[1]: Leaving directory > `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:41:58.060* > make: *** [ovirt-engine-appliance-manifest-rpm] Error 2*00:41:58.065* > Took 2325 seconds > wasting 20 minutes of jenkins slave time testing something already known > broken. > While working on fixing this job, please investigate while it's failing and > open a separate issue or bugzilla for it. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-837) artifactory /opt dir isn't monitored for space
by Barak Korren (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-837?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-837: ------------------------------------ /var/opt/jfrog needs to be monitored, not /opt since /opt is on the root file system and does not get filled. > artifactory /opt dir isn't monitored for space > ---------------------------------------------- > > Key: OVIRT-837 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-837 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > Artifactory application is running on /opt and if the disk is full the application is failing to provide jars and gets very slow ( but errors on out of space are seen in the logs ). -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-837) artifactory /opt dir isn't monitored for space
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-837?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-837: -------------------------------------------- Epic Link: OVIRT-403 > artifactory /opt dir isn't monitored for space > ---------------------------------------------- > > Key: OVIRT-837 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-837 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > Artifactory application is running on /opt and if the disk is full the application is failing to provide jars and gets very slow ( but errors on out of space are seen in the logs ). -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-837) artifactory /opt dir isn't monitored for space
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

eyal edri [Administrator] created OVIRT-837: ----------------------------------------------- Summary: artifactory /opt dir isn't monitored for space Key: OVIRT-837 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-837 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra Priority: High Artifactory application is running on /opt and if the disk is full the application is failing to provide jars and gets very slow ( but errors on out of space are seen in the logs ). -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #3303 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Nov '16

13 Nov '16

------=_Part_284_55668604.1479048726295 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3303/, Build Number: 3303, Build Status: FAILURE ------=_Part_284_55668604.1479048726295--

1 1

[JIRA] (OVIRT-836) add more lago slaves
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

eyal edri [Administrator] created OVIRT-836: ----------------------------------------------- Summary: add more lago slaves Key: OVIRT-836 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-836 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Priority: High Now that we have more Jenkins slaves ( and soon we'll have stronger machines with higher RAM to add even more) we need to move a few hypervisors to be Lago slaves so we can handle an increase of load which we're already seeing with new tests and suites being added. It will be much more challenging once we'll introduce Gating jobs with Zuul which will require even more slaves. -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-836) add more lago slaves
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-836?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-836: -------------------------------------------- Epic Link: OVIRT-400 > add more lago slaves > -------------------- > > Key: OVIRT-836 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-836 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > Now that we have more Jenkins slaves ( and soon we'll have stronger machines with higher RAM to add even more) we need to move a few hypervisors to be Lago slaves so we can handle an increase of load which we're already seeing with new tests and suites being added. > It will be much more challenging once we'll introduce Gating jobs with Zuul which will require even more slaves. -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-835) Install a Zuul server and integrate with oVirt infra
by Barak Korren (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-835?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-835: ------------------------------- Summary: Install a Zuul server and integrate with oVirt infra (was: Install a Zool server and integrate with oVirt infra) > Install a Zuul server and integrate with oVirt infra > ---------------------------------------------------- > > Key: OVIRT-835 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-835 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > Setup zool.phx.ovirt.org > Install Zool and all zervices needed to run it > Integrate Zool with oVirt Gerrit and Jenkins -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-835) Install a Zuul server and integrate with oVirt infra
by Barak Korren (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-835?page=com.atlassian.jira.p… ] Barak Korren reassigned OVIRT-835: ---------------------------------- Assignee: Barak Korren (was: infra) > Install a Zuul server and integrate with oVirt infra > ---------------------------------------------------- > > Key: OVIRT-835 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-835 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > Setup zool.phx.ovirt.org > Install Zool and all zervices needed to run it > Integrate Zool with oVirt Gerrit and Jenkins -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0