Bug 688938

Summary:	Not able install packages with CDS
Product:	[Retired] Pulp	Reporter:	Preethi Thomas <pthomas>
Component:	nodes	Assignee:	Jay Dobies <jason.dobies>
Status:	CLOSED NOTABUG	QA Contact:	Preethi Thomas <pthomas>
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	jconnor
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-30 16:47:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Preethi Thomas 2011-03-18 15:20:26 UTC

Description of problem:


[root@pulp-client ~]# rpm -q pulp-client
pulp-client-0.0.151-1.fc14.noarch

If you have a CDS to talk to the pulp-server and try to install packages on the client, It fails.



[root@pulp-client ~]# yum install zsh --disablerepo=* --enablerepo=f14
Repository 'f14': Error parsing config: Error parsing "mirrorlist = '/etc/yum.repos.d/f14.mirrorlist'": URL must be http, ftp, file or https not ""


Error getting repository data for f14, repository not found


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

Comment 1 Jay Dobies 2011-03-18 15:26:16 UTC

commit	4421b3c525728b8de3b6ddf6493fceeeec0059b8
tree	246b98e8d289a320c0249c1c51022c7ecd0df0c7


688938 - Added missing protocol prefix.


src/pulp/client/repolib.py

Comment 2 Jeff Ortel 2011-03-18 22:12:28 UTC

Build: 0.154

Comment 3 Jay Dobies 2011-03-25 17:33:31 UTC

From the pastebin, yum is trying to access:

https://pulp-cds.usersys.redhat.com/pulp/repos/released/F-14/GOLD/Fedora/x86_64/os/repodata/repomd.xml

But for some reason, looking on the filesystem on the CDS I see:

[root@pulp-cds pulp-cds]# ll released/F-14/GOLD/Fedora/x86_64/os/repodata.new/repomd.xml 
-rw-r--r--. 1 root root 3819 Mar 25 13:16 released/F-14/GOLD/Fedora/x86_64/os/repodata.new/repomd.xml

I'm not sure why grinder would have syncced the repo to "repodata.new".

Comment 4 Jay Dobies 2011-03-30 16:47:49 UTC

After speaking with jmatthews, it turns out that repodata.new is intentional. It's a temporary state during a sync.

In this case, I think a package install was attempted against a CDS that was still synchronizing. When the sync finished and repodata.new was renamed to repodata, I was able to install zsh successfully.