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

symlink not being created in duplicated IOU devices or IOU projects in 2.1.12 #2699

Closed
highslater opened this issue Feb 4, 2019 · 7 comments
Assignees
Labels
Milestone

Comments

@highslater
Copy link

highslater commented Feb 4, 2019

LINUX

The feature "Automatically create a symbolic link to the IOU image in the IOU working directory." is possibly causing problems.

This worked in 2.1.11, but not in 2.1.12 LINUX

1.) open a new project "TEST"
2.) insert an IOU router >>> START.
3.) STOP router and save project as "TEST_COPY"
4.) START >>> ERRNO 17 "cannot create symlink, FILE EXISTS.

This happens with anything involving duplication of devices or projects.
-when a router is first created and started the symlink is properly created in the devices iou folder.
-when the project is copied or the device is duplicated the devices iou file has what it thinks is a bin file.
-if this pseudo bin file is deleted and the the duplicated device restarted the device works. Not a great
workaround for projects with 30 devices.

This sounds like the common symlink creation problem that is usually handled with
ln -sfn /new/target /path/to/symlink
But I am guessing.

@grossmj grossmj added this to the 2.1.13 milestone Feb 12, 2019
@grossmj grossmj added the Bug label Feb 12, 2019
@grossmj grossmj self-assigned this Feb 18, 2019
@grossmj
Copy link
Member

grossmj commented Feb 18, 2019

Indeed symlinks were not copied when duplicating a node. This is fixed now, thanks for reporting it.

@grossmj grossmj closed this as completed Feb 18, 2019
@highslater
Copy link
Author

Ok.
1.) I pasted this code into 2.1.12 and you can indeed duplicate a router within a project.
however this still happens when ...

2.) A project (test) is "saved as" (test_copy) using FILE > Save project as ...
[ you would do this when making a back-up copy or as a simple version control ]

3.) A project (test) is "duplicated" (test_copy) using FILE > New blank project > Projects library (select "test" > Duplicate).

2 and 3 might be the same bug.

@grossmj grossmj reopened this Feb 19, 2019
@grossmj
Copy link
Member

grossmj commented Feb 19, 2019

This commit should cover these cases: GNS3/gns3-server@ae35154

Please let me know if there is still a problem.

Thanks again!

@grossmj grossmj closed this as completed Feb 19, 2019
@highslater
Copy link
Author

The Above worked Flawlessly when using a local server.
When using a client to access an esxi gns3_vm however, it does not.
It might be the way I edited the files, however.
I am going to make a fresh VM and test that.

thanks

@odie213
Copy link

odie213 commented Mar 15, 2019

I can verify this doesn't work with gns3_vm. I can save project A as another project B. Shut GNS3 off, turn it all back on and only project A will start up. Project B opens but if I try to start it, I get "could not create symbolic link" errors. I am using 2.1.14

@grossmj grossmj reopened this Mar 15, 2019
@grossmj grossmj modified the milestones: 2.1.13, 2.1.15 Mar 15, 2019
@grossmj
Copy link
Member

grossmj commented Mar 18, 2019

Fixed in GNS3/gns3-server@e291ec1

@grossmj grossmj closed this as completed Mar 18, 2019
@odie213
Copy link

odie213 commented Mar 18, 2019

That worked! Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants