Bug 1014649

Summary:	Not able to update relative-url to default
Product:	[Retired] Pulp	Reporter:	Preethi Thomas <pthomas>
Component:	rpm-support	Assignee:	pulp-bugs
Status:	CLOSED UPSTREAM	QA Contact:	pulp-qe-list
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	Master	CC:	mhrivnak, skarmark
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:	2015-02-28 21:59:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Preethi Thomas 2013-10-02 13:23:35 UTC

Description of problem:

If you have repo with relative url specified, it wont change it back to default with repo update 

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

[root@pulp-v2-server ~]# rpm -qa pulp-server
pulp-server-2.3.0-0.16.alpha.el6.noarch

How reproducible:


Steps to Reproduce:
1. create a repo with feed and --reltive-url
2. see repo list details and notice that --relatove-url is set
3. run repo update with --relative-url "" 
4. See repo list details again and notice that relative url is still the one from step 2

Actual results:

[root@pulp-v2-server ~]# pulp-admin rpm repo create --repo-id demo --feed http://repos.fedorapeople.org/repos/pulp/pulp/demo_repos/pulp_unittest/ --relative-url /demo/url
Successfully created repository [demo]

 pulp-admin repo list --details
+----------------------------------------------------------------------+
                              Repositories
+----------------------------------------------------------------------+


Id:                  demo
Display Name:        demo
Description:         None
Content Unit Counts: 
Notes:               
Importers:           
  Config:           
    Feed: http://repos.fedorapeople.org/repos/pulp/pulp/demo_repos/pulp_unittest
          /
  Id:               yum_importer
  Importer Type Id: yum_importer
  Last Sync:        None
  Repo Id:          demo
  Scheduled Syncs:  
Distributors:        
  Auto Publish:        True
  Config:              
    Http:         False
    Https:        True
    Relative URL: /demo/url
  Distributor Type Id: yum_distributor
  Id:                  yum_distributor
  Last Publish:        None
  Repo Id:             demo
  Scheduled Publishes: 
  Auto Publish:        False
  Config:              
    Http:  False
    Https: True
  Distributor Type Id: export_distributor
  Id:                  export_distributor
  Last Publish:        None
  Repo Id:             demo
  Scheduled Publishes: 


[root@pulp-v2-server ~]# 
[root@pulp-v2-server ~]# pulp-admin rpm repo update --repo-id demo  --relative-url  ""
Repository [demo] successfully updated


Id:                  demo
Display Name:        demo
Description:         None
Content Unit Counts: 
Notes:               
Importers:           
  Config:           
    Feed: http://repos.fedorapeople.org/repos/pulp/pulp/demo_repos/pulp_unittest
          /
  Id:               yum_importer
  Importer Type Id: yum_importer
  Last Sync:        None
  Repo Id:          demo
  Scheduled Syncs:  
Distributors:        
  Auto Publish:        True
  Config:              
    Http:         False
    Https:        True
    Relative URL: /demo/url
  Distributor Type Id: yum_distributor
  Id:                  yum_distributor
  Last Publish:        None
  Repo Id:             demo
  Scheduled Publishes: 
  Auto Publish:        False
  Config:              
    Http:  False
    Https: True
  Distributor Type Id: export_distributor
  Id:                  export_distributor
  Last Publish:        None
  Repo Id:             demo
  Scheduled Publishes: 



Expected results:


Additional info:

Comment 1 Michael Hrivnak 2013-10-02 18:02:24 UTC

Part of what makes this challenging is that we're deriving a distributor config value based on an importer config value (the feed). It's possible that repo creation time is the only reasonable time (if any) for us to make an assumption that a missing distributor config value can be generated based on the supplied importer config value (the feed). Generally speaking, importers and distributors should be as independent as possible.

Comment 2 Brian Bouterse 2015-02-28 21:59:08 UTC

Moved to https://pulp.plan.io/issues/376