Skip to:

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

Disable external repos on Lago VMs ( master suite )

Description

In order to keep OST's environment isolated, we must have only lago's internal repo enabled inside the VMs during OST.

Activity

Show:

Nadav Goldin April 18, 2017 at 2:03 PM

Which Lago issue? the el6 one - https://github.com/lago-project/lago/issues/504?
If so, then unfortunately no, didn't get to it yet. I hope it will get into 0.37 if time suffices, if not it will be in 0.38.

Eyal Edri April 18, 2017 at 1:59 PM

any update on a fix on Lago side?

Former user April 12, 2017 at 7:10 AM

Waiting for a fix for Lago's issue. Shhing to CentOS 6 hosts takes too log.

Former user April 2, 2017 at 1:22 PM

I've sent a patch to restore the change Gerrit but currently there is an issue with the epel repo (not related to us)

Eyal Edri March 27, 2017 at 2:01 PM

Yes,
I think we fixed the issues we've had and if there are still issues we can
fix them on the patch that reverts the change.

On Mon, Mar 27, 2017 at 4:49 PM, Barak Korren (oVirt JIRA) <

–

Eyal edri

ASSOCIATE MANAGER

RHV 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)

Barak Korren March 27, 2017 at 1:49 PM

Do you think we can switch the VMs back to using only the localrepo, this will prevent this kind of failures, but we'll need to update includes/excludes probably.

Fixed

Details

Assignee

Reporter

Priority

Parent

Created March 27, 2017 at 12:56 PM
Updated June 4, 2018 at 6:29 AM
Resolved May 1, 2018 at 7:32 AM