GNS3 2.2.49+ New projects with IOU work, previous GNS3 2.2.47 IOU projects fail to OPEN alleging image is missing

[e-thibault]

This applies to GNS3 installation on ubuntu, the issue was found on ubuntu 24.04 and GNS3 2.2.49
but is still present in GNS3 2.2.50.

The issue in GNS3 2.2.49 and following has been reported first there :
https://gns3.com/community/featured/gns3-2-2-49-on-ubuntu-24-04-does-not-recognize-gns3-2-2-47-projects-working-on-ubuntu-22-04

No-body else than me replied.
Thinking GNS3 2.2.50 could may be have corrected it, I upgraded to GNS3 2.2.50
I hit the issue of users rights which I reported in gns3 comunity.

When the GNS3 2.2.50 user right issue got corrected, I upgraded to the new GNS3 2.2.50
the user right issue is corrected.
The previous issue with existing IOU projects with previous GNS3 2.2.47 .gns3 project files still exist so I create this issue.

Describe the bug

I can create a new project with my IOU device, I can start it I can console in it.
But when I OPEN (not even launch) a previous project with the same IOU device
I get the error :
the image is missing

To Reproduce

You need to have a previous .gns3 project file with an IOU device used in it,
a project file created in GNS3 2.2.47 or before.
You need to have created the same device, with the image.

You will see the new projects using the IOU image will work.
But at the time of OPENING a previous .gns3 project with an IOU device referenced (created in GNS3 2.2.47 or before)

Screenshots or videos

1. screenshot of the error at the OPENING of a previous .gns3 project:

N.B. this project works 100% fine on ubuntu 22.04 on GNS3 2.2.47

2. screenshot proving the image is NOT missing

3. screenshot proving the image is running and 100% operational for NEW PROJECTS

[e-thibault]

since it was the first time I launched GNS3 after reinstallation in 2.2.50 I opened it by typing 'gns3' in a terminal window,
so in the terminal window I got the logs of the error I add here below in case it could help:
thibault@NetAuto2404:~$ gns3 2024-10-23 15:00:06 INFO root:126 Log level: INFO 2024-10-23 15:00:06 INFO main:265 GNS3 GUI version 2.2.50 2024-10-23 15:00:06 INFO main:266 Copyright (c) 2007-2024 GNS3 Technologies Inc. 2024-10-23 15:00:06 INFO main:267 Application started with /usr/bin/gns3 2024-10-23 15:00:07 INFO controller:437 Listening for controller notifications on 'ws://localhost:3080/v2/notifications/ws' 2024-10-23 15:00:35 INFO project:647 Listening for project notifications on 'ws://localhost:3080/v2/projects/19cfbfc7-2271-4d15-a954-45f2ebfbe260/notifications/ws' 2024-10-23 15:01:50 CRITICAL topology.py:258 The image i86bi_linux-adventerprisek9-ms.154-1.T_A is missing 2024-10-23 15:09:25 INFO project:647 Listening for project notifications on 'ws://localhost:3080/v2/projects/ec6c934e-9666-49f4-98dc-7e1cb2d4ac33/notifications/ws' 2024-10-23 15:12:16 INFO project:647 Listening for project notifications on 'ws://localhost:3080/v2/projects/b4d6df98-09de-40da-85bb-544c14911b96/notifications/ws' thibault@NetAuto2404:~$

[stutzzzz]

Having same issue. Also crashes on cosmic using wayland not sure if its related.

[e-thibault]

it seems there was not a GNS3 2.2.50 new version with corrections for cosmic (i.e 18.10) judging by Jeremy's message:
#3646 (comment)

[e-thibault]

OK in the message above the error was issued by the module : topology.py line 258.

So I've edited the file to see if I could see something:
in topology.py the lines around line 258 are :

def _projectCreationErrorSlot(self, message):
    if self._project:
        self._project.project_creation_error_signal.disconnect(self._projectCreationErrorSlot)
        self.setProject(None)
        QtWidgets.QMessageBox.critical(self._main_window, "New project", message)

line 258 is: QtWidgets.QMessageBox.critical(self._main_window, "New project", message)

the last function called:
_projectCreationErrorSlot(self, message)
is the same as in GNS3 2.2.47 so it does not come from it.
_projectCreationErrorSlot(self, message)
function is not called in the module topology.py so it must be called from elsewhere

What is definitely not NORMAL is that we go through the function "_projectCreationErrorSlot(self, message)"
because it was NOT a project creation but on the contraryI was just opening an existing .gns3 project file !

How come we end up in this case ?
I don't know but it's 100% reproductible

[stutzzzz]

