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

FortiGate 7.4.4 wrong build number #906

Closed
bikkio opened this issue Aug 8, 2024 · 3 comments · Fixed by #907
Closed

FortiGate 7.4.4 wrong build number #906

bikkio opened this issue Aug 8, 2024 · 3 comments · Fixed by #907
Labels

Comments

@bikkio
Copy link

bikkio commented Aug 8, 2024

Hi all

in GNS3 2.2.49 i noticed that the FortiGate template for version 7.4.4 report the same build number of 7.4.3.

Wrong:
FGT_VM64_KVM-v7.4.4.F-build2573-FORTINET.out.kvm.qcow2
FGT_VM64_KVM-v7.4.3.F-build2573-FORTINET.out.kvm.qcow2

It should be FGT_VM64_KVM-v7.4.4.F-build2662-FORTINET.out.kvm.qcow2

Regards

Marco

@bikkio bikkio added the bug label Aug 8, 2024
@bikkio bikkio changed the title Fortigate 7.4.4 wrong buind number FortiGate 7.4.4 wrong build number Aug 8, 2024
@grossmj grossmj transferred this issue from GNS3/gns3-gui Aug 10, 2024
@grossmj
Copy link
Member

grossmj commented Aug 10, 2024

@bikkio thank for spotting this. Do you know if the size is the same as FGT_VM64_KVM-v7.4.3.F-build2573-FORTINET.out.kvm.qcow2? (100728832 bytes)

@bikkio
Copy link
Author

bikkio commented Aug 12, 2024

@grossmj the size is different

FGT_VM64_KVM-v7.4.3.F-build2573-FORTINET.out.kvm.qcow2 (100728832 bytes)
FGT_VM64_KVM-v7.4.4.F-build2662-FORTINET.out.kvm.qcow2 (102170624 bytes)

@grossmj grossmj linked a pull request Aug 13, 2024 that will close this issue
@grossmj
Copy link
Member

grossmj commented Aug 13, 2024

@bikkio thanks, I have created a PR to fix this issue: #907

Please review and I will merge if everything is good. Thanks.

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

Successfully merging a pull request may close this issue.

2 participants