May 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1421) Docker storage issues on FC24 nodes
by Barak Korren (oVirt JIRA) 31 May '17

31 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1421?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1421: -------------------------------- Summary: Docker storage issues on FC24 nodes (was: Docker storage issues on FC25 nodes) > Docker storage issues on FC24 nodes > ----------------------------------- > > Key: OVIRT-1421 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1421 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: containers > > docekr startup seems to be failing on FC24 nodes and making other dokcer commands get stuck forever. > The core reason behind the failure seems to be that the Docker storage setup failed: > {code} > [root@vm0064 ~]# systemctl status docker-storage-setup > ● docker-storage-setup.service - Docker Storage Setup > Loaded: loaded (/usr/lib/systemd/system/docker-storage-setup.service; disabled; vendor preset: disabled) > Active: failed (Result: exit-code) since Tue 2017-05-30 03:14:49 UTC; 1 day 2h ago > Process: 1489 ExecStart=/usr/bin/docker-storage-setup (code=exited, status=1/FAILURE) > Main PID: 1489 (code=exited, status=1/FAILURE) > May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: Starting Docker Storage Setup... > May 30 03:14:49 vm0064.workers-phx.ovirt.org docker-storage-setup[1489]: INFO: Volume group backing root filesystem could not be determined > May 30 03:14:49 vm0064.workers-phx.ovirt.org docker-storage-setup[1489]: ERROR: No valid volume group found. Exiting. > May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: docker-storage-setup.service: Main process exited, code=exited, status=1/FAILURE > May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: Failed to start Docker Storage Setup. > May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: docker-storage-setup.service: Unit entered failed state. > May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: docker-storage-setup.service: Failed with result 'exit-code'. > {code} > This seem to be does to the fact that the system's root filesystem is on a plain disk rather then LVM. This is although the docker default DM storage driver is supposed to be able to use a plaing file on the filesystem. Need to check if this is an issue specific to this slave of something that has to do with all FC24 slaves. -- This message was sent by Atlassian JIRA (v1000.1010.2#100044)

1 0

[JIRA] (OVIRT-1421) Docker storage issues on FC25 nodes
by Barak Korren (oVirt JIRA) 31 May '17

31 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1421?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1421: -------------------------------- Labels: containers (was: ) > Docker storage issues on FC25 nodes > ----------------------------------- > > Key: OVIRT-1421 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1421 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: containers > > docekr startup seems to be failing on FC24 nodes and making other dokcer commands get stuck forever. > The core reason behind the failure seems to be that the Docker storage setup failed: > {code} > [root@vm0064 ~]# systemctl status docker-storage-setup > ● docker-storage-setup.service - Docker Storage Setup > Loaded: loaded (/usr/lib/systemd/system/docker-storage-setup.service; disabled; vendor preset: disabled) > Active: failed (Result: exit-code) since Tue 2017-05-30 03:14:49 UTC; 1 day 2h ago > Process: 1489 ExecStart=/usr/bin/docker-storage-setup (code=exited, status=1/FAILURE) > Main PID: 1489 (code=exited, status=1/FAILURE) > May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: Starting Docker Storage Setup... > May 30 03:14:49 vm0064.workers-phx.ovirt.org docker-storage-setup[1489]: INFO: Volume group backing root filesystem could not be determined > May 30 03:14:49 vm0064.workers-phx.ovirt.org docker-storage-setup[1489]: ERROR: No valid volume group found. Exiting. > May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: docker-storage-setup.service: Main process exited, code=exited, status=1/FAILURE > May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: Failed to start Docker Storage Setup. > May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: docker-storage-setup.service: Unit entered failed state. > May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: docker-storage-setup.service: Failed with result 'exit-code'. > {code} > This seem to be does to the fact that the system's root filesystem is on a plain disk rather then LVM. This is although the docker default DM storage driver is supposed to be able to use a plaing file on the filesystem. Need to check if this is an issue specific to this slave of something that has to do with all FC24 slaves. -- This message was sent by Atlassian JIRA (v1000.1010.2#100044)

1 0

[JIRA] (OVIRT-1421) Docker storage issues on FC25 nodes
by Barak Korren (oVirt JIRA) 31 May '17

31 May '17

Barak Korren created OVIRT-1421: ----------------------------------- Summary: Docker storage issues on FC25 nodes Key: OVIRT-1421 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1421 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Barak Korren Assignee: infra Priority: High docekr startup seems to be failing on FC24 nodes and making other dokcer commands get stuck forever. The core reason behind the failure seems to be that the Docker storage setup failed: {code} [root@vm0064 ~]# systemctl status docker-storage-setup ● docker-storage-setup.service - Docker Storage Setup Loaded: loaded (/usr/lib/systemd/system/docker-storage-setup.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2017-05-30 03:14:49 UTC; 1 day 2h ago Process: 1489 ExecStart=/usr/bin/docker-storage-setup (code=exited, status=1/FAILURE) Main PID: 1489 (code=exited, status=1/FAILURE) May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: Starting Docker Storage Setup... May 30 03:14:49 vm0064.workers-phx.ovirt.org docker-storage-setup[1489]: INFO: Volume group backing root filesystem could not be determined May 30 03:14:49 vm0064.workers-phx.ovirt.org docker-storage-setup[1489]: ERROR: No valid volume group found. Exiting. May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: docker-storage-setup.service: Main process exited, code=exited, status=1/FAILURE May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: Failed to start Docker Storage Setup. May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: docker-storage-setup.service: Unit entered failed state. May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: docker-storage-setup.service: Failed with result 'exit-code'. {code} This seem to be does to the fact that the system's root filesystem is on a plain disk rather then LVM. This is although the docker default DM storage driver is supposed to be able to use a plaing file on the filesystem. Need to check if this is an issue specific to this slave of something that has to do with all FC24 slaves. -- This message was sent by Atlassian JIRA (v1000.1010.2#100044)

