Flavor Name that contains dash character disappears and prevents Template creation.

[allanster]

Currently cannot use dash character - in the Flavor Name or it will report success but then Templates cannot choose Operating System and Flavor. Workaround for now is to not use dash characters for Flavor Name.

Took me awhile to isolate this issue because I nave never used appliance before and assumed I must be doing something wrong. The popup information on permissible characters when creating Flavor Name is what misled me into thinking I could use dash characters in name:

"The Flavor Name field must contain a valid value. It must start with an alphabetic character followed by alphabetic charaters and/or numbers and or/the and/or the - character. It can not contain spacing, quotes or other special characters like %, *, #, . etc..."_

I have watched your videos and read Mike's pdf guide and after a few hours of troubleshooting am fairly confident that I am now using the appliance properly. It was my unfortunate choice of using dash characters that was causing me such grief.

Testing was done with single iso file uploaded to Local storage, have reproduced this behavior on:

Build uda30build143.ova with no patches applied uda30build143.ova with patch uda30P2.tgz applied

Storage Local: ESXi-6.7.0-201901001-standard-82583v.iso

OS Flavor Name: thisFlavor-disappears Operating System: VMware ESX 6.7i installable

Templates Operating System: dropdown field has no choices (unpopulated) Flavor: dropdown field has no choices (unpopulated)

Hypervisor ESXi 6.7 physical host

---

Workaround: once I create a new Flavor Name that does not contain any dash characters then Templates drodown choices for Operating System and Flavor are again populated.

OS Flavor Name: thisFlavor_works Operating System: VMware ESX 6.7i installable

Templates Operating System: VMware ESX 6.7i installable Flavor: thisFlavor_works

[TheNetworkIsDown]

Can confirm. uda30P4 also affected.