Bug 696940

Summary: Unexpected error while creating custom repo
Product: Red Hat Update Infrastructure for Cloud Providers Reporter: Sachin Ghai <sghai>
Component: ToolsAssignee: Jay Dobies <jason.dobies>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.0CC: tsanders
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-31 12:52:15 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 Sachin Ghai 2011-04-15 11:06:37 UTC
Description of problem:
Got unexpected error while creating the protected custom repo

Version-Release number of selected component (if applicable):
rh-rhui-tool-2.0.12-1.el6

How reproducible:
Always

Steps to Reproduce:

------------------------------------------------------------------------------
rhui (repo) => c

Unique ID for the custom repository (alphanumerics, _, and - only):
custom_repo1

Display name for the custom repository [custom_repo1]:
protected repo1

Path at which the repository will be served [custom_repo1]:
/protected/x86_64/os

Should the repository require an entitlement certificate to access? (y/n)
y

Based on the repository's relative path, the suggested entitlement path is:
  /protected/$basearch/os

Path that should be used when granting an entitlement for this repository. This
may use yum variable substitutions (e.g. $basearch) to group this together with
other repositories that share the entitlement [/protected/$basearch/os]:


The following repository will be created:
  ID:          custom_repo1
  Name:        protected repo1
  Path:        /protected/x86_64/os
  Entitlement: /protected/$basearch/os
Proceed? (y/n) y

  
Actual results:
An unexpected error has occurred during the last operation.
More information can be found in /root/.rhui/rhui.log.

Expected results:
Custom repo should be created successfully

Additional info:

[root@pulp-server ~]# tail -f /root/.rhui/rhui.log 
    self.listen(clear=first_run)
  File "/usr/lib/python2.6/site-packages/rhui/tools/shell.py", line 90, in listen
    Shell.listen(self)
  File "/usr/lib/python2.6/site-packages/rhui/common/shell.py", line 191, in listen
    item.func(*args, **item.kwargs)
  File "/usr/lib/python2.6/site-packages/rhui/tools/screens/repo.py", line 389, in create_custom
    success = self.pulp.create_custom_repo(id, name, path, entitlement_path, protected)
  File "/usr/lib/python2.6/site-packages/rhui/tools/pulp_api.py", line 270, in create_custom_repo
    notes=notes,
TypeError: create() got an unexpected keyword argument 'notes'

Comment 1 Jay Dobies 2011-04-15 12:06:09 UTC
This is because you're running an old Pulp build before the notes field was added.

I'm going to work on a build process for the RHUI branch of Pulp today that you can use to help standardize on the version of Pulp to test against.

Comment 2 Jay Dobies 2011-04-15 18:49:24 UTC
Please try this again on the RHUI Pulp build 0.165.

Comment 3 Sachin Ghai 2011-04-18 10:19:24 UTC
Yes, now I can create custom repo. I tried this on RHUI pulp build 0.166.

~~~~~~~~~~

The following repository will be created:
  ID:          repo1
  Name:        protected repo1
  Path:        /protected/x86_64/os
  Entitlement: /protected/$basearch/os
Proceed? (y/n) y

Successfully created repository protected repo1

------------------------------------------------------------------------------
rhui (repo) => l

Custom Repositories
  protected repo1
~~~~~~~~~~~

thanks, sachin

Comment 4 wes hayutin 2011-08-01 21:38:42 UTC
moving to release pending

Comment 5 wes hayutin 2012-05-31 12:52:15 UTC
closing out, product released