[
https://issues.apache.org/jira/browse/IGNITE-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571021#comment-16571021
]
Ilya Borisov edited comment on IGNITE-9191 at 8/7/18 2:01 AM:
--------------------------------------------------------------
[~pkonstantinov] I need more info about your environment. Did you have any
cluster configs prior to test? Maybe you removed some? When you got the name
clash error, was there a cluster with such a name or it matched the name of
cluster you've already removed? The issue you experienced might be another case
of corrupted state in DB, similar to what you used to get after configuration
migrations.
was (Author: klaster_1):
[~pkonstantinov] I need more info about your environment. Did you have any
cluster configs prior to test? Maybe you removed some? When you got the name
clash error, was there a cluster with such a name or it matched the name of
cluster you've already removed?
> Web Console: Cluster saved with empty name in special case
> ----------------------------------------------------------
>
> Key: IGNITE-9191
> URL: https://issues.apache.org/jira/browse/IGNITE-9191
> Project: Ignite
> Issue Type: Task
> Components: wizards
> Reporter: Alexey Kuznetsov
> Assignee: Ilya Borisov
> Priority: Major
> Fix For: 2.7
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> # Create a new cluster, DON'T save
> # Open Advanced screen
> # Go to caches.
> # Create cache.
> # Save cache.
> # Clsuter saved with EMPTY name (bug).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
