storageName does not do a good enough job of being globally unique.

[Goobaroo]

Do you already have an issue opened with F5 support?

Github Issues are consistently monitored by F5 staff, but should be considered as best effort only and you should not expect to receive the same level of response as provided by F5 Support. Please open an case with F5 if this is a critical issue.

Description

Describe the problem you're having or the enhancement you'd like to request. storageName does not do a good enough job of being globally unique.

This is how the name is currently set in the byol 3nic deployment. storageName = 'f5-bigip-storage-' + context.env['deployment']

This was our fix: storageName = 'f5-bigip-storage-' + context.env['deployment'] + "-" + context.env['project'] storageName = (storageName[:63]) if len(storageName) > 63 else storageName

Template

For bugs, enter the template with which you are experiencing issues below. All the templates seem to set the storageName value the same way.

Severity Level

For bugs, enter the bug severity level. Do not set any labels.

Severity: 3

Severity level definitions:

1. Severity 1 (Critical) : Defect is causing systems to be offline and/or nonfunctional. immediate attention is required.
2. Severity 2 (High) : Defect is causing major obstruction of system operations.
3. Severity 3 (Medium) : Defect is causing intermittent errors in system operations.
4. Severity 4 (Low) : Defect is causing infrequent interuptions in system operations.
5. Severity 5 (Trival) : Defect is not causing any interuptions to system operations, but none-the-less is a bug.

[shyawnkarim]

Closing.

We are focused on developing our next generation templates and won't be implementing your enhancement request. Your workaround seems to have fixed the issue for you.