Red Hat Bugzilla – Bug 1402528
Azure : Instance name restriction should be shown in UI when creating a catalog item for Azure
Last modified: 2017-02-27 14:27:16 EST
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/0f4142ff5b86bdc72f4cc60cf3090868b3228718 commit 0f4142ff5b86bdc72f4cc60cf3090868b3228718 Author: Greg McCullough <gmccullo@redhat.com> AuthorDate: Tue Dec 6 10:10:10 2016 -0500 Commit: Satoe Imaishi <simaishi@redhat.com> CommitDate: Mon Jan 9 12:58:01 2017 -0500 Merge pull request #12947 from djberg96/provision_template Update Azure provision template to restrict VM names (cherry picked from commit 5f9094f3e2b9dd8fe5174e70bba36b51dade5982) https://bugzilla.redhat.com/show_bug.cgi?id=1402528 .../miq_dialogs/miq_provision_azure_dialogs_template.yaml | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-)
https://github.com/ManageIQ/manageiq/pull/12947
Does this bug feature require the new Armrest version as well. I see some things working but some not. For instance, it caps it at 15 chars just fine, but it accepts this 1111111 which should generate the message but doesn't
Jeff, I didn't see anything in the docs that stated that it could not contain only numbers. However, I can tell by using the portal that restriction does exist, so I'll need to update the regex. Still, what I have gets us most of the way there.
https://github.com/ManageIQ/manageiq/pull/13730
Please note this only addresses the azure provisioning dialogs and not the orchestration dialogs that are created by the orchestration templates themselvesm which may or may not included error checking. Errors on the latter are now reported via Events and are easier to find. For the implementation, the name error trapping is working as expected so I'm moving it to verified on 5.7.1.0.1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2017-0320.html