Actions
Issue #9088
closedMigrated SUSE repos end up w/ auth-token in URL and no sles_auth_token set on the resulting remote
Status:
CLOSED - NOTABUG
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Steps:
Set up a SUSE repo:
pulp-admin rpm repo create \
--repo-id sles12-backport-sp5-standard \
--feed https://updates.suse.com/SUSE/Backports/SLE-12-SP5_x86_64/standard/?<REPO-AUTH-TOKEN> \
--download-policy on_demand
Migrate
PLAN_HREF=$(pulp migration plan create --plan '{"plugins": [{"type": "rpm"}]}' | jq -r .pulp_href)
echo "Plan: $PLAN_HREF"
pulp -T 0 migration plan run --href ${PLAN_HREF}
Look at the resulting pulp3 remote
REMOTE_HREF=$(pulp rpm repository show --name sles12-backport-sp5-standard | jq -r .remote)
echo "Remote-href: ${REMOTE_HREF}"
pulp rpm remote show --href ${REMOTE_HREF}
Attempt to sync:
pulp rpm repository sync --name sles12-backport-sp5-standard
Started background task /pulp/api/v3/tasks/5c78105a-a25e-41c5-860a-53b02ba08f0b/
.Error: Task /pulp/api/v3/tasks/5c78105a-a25e-41c5-860a-53b02ba08f0b/ failed: '404, message='Not Found',
url=URL('https://updates.suse.com/SUSE/Backports/SLE-12-SP5_x86_64/standard/?<REPO-AUTH-TOKEN>')'
Be sad.
Updated by ggainey over 1 year ago
- Status changed from NEW to CLOSED - NOTABUG
Closing NOTABUG - while ? "works" in Pulp2, it's not the right Pulp2 way to identify the sles_auth_token to use for a repo. The right way is to add query_auth_token=token to the importer_config for a repo. If you do that, 2to3 finds the token and sets up sles_auth_token in Pulp3.
Actions