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 <era...@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/consoleFull
>
> I am fully rebased on ost master.
>
> Can you have a look?
>
> Thank you
>
>
> ---------- Forwarded message ---------
> From: Galit Rosenthal <grose...@redhat.com>
> Date: Mon, Feb 25, 2019 at 8:35 AM
> Subject: Re: INVALID_SERVICE: ovirtlago
> To: Eitan Raviv <era...@redhat.com>
>
>
> I think you should consult Barak
>
> On Sun, Feb 24, 2019 at 8:26 PM Eitan Raviv <era...@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/consoleFull
>>
>>
>
> --
>
> GALIT ROSENTHAL
>
> SOFTWARE ENGINEER
>
> Red Hat
>
> <https://www.redhat.com/>
>
> ga...@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-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/CYPPTQFSNMZXNAXIS44QMFSXO6UM3KHK/

Reply via email to