Bug 1155352

Summary:	Fedora 21 Beta: Roles do not report firewall status via rolectl
Product:	[Fedora] Fedora	Reporter:	Adam Williamson <awilliam>
Component:	rolekit	Assignee:	Stephen Gallagher <sgallagh>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	robatino, sgallagh, twoerner
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	x86_64
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-20 14:17:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Adam Williamson 2014-10-22 01:16:14 UTC

We wrote this into the F21 Beta criteria:

"Release-blocking roles must be able to report their status in regard to the system firewall as described in the technical specification."

AFAICS, this has not been implemented. 'rolectl settings (instance)' gives a read out of the role's *configuration*, but that doesn't seem to be the same thing as 'status'. The wording in the tech spec is this:

"Roles will be required to support the following API:  ...  A query interface providing metadata information about the role (not all roles must implement all parts of this, bold lines are mandatory):  ...  A list of the ports that the role operates on, as well as data about whether those ports are currently firewalled. "

rolectl currently tells you firewalld services, not ports, and AFAICS there's no rolekit interface that reports the current status of the ports.

Proposing as a Beta blocker, per the criterion.

Comment 1 Adam Williamson 2014-10-22 17:12:50 UTC

Un-proposing, as the Server WG voted to drop the criterion:

https://lists.fedoraproject.org/pipermail/server/2014-October/001520.html

this kind of futzing around with criteria is a bad idea, but possibly inevitable in the short term as we shake out the Product stuff. It needs to stop happening as things settle down, though.

Comment 2 Thomas Woerner 2014-11-13 16:58:29 UTC

Port numbers and also predefined services from firewalld can be used for the firewall settings in roles.

Comment 3 Fedora End Of Life 2015-11-04 14:53:44 UTC

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.

Comment 4 Adam Williamson 2015-11-04 20:24:41 UTC

AFAICS this still hasn't been implemented.

Comment 5 Fedora Admin XMLRPC Client 2016-03-17 14:43:04 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Stephen Gallagher 2016-07-20 14:17:15 UTC

rolekit upstream is currently in maintenance mode. No new feature work is expected for the immediate future.