Uploaded image for project: 'CoreOS OCP'
  1. CoreOS OCP
  2. COS-3291

[coreos/fedora-coreos-tracker] coreos-ostree-importer: migrate from deploymentConfig to deployement

XMLWordPrintable

    • Upstream
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • 0

      [3068674646] Upstream Reporter: Adam Piasecki
      Upstream issue status: Closed
      Upstream description:

      As a [previous migration attempt](https://github.com/coreos/fedora-coreos-pipeline/issues/1140) was not completed as expected, it is now time to fix this.

      Affected repositories:

      https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps/coreos-cincinnati.yml
      https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps/coreos-koji-tagger.yml
      https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps/coreos-ostree-importer.yml
      https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/openshift-apps/fedora-ostree-pruner.yml

      Let's tackle each project from the above list independently as it seems slightly more complex than I originally anticipated.

      This issue can be only closed once the `oc describe deployment` command returns expected output in production environment.

              apiaseck@redhat.com Adam Piasecki (Inactive)
              upstream-sync Upstream Sync
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: