I think the error before it might be more relevant? Failing to start Docker: - Subject: Unit docker.service has failed 09:18:12 -- Defined-By: systemd 09:18:12 -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel 09:18:12 -- 09:18:12 -- Unit docker.service has failed. 09:18:12 -- 09:18:12 -- The result is failed. 09:18:12 Mar 17 09:18:12 openshift-integ-tests-container-9f7tz systemd[1]: Unit docker.service entered failed state. 09:18:12 Mar 17 09:18:12 openshift-integ-tests-container-9f7tz systemd[1]: docker.service failed. 09:18:12 + log ERROR 'Failed to start docker service' 09:18:12 + local level=ERROR 09:18:12 + shift Gal,Daniel,Barak - do we have any solution for this? maybe don't run the jnlp agent if Docker service doesn't start? On Sun, Mar 17, 2019 at 12:28 PM Eitan Raviv <eraviv@redhat.com> wrote:
Reproduced just now on https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/3773
On Wed, Feb 27, 2019 at 9:01 AM Barak Korren <bkorren@redhat.com> wrote:
On Tue, 26 Feb 2019 at 18:25, Gal Ben Haim <gbenhaim@redhat.com> wrote:
I've run 48 suites, and the issue didn't appear. I suggest merging [1], which will help us to understand the cause of the problem.
merged.
On Tue, Feb 26, 2019 at 2:43 PM Eitan Raviv <eraviv@redhat.com> wrote:
certainly more than a dozen.
On Mon, Feb 25, 2019 at 11:17 AM Gal Ben Haim <gbenhaim@redhat.com> wrote:
Eitan,
How many times did you see this error?
On Mon, Feb 25, 2019 at 9:49 AM Barak Korren <bkorren@redhat.com> wrote:
That is not the real issue, the real issue seems to be this:
+ sudo -n systemctl start docker Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. + sudo -n systemctl status docker ● docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled) Active: activating (auto-restart) (Result: exit-code) since Mon 2019-02-25 04:03:52 UTC; 45ms ago Docs: https://docs.docker.com Process: 15496 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE) Main PID: 15496 (code=exited, status=1/FAILURE) Feb 25 04:03:52 openshift-integ-tests-container-6bmr3 systemd[1]: Failed to start Docker Application Container Engine. Feb 25 04:03:52 openshift-integ-tests-container-6bmr3 systemd[1]: Unit docker.service entered failed state. Feb 25 04:03:52 openshift-integ-tests-container-6bmr3 systemd[1]: docker.service failed. + : + log ERROR 'Failed to start docker service' + local level=ERROR
So docker is failing to start in the integ-test container. Here is the podspec that was used:
---apiVersion: v1kind: Podmetadata: generateName: jenkins-slave labels: integ-tests-container: "" namespace: jenkins-ovirt-orgspec: containers: - env: - name: JENKINS_AGENT_WORKDIR value: /home/jenkins - name: CI_RUNTIME_UNAME value: jenkins - name: STDCI_SLAVE_CONTAINER_NAME value: im_a_container - name: CONTAINER_SLOTS value: /var/lib/stdci image: docker.io/ovirtinfra/el7-runner-node:12c9f471a6e9eccd6d5052c6c4964fff3b6670c9 command: ['/usr/sbin/init'] livenessProbe: exec: command: ['systemctl', 'status', 'multi-user.target'] initialDelaySeconds: 360 periodSeconds: 7200 name: jnlp resources: limits: memory: 32Gi requests: memory: 32Gi securityContext: privileged: true volumeMounts: - mountPath: /var/lib/stdci name: slave-cache - mountPath: /dev/shm name: dshm workingDir: /home/jenkins tty: true nodeSelector: model: r620 serviceAccount: jenkins-slave volumes: - hostPath: path: /var/lib/stdci type: DirectoryOrCreate name: slave-cache - emptyDir: medium: Memory name: dshm
Adding Gal and infra list.
On Mon, 25 Feb 2019 at 08:45, Eitan Raviv <eraviv@redhat.com> wrote:
> Hi, > I have some OST patches failing on: > > *04:03:53* Error: INVALID_SERVICE: ovirtlago > > e.g. https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/3443/c... > > I am fully rebased on ost master. > > Can you have a look? > > Thank you > > > ---------- Forwarded message --------- > From: Galit Rosenthal <grosenth@redhat.com> > Date: Mon, Feb 25, 2019 at 8:35 AM > Subject: Re: INVALID_SERVICE: ovirtlago > To: Eitan Raviv <eraviv@redhat.com> > > > I think you should consult Barak > > On Sun, Feb 24, 2019 at 8:26 PM Eitan Raviv <eraviv@redhat.com> > wrote: > >> *13:58:57* ++ sudo -n firewall-cmd --query-service=ovirtlago*13:58:58* Error: INVALID_SERVICE: ovirtlago >> >> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/3430/c... >> >> > > -- > > GALIT ROSENTHAL > > SOFTWARE ENGINEER > > Red Hat > > <https://www.redhat.com/> > > galit@gmail.com T: 972-9-7692230 > <https://red.ht/sig> >
-- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted _______________________________________________ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-leave@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/CYPPTQFSNMZXNA...
-- *GAL bEN HAIM* RHV/CNV DEVOPS
-- *GAL bEN HAIM* RHV/CNV DEVOPS
-- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
_______________________________________________ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-leave@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/DDXLRUGIRHR4NG...
-- Eyal edri MANAGER RHV/CNV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)