Bug 1408365 - Starting firewalld gives warning when cockpit is not installed
Summary: Starting firewalld gives warning when cockpit is not installed
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: firewalld
Version: 25
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Eric Garver
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-23 05:26 UTC by Christopher Archer
Modified: 2017-12-12 10:26 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1171114
Environment:
Last Closed: 2017-12-12 10:26:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Christopher Archer 2016-12-23 05:26:47 UTC
+++ This bug was initially created as a clone of Bug #1171114 +++

Description of problem:
During the startup of firewalld a warning is logged when the cockpit package is not installed.

Version-Release number of selected component (if applicable):
firewalld-0.3.13-1.fc21.noarch
firewalld-config-workstation-0.3.13-1.fc21.noarch
firewalld-filesystem-0.3.13-1.fc21.noarch

How reproducible:
always

Steps to Reproduce:
1. Install Fedora 21 workstation
2. Boot system
3.

Actual results:
The following line is written to /var/log/firewalld when firewalld starts:
WARNING: FedoraServer: INVALID_SERVICE: cockpit

Expected results:
No warning

Additional info:
The cockpit service is referenced in file /usr/lib/firewalld/zones/FedoraServer.xml, which is part of the firewalld rpm. However the cockpit service is defined in /usr/lib/firewalld/services/cockpit.xml, which is part of the cockpit rpm. Perhaps the zone defined in FedoraServer.xml should only be installed on Fedora Server and not on Fedora Workstation?

--- Additional comment from Christian Stadelmann on 2015-03-25 07:22:31 EDT ---

I can confirm this issue on F22 alpha.

--- Additional comment from Michael on 2015-03-30 06:52:52 EDT ---

I can confirm this issue on (my) F21

--- Additional comment from valtestad on 2015-04-20 06:48:56 EDT ---

confirmed on my F21 installation as well.

--- Additional comment from crf on 2015-06-12 18:58:56 EDT ---

This affects my Fedora 22.

--- Additional comment from Derek Atkins on 2015-09-11 20:39:24 EDT ---

I'm seeing this on Fedora-22 ARM

--- Additional comment from Fedora End Of Life on 2015-11-04 05:33:27 EST ---

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

--- Additional comment from Christian Stadelmann on 2015-11-04 05:35:20 EST ---

Still present on F23. Please change the product version.

--- Additional comment from Zirui Zhuang on 2015-12-31 04:28:20 EST ---

Still present on 23

It was discovered as the boot time of firewalld is strangely long, and after digging the log of firewalld, we have:

WARNING: FedoraServer: INVALID_SERVICE: cockpit

and the cockpit is not installed at all.

--- Additional comment from Alex Regan on 2016-01-17 10:11:07 EST ---

It appears that even though --list-services shows it's not there, it actually is. Use --remove-service=cockpit appears to fix it.

# firewall-cmd --list-services --zone=FedoraServer
dhcpv6-client ssh

# firewall-cmd --zone=FedoraServer --add-service=cockpit
Warning: ALREADY_ENABLED: cockpit

# firewall-cmd --zone=FedoraServer --remove-service=cockpit
success

--- Additional comment from aurelien on 2016-03-13 04:18:35 EDT ---

--remove-service does not fit and send back another error

aurelien@bigfoot:/var/log$ sudo firewall-cmd --zone=FedoraWorkstation --remove-service=cockpit
Error: INVALID_SERVICE: cockpit
aurelien@bigfoot:/var/log$ sudo firewall-cmd --complete-reload
success
aurelien@bigfoot:/var/log$ sudo firewall-cmd --zone=FedoraWorkstation --remove-service=cockpit
Error: INVALID_SERVICE: cockpit
aurelien@bigfoot:/var/log$ sudo firewall-cmd --complete-reload
success
aurelien@bigfoot:/var/log$ uname -a
Linux bigfoot 4.4.4-301.fc23.x86_64 #1 SMP Fri Mar 4 17:42:42 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

--- Additional comment from aurelien on 2016-03-13 05:00:07 EDT ---

Same as root
# firewall-cmd --zone=FedoraWorkstation --remove-service=cockpit
Error: INVALID_SERVICE: cockpit

--- Additional comment from Steve Bryant on 2016-04-17 07:48:06 EDT ---

firewalld-0.4.0-2.fc23.noarch provides file /usr/lib/firewalld/zones/FedoraServer.xml which contains the following service name definition:

    <service name="cockpit"/>

However the file /usr/lib/firewalld/services/cockpit.xml does not exist, so every firewall startup produces the error:

    "WARNING: FedoraServer: INVALID_SERVICE: cockpit"

WORKAROUND
----------
Create a file /usr/lib/firewalld/services/cockpit.xml containing the following (as extracted from cockpit-ws-0.96-1.fc23.x86_64.rpm):

<?xml version="1.0" encoding="utf-8"?>
<service>
  <!-- This is a firewalld service definition for Cockpit -->
  <short>Cockpit</short>
  <description>Cockpit lets you access and configure your server remotely.</description>
  <port protocol="tcp" port="9090"/>
</service>

Service "cockpit" is then also listed in the "Firewall Configuration" (firewall-config) application.

--- Additional comment from David Tonhofer on 2016-07-31 03:44:37 EDT ---

Observing this in Fedora 24 Workstation.

firewalld-0.4.3.2-1.fc24.noarch

Please increase OS version.

--- Additional comment from Christian Stadelmann on 2016-09-28 18:38:39 EDT ---

(In reply to David Tonhofer from comment #13)
> Observing this in Fedora 24 Workstation.
> 
> firewalld-0.4.3.2-1.fc24.noarch
> 
> Please increase OS version.

Still present on F25.

--- Additional comment from Fedora End Of Life on 2016-11-24 06:19:24 EST ---

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

--- Additional comment from Christian Stadelmann on 2016-11-24 12:35:03 EST ---

Please change version number to 25.

Comment 1 Christopher Archer 2016-12-23 05:28:30 UTC
Cloned for Fedora 25 - confirmed this bug still exists in that version.

Comment 2 Christopher Archer 2017-09-19 18:51:04 UTC
No longer seeing this problem since upgrade to Fedora 26

Comment 3 Christian Stadelmann 2017-09-19 18:55:02 UTC
(In reply to Christopher Archer from comment #2)
> No longer seeing this problem since upgrade to Fedora 26

I still do.

Comment 4 Christian Stadelmann 2017-10-25 20:58:51 UTC
Please close in favor of the original bug #1171114.

Comment 5 Fedora End Of Life 2017-11-16 18:57:00 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2017-12-12 10:26:57 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.