Almost perfect upgrade 2.3.2 to 2.3.2p1



  • Upgrade on Master pfsense, flawless.
    Upgrade on Backup pfsense, successful (maybe?) as upon reboot, the GUI showed 2.3.2 with the update available.
    If you clicked the icon to upgrade and confirmed the upgrade, it would start the upgrade process just to come back and say "Up to date" whhaatt?
    Rebooted, still the same. Used option 13 and it did download and upgraded files.
    Rebooted, Backup pfsense now shows 2.3.2p1 and no option to upgrade, yeehh.

    Upgrades getting better, thank you pfsense team.



  • Seems I got 'lucky' (this time) as other people are still having (basic) install issues when upgrading.

    What is the problem here? Technology? Coding? Tools?
    Or just 'random' computer stuff? (because that is how computers work, right?).

    @pppfsense:

    Upgrade on Master pfsense, flawless.
    Upgrade on Backup pfsense, successful (maybe?) as upon reboot, the GUI showed 2.3.2 with the update available.
    If you clicked the icon to upgrade and confirmed the upgrade, it would start the upgrade process just to come back and say "Up to date" whhaatt?
    Rebooted, still the same. Used option 13 and it did download and upgraded files.
    Rebooted, Backup pfsense now shows 2.3.2p1 and no option to upgrade, yeehh.

    Upgrades getting better, thank you pfsense team.



  • @pppfsense:

    Seems I got 'lucky' (this time) as other people are still having (basic) install issues when upgrading.

    What is the problem here? Technology? Coding? Tools?
    Or just 'random' computer stuff? (because that is how computers work, right?).

    @pppfsense:

    Upgrade on Master pfsense, flawless.
    Upgrade on Backup pfsense, successful (maybe?) as upon reboot, the GUI showed 2.3.2 with the update available.
    If you clicked the icon to upgrade and confirmed the upgrade, it would start the upgrade process just to come back and say "Up to date" whhaatt?
    Rebooted, still the same. Used option 13 and it did download and upgraded files.
    Rebooted, Backup pfsense now shows 2.3.2p1 and no option to upgrade, yeehh.

    Upgrades getting better, thank you pfsense team.

    What you're not seeing here are the thousands and thousands of people that update/upgrade without any issues, including my pfSense install that updated just fine.



  • Today performed my very first ever upgrade, not knowing exactly what to expect.
    Seemed to work just fine.  No problems.



  • Not what I am saying.

    It has gotten better, but in my experience, with other similar free software, the failure rate is very, very low.
    I, for one, have never had an upgrade failure with Untangle, and I have been using it longer than pfsense.

    With pfsense, in the last few years, every upgrade has had issues for me. Most of them small enough, but that
    is not the point here: This code is known and it does get to fail in vanilla configurations.
    Some condition/exception is not being detected or handled properly.

    Example: https://forum.pfsense.org/index.php?topic=119344.msg661368#msg661368

    When I see the word 'odds' as a possible explanation of why the upgrade went wrong, it proves my point:
    Something is missing or being missed….

    I know it is hard and I appreciate the efforts, but in order to get better, we need to admit the issues.

    @JonH:

    Today performed my very first ever upgrade, not knowing exactly what to expect.
    Seemed to work just fine.  No problems.



  • @pppfsense:

    Not what I am saying.

    It has gotten better, but in my experience, with other similar free software, the failure rate is very, very low.
    I, for one, have never had an upgrade failure with Untangle, and I have been using it longer than pfsense.

    With pfsense, in the last few years, every upgrade has had issues for me. Most of them small enough, but that
    is not the point here: This code is known and it does get to fail in vanilla configurations.
    Some condition/exception is not being detected or handled properly.

    Example: https://forum.pfsense.org/index.php?topic=119344.msg661368#msg661368

    When I see the word 'odds' as a possible explanation of why the upgrade went wrong, it proves my point:
    Something is missing or being missed….

    I know it is hard and I appreciate the efforts, but in order to get better, we need to admit the issues.

    @JonH:

    Today performed my very first ever upgrade, not knowing exactly what to expect.
    Seemed to work just fine.  No problems.

    lol… everyone knows that all complex software has bugs, known and unknown. This is not an interesting or useful observation.

    So, we admit there are issues... now what? Bug reports require details so that others can reliably and repeatably recreate your situation. Without these details there is nothing anyone can do. Things like "The update failed! HELP!!!" are not helpful.

    Also, don't forget about user error. :)



  • There, that's all I am saying, it is a bug when the upgrade on vanilla systems fails.

    @Nullity:

    @pppfsense:

    Not what I am saying.

    It has gotten better, but in my experience, with other similar free software, the failure rate is very, very low.
    I, for one, have never had an upgrade failure with Untangle, and I have been using it longer than pfsense.

    With pfsense, in the last few years, every upgrade has had issues for me. Most of them small enough, but that
    is not the point here: This code is known and it does get to fail in vanilla configurations.
    Some condition/exception is not being detected or handled properly.

    Example: https://forum.pfsense.org/index.php?topic=119344.msg661368#msg661368

    When I see the word 'odds' as a possible explanation of why the upgrade went wrong, it proves my point:
    Something is missing or being missed….

    I know it is hard and I appreciate the efforts, but in order to get better, we need to admit the issues.

    @JonH:

    Today performed my very first ever upgrade, not knowing exactly what to expect.
    Seemed to work just fine.  No problems.

    lol… everyone knows that all complex software has bugs, known and unknown. This is not an interesting or useful observation.

    So, we admit there are issues... now what? Bug reports require details so that others can reliably and repeatably recreate your situation. Without these details there is nothing anyone can do. Things like "The update failed! HELP!!!" are not helpful.

    Also, don't forget about user error. :)