Bug 750256 - Creating custom repos failing
Summary: Creating custom repos failing
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: Unspecified
Assignee: Partha Aji
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: katello-blockers
TreeView+ depends on / blocked
 
Reported: 2011-10-31 13:59 UTC by Corey Welton
Modified: 2013-03-27 20:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
katello-0.1.97-1.git.0.46f6b93.el6.x86_64 katello-cli-common-0.1.10-1.git.922.f2329b3.el6.noarch katello-cli-0.1.10-1.git.922.f2329b3.el6.noarch katello-glue-pulp-0.1.97-1.git.0.46f6b93.el6.x86_64 katello-configure-0.1.7-1.git.29.b94a200.el6.noarch katello-repos-0.1.3-1.git.0.db2bd1d.el6.noarch katello-glue-foreman-0.1.97-1.git.0.46f6b93.el6.x86_64 katello-common-0.1.97-1.git.0.46f6b93.el6.noarch katello-all-0.1.97-1.git.0.46f6b93.el6.x86_64 katello-glue-candlepin-0.1.97-1.git.0.46f6b93.el6.x86_64 pulp-0.0.237-5.el6.noarch katello-glue-pulp-0.1.97-1.git.0.46f6b93.el6.x86_64 pulp-common-0.0.237-5.el6.noarch m2crypto-0.21.1.pulp-5.el6.x86_64
Last Closed: 2011-11-18 03:01:31 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Corey Welton 2011-10-31 13:59:14 UTC
Description of problem:
Reporting this here, though I am not sure if this is a katello or pulp issue.

Attempting to create a custom repo in katello is failing with a pulp error. Whether this is due to something katello is passing pulp is unsure.


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


How reproducible:


Steps to Reproduce:
1.  Do a fresh install of katello.  Be sure no old databases etc exist for katello, pulp, etc.
2.  Create a new provider, "fedora"
3.  Create a new product, "fedora 15"
4.  Attempt to create a new repo for "fedora 15", called "fedora 15 - x86_64" - and give it a valid repo URL
  
Actual results:

* In the UI:
Pulp::Repository: 401 Unauthorized "Invalid OAuth Credentials" (GET /pulp/api/repositories/?_intersect=groupid&groupid=product:1320028380061&groupid=env:1&name=fedora 15 -x86_64)

* In Pulp logs:
2011-10-31 09:35:13,157 2196:140024513292032: pulp.server.auth.authentication:ERROR: authentication:214 error verifying OAuth signature: Invalid signature. Expected signature base string: GET&https%3A%2F%2Flocalhost%2Fpulp%2Fapi%2Frepositories%2F&_intersect%3Dgroupid%26groupid%3Dproduct%253A1320028380061%26name%3Dfedora%252015%2520-x86_64%26oauth_consumer_key%3Dkatello%26oauth_nonce%3DpCfNPFWxVtDoRx96mOAkWMhMWbIvLrzYeDU5Lo05j7w%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1320068113%26oauth_version%3D1.0

Expected results:
Ability to create repo

Additional info:
Pinging the katello server returns no errors:
[root@se-rhelbox pulp]# curl -k https://localhost/katello/api/ping 
{"result":"ok","status":{"candlepin_auth":{"result":"ok","duration_ms":"65"},"pulp":{"result":"ok","duration_ms":"2624"},"pulp_auth":{"result":"ok","duration_ms":"134"},"candlepin":{"result":"ok","duration_ms":"5591"}}}

Also, running 'reset-oauth' (and restarting services as appropriate) seems to do nothing.

Comment 1 Corey Welton 2011-10-31 14:03:48 UTC
Actually - this is likely an issue with the way we are caching things in the browser. Using the same steps in a different browser, I was able to create repo.  In my open browser (Chrome), it failed.  I opened a new, separate (FF) browser, it created successfully.  Returning to Chrome and forcing a refresh of the page (ctrl-shift-r) allowed me to mysteriously create repos again.

So it seems to be an authentication issue of some sort, where auth is not getting cleared out/updated accordingly, perhaps over repeated katello installs or what have you. Maybe we need to tell users to clear browser cache after performing any (new) installs of katello, but that seems... sub-optimal.

Comment 2 Corey Welton 2011-10-31 14:09:52 UTC
I take all/most of comment #1 back, it does seem to be intermittently occurring even after i cleared browser cache, etc.

Comment 3 Corey Welton 2011-11-18 03:01:31 UTC
This is fixed now. I think it was due to the issues seen in bug #752863, with the unclean start.  Assuring a clean start seems to have resolved it.

I'll go ahead and close this bz


Note You need to log in before you can comment on or make changes to this bug.