Ruby bindings: partial_update returns no task data (Katello)

[ianballou]

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.

[pedro-psb]

The Pulp server correctly generates openapi-spec that defines the correct response types for each response code.
On the response section for "patch" , the spec provides the correct types, so probably not a spec generation issue.

"200": { "$ref": "#/components/schemas/rpm.RpmRemoteResponse" },
"202": { "$ref": "#/components/schemas/AsyncOperationResponse" }

Using curl, I get the expected response for 200 (when the patch don't change anything) and for 202 (where it returns the task). So it's not a server issue.

On the other hand, I was able to reproduce the issue with ruby bindings (using pulp-openapi-generator).
If it's not server issue and not openapi spec issue, it must be client generation issue, which is probably unable to choose the correct response schema based on response code.

[pedro-psb]

I'll touch base with the team just to confirm we are not leaning towards reverting that polymorphism (as I think we are not). Then I can move it to pulp-openapi-generator. There I can try updating the generator (and hope they fixed it) or add your patch directly to the generator.

[pedro-psb]

Sad news, I've tested against the latest generator and it's still failing...

[ianballou]

We can hang on to our patch for a bit now that we know it's the openapi-generator, up to you if you want to use our patch here as well.