Kernel panic after upgrade

[psycmos]

The link to the snapshot is not working. The host pkg.opnsense.org is unreachable.

Hi bimmerdriver.
You can download it from:
https://opnsense.c0urier.net/FreeBSD%3A11%3Aamd64/snapshots/

Somebody can help me?

I'm using unraid with NIC Intel 82575EB.
Version 18.7 intel NIC works well, but version OPNsense-201903080927-OpenSSL-dvd-amd64.iso.bz2 not recognize my intel. So There any any way to get it working on 19.1?

Thanks for this topic
Best Regards, Nuno

[bimmerdriver]

The website is back up so I downloaded the iso. I installed it on windows server hyper-v 2012R2 using a generation 2 vm. It booted properly. Now, I'm back to the problem where the installer hangs at the point of selecting a guided installation or other installation. I interrupted it with <CTRL-C>, logged in again as installer and this time it proceeded to install. I did not complete the installation, but I think this confirms the fix on hyper-v 2012R2.

[bimmerdriver]

I totally agree on that. But I still feel some of the devs could be more professional in their communication as well.

If I've made a mistake in my community interactions, please let me know. I'd like to learn from the experience in order to serve the community better. Life is a journey, mistakes are made, and hopefully learned from.

You've made no mistakes, neither has Franco.. Keep up the good work.

Agreed. Keep up the great work.

[TheGrandWazoo]

Good, thank you for testing this so quickly. The core team discussed this internally and we have an accelerated plan of action for 19.1.4 next week:

1. Release the bad commit revert in a new kernel to restore the previous behaviour for everyone.
2. Change the upgrade paths to the new 19.1.4 for the 18.7 major upgrades one or two days after the 19.1.4 release.
3. Release new images based on 19.1.4 in the following week.
4. Rework the bad patch further to make it work for everyone and release it in a subsequent 19.1.x update together with the Netmap rework. This will require new test image runs with user participation. The time frame for this is very roughly April/May.

All further confirmations or new problem reports arising from the test image are welcome.

I hope this episode shows that we don't always get it 100% right but with a reasonable amount of patience and a level head we can move past almost anything together.


Cheers,
Franco

You tell me where the ISO's are or what to use to update for testing and I will test them on my VM's...well the best I can. I am using Proxmox VE 5.3 which is KVM/QEMU based on Debian distro with modified Ubunta LTS kernel. Also running ZFS over iSCSI to FreeNAS if you need something tested there.

I have two VM's in a HA configuration...one with UEFI and the other is BIOS with LibrsSSL, IPS and VIRTIO enabled.

I have two other VM's waiting to install from ISO with UEFI and BIOS.

-WAZ

[franco]

19.1.4 will be out tomorrow... can publish a test image the day after. Official images next week...


Cheers,
Franco

[JDtheHutt]

I had this issue too and it did cause breakage at home. Sure, I'd rather it hadn't happened, but I get this stuff for free and it's generally solid work, so I am appreciative of all the effort made by the Devs. I am consistently amused, puzzled, and annoyed by those who keep ranting on about how their essential production business system has been affected. I'm no expert, but I'm pretty sure that if I were running something like that I would a) not just mash the upgrade button the second a release is out b) not do it without testing on a standalone box first c) not do it without backups with a restore strategy I can revert to d) maybe consider paying for the proper support levels if I'm profiting from this and need the help urgently. But as I said, I'm no expert, maybe throwing my expensive business kit into the fire with no plan is how people roll these days.

[TheGrandWazoo]

19.1.4 will be out tomorrow... can publish a test image the day after. Official images next week...


Cheers,
Franco

Upgraded to 19.1.4 on a BIOS and UEFI firmware boot without issues.

Great job and thanks again, OPNsense Team.

-Waz

[buddwm]

Upgraded to 19.1.4 and can confirm all is well.  Great job on getting this out so quickly.

[bimmerdriver]

I upgraded also on a windows server 2012r2 hyper-v with a generation 2 (uefi) vm. No problems.

[newsense]

I upgraded also on a windows server 2012r2 hyper-v with a generation 2 (uefi) vm. No problems.

Quickly...it was not. Such a catastrophic bug should have been caught way early in testing and never make it to GA, let alone 4 releases later over many weeks. While I may be lacking all the information, it was a combination of multiple factors that led to 19.1 being shipped with it.

In the aftermath of this bug being fixed as a community effort, the most troublesome fact remains for the casual and perhaps not 100% informed viewer that the core team behind OPNsense didn't seem have the business' support it needed when it was high time for it - leaving the devs scrambling to find proper hardware to further troubleshoot and test regressions.


Here's hope lessons learned will be taken into consideration and the core team has the adequate support going forward -- as I don't see a future where the success of this entire project is ensured by testing it (mainly) of a handful of 'branded' appliances.

[jschellevis]

@newsense, as said by others before an open source project is a community effort. This means that if you want to catch issues before a release it relies fully on your input and that of others.

The core team cannot test on any exotic piece of hardware, you will have to do that work yourself.

There are a lot of people participating in testing and running the development version long before it's release, they are reporting issues and help getting them fixed.

We are grateful for everyone putting in the work required to make this project as great as it is.

For those looking for professional support, just buy support from us.. we'll help you regardless of your hardware choice, but keep in mind that bug fixing is time consuming work.

[golebole]

Hi,

Thanks for the good news. I saw yesterday the update and clicked update. I think I still get an older version, right? I had the same issue with the fatal error again. When do you think can I use the official update function?

Best regards
Christian

[franco]

@newsense please don't start gaslighting after the fact.

I came here to announce that upgrades from 18.7 now land in 19.1.4 directly, but your comment takes all achievement away from everyone who contributed to the solution and the extra hours put in to make it happen on a tight schedule. It seems rather petty to me.

The discussion is already utterly absurd due to freaking out over indications that particular technical issues may never be fixed (can you fix all your problems in your real life, at work, for the planet?) and a general lack of understanding that 2-Clause BSD comes with no warranty or liability as others have pointed out.

The new 11.2 base has publicly called for testing since October 2018. If the community can't find a bug that we can't find we have to assume that it's not a big deal contrary to your "catastrophic" assessment.

If people could get their facts straight before going into a discussion about how much one can coerce a project to do what one wants that does indeed already do *a lot* to move forward that would be great.


Thank you,
Franco

[bitwolf]

@franco can you please confirm what the direct upgrade from 18.7.10 to 19.1.4 you mentioned should look like in the UI?

I just tried to kick it off on a firewall I had kept back on 18.7, and while 19.1.4 is indeed shown as available, it displays the release notes for the initial 19.1, not 19.1.4 (screenshot attached).

Is this the expected behaviour?

[lattera]

I kinda wonder if it'd be best to show all changelogs from 19.1 to 19.1.4.