pulp / pulp/pulp-openapi-generator

Ruby bindings: partial_update returns no task data (Katello)

Open
#128 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Triage-Needed
Dominant language
Mustache
Stars
4
Forks
29
PR merge metrics
No merged PRs in 30d

Description

Version

      "versions": {
        "deb": "3.8.1",
        "rpm": "3.35.2",
        "core": "3.105.4",
        "file": "3.105.4",
        "ostree": "2.6.0",
        "python": "3.27.2",
        "ansible": "0.29.7",
        "certguard": "3.105.4",
        "container": "2.27.6"
      }

Pulpcore bindings version: 3.105.5
Pulp RPM bindings version: 3.35.2

Describe the bug
When updating a remote via the Ruby bindings, the data returned is nil:

[11] pry(main)> task = api.remotes_api.partial_update_with_http_info(remote.pulp_href, PulpRpmClient::PatchedrpmRpmRemote.new(name: "test-#{rand(9999)}"))

=> [#<PulpRpmClient::RpmRpmRemoteResponse:0x00007f325fd1c7f0 @name=nil, @url=nil>,
 202,
 {"date"=>"Fri, 08 May 2026 21:59:36 GMT",
  "server"=>"gunicorn",
  "content-type"=>"application/json",
  "vary"=>"Accept,Cookie",
  "allow"=>"GET, PUT, PATCH, DELETE, HEAD, OPTIONS",
  "x-frame-options"=>"DENY",
  "content-length"=>"67",
  "x-content-type-options"=>"nosniff",
  "referrer-policy"=>"same-origin",
  "cross-origin-opener-policy"=>"same-origin",
  "correlation-id"=>"b2d160cf416f469ca32effc3159f4d3d",
  "access-control-expose-headers"=>"Correlation-ID",
  "via"=>"1.1 toads.example.com"}]

See the response returned no task even though the code is a 202.

Katello currently has a patch to deal with this. We had it already in place before upgrading to 3.105 and left it in, not knowing that once it was removed we'd still have a bug.

To Reproduce
Follow the commands I posted above - update a remote, or anything else that uses the polymorphic update response.

Expected behavior
We can see the task and track it.

Additional context
Add any other context about the problem here. Please provide links to any previous discussions via Discourse or Bugzilla.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Use the Ruby bindings' partial_update_with_http_info example as the entry point and trace the polymorphic update response in this OpenAPI generator. Verify that a 202 partial update exposes task data, then repeat the remote-update reproduction to confirm the returned task can be tracked.

Written by the indexing model from the issue text.

Assessment

Tech stack
openapi, ruby
Domain
api, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.