it seems there was not a GNS3 2.2.50 new version with corrections for cosmic (i.e 18.10) judging by Jeremy's message: #3646 (comment)

Sorry I meant System76 Cosmic that is 22.04 using wayland

[stutzzzz]

Installed the recent update still unable to locate images that were installed

[grossmj]

I cannot reproduce the error, even though I created an IOU project with v2.2.47 and opened it with v2.2.50.

Please can you provide the output of ls -la /home/thibault/GNS3/images/IOU/?

Also, do you have the same issue if you create a project with IOU nodes under v2.2.50?

Thanks.

[e-thibault]

Hello, Please can you provide the output of ls -la /home/thibault/GNS3/images/IOU/? For the moment I cannot because the VM is on my pro laptop which has been "upgraded" in such a way that none of my VM can start now I have open a ticket and wait for a solution as soon as I can reply I will. Le dimanche 27 octobre 2024 à 11:07:51 UTC+1, Jeremy Grossmann ***@***.***> a écrit : I cannot reproduce the error, even though I created an IOU project with v2.2.47 and opened it with v2.2.50. Please can you provide the output of ls -la /home/thibault/GNS3/images/IOU/? Also, do you have the same issue if you create a project with IOU nodes under v2.2.50? No, as I said for new projects created under GNS3 2.2.50 I could run them (when I had my VM...) Thanks. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[grossmj]

@e-thibault I would like to release v2.2.51 soon. Any news about this?

[e-thibault]

HiUnfortunately even though the ticket I raised has been solved, I still cannot launch my VMs on my pro laptop (VMware worstation telling me to train to regain ownership which fails)For the moment I have to concentrate on my mission for a customer next week I'll have more time I think. Best Regards Thibault Le lundi 4 novembre 2024 à 05:50:35 UTC+1, Jeremy Grossmann ***@***.***> a écrit : @e-thibault I would like to release v2.2.51 soon. Any news about this? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[e-thibault]

Hello Jeremy, My VMs finally work again (another windows update ?) I managed to enter the command you have asked for and I put the result in :https://gns3.com/community/featured/after-upgrade-2-2-50-router-is-missing-even-if-it-exist I found something else interesting that could help understand the issue, on my ubuntu 22.04 VM with GNS3 2.2.47 when I launch GNS3 and I click on "Projects Library",I get that (i.e. normal) : ubuntu 22.04 GNS3 2.2.47 | | | | 18-11_directory_project_u2204_GNS3_2-2-47.png | | | on my ubuntu 24.04 VM with GNS3 2.2.50 when I launch GNS3 and I click on "Projects Library",I get that (weird) : ubuntu 24.04 GNS3 2.2.50 | | | | 18-11_directory_project_u2404_GNS3_2-2-50.png | | | I hope it helps, Best Regards Thibault Le dimanche 27 octobre 2024 à 11:07:51 UTC+1, Jeremy Grossmann ***@***.***> a écrit : I cannot reproduce the error, even though I created an IOU project with v2.2.47 and opened it with v2.2.50. Please can you provide the output of ls -la /home/thibault/GNS3/images/IOU/? Also, do you have the same issue if you create a project with IOU nodes under v2.2.50? Thanks. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[grossmj]

Please can you send me your project?

[e-thibault]

Hello, here is the whole directory of the project from my ubuntu 24.04 project This is a reproduction of the former TSHOOT lab, I use it as a test often because there are several device types used in itand with nearly a simple ping I can see if it works, I copy an extract of the readme (in French) "faire dhcp dans les PC pour récupérer une IP et ping 209.65.200.241ça fonctionne mais "duplex mismatch sur R4" corrigible mais ça revient tout seul ..." Best Regards Thibault Le mercredi 27 novembre 2024 à 06:35:19 UTC+1, Jeremy Grossmann ***@***.***> a écrit : Please can you send me your project? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[e-thibault]

Hello again, By the way please let me know if you have found anything and even if you have found nothing,Bon courage ! Thibault Le mercredi 27 novembre 2024 à 06:35:19 UTC+1, Jeremy Grossmann ***@***.***> a écrit : Please can you send me your project? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[grossmj]

Hello, here is the whole directory of the project from my ubuntu 24.04 project

I don't see it, have you shared a link or an attachment? thanks 👍

Aussi, pas de probleme avec le francais.

[e-thibault]

Hello an attachments Yahoo Mail : Recherchez, organisez, maîtrisez Le jeu., nov. 28, 2024 à 3:53, Jeremy ***@***.***> a écrit: Hello, here is the whole directory of the project from my ubuntu 24.04 project I don't see it, have you shared a link or an attachment? thanks 👍 Aussi, pas de probleme avec le francais. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>