1 0

[JIRA] (OVIRT-1421) Docker storage issues on FC25 nodes
by Barak Korren (oVirt JIRA) 31 May '17

31 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1421?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1421: -------------------------------- Epic Link: OVIRT-400 > Docker storage issues on FC25 nodes > ----------------------------------- > > Key: OVIRT-1421 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1421 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: High > > docekr startup seems to be failing on FC24 nodes and making other dokcer commands get stuck forever. > The core reason behind the failure seems to be that the Docker storage setup failed: > {code} > [root@vm0064 ~]# systemctl status docker-storage-setup > ● docker-storage-setup.service - Docker Storage Setup > Loaded: loaded (/usr/lib/systemd/system/docker-storage-setup.service; disabled; vendor preset: disabled) > Active: failed (Result: exit-code) since Tue 2017-05-30 03:14:49 UTC; 1 day 2h ago > Process: 1489 ExecStart=/usr/bin/docker-storage-setup (code=exited, status=1/FAILURE) > Main PID: 1489 (code=exited, status=1/FAILURE) > May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: Starting Docker Storage Setup... > May 30 03:14:49 vm0064.workers-phx.ovirt.org docker-storage-setup[1489]: INFO: Volume group backing root filesystem could not be determined > May 30 03:14:49 vm0064.workers-phx.ovirt.org docker-storage-setup[1489]: ERROR: No valid volume group found. Exiting. > May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: docker-storage-setup.service: Main process exited, code=exited, status=1/FAILURE > May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: Failed to start Docker Storage Setup. > May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: docker-storage-setup.service: Unit entered failed state. > May 30 03:14:49 vm0064.workers-phx.ovirt.org systemd[1]: docker-storage-setup.service: Failed with result 'exit-code'. > {code} > This seem to be does to the fact that the system's root filesystem is on a plain disk rather then LVM. This is although the docker default DM storage driver is supposed to be able to use a plaing file on the filesystem. Need to check if this is an issue specific to this slave of something that has to do with all FC24 slaves. -- This message was sent by Atlassian JIRA (v1000.1010.2#100044)

1 0

[JIRA] (OVIRT-1420) Add timeout to Docker setup and cleanup operations
by Barak Korren (oVirt JIRA) 31 May '17

31 May '17

Barak Korren created OVIRT-1420: ----------------------------------- Summary: Add timeout to Docker setup and cleanup operations Key: OVIRT-1420 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1420 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Priority: Highest It seems that some docker operation cat get stuck forever if some docker configuration stages fail. We need to add time-outs for those operations and generate proper error messages. for example failure see: http://jenkins.ovirt.org/job/ovirt-release_4.1_build-artifacts-el7-x86_64/2… -- This message was sent by Atlassian JIRA (v1000.1010.2#100044)

1 0

[JIRA] (OVIRT-1420) Add timeout to Docker setup and cleanup operations
by Barak Korren (oVirt JIRA) 31 May '17

31 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1420?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1420: -------------------------------- Epic Link: OVIRT-400 > Add timeout to Docker setup and cleanup operations > -------------------------------------------------- > > Key: OVIRT-1420 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1420 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > It seems that some docker operation cat get stuck forever if some docker configuration stages fail. > We need to add time-outs for those operations and generate proper error messages. > for example failure see: > http://jenkins.ovirt.org/job/ovirt-release_4.1_build-artifacts-el7-x86_64/2… -- This message was sent by Atlassian JIRA (v1000.1010.2#100044)

1 0

oVirt infra daily report - unstable production jobs - 338
by jenkins＠jenkins.phx.ovirt.org 31 May '17

31 May '17

------=_Part_188_627005002.1496185206254 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/338//artifact/exported-a… Cheers, Jenkins ------=_Part_188_627005002.1496185206254 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 30/05/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/">ovirt_4.1_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/">test-repo_ovirt_experimental_4.1</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_188_627005002.1496185206254--

1 0

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #1798 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 30 May '17

30 May '17

------=_Part_176_941409922.1496140818278 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/1798/ Build Name: 1798 ovirt-engine (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/76705 - title: engine: Reduce AuditLogDirector visibily to private in Commands - project: ovirt-engine - branch: master - author: Moti Asayag <masayag(a)redhat.com> ------=_Part_176_941409922.1496140818278--

1 0

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #1802 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 30 May '17

30 May '17

------=_Part_174_1643814379.1496140741952 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/1802/ Build Name: 1802 ovirt-engine (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/77219 - title: engine: Use AuditLogableImpl for audit logging - project: ovirt-engine - branch: master - author: Moti Asayag <masayag(a)redhat.com> ------=_Part_174_1643814379.1496140741952--

1 0

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #1799 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 30 May '17

30 May '17

------=_Part_172_916848938.1496140712984 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/1799/ Build Name: 1799 ovirt-engine (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/77218 - title: engine: Use AuditLogableImpl when possible - project: ovirt-engine - branch: master - author: Moti Asayag <masayag(a)redhat.com> ------=_Part_172_916848938.1496140712984--

1 0