[GNS3 3.0.0] All custom appliances disappeared + Unable to reimport

[ajbxfinest24]

Describe the bug
I took a timeshift snapshot of the operating system before I upgraded GNS3 from 2.2.52 to 3.0.0. The install was successful, but upon launching the new application all of my custom appliances disappeared. I was able to install ipterm, but when I attempted to reimport Cisco, Arista, F5 or Fortigate appliances I get the error below

****** Exception detected, traceback information saved in /home/xxx/.config/GNS3/3.0/exceptions.log ******

PLEASE REPORT ON https://www.gns3.com

TypeError: invalid result from ApplianceWizard.validateCurrentPage(), a 'bool' is expected not 'NoneType'

I am able to launch my old projects, but when I attempted to connect to my Arista appliance a booting loop occurs. Photos are attached.

GNS3 version and operating system (please complete the following information):

• OS: Linux Mint
• GNS3 version 3.0.0

[grossmj]

What Cisco appliance have you tried to install?

[smart2128]

I can confirm the same behavior on Arch Linux for every appliance I try to install (e.g. VyOS, FRR, Cisco IOSvLx, RockyLinux, Kali)
I'm not sure if this might be related to the new Python 3.13.

[ajbxfinest24]

What Cisco appliance have you tried to install?

I tried to import the CSR1000v, IOSv2, Cisco 7200 appliances, different Fortigate, F5, Arista images. All give me the appliance wizard error listed above. I can only import docker based images like IPTerm, Kali Linux CLI, Toolbox etc...

[ajbxfinest24]

Just to confirm, I am able to open some of my previous projects. It loads the appliances configured for the project even the appliances not listed in the all devices column which is strange. Some of my projects that contained the network_automation docker image gives me an error message and I can't open it anymore

"Could not pull the 'gns3/network_automation:latest' image from Docker Hub, please check your Internet connection (original error: Docker has returned an error: 404 pull access denied for gns3/network_automation, repository does not exist or may require 'docker login': denied: requested access to the resource is denied)"

So it seems to be hit or miss when it comes to specific projects. I don't mind starting over with re-importing all appliances, but right now that portion doesn't work and I can't use this software. I will look out for your recommendations.

[smart2128]

Just to confirm, I am able to open some of my previous projects. It loads the appliances configured for the project even the appliances not listed in the all devices column which is strange. Some of my projects that contained the network_automation docker image gives me an error message and I can't open it anymore

Templates are not migrated automatically, you have to re-create them manually, as already answered by @grossmj in my closed issue #3667

"Could not pull the 'gns3/network_automation:latest' image from Docker Hub, please check your Internet connection (original error: Docker has returned an error: 404 pull access denied for gns3/network_automation, repository does not exist or may require 'docker login': denied: requested access to the resource is denied)"

There is no gns3/network_automation in docker hub, that's probably why it returns that error.
If I add the network_automation container from the wizard, it pulls a different image (adosztal/network_automation).

[ajbxfinest24]

Just to confirm, I am able to open some of my previous projects. It loads the appliances configured for the project even the appliances not listed in the all devices column which is strange. Some of my projects that contained the network_automation docker image gives me an error message and I can't open it anymore

Templates are not migrated automatically, you have to re-create them manually, as already answered by @grossmj in my closed issue #3667

"Could not pull the 'gns3/network_automation:latest' image from Docker Hub, please check your Internet connection (original error: Docker has returned an error: 404 pull access denied for gns3/network_automation, repository does not exist or may require 'docker login': denied: requested access to the resource is denied)"

There is no gns3/network_automation in docker hub, that's probably why it returns that error. If I add the network_automation container from the wizard, it pulls a different image (adosztal/network_automation).

Yes, i wasn't aware from the e-mail notification from github that the templates and appliances would not be migrated from 2.2 -> 3.0. If i received that in the notification like it's displayed on the blog currently I would've held off until there was a proper format with creating templates and importing a device. I tried to create a template manually from scratch and my Arista appliance doesn't boot up. Maybe I will continue to work on this at some point during the holiday break, but I attempted to restore my snapshot on my linux machine to a state with 2.2.52 installed, but because the project was opened using 3.0 It says I can't open it on 2.2.52, because it was created on a newer version of gns3 which that is not the case. So I have to use 3.0 after all but I can't get it to work.

[grossmj]

Sorry about these issues. I am working on a fix and will probably release v3.0.1 soon.

[grossmj]

@ajbxfinest24 I believe you use Linux Mint right? How have you installed version 3.0? Thanks 👍

[ajbxfinest24]

@ajbxfinest24 I believe you use Linux Mint right? How have you installed version 3.0? Thanks 👍

@grossmj Yes, I use Linux Mint 22. I installed it from the ppa that you provided to me in the GNS3 3.0 RC2 response to my question

sudo add-apt-repository ppa:gns3/ppa-v3
sudo apt install gns3-gui

[grossmj]

Unfortunately I installed a fresh Linux Mint 22 and couldn't reproduce the issue.

When do you get this error?

TypeError: invalid result from ApplianceWizard.validateCurrentPage(), a 'bool' is expected not 'NoneType'

[smart2128]

In my case, but I believe it's the same for @ajbxfinest24, it happens every time I try to install a Qemu appliance from the GNS3 server using the appliance wizard.
No issues with Docker's appliances or manually created ones.

[grossmj]

I finally found the problem. Thanks everyone for your help!

This will be fixed in v3.0.1 to be released in the next few days.