Project

Profile

Help

Issue #3666

rpm repo copy not 1:1

Added by vaclav.adamec@suchy-zleb.cz over 2 years ago. Updated over 1 year ago.

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

History

#1 Updated by ipanova@redhat.com over 2 years ago

the copy is 1:1, but repoB once it is coped from repoA is not changed based on changes happened in repoA

#2 Updated by ipanova@redhat.com over 2 years ago

if previous comment answers your question can you close this issue or in other case provide more info?thank you

#3 Updated by vaclav.adamec@suchy-zleb.cz over 2 years ago

and is there any way to change it ? remove-missing=true and repository with no feed than make no sense for me, you will end up with one 'live' repository which is clean and up2date and second which will just add new packages and grow and grow ....

#4 Updated by dalley over 2 years ago

  • Status changed from NEW to CLOSED - NOTABUG

#5 Updated by ipanova@redhat.com over 2 years ago

  • Status changed from CLOSED - NOTABUG to NEW

when you copy repoA into repoB you copy repoA at that particular moment and set of content.
if repoA changed and you want an updated version that contains different set of packages then another copy is meant to be made and it would be repoC

--remove-missing is applied just to the repos that have feed.
I am closing this issue, in case you'd have more questions please join us on freenode #pulp #pulp-dev

#6 Updated by ipanova@redhat.com over 2 years ago

  • Status changed from NEW to CLOSED - NOTABUG

#7 Updated by bmbouter over 1 year ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF