Bug 1297161 - output of commands "firewall-cmd --permanent --list-all-zones" & firewall-cmd --list-all-zones are not consistent.
output of commands "firewall-cmd --permanent --list-all-zones" & firewall-cmd...
Status: CLOSED DUPLICATE of bug 1398887
Product: Fedora
Classification: Fedora
Component: firewalld (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Thomas Woerner
Fedora Extras Quality Assurance
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2016-01-09 19:41 EST by John Dodson
Modified: 2016-12-29 03:16 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-29 03:16:04 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John Dodson 2016-01-09 19:41:04 EST
Description of problem:

The output of the commands:

        firewall-cmd --permanent --list-all-zones
        firewall-cmd --list-all-zones

are not consistent, each lists the entry

        ports: 1025-65535/udp 1025-65535/tcp
        ports: 1025-65535/tcp 1025-65535/udp
Note that udp/tcp are inverted on the line for each invocation.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. firewall-cmd --permanent --list-all-zones >fdp.txt
2. firewall-cmd --list-all-zones >fdr.txt
3. diff fdp.txt fdr.txt

Actual results:

<   ports: 1025-65535/udp 1025-65535/tcp
>   ports: 1025-65535/tcp 1025-65535/udp

Expected results:

No output except the insignificant differences.

Additional info:

The above makes it hard to check automatically if the running & permanant configs are different in any subtle way.
Comment 1 Fedora End Of Life 2016-11-24 09:49:04 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.
Comment 2 Fedora End Of Life 2016-12-20 12:44:43 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 3 John Dodson 2016-12-29 03:14:04 EST
Same problem exists in

Comment 4 John Dodson 2016-12-29 03:15:24 EST
duplicate of Bug 1398887
Comment 5 John Dodson 2016-12-29 03:16:04 EST

*** This bug has been marked as a duplicate of bug 1398887 ***

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