Bug 1232714

Summary: Host deploy fails on CentOS7 if there is no "baseurl" in yum repos
Product: [oVirt] otopi Reporter: Daniel Helgenberger <daniel.helgenberger>
Component: Plugins.packagersAssignee: Alon Bar-Lev <alonbl>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 1.3.0CC: bazulay, bugs, daniel.helgenberger, dougsland, ecohen, gklein, iheim, lsurette, yeylon
Target Milestone: ---Flags: daniel.helgenberger: needinfo-
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 18:32:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
host-deply.log snip
none
miniyum.py
none
miniyum.py.out none

Description Daniel Helgenberger 2015-06-17 11:15:02 UTC 
Created attachment 1039881 [details]
host-deply.log snip

Description of problem:
On CentOS7, ovirt host deploy fails with the error:

RepoError: Cannot find a valid baseurl for repo: base/7/x86_64

while the default base.repo has baseurl commented out in favor for mirrorlist:
[base]
name=CentOS-$releasever - Base
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7


Version-Release number of selected component (if applicable):
ovirt 3.5.3

How reproducible:
always

Steps to Reproduce:
1. In ovrt, set host to maintaince and run 'reinstall'
2.
3.

Actual results:
Host deploy fails with RepoError: Cannot find a valid baseurl for repo: base/7/x86_64

Expected results:
Host deploy does not fail

Additional info:
Workaround:
By removing the comments from baseurl in the CentOS-CentOS-Base.repo host deploy succeeds.
Comment 1 Alon Bar-Lev 2015-06-17 11:22:09 UTC 
Does yum have also present warnings in this state?
These warnings/messages are received from yum directly.

Try: yum search xxx
Comment 2 Daniel Helgenberger 2015-06-17 11:33:13 UTC 
The yum transactions are running fine, no errors or warnings:
[root@hv02 ~]# yum search iproute
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * epel: ftp.fau.de
 * ovirt-3.5: ftp.nluug.nl
 * ovirt-3.5-epel: ftp.fau.de
=========================================================== N/S matched: iproute ===========================================================
iproute-devel.i686 : iproute development files
iproute-devel.x86_64 : iproute development files
iproute.x86_64 : Advanced IP routing and network device configuration tools
iproute-doc.x86_64 : ip and tc documentation with examples
Comment 3 Alon Bar-Lev 2015-06-17 11:42:59 UTC 
Created attachment 1039885 [details]
miniyum.py

Please run this script and send me the output.

Please also send output of:

# yum clean expire-cache
# yum install iproute

Thanks!
Comment 4 Daniel Helgenberger 2015-06-17 12:54:46 UTC 
I think it has notthing to do with iproute in particular; since it was already installed in the first place:
[root@hv02 ~]# yum history package-list  iproute
Loaded plugins: fastestmirror
ID     | Action(s)      | Package                                              
-------------------------------------------------------------------------------
     1 | Install        | iproute-3.10.0-21.el7.x86_64                         
history package-list
[root@hv02 ~]# yum history 1

[root@hv02 ~]# yum history list 1
Loaded plugins: fastestmirror
ID     | Login user               | Date and time    | Action(s)      | Altered
-------------------------------------------------------------------------------
     1 | System <unset>           | 2015-05-19 16:11 | Install        |  290   
history list

But here you go:

[root@hv02 ~]# yum clean expire-cache
Loaded plugins: fastestmirror
Cleaning repos: base epel extras ovirt-3.5 ovirt-3.5-epel ovirt-3.5-glusterfs-epel ovirt-3.5-glusterfs-noarch-epel
              : ovirt-3.5-patternfly1-noarch-epel puppetlabs-deps puppetlabs-products updates
12 metadata files removed
[root@hv02 ~]# yum install iproute
Loaded plugins: fastestmirror
base                                                                                                                | 3.6 kB  00:00:00     
epel/x86_64/metalink                                                                                                |  25 kB  00:00:00     
extras                                                                                                              | 3.4 kB  00:00:00     
ovirt-3.5                                                                                                           | 2.9 kB  00:00:00     
ovirt-3.5-epel/x86_64/metalink                                                                                      |  25 kB  00:00:00     
ovirt-3.5-glusterfs-epel                                                                                            | 2.9 kB  00:00:00     
ovirt-3.5-glusterfs-noarch-epel                                                                                     | 2.9 kB  00:00:00     
ovirt-3.5-patternfly1-noarch-epel                                                                                   | 3.0 kB  00:00:00     
puppetlabs-deps                                                                                                     | 2.5 kB  00:00:00     
puppetlabs-products                                                                                                 | 2.5 kB  00:00:00     
updates                                                                                                             | 3.4 kB  00:00:00     
Loading mirror speeds from cached hostfile
 * epel: ftp.fau.de
 * ovirt-3.5: ftp.nluug.nl
 * ovirt-3.5-epel: ftp.fau.de
