Red Hat Bugzilla – Bug 1315945
Cannot select Azure Subnet if first VIrtual Private Cloud is selected.
Last modified: 2017-08-30 08:18:12 EDT
Description of problem:
I'm provisioning a VM from an image, when I get to the Environment page, if the first Virtual Private Cloud occurrence is the one I want, then you cannot select it's subnet. To do so, you have to select the second or some other VPC and then select the first one again. Only then can you select the Subnet.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Provision an Azure Instance from an Image.
2. At the environment page, with selecting a VPC, try to select the first entry's subnet.
3. Select the second entry and then select the first and then it works.
Can't select the desired subnet on the first choice.
Find me if you need a quick meeting to see it.
New commit detected on ManageIQ/manageiq/master:
Author: Harpreet Kataria <firstname.lastname@example.org>
AuthorDate: Thu Mar 10 10:34:30 2016 -0500
Commit: Harpreet Kataria <email@example.com>
CommitDate: Thu Mar 10 10:34:30 2016 -0500
Show <choose> in Virtual Private Cloud select by default.
Removed default: nil from dialog, so VPC pull down displays <Choose> as default selected option to get other pull downs on the screen populated appropriately based upon Virtual Private Cloud pull down selection.
product/dialogs/miq_dialogs/miq_provision_amazon_dialogs_template.yaml | 1 -
product/dialogs/miq_dialogs/miq_provision_azure_dialogs_template.yaml | 1 -
2 files changed, 2 deletions(-)
This is a perfect solution. Nice job. Moving to Verified using Beta1 on https://10.16.6.85/miq_request
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.