On Mon, Feb 12, 2018 at 2:45 PM, Eyal Edri <eedri@redhat.com> wrote:

On Mon, Feb 12, 2018 at 2:30 PM, Martin Perina <mperina@redhat.com> wrote:

On Mon, Feb 12, 2018 at 1:18 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:

2018-02-12 13:10 GMT+01:00 oVirt Jenkins <jenkins@ovirt.org>:

Change 79842,3 (ovirt-vmconsole) is probably the reason behind recent system
test failures in the "ovirt-4.2" change queue and needs to be fixed.

No it isn't.

The failure is due to:

13:10:09 [basic-suit] + yum install --nogpgcheck -y --downloaddir=/dev/shm ntp net-snmp ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' otopi-debug-plugins
13:10:09 [basic-suit] Error: Package: ovirt-ansible-roles-1.1.3-1.el7.centos.noarch (alocalsync)
13:10:09 [basic-suit]            Requires: ovirt-ansible-repositories >= 1.1.0
13:10:09 [basic-suit] Error: Package: ovirt-ansible-roles-1.1.3-1.el7.centos.noarch (alocalsync)
13:10:09 [basic-suit]            Requires: ovirt-ansible-engine-setup >= 1.1.0
13:10:09 [basic-suit] Error: Package: ovirt-ansible-roles-1.1.3-1.el7.centos.noarch (alocalsync)
13:10:09 [basic-suit]            Requires: ovirt-ansible-disaster-recovery >= 0.1

I think this may be caused by repository filtering done in OST

Maor pointed out that there might be an issue with current version of 1.1, is it related?

Also, there is a reason why we send this to infra and not devel, so we can look at it and decide if its a real issue or something in the framework like updating reposync file.

 

​Is there anything we should do to enable those ansible-roles packages in OST? They are properly built and added to the release both upstream and downstream, so I'm curious what's the issue there ...

If its indeed a mandatory pkg now and its required, we need to update the reposync file with it.

We have plans to automate this process, but its not simple and will require some design and planning, mostly because we want to be aware of any new deps coming in, which will help debug issues. 

I'll help with a patch to reposync file 4.2 to add the new file. ( we also have a new automated tool to help with regenerating the list of deps per repo )

Actually, I'm not sure this is the case, I don't see any ovirt-ansible pkgs on 4.2 tested repo [1].

Were they mapped in the repo properly for deployment to 4.2? i'm guessing you need to do it on the GitHub repo side since you're using the new yaml files.

[1] http://resources.ovirt.org/repos/ovirt/tested/4.2/rpm/el7/noarch/

 

 

​

 

 

This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.

For further details about the change see:
https://gerrit.ovirt.org/#/c/79842/3

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/694/
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

--

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA

TRIED. TESTED. TRUSTED.

--

Martin Perina
Associate Manager, Software Engineering
Red Hat Czech s.r.o.

--

Eyal edri

MANAGER

RHV DevOps

EMEA VIRTUALIZATION R&D

Red Hat EMEA

TRIED. TESTED. TRUSTED.

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)

--

Eyal edri

MANAGER

RHV DevOps

EMEA VIRTUALIZATION R&D

Red Hat EMEA

TRIED. TESTED. TRUSTED.

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)