Hot!Bug tracker? Or, how to know if a bug fix is relevant in release notes?

Author
ispcolohost
Silver Member
  • Total Posts : 93
  • Scores: 1
  • Reward points: 0
  • Joined: 2014/11/18 08:06:51
  • Status: offline
2015/07/30 09:12:43 (permalink)
0

Bug tracker? Or, how to know if a bug fix is relevant in release notes?

Hello, I found this thread:
 
https://forum.fortinet.com/tm.aspx?m=68922
 
from four years ago discussing whether or not there is a bug tracker that is accessible.  I couldn't find one so I have to guess no is still the answer.  That leads to the question, if release notes only tell you the following bugs were fixed, how are you supposed to know if the fixed bugs are actually relevant to your environment, and/or a security concern?  
 
I'm running 2.5.3 and 2.5.4 just came out.  It fixes seven bugs, identified only by ID number.  Are they critical security issues?  Display issues that I could care less about?  Should I schedule an emergency outage now?  Or never since the bugs don't matter to me?
 
How does one make the decision with no information?
 
 
#1

11 Replies Related Threads

    kernal
    New Member
    • Total Posts : 8
    • Scores: 0
    • Reward points: 0
    • Joined: 2020/08/26 04:04:35
    • Status: offline
    Re: Bug tracker? Or, how to know if a bug fix is relevant in release notes? 2020/09/02 06:20:49 (permalink)
    0
    I know this is an old "thread" - but five years later I have the same question.

    • FortiGate Active/Passive Cluster w/ FortiOS v6.2.1 build0932 (GA)
    • FortiAnalyzer (FAZVM64) v6.4.1-build2072 200615 (GA)
    • FortiClient EMS 6.4.1 build 1498
    • FortiClient 6.4.1
    #2
    Yurisk
    Silver Member
    • Total Posts : 116
    • Scores: 22
    • Reward points: 0
    • Joined: 2011/12/04 03:30:01
    • Status: offline
    Re: Bug tracker? Or, how to know if a bug fix is relevant in release notes? 2020/09/03 01:27:10 (permalink)
    0
    Indeed, good question. I still can't find any bug tracking tool - neither open to public, nor open to Partners. 
    May be Fortinet folks will have more to say.
     
    #3
    ispcolohost
    Silver Member
    • Total Posts : 93
    • Scores: 1
    • Reward points: 0
    • Joined: 2014/11/18 08:06:51
    • Status: offline
    Re: Bug tracker? Or, how to know if a bug fix is relevant in release notes? 2020/09/03 04:54:54 (permalink)
    0
    I'm not holding my breath given it's been five years since I posted that; it's the same company that charges a fee for TOTP auth...  Well I shouldn't say that, perhaps they'll release FortiBugtrack where we have to pay for access to know what bugs exist in our hardware/software.
     
    Cisco has really done well in this area the past few years.  I can now subscribe to given hardware/software products and get notifications any time there is an update for them, even specifying major/minor, what to ignore.  I can also not only see the bug id's, I can subscribe to specific bug id's to know when there is a release directly affecting that bug id, or if a workaround to it has been posted/created.  I can even go directly to forum posts related to a given bug id.
    #4
    Admin_FTNT
    Administrator
    • Total Posts : 97
    • Scores: 6
    • Reward points: 0
    • Joined: 2003/11/28 00:00:00
    • Status: offline
    Re: Bug tracker? Or, how to know if a bug fix is relevant in release notes? 2020/09/03 07:47:56 (permalink)
    0
    Yuri,
     
    There is a Bugtracker tool available when you access the Support Portal using your partner credentials.
     
    Regards,
    Admin.
    #5
    emnoc
    Expert Member
    • Total Posts : 5863
    • Scores: 387
    • Reward points: 0
    • Joined: 2008/03/20 13:30:33
    • Location: AUSTIN TX AREA
    • Status: offline
    Re: Bug tracker? Or, how to know if a bug fix is relevant in release notes? 2020/09/03 07:58:51 (permalink)
    0
    Yes FTNT need a bugtrack or PR tool and we should not need to engage a partner or support for that.  Cisco and junos both others this for any customer or partner as standard support offer. No need to open a support case to track bugs or problems between versions , platforms, etc.....
     
    Hint FTNT should follow lead and provide a simple tool option access. This is not the 19 nineties any more ;)
     
    Ken Felix

    PCNSE 
    NSE 
    StrongSwan  
    #6
    Yurisk
    Silver Member
    • Total Posts : 116
    • Scores: 22
    • Reward points: 0
    • Joined: 2011/12/04 03:30:01
    • Status: offline
    Re: Bug tracker? Or, how to know if a bug fix is relevant in release notes? 2020/09/03 10:41:16 (permalink)
    0
    Admin_FTNT
    Yuri,
    There is a Bugtracker tool available when you access the Support Portal using your partner credentials.
     Regards,
    Admin.

    Thanks, that would be great news, any chance of pointing me in the right direction ?
    Here is the screenshot of the Portal and clicking through I somehow cant find the Bug tracker:
    [Edit] On the other hand - never mind, you are Forums admin, not Portal admin, so I will open a ticket with TAC if I don't find it myself .
    Good week end everyone.
     
    post edited by Yurisk - 2020/09/03 10:52:14
    #7
    ispcolohost
    Silver Member
    • Total Posts : 93
    • Scores: 1
    • Reward points: 0
    • Joined: 2014/11/18 08:06:51
    • Status: offline
    Re: Bug tracker? Or, how to know if a bug fix is relevant in release notes? 2020/09/03 10:43:31 (permalink)
    5 (1)
    And customers are just hung out to dry then?  Or should I expect my partner to keep track of every hardware model we have, they give me every bug ID, I then let them know every bug ID I care about, I audit that they are continuing to let me know about every bug ID I care about, I tell our regulatory compliance auditors that hey, I'm sure my partner will let me know if anything important comes up...
    #8
    emnoc
    Expert Member
    • Total Posts : 5863
    • Scores: 387
    • Reward points: 0
    • Joined: 2008/03/20 13:30:33
    • Location: AUSTIN TX AREA
    • Status: offline
    Re: Bug tracker? Or, how to know if a bug fix is relevant in release notes? 2020/09/03 11:12:32 (permalink)
    0
    I think you need partner access. Are you a partner?
     
    Ken Felix
     

    PCNSE 
    NSE 
    StrongSwan  
    #9
    ispcolohost
    Silver Member
    • Total Posts : 93
    • Scores: 1
    • Reward points: 0
    • Joined: 2014/11/18 08:06:51
    • Status: offline
    Re: Bug tracker? Or, how to know if a bug fix is relevant in release notes? 2020/09/03 11:13:12 (permalink)
    0
    No, customer.
    #10
    kernal
    New Member
    • Total Posts : 8
    • Scores: 0
    • Reward points: 0
    • Joined: 2020/08/26 04:04:35
    • Status: offline
    Re: Bug tracker? Or, how to know if a bug fix is relevant in release notes? 2020/09/03 23:18:45 (permalink)
    0
    Why only for partners? Is Fortinet still believing in security through obscurity?

    I have currently an issue with Forticlient v6.4.1, which is documented in the release news for v6.0.8 as "Known Issue". The issue is not mentioned anymore in the release notes of the later clients, neither as "Known" nor as "Fixed". But I still *have* the issue.
     
    What I have learnt from this is, if an issue is not explicity mentioned in the "Fixed Issues" section of the release notes, the issue is not and maybe will not be fixed.

    • FortiGate Active/Passive Cluster w/ FortiOS v6.2.1 build0932 (GA)
    • FortiAnalyzer (FAZVM64) v6.4.1-build2072 200615 (GA)
    • FortiClient EMS 6.4.1 build 1498
    • FortiClient 6.4.1
    #11
    ispcolohost
    Silver Member
    • Total Posts : 93
    • Scores: 1
    • Reward points: 0
    • Joined: 2014/11/18 08:06:51
    • Status: offline
    Re: Bug tracker? Or, how to know if a bug fix is relevant in release notes? 2020/09/04 02:54:04 (permalink)
    0
    I can give you an example of why such a public bug tracker would be useful.  I recently purchased and installed FortiAnalyzer VM.  6.4.2 had not come out yet, but was imminent.  I installed 6.4.1.  Unbeknownst to me, there is a bug in 6.4.1 where the stupid thing allocates a ridiculously low number of inodes per gigabyte of storage assigned, and the result was my FortiAnalyzer failing after a month because it had run out of inodes from report generation, while disk space was only at 5%.  Figuring this whole mess out wasted countless hours with support, manual regeneration of the relevant reports that had failed for two weeks, and ultimately a fresh install of 6.4.2 to then backup and restore into.  All because you can't be bothered to release a public bug tracker.  Had there been one, and I saw this relevant bug, I'd have thin-allocated a massive amount of space for the 6.4.1 deployment to not later have an outage as a result, then I could have downsized into a backup/restore 6.4.2 instance at my leisure.
    #12
    Jump to:
    © 2020 APG vNext Commercial Version 5.5