SLES 12 SP4 - Can't manage firewall due to error

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

Comments

  • 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


    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│
    "

    Could somebody help us, please?
  • KEVINKEVIN Knowledge Partner
    soportei3s wrote:

    > Could somebody help us, please?


    This is a known issue: Bug 1121849
    https://bugzilla.suse.com/show_bug.cgi?id=1121849

    It is high priority and being worked on.

    I have no other details at the moment.

    --
    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.
  • KEVINKEVIN Knowledge Partner
    KBOYLE wrote: »
    This is a known issue: Bug 1121849
    https://bugzilla.suse.com/show_bug.cgi?id=1121849

    This issue has been resolved.

    To obtain a fix, open an SR and refer to Bug 1121849.
  • ttrcfttrcf Established Member
    KBOYLE wrote: »
    This issue has been resolved.

    To obtain a fix, open an SR and refer to Bug 1121849.

    Can you give some details on how to do this?

    Will this be fixed by an update?

    Thanks
  • KEVINKEVIN Knowledge Partner
    ttrcf wrote:

    > > To obtain a fix, open an SR and refer to Bug 1121849.

    >
    > Can you give some details on how to do this?


    How to Access and Use SUSE Technical Support
    https://www.suse.com/support/handbook/

    Open an Incident
    https://www.suse.com/support/handbook/#open


    > Will this be fixed by an update?


    Very likely but the question is: When?

    You can check for patches here:
    Patch Finder
    https://download.novell.com/patch/finder/

    These are the patches currently available for SLES 12 SP4.
    https://download.novell.com/patch/finder/#bu=novell&bu=netiq&bu=suse&familyId=7261&productId=60328&dateRange=&startDate=&endDate=&priority=&architecture=&keywords=&xf=7261&xp=7261_60328

    --
    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.
  • MarvinMarvin New or Quiet Member
    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.
  • KEVINKEVIN Knowledge Partner
    MARVHUFFAKER wrote:

    >
    > 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.


    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.
  • MarvinMarvin New or Quiet Member
    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.
  • KEVINKEVIN Knowledge Partner
    MARVHUFFAKER wrote:

    >
    > 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.


    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.
  • smfloodsmflood Knowledge Partner
    "Kevin Boyle" Wrote in message:

    > It's good to know that the patch has already made its way into the
    > patch channel. We appreciate that update.


    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).

    HTH.
    --
    Simon Flood
    SUSE Knowledge Partner


    ----Android NewsGroup Reader----
    http://usenet.sinaapp.com/
Sign In or Register to comment.