Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-18034

Sources don't map properly to compose-cli, mixing id and names

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • cockpit-composer
    • None
    • None
    • None
    • rhel-sst-image-builder
    • ssg_front_door
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None

      What were you trying to do that didn't work?

      • What I created using "composer-cli", I can't properly edit using cockpit.

      Please provide the package NVR for which bug is seen:

      • cockpit-composer.noarch == 47-1.el9

      How reproducible:

      No special requirements.

      Steps to reproduce

      1. Via terminal, using composer-cli:
        1. Create a new blueprint with an id like "aap-2.4-rhel-9" (no special chars) and a name like "Red Hat Ansible Automation Platform 2.4 for RHEL 9 x86_64 (RPMs)" (using special chars).
      2. Via cockpit, using Image Builder:
        1. Go to the "Sources" tab
        2. Edit the source "Red Hat Ansible Automation Platform 2.4 for RHEL 9 x86_64 (RPMs)" and save it
      3. Via terminal, using composer-cli:
        1. List all sources
        2. BUG: instead of updating the source with the id  "aap-2.4-rhel-9", it created a new source with the id "Red Hat Ansible Automation Platform 2.4 for RHEL 9 x86_64 (RPMs)".

      Expected results

      • I should be able to edit any source made by compose-cli.

      Actual results

      • BUG: instead of updating the source with the id  "aap-2.4-rhel-9", it created a new source with the id "Red Hat Ansible Automation Platform 2.4 for RHEL 9 x86_64 (RPMs)".

              gzuccare@redhat.com Gianluca Zuccarelli
              rhn-support-lufernan Luiz Felipe Fernandes Machado Costa
              Jacob Kozol Jacob Kozol (Inactive)
              Yi He Yi He
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: