Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

ovirt-provider-ovn fails in 4.2 due to lago's repolock

Description

build that failed: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3468/

basic suite was running on ovirt-srv21.phx.ovirt.org

Activity

Show:

Former user November 12, 2018 at 9:44 AM

Indeed, none of our systems are directly accessible from the Internet via SSH. It should be possible to offline them in Jenkins, however. Then such systems can be rebooted to fix the issue (i.e. killing any hung processes) and enabled again.

Barak Korren November 11, 2018 at 7:38 AM

To reach oVirt CI hosts you have to be connected to the oVirt PHX VPN (The OpenVPN instance that maintains. Not sure if you were at the time...

Anyway I removed the lock manually.

Dafna Ron November 9, 2018 at 2:34 PM

I am unable to ssh to the host so cannot clean the lock
dron@dron ~]$ ssh ovirt-srv21.phx.ovirt.org
ssh: connect to host ovirt-srv21.phx.ovirt.org port 22: Connection timed out
[dron@dron ~]$

Fixed

Details

Assignee

Reporter

Priority

Created November 9, 2018 at 2:29 PM
Updated August 29, 2019 at 2:12 PM
Resolved November 12, 2018 at 9:44 AM