Project

General

Profile

Actions

Bug #6365

closed

Failed validation on Repository label raises a weird error message on

Added by Partha Aji almost 10 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Difficulty:
trivial
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

1) Create a repository
2) then create a second one with same label. Something like

$ hammer repository create --name=boo1 --label=boo --product=justin --organization-id=1 --content-type=yum --url=http://justin.com
Could not create the repository:
Validation failed: Pulp has already been taken, Label has already been taken for this product.

This call is raising the right error and telling me correctly that the label has already been taken. But I don't know why it says Pulp has already been taken. I have no product or repos called pulp.

Basically this happens because of
https://github.com/Katello/katello/blob/master/app/models/katello/repository.rb#L65

validates :pulp_id, :presence => true, :uniqueness => true

However the user has no concept of a "pulp_id". Its more an internal attribute that is required to connect repos from katello to pulp . We need to somehow suppress this error message.

Actions #1

Updated by Eric Helms over 9 years ago

  • Category set to 81
  • Difficulty set to trivial
  • Triaged changed from No to Yes
Actions #2

Updated by Eric Helms over 8 years ago

  • translation missing: en.field_release set to 86
Actions #3

Updated by Eric Helms about 8 years ago

  • translation missing: en.field_release changed from 86 to 114
Actions #4

Updated by John Mitsch over 4 years ago

  • Status changed from New to Rejected
  • Target version deleted (Katello Backlog)

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Actions

Also available in: Atom PDF