Package iproute-3.10.0-21.el7.x86_64 already installed and latest version
Nothing to do
Comment 5 Daniel Helgenberger 2015-06-17 13:02:39 UTC 
Created attachment 1039941 [details]
miniyum.py.out

output from miniyum.py
Comment 6 Alon Bar-Lev 2015-06-17 16:03:07 UTC 
(In reply to Daniel Helgenberger from comment #5)
> Created attachment 1039941 [details]
> miniyum.py.out
> 
> output from miniyum.py

the error is expected here... so no error in yum and no error when using miniyum... are you sure your repo missing the baseurl?
Comment 7 Daniel Helgenberger 2015-06-17 16:21:44 UTC 
No, as I said I uncommented the 'baseurl' part in base.repo to get it to work. Reverting this, I get no error ether?

Also, maybe some imported thing I forgot to mention; I am on hosted engine. With another matter, Simone Tiraboschi did advise me against using 'reinstall' with HA nodes; maybe related? But it worked quite well in the past...

VERB: -->Loaded plugins: fastestmirror<--
VERB: -->Loaded plugins: fastestmirror<--
VERB: -->Cleaning caches: ['expire-cache'].<--
VERB: -->queue package iproute for install<--
VERB: -->Loading mirror speeds from cached hostfile<--
VERB: -->Downloading: epel/x86_64/metalink (0%)<--
VERB: -->Downloading: epel/x86_64/metalink 25 k(100%)<--
VERB: -->Downloading: ovirt-3.5-epel/x86_64/metalink (0%)<--
VERB: -->Downloading: ovirt-3.5-epel/x86_64/metalink 25 k(100%)<--
VERB: --> * base: mirror.de.leaseweb.net<--
VERB: --> * epel: ftp.fau.de<--
VERB: --> * extras: centos.mirrors.as250.net<--
VERB: --> * ovirt-3.5: ftp.nluug.nl<--
VERB: --> * ovirt-3.5-epel: ftp.fau.de<--
VERB: --> * updates: mirror.23media.de<--
VERB: -->Downloading: base/7/x86_64 (0%)<--
VERB: -->Downloading: base/7/x86_64 3.6 k(100%)<--
VERB: -->Downloading: extras/7/x86_64 (0%)<--
VERB: -->Downloading: extras/7/x86_64 3.4 k(100%)<--
VERB: -->Downloading: ovirt-3.5/7 (0%)<--
VERB: -->Downloading: ovirt-3.5/7 2.9 k(100%)<--
VERB: -->Downloading: ovirt-3.5-glusterfs-epel/7/x86_64 (0%)<--
VERB: -->Downloading: ovirt-3.5-glusterfs-epel/7/x86_64 2.9 k(100%)<--
VERB: -->Downloading: ovirt-3.5-glusterfs-noarch-epel/7 (0%)<--
VERB: -->Downloading: ovirt-3.5-glusterfs-noarch-epel/7 2.9 k(100%)<--
VERB: -->Downloading: ovirt-3.5-patternfly1-noarch-epel/x86_64 (0%)<--
VERB: -->Downloading: ovirt-3.5-patternfly1-noarch-epel/x86_64 3.0 k(100%)<--
VERB: -->Downloading: puppetlabs-deps/x86_64 (0%)<--
VERB: -->Downloading: puppetlabs-deps/x86_64 2.5 k(100%)<--
VERB: -->Downloading: puppetlabs-products/x86_64 (0%)<--
VERB: -->Downloading: puppetlabs-products/x86_64 2.5 k(100%)<--
VERB: -->Downloading: updates/7/x86_64 (0%)<--
VERB: -->Downloading: updates/7/x86_64 3.4 k(100%)<--
VERB: -->Building transaction<--
VERB: -->Empty transaction<--
VERB: -->Transaction Summary:<--
Comment 8 Alon Bar-Lev 2015-06-17 16:27:31 UTC 
(In reply to Daniel Helgenberger from comment #7)
> No, as I said I uncommented the 'baseurl' part in base.repo to get it to
> work. Reverting this, I get no error ether?

I do not follow.
If you want to work to resolve an issue, please make sure there is an issue.
There is no point in running/providing output for a state in which you applied workaround.

Please provide comment#3 outputs while you reproduce the host-deploy issue, probably comment back the baseurl.
Comment 9 Alon Bar-Lev 2015-06-23 14:54:53 UTC 
any news?
Comment 10 Alon Bar-Lev 2015-06-30 18:32:38 UTC 
Please reopen if you can provide the information requested.