Container Name Collision

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • 4.9.2
    • Affects Version/s: master, panorama, 4.9.1
    • Component/s: Pegasus Lite
    • None

      When assigning names to containers we use the date function to provide a unique name.
      However, because the granularity is in seconds, when planning multiple instances of the same workflow, this can lead to name collisions.
      Collisions will only affect the runs if the jobs will attempt to run simultaneously on the same host machine.

      A possible fix is to use the guid function instead of a timestamp.

            Assignee:
            George Papadimitriou
            Reporter:
            George Papadimitriou
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: