Task #4371: Document how to use the newly added recursive_conservative - RPM Support - Pulp

Actions

Send by e-mail Copy link

Task #4371

closed

Document how to use the newly added recursive_conservative

Added by kersom almost 6 years ago. Updated over 5 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

ttereshc

Sprint/Milestone:

Pulp - 2.19.0

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

2.19.0

Groomed:

Yes

Sprint Candidate:

Tags:

Documentation, Pulp 2

Sprint:

Sprint 50

Quarter:

Description

Pulp 2.18.1 is introducing a new flag to `recursive_conservative`.

It is not clear in the documentation how this new flag should be used, and how to use this with already existent `recursive` flag.

I suggest this use case use to be added to the documentatio

Files

dev_baseline_meeting.log (2.5 KB) dev_baseline_meeting.log

Raw Meeting notes

bherring, 02/19/2019 04:53 PM

Related issues

Actions

Copy link

Updated by kersom almost 6 years ago

Related to Issue #4152: Regression Pulp 2.17.1: recursive copy of RPMs does not copy partially resolvable dependencies added

Actions

Copy link

Updated by kersom almost 6 years ago

Description updated (diff)

Actions

Copy link

Updated by kersom almost 6 years ago

Related to Issue #4375: Recursive copy doesn't solve rich dependencies correctly added

Actions

Copy link

Updated by bherring almost 6 years ago

Description updated (diff)

QE Notes¶

Specific to #4364 , I am not sure at this time what all the defined behaviors and full interesting permutations should be.

This is partly due to documentation of functionality with all available flags, previous modular content on a copied server.

Also, it is partly due to modularity is currently non-testable in 2.19master [0]. Therefore, I cannot tell you what Pulp 2.19 actually does, and if we are OK with that.

For simplicity of information discover-ability, here are my current questions.

If there is a development test fixture created, PLEASE link me to it so I do not have to recreate the wheel.

If anything is not clear, please reach me for questions.

Also, if there are `conical` answers generated, please put those in this RM ticket in the top!

Thanks!

#4364 Test Permutation Questions¶

Questions and Answers¶

recursive and recursive_conservative¶

The recursive/recursive_conservative flags should not affect how modular artifacts are copied, correct? All module + dependencies for all versions should be copied always, right?
- not specifying 'recursive' should copy the module and all of it's artifacts
  [13:47:25] <dkliban>when --recursive is specified the module, it's artifacts, and it's modular dependencies their artifacts should be copied

it's possible for modular RPMs to have non-modular dependencies?¶

Yes (answered by Tanya)

Notes¶

Should Test Items, Basic:¶

With modular only for basic tests
With Mixed-repo for basic tests (same results as modular)
with recursive == False (only the module specified)
with recursive == True (module + modular deps)
With recursive_conservative == Either, should not change either above.
Same, but with Mixed-repo (unsure if the non-modular units would be copied as well -- think so)

Should Test Edge Cases:¶

Mixed-repo, NEVRA over-lap and copy content modules
- Verify what and how many are copied
- Believe the same as above, however initial setup has additional over-lapping NEVRA versions on A to copy to B