I would expect only ovirt repository to be enabled and only ovirt-engine-appliance and ovirt-node-ng-update available. Installed oVirt Node 4.2.3.1 ISO from https://resources.ovirt.org/pub/ovirt-4.2/iso/ovirt-node-ng-installer-ovirt/4.2-2018053012/ovirt-node-ng-installer-ovirt-4.2-2018053012.iso and it has also ovirt-4.2-epel repository enabled with all its content. We should have it disabled by default on oVirt Node.
It is enabled but has an includepkgs for ovirt-node-ng-image-update and ovirt-engine-appliance, is that not enough ?
(In reply to Yuval Turgeman from comment #1) > It is enabled but has an includepkgs for ovirt-node-ng-image-update and > ovirt-engine-appliance, is that not enough ? ovirt is enabled with those 2: # imgbased: set-enabled [ovirt-4.2] enabled=1 name=Latest oVirt 4.2 Release includepkgs=ovirt-node-ng-image-update ovirt-node-ng-image ovirt-engine-appliance baseurl=http://resources.ovirt.org/pub/ovirt-4.2-pre/rpm/el$releasever/ skip_if_unavailable=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.2 but ovirt-epel is enabled without restrictions. # imgbased: set-enabled [ovirt-4.2-epel] enabled=1 name=Extra Packages for Enterprise Linux 7 - $basearch includepkgs=ovirt-node-ng-image-update ovirt-node-ng-image ovirt-engine-appliance #baseurl=http://download.fedoraproject.org/pub/epel/7/$basearch mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch failovermethod=priority includepkgs= ansible, ansible-doc, epel-release, ioprocess, libtomcrypt, libtommath, ovirt-guest-agent*, puppet, python2-crypto, python2-ecdsa, python2-paramiko, python34*, python-argparse, python-ecdsa, python-ioprocess, python-ordereddict, python-paramiko, python-ply, rubygem-rgen, nbdkit, nbdkit-devel gpgcheck=1 gpgkey=https://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-7 also the other repos in /etc/yum.repos.d/ovirt-4.2-dependencies.repo are enabled.
Test Version: ovirt-node-ng-installer-ovirt-4.2-2018053012.iso Test Steps: 1. Clean install oVirt Node 4.2.3.1 ISO (ovirt-node-ng-installer-ovirt-4.2-2018053012.iso) 2. Check the repo files in /etc/yum.repos.d/ 1) ovirt-4.2.repo 2) ovirt-4.2-dependencies.repo Result: 1). ovirt repository is enabled and ovirt-engine-appliance and ovirt-node-ng-update available in /etc/yum.repos.d/ovirt-4.2.repo 2). ovirt-4.2-epel repository is enabled without restrictions in /etc/yum.repos.d/ovirt-4.2-dependencies.repo So QE can reproduce this bug. Change flag testing-ack to "+".
Test Version: ovirt-node-ng-installer-ovirt-4.2-pre-2018072416.iso Test Steps: 1. Clean install ovirt-release42-4.2.5_rc3 (ovirt-node-ng-installer-ovirt-4.2-pre-2018072416.iso) 2. Check the repo files in /etc/yum.repos.d/ 1) ovirt-4.2-pre.repo 2) ovirt-4.2-pre-dependencies.repo Result: 1). ovirt repository is enabled and ovirt-engine-appliance and ovirt-node-ng-update available. # imgbased: set-enabled [ovirt-4.2-pre] enabled=1 name = oVirt 4.2 Pre-Release baseurl = http://resources.ovirt.org/pub/ovirt-4.2-pre/rpm/el$releasever/ enabled = 1 skip_if_unavailable = 1 gpgcheck = 1 gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.2 includepkgs = ovirt-node-ng-image-update ovirt-node-ng-image ovirt-engine-appliance [ovirt-4.2] enabled=1 name = Latest oVirt 4.2 Release baseurl = http://resources.ovirt.org/pub/ovirt-4.2/rpm/el$releasever/ enabled = 1 skip_if_unavailable = 1 gpgcheck = 1 gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.2 includepkgs = ovirt-node-ng-image-update ovirt-node-ng-image ovirt-engine-appliance 2). ovirt-4.2-epel repository is enabled but ovirt-engine-appliance and ovirt-node-ng-update available with restrictions. # imgbased: set-enabled [ovirt-4.2-epel] enabled=1 name = Extra Packages for Enterprise Linux 7 - $basearch mirrorlist = https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch failovermethod = priority enabled = 1 gpgcheck = 1 gpgkey = https://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-7 includepkgs = ovirt-node-ng-image-update ovirt-node-ng-image ovirt-engine-appliance ..... So the bug is fixed, change status to VERIFIED.
This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.5 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.