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

Export portable project does not export all base images #1928

Closed
david-ramsden opened this issue Mar 13, 2017 · 8 comments
Closed

Export portable project does not export all base images #1928

david-ramsden opened this issue Mar 13, 2017 · 8 comments
Labels
Milestone

Comments

@david-ramsden
Copy link

david-ramsden commented Mar 13, 2017

GNS3 version 2.0.0rc2 on Windows (64-bit) with Python 3.6.0 Qt 5.8.0 and PyQt 5.8.

This is using GNS3 GUI and GNS3 VM. VM version is actually 2.0.0b4 and GUI is 2.0.0rc2. But I have tried this with GNS3 GUI and GNS3 VM versions 2.0.0b4, 2.0.0rc1 and 2.0.0rc2.

I have a project which makes use of Dynamips, IOU and QEMU images. When I use the "Export portable project" function and I select Yes to export base images, a .gns3project file is produced and no errors are displayed.

If I open the .gns3project file using 7-Zip, the images directory only contains the Dynamips image:

image
image

The project-files directory does contain Dynamips, IOS and QEMU data. For example:

image
image
image

When trying to import this portable project I get the following error:

ImportProjectWorker thread stopping with an error: Could not import the project: [Errno 13] Permission denied: 'None'
Could not import the project: [Errno 13] Permission denied: 'None'

I'm wondering if this error happens because some of the base images are missing?

@david-ramsden
Copy link
Author

GNS3 GUI full debug when trying to import project: http://pastebin.com/raw/660jh0MS

@julien-duponchelle
Copy link
Contributor

What is the permissions of your images directory?

@julien-duponchelle julien-duponchelle added this to the 2.0 milestone Mar 13, 2017
@david-ramsden
Copy link
Author

david-ramsden commented Mar 13, 2017

On the GNS3 VM /opt/gns3/images is chmod 755 and chown gns3:gns3.

image

I've also tried importing to a clean install of 2.0.0rc2 running on ESXi as a remote main server and encounter the same issue. Again /opt/gns3/images is chmod 755 and chown gns3:gns3 out of the box.

@julien-duponchelle
Copy link
Contributor

Could you export the project and go to the GUI menu Help / Export Debug informations and send me the zip and the resulting exported project to julien@gns3.net

Thanks a lot for the help

@david-ramsden
Copy link
Author

david-ramsden commented Mar 13, 2017

Email sent @noplay

@julien-duponchelle
Copy link
Contributor

Thanks I found the issue.

If you don't have a copy of the image use on the remote server during export, you will have missing images.

I fixed the trouble by showing an error. I know it's not perfect but it's too risky to change this now that we are close to the release.

@WarpRat
Copy link

WarpRat commented Feb 21, 2018

In 2.1.3 this appears to still be an issue and doesn't give any error.

When exporting a portable project with IOU images and selecting include base images the IOU images aren't included in the portable project. The permissions and ownership are the same (755 & gns3:gns3) as syndgr, although I also tried setting the permissions of the images directory and everything in it to 777 for testing with no success.

I haven't been able to export the debug information from the gui as I'm using a remote server running Ubuntu 16.04. I did read through all the logs I could find on the server and nothing jumped out at me. I've attempted this from a gns3-gui running on Ubuntu 17.10, 17.04, and MacOS 10.13 all using the same remote server.

I was able to open the portable project and manually insert the IOU images in the proper files structure and successfully load the project in another GNS3 gui, but it's an inelegant solution if you need to often create portable projects.

Please let me know if I can provide any additional information for you or if you'd like me to open a separate bug report. Thank you.

@ziajka
Copy link
Contributor

ziajka commented Feb 22, 2018

Hi @WarpRat,

Thank you for reporting this. If you may, please open the new issue with reference to this one. Probably it can be similar problem but different solution.

Cheers,
Dominik

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

4 participants