Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VIC plugin throws a parsing error when customer tries to specify only the gateway for management network. #7602

Closed
yeshwantbabar opened this issue Mar 29, 2018 · 6 comments
Labels
area/ui The Virtual Container Host administration UI kind/defect Behavior that is inconsistent with what's intended priority/p2 source/customer Reported by a customer, directly or via an intermediary status/needs-triage The issue needs to be evaluated and metadata updated team/lifecycle

Comments

@yeshwantbabar
Copy link

screen shot 2018-03-22 at 12 53 13 pm
When you provide a gateway for the management network, it's mandatory to provide at least one routing destination. UI Plugin doesn't reflect that. It has two separate fields for Gateway and Routing destinations. If the customer doesn't provide both the fields properly, plugin throws a weird parsing error [Refer to the screenshot].

There should be just one text field, Routing Destinations:Gateway along with a tooltip/help which explains this configuration.

The same thing applies to client network configurations as well.

@andrewtchin andrewtchin added area/ui The Virtual Container Host administration UI status/needs-triage The issue needs to be evaluated and metadata updated team/lifecycle labels Mar 29, 2018
@andrewtchin andrewtchin added this to the Sprint 29 Lifecycle milestone Mar 29, 2018
@mdubya66 mdubya66 added the kind/defect Behavior that is inconsistent with what's intended label Apr 10, 2018
@mdubya66

This comment has been minimized.

@AngieCris

This comment has been minimized.

@mdubya66 mdubya66 added priority/p2 impact/doc/note Requires creation of or changes to an official release note and removed priority/p1 labels Apr 17, 2018
@andrewtchin andrewtchin removed this from the Sprint 30 Lifecycle milestone Apr 25, 2018
@stuclem
Copy link
Contributor

stuclem commented May 15, 2018

Proposed release note:

  • Create Virtual Container Host wizard plugin throws a parsing error when you specify only the gateway for the management or client networks. #7602
    When you provide a gateway for the management or client network, it is mandatory to provide at least one routing destination. The Create Virtual Container Host wizard does not conform to this behavior and has two separate fields for the Gateway and Routing destinations. If you do not fill in both the fields correctly, the wizard reports a parsing error.

I added this in both the vic and vic-ui release notes.

@zjs
Copy link
Member

zjs commented May 22, 2018

From discussion with @pdaigle: Management network should be restructured to make it clearer that the when a gateway is entered, one or more routing destinations must be entered. Client-side validation should be added to enforce this. This will be more consistent with the CLI.

@zjs
Copy link
Member

zjs commented Jul 31, 2018

Issue moved to vmware/vic-ui #568 via ZenHub

@zjs zjs closed this as completed Jul 31, 2018
@stuclem
Copy link
Contributor

stuclem commented Sep 17, 2018

Moved in to resolved issues in https://github.com/vmware/vic/releases/edit/v1.4.3

@stuclem stuclem removed the impact/doc/note Requires creation of or changes to an official release note label Sep 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ui The Virtual Container Host administration UI kind/defect Behavior that is inconsistent with what's intended priority/p2 source/customer Reported by a customer, directly or via an intermediary status/needs-triage The issue needs to be evaluated and metadata updated team/lifecycle
Projects
None yet
Development

No branches or pull requests

6 participants