Bug 1303039

Description of problem:

If to create the custom repo, the ID is required to be unique. There is no such requirement for a repo path. If the path of a new repo duplicates the path of the existing repo, the unknown error is reported and a traceback is displayed in logs.

Version-Release number of selected component (if applicable):
>> rpm -qa "*rhui*"
rh-amazon-rhui-client-rhs30-2.2.124-1.el7.noarch
rhui-installer-base-0.0.24-1.el7ui.noarch
rh-rhui-tools-libs-pre.3.0.16-1.el7ui.noarch
rhui-installer-0.0.24-1.el7ui.noarch
rh-rhui-tools-pre.3.0.16-1.el7ui.noarch
rhui-default-ca-1.0-1.noarch
rh-amazon-rhui-client-2.2.118-1.el7.noarch

RHUI iso 20151013

How reproducible:
always

Steps to Reproduce:

Create one custom repo and then create the second custom repo with the same 'path at which the repository will be served' like for the first repo.

From home screen: 
1 'r' -  manage repositories
2. 'c' - create a new custom repository (RPM content only)

>>rhui (repo) => c

>>Unique ID for the custom repository (alphanumerics, _, and - only):
custom-i386-x86_64

>>Display name for the custom repository [custom-i386-x86_64]:
[ENTER]

>>Path at which the repository will be served [custom-i386-x86_64]:
custom/i386/x86_64

>> Algorithm to use when calculating the checksum values for repository metadata:
>>* Select "sha256" for RHEL6:
>>* Select "sha1" for either RHEL5 or RHEL6:

>>  1  - sha256
>>  2  - sha1
>> Enter value (1-2) or 'b' to abort:
1

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

>> Based on the repository's relative path, the suggested entitlement path is:
  custom/i386/x86_64


>> 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 [custom/i386/x86_64]:
[ENTER]

>> Should the repository require clients to perform a GPG check and
verify packages are signed by a GPG key? (y/n)
n

>> The following repository will be created:
>>  ID:              custom-i386-x86_64
>>  Name:            custom-i386-x86_64
>>  Path:            custom/i386/x86_64
>>  Entitlement:     custom/i386/x86_64
>>  GPG Check        No
>>  Red Hat GPG Key: No
>> Proceed? (y/n)
y

Successfully created repository custom-i386-x86_64

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

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

>>Display name for the custom repository [custom-x86_64-x86_64]:
[ENTER]

>>Path at which the repository will be served [custom-x86_64-x86_64]:
custom/i386/x86_64

>>Algorithm to use when calculating the checksum values for repository metadata:
>>* Select "sha256" for RHEL6:
>>* Select "sha1" for either RHEL5 or RHEL6:
>>
>>  1  - sha256
>>  2  - sha1
>>Enter value (1-2) or 'b' to abort:
1

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

>> Based on the repository's relative path, the suggested entitlement path is:
  custom/i386/x86_64

>> 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 [custom/i386/x86_64]:
[ENTER]

>> Should the repository require clients to perform a GPG check and
verify packages are signed by a GPG key? (y/n)
n

>> The following repository will be created:
>>  ID:              custom-x86_64-x86_64
>>  Name:            custom-x86_64-x86_64
>>  Path:            custom/i386/x86_64
>>  Entitlement:     custom/i386/x86_64
>>  GPG Check        No
>>  Red Hat GPG Key: No
>> Proceed? (y/n) 
y

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

>> less /root/.rhui/rhui.log
2016-01-29 06:16:01,560 - <class 'pulp.bindings.exceptions.BadRequestException'>
2016-01-29 06:16:01,560 - Unexpected error caught at the shell level
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/rhui/tools/shell.py", line 88, in safe_listen
    self.listen(clear=first_run)
  File "/usr/lib/python2.7/site-packages/rhui/tools/shell.py", line 122, in listen
    Shell.listen(self)
  File "/usr/lib/python2.7/site-packages/rhui/common/shell.py", line 186, in listen
    item.func(*args, **item.kwargs)
  File "/usr/lib/python2.7/site-packages/rhui/tools/screens/repo.py", line 520, in create_custom
    rh_gpg_key)
  File "/usr/lib/python2.7/site-packages/rhui/tools/pulp_api.py", line 783, in create_custom_repo
    distributors)
  File "/usr/lib/python2.7/site-packages/pulp/bindings/repository.py", line 81, in create_and_configure
    return self.server.POST(path, repo_data)
  File "/usr/lib/python2.7/site-packages/pulp/bindings/server.py", line 98, in POST
    log_request_body=log_request_body)
  File "/usr/lib/python2.7/site-packages/pulp/bindings/server.py", line 161, in _request
    self._handle_exceptions(response_code, response_body)
  File "/usr/lib/python2.7/site-packages/pulp/bindings/server.py", line 202, in _handle_exceptions
    raise code_class_mappings[response_code](response_body)
BadRequestException: RequestException: POST request on /pulp/api/v2/repositories/ failed with 400 - Relative URL [custom/i386/x86_64] for repository [custom-x86_64-x86_64] conflicts with existing relative URL [custom/i386/x86_64] for repository [custom-i386-x86_64]

Expected results:
During repo creation dialogue
1. Change "Path at which the repository will be served" for "Unique path at which the repository will be served"
2. If the user specifies the repo path which duplicates already existing one, through a message "Relative URL [$url] for repository [$new_repo] conflicts with existing relative URL [$url] for repository [$existing_repo]" and allow the user to enter a different path and continue
3. No traceback in logs, just an error message