Uploaded image for project: 'Automation Hub'
  1. Automation Hub
  2. AAH-1905

Execution enviroment sign task does not fail on unsynced remote containers

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • 2.3
    • Unspecified
    • QE
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Do Not Include (note: this means to exclude from release notes and errata)

      When you create remote Execution environment which is not synced, signing task is completed without errors, but signing state still remains unsigned.

      Expected task to be failed.

              hhummel@redhat.com Henderson Hummel (Inactive)
              mipospis@redhat.com Milan Pospisil
              Christian Torrens Christian Torrens (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: