Actions
Issue #3666
closedrpm repo copy not 1:1
Status:
CLOSED - NOTABUG
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Master
Platform Release:
OS:
CentOS 7
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
Is it expected that rpm repo copy is not 1:1 but additive (remove-missing=true is ignored for non feeds) ? Is there any safe way to exact copy repo (delete and create again works, but not safe for clients) ? Trying to create simple staging
pulp-admin rpm repo update \
--repo-id=live-google-chrome \
--display-name="Google Chrome repository" \
--description="Google Chrome repository" \
--feed="http://dl.google.com/linux/chrome/rpm/stable/x86_64" \
--gpg-key=/etc/pki/rpm-gpg/RPM-GPG-KEY-chrome \
--serve-http=False --serve-https=True \
--validate=true \
--generate-sqlite=false \
--max-downloads=10 \
--remove-missing=true \
--skip=erratum,srpm,drpm \
--download-policy=immediate \
--retain-old-count=0 \
--relative-url=x86_64/oel/7/google-chrome/qa
pulp-admin rpm repo update \
--repo-id=live-google-chrome-stable \
--display-name="Google Chrome repository" \
--description="Google Chrome repository" \
--gpg-key=/etc/pki/rpm-gpg/RPM-GPG-KEY-chrome \
--serve-http=False --serve-https=True \
--validat= true \
--generate-sqlite=false \
--remove-missing=true \
--skip=erratum,srpm,drpm \
--download-policy=immediate \
--retain-old-count=0 \
--relative-url=x86_64/oel/7/google-chrome/stable
pulp-admin rpm repo sync run --repo-id live-google-chrome
pulp-admin rpm repo copy rpm --from-repo-id=live-google-chrome --to-repo-id=live-google-chrome-stable
pulp-admin rpm repo publish run --repo-id live-google-chrome-stable
Actions