| Summary: | Katello CLI - promoting only distros should not trigger genpkgmetadata.py | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | James Laska <jlaska> |
| Component: | katello-agent | Assignee: | Bryan Kearney <bkearney> |
| Status: | CLOSED WONTFIX | QA Contact: | Katello QA List <katello-qa-list> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.0.1 | CC: | bbuckingham, jsherril, jturner, lzap, tstrachota |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-03-11 16:44:11 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
James Laska
2012-02-29 16:04:36 UTC
Distro = repository in Pulp. If you want to promote a distro, you are actually promoting a repository. You need to do createrepo. It is not possible to promote a distro without promoting a repositorory. It simply does not make sense. Katello should never gets into state when repository was promoted, but distro not. This is not possible in Pulp. If you have such a state, it's a bug. Changeset containing a distro without its "own" repository should not be valid and promotable. What about situations where the repo did not have a distro but now it does? Katello would be in just a situation. There is also the situation where the distribution associated with a repo will change in library, such as 6Server. When a new 6.Y is released, the distribution in the 6Server repo will change from 6.Y-1 to 6.Y. We currently do not allow promoting of distros without repos in the CLI: Validation failed: Repository of the distribution 'ks-Test Family-TestVariant-16-x86_64' has not been promoted into the target environment! (In reply to comment #3) > We currently do not allow promoting of distros without repos in the CLI: I believe I did that on the command-line (see steps to reproduce in comment#0). Am I misunderstanding? lzap that error simply states that the repo is not already promoted, not that the repo must be promoted with the distro. All subcontent (packages, errata, distros) must have the repo promoted before promoting them. This does not mean they cannot be promoted by themselves. As james said, the cli does support promoting distros, the repo just has to have already been promoted at some point. Justin I understand when .treeinfo changes we would need to repromote distro only. But again - this is not possible in Pulp. Distributions do not live on their own there. Promotion = repo clone in Pulp. And repo cloning is the only way of getting Distribution object (what we see in Katello) promoted. Now, correct me if I am wrong, but I say: It is not possible to promote a distribution without generating metadata. Because to promote a distribution you need to promote whole repository (e.g. distributions, packages, everything there). Lukas, what you say is true only for first promotion. Second time and on the actual repo is already cloned in Pulp and you can update the distribution alone. We had a discussion in irc but to clarify: (In reply to comment #10) > Justin I understand when .treeinfo changes we would need to repromote distro > only. > > But again - this is not possible in Pulp. Distributions do not live on their > own there. > > Promotion = repo clone in Pulp. And repo cloning is the only way of getting > Distribution object (what we see in Katello) promoted. Not exactly. A promotion could result in a repo clone, but that's only in the case of repo or product promotion. Package, errata, or distribution promotion does not result in a repo clone. > Now, correct me if I am wrong, but I say: It is not possible to promote a > distribution without generating metadata. Because to promote a distribution you > need to promote whole repository (e.g. distributions, packages, everything > there). It is possible. Pulp has an add_distribution api call that we are using. I am presuming this functions as we intend. Ok I think I understand where the problem is now. Ok this is 1.1 one. getting rid of 6.0.0 version since that doesn't exist Closing old bugs which are not relevant based on new UI and CLI |