The Firewall management seems to be broken on SLES12 SP4.
I had it happen on a new install
I just tested on a SP3 to SP4 online update, same results. (I confirmed it was working on SP3 prior to the upgrade).
When I go into YAST → Firewall… I receive the following error (Happens in GUI and text mode):
âError â
âInternal error. Please report a bug report with logs. â
âRun save_y2logs to get complete logs. â
âDetails: cannot load such file – network/firewall_chooser â
âCaller: /usr/lib64/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `requâ
[QUOTE=MARVHUFFAKER;56106]The Firewall management seems to be broken on SLES12 SP4.
I had it happen on a new install
I just tested on a SP3 to SP4 online update, same results. (I confirmed it was working on SP3 prior to the upgrade).
When I go into YAST → Firewall… I receive the following error (Happens in GUI and text mode):
âError â
âInternal error. Please report a bug report with logs. â
âRun save_y2logs to get complete logs. â
âDetails: cannot load such file – network/firewall_chooser â
âCaller: /usr/lib64/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `requâ
Is this a known bug?
Marvin[/QUOTE]
Dear Marvin,
I have exactly the same error. Indeed I have installed SUSE 12 SP4 on December the 28th of last year and then I could configure my firewall correctly.
But today after the last updates I can’t launch the firewall configuration nor from graphical interface, nor from console.
The verror is exactly the same:
"
âError â
âInternal error. Please report a bug report with logs. â
âRun save_y2logs to get complete logs. â
âDetails: cannot load such file – network/firewall_chooser â
âCaller: /usr/lib64/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `requâ
"
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
I’ve had an SR open since Jan 11th, I’ve requested the fix and
referenced the bug, and I have not received a single response from
anybody.[/color]
Hi Marvin,
You should treat this like any other SR you feel is not getting the
proper attention.
Contact Customer Support.
Give them the SR number.
Tell them you want the SR escalated.
Tell them you heard there is a fix available and that you need it, even
if it is only a Program Temporary Fix (PTF).
In the future, if you have an SR linked to a bug, you can ask the
engineer to CC you on the bug. That way you will be notified about the
status if a bug as it is being worked on.
Your engineer should also receive these status reports but may have
missed them.
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
An engineer finally contacted me today and let me know that the fix is available from the update channel. He did not offer any additional details.
"With this bug being fixed running “zypper patch” on the server would pull the bug fix in and allow for firewall management. "
I’m working on testing it now. There is an update to the yast-firewall module, I assume that’s where the problem is at.
An engineer finally contacted me today and let me know that the fix is
available from the update channel. He did not offer any additional
details.
-*
"With this bug being fixed running “zypper patch” on the server would
pull the bug fix in and allow for firewall management. "*-
I’m working on testing it now. There is an update to the yast-firewall
module, I assume that’s where the problem is at.[/color]
It’s good to know that the patch has already made its way into the
patch channel. We appreciate that update.
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
It’s good to know that the patch has already made its way into the
patch channel. We appreciate that update.[/color]
Whilst the bug number is different I’m guessing from the reference
to “firewall_chooser” that it might the more recent
yast2-firewall update released on 18 January 2019
https://download.suse.com/patch/finder/#bu=suse&
familyId=7261&productId=60328&dateRange=&startDa
te=&endDate=&priority=&architecture=&keywords=ya
st2-firewall&xf=7261&xp=7261_60328 (URL may not wrap).