Project

Profile

Help

Issue #4091

The master branch is failing

Added by daviddavis 12 months ago. Updated 6 months ago.

Status:
MODIFIED
Priority:
High
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Severity:
2. Medium
Version:
Platform Release:
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 44

Description

Example:

https://travis-ci.org/pulp/pulp/builds/443310599

I believe it's probably due to the new version of DRF (3.9.0) which just came out today.

Associated revisions

Revision 9c29ece0 View on GitHub
Added by daviddavis 12 months ago

Use /pulp/api/v3/users to test auth

I don't think using the /pulp/api/v3/ is a good test for authentication.
It doesn't require a user necessarily and it's not something we've
intentionally created in our application. I think something like
/pulp/api/v3/users/ might be better.

fixes #4091
https://pulp.plan.io/issues/4091

Revision 9c29ece0 View on GitHub
Added by daviddavis 12 months ago

Use /pulp/api/v3/users to test auth

I don't think using the /pulp/api/v3/ is a good test for authentication.
It doesn't require a user necessarily and it's not something we've
intentionally created in our application. I think something like
/pulp/api/v3/users/ might be better.

fixes #4091
https://pulp.plan.io/issues/4091

Revision 9c29ece0 View on GitHub
Added by daviddavis 12 months ago

Use /pulp/api/v3/users to test auth

I don't think using the /pulp/api/v3/ is a good test for authentication.
It doesn't require a user necessarily and it's not something we've
intentionally created in our application. I think something like
/pulp/api/v3/users/ might be better.

fixes #4091
https://pulp.plan.io/issues/4091

History

#1 Updated by dalley 12 months ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 44
  • Tags Pulp 3 added

#2 Updated by daviddavis 12 months ago

Looks like with DRF 3.8, you get a json response when you hit the base url (/pulp/api/v3/). Now with 3.9, we get:

info:
  description: ''
  title: Pulp API
  version: ''
openapi: 3.0.0
paths: {}
servers:
- url: http://localhost:8000/pulp/api/v3/

pulp-smash is hitting this base url to test authentication and they are expecting back json.

From the release notes that @dalley posted:

The get_schema_view(...) method now defaults to OpenAPI YAML, with CoreJSON as a secondary option if it is selected via HTTP content negotiation.

#3 Updated by daviddavis 12 months ago

I don't think using the base_url is a good test for authentication. It doesn't require a user necessarily and it's not something we've intentionally created in our application. I think something like /pulp/api/v3/users/ might be better.

#4 Updated by daviddavis 12 months ago

  • Status changed from NEW to POST
  • Assignee set to daviddavis

#5 Updated by daviddavis 12 months ago

  • Status changed from POST to MODIFIED

#6 Updated by daviddavis 6 months ago

  • Sprint/Milestone set to 3.0

#7 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF