Project

General

Profile

Actions

Bug #37455

closed

Create Katello push repositories as needed at container push time

Added by Quinn James 7 months ago. Updated 6 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Container
Target version:
Fixed in Releases:
Found in Releases:

Description

This issue is a clone of https://issues.redhat.com/browse/SAT-18582 and is a component of https://issues.redhat.com/browse/SAT-23846

There is a decent amount of discussion on this card on JIRA, I have summarized the issue below:

  • When using podman to push containers to Katello, ensure that the container name is of a valid format:
    - <org_label>/<product_label>/<container_name>[:tag] (downcase all letters)
    - id/<org_id>/<product_id>/<container_name>[:tag]
  • Create a new push repository matching the container name under the appropriate product where required.
  • Update existing push repos where required.
  • Run content indexing after completion of the container upload.
  • Ensure the root repository fields are correct after upload:
    - name: matches container_name
    - label: matches container_name
    - content_type: docker
    - product_id: matches product
  • Ensure that the repository fields are correct after upload:
    - relative_path: matches the uploaded container name (exactly what the user entered to podman, either format)
    - environment_id: correct for product
    - content_view_version_id: correct for product
    - version_href: pulp container href
    - container_repository_name: <org_label>/<product_label>/<container_name> with proper capitalization OR follows LE pattern (further discussion needed)
  • Ensure the repository is pushed to a capsule if a user has "Sync Smart Proxies after content view promotion" enabled.
Actions

Also available in: Atom PDF