Project

Profile

Help

Issue #8727

Type for Remote ... does not match Repository

Added by knzivid 7 months ago. Updated 7 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Debian:
Platform Release:
Target Release - Debian:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
API Bindings
Sprint:
Quarter:

Description

What does remote field of an apt repository mean?

I am trying to create an apt repository with the field remote.pulp_href = "/pulp/api/v3/remotes/deb/apt/1f753d3b-1863-4282-a42f-cc94b0656dce/"

RepositoriesAptApi.create(DebAptRepository(name=self.name, remote=remote.pulp_href))

This gives me an error

{"remote":["Type for Remote 'my-remote-name' does not match Repository."]}

Does this mean apt remotes can not be a remote of apt repositories? Did I misunderstand what remote means here?

History

#1 Updated by quba42 7 months ago

What version of pulp_deb are you on?

The ability to associate remotes was only recently added with version 2.12.0.

See the release notes here: https://docs.pulpproject.org/pulp_deb/changes.html#id2

Note that pulp_deb 2.12.0 is also affected by a rather nasty bug that also affects version 2.11.1, 2.10.1, and 2.9.1, so it may be best to wait for a fix (and 2.12.1 release) before upgrading.

#2 Updated by knzivid 7 months ago

Server - pulp-deb==2.11.1, Client - pulp_deb_client==2.11.1

Thank you for the heads up on 2.12. I will wait until 2.12.1 and retry remote=... again. Meanwhile, you can close this issue.

When is 2.12.1 scheduled to be released? Is there a release timeline for pulpcore and pulp_deb somewhere I can subscribe to?

#3 Updated by quba42 7 months ago

There is a mailing list for release announcements, that you can subscribe to here: https://listman.redhat.com/mailman/listinfo/pulp-list

You can also see a archive of all past announcements to this list here: https://listman.redhat.com/archives/pulp-list/

2.12.1 will be released as soon as I have a fix for this issue: https://pulp.plan.io/issues/8671

The version you are on now (2.11.1) is also affected by this issue so from this point of view it does not matter if you wait or upgrade now.

#4 Updated by quba42 7 months ago

  • Status changed from NEW to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF