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.

Sign up for GitHub

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

Jump to bottom

[2.0] error with {name} in name of own cloud #1833

Closed
Raizo62 opened this issue Feb 1, 2017 · 3 comments
Closed

[2.0] error with {name} in name of own cloud #1833

Raizo62 opened this issue Feb 1, 2017 · 3 comments
Labels
Bug
Milestone
2.0.1

Comments

@Raizo62
Copy link

Raizo62 commented Feb 1, 2017 •
edited
Loading

Hi

In built-in device, with cloud nodes, i have tried to use {name}-{0} for default name format . I wish do the same as VirtualBox VM template.

When i use this cloud device, GNS3 shows error message.
@julien-duponchelle julien-duponchelle added this to the 2.0 milestone Feb 2, 2017
julien-duponchelle added a commit that referenced this issue Feb 3, 2017
@julien-duponchelle
Support {name} in cloud template
1629938 
Fix #1833
@julien-duponchelle
Copy link
Contributor

Fixed thanks

@Raizo62
Copy link
Author

Raizo62 commented Feb 3, 2017

Sorry, but, is it a bug again if GNS3 shows same red message if i use {Name} (with Uppercase) ?

julien-duponchelle added a commit to GNS3/gns3-server that referenced this issue Feb 6, 2017
@julien-duponchelle
Raise an error if you put an invalid key in node name
9c7d2e9 
Fix GNS3/gns3-gui#1833
@julien-duponchelle
Copy link
Contributor

Ok now it's raise a proper error when the key is unknown.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug
Projects
None yet
Milestone
2.0.1
Development

No branches or pull requests
2 participants
@julien-duponchelle @Raizo62