Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a catalog item for Azure 2. if the Instance name provided is more than 15 chars or has special chars ,the request fails. 3. It will be good to show this restriction while creating the item Actual results: Expected results: Additional info:
I'll take this one too. Especially since the rules keep changing.
https://github.com/ManageIQ/manageiq/pull/12947
Added new test case id above - I'm checking the 1 character vm name now.
This bug is the same as the password bug, which is to say it's two bugs. One is fixed in basic lifecycle provision, this one, but another bug needs to be fixed for the azure provision template JSON.
I'm going to rename these and move them to verified. Then open up a consolidate bug for Bill to update the template with these validations. There should have been two bugs for this issue, but since Dan already submitted commits to fix the none-orchestration UI. This is working otherwise when LifeCycle deploying templates.