Bug 1535236

Summary:	ser2net-2.9.1-6 doesn't open tcp ports on CentOS 7.4
Product:	[Fedora] Fedora EPEL	Reporter:	Ben B <mysticknight487>
Component:	ser2net	Assignee:	Tom "spot" Callaway <tcallawa>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	mr.marcelo.barbosa, tcallawa
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ser2net-3.5-1.el7 ser2net-3.5-1.fc27	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-27 20:38:54 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 Ben B 2018-01-16 22:09:50 UTC

Description of problem: ser2net-2.9.1-6 doesn't open tcp port on CentOS 7.4


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


How reproducible: very


Steps to Reproduce:
1. add user to dialout group and relogin
2. yum install ser2net
3. ser2net -C "0.0.0.0:10100:raw:0:ttyS0:9600 NONE 1STOPBIT 8DATABITS -XONXOFF -RTSCTS"
3. netstat -vatn
4. No port 10100 open

Actual results: netstat doesn't report port 10100 as open


Expected results: netstat shows tcp port 0.0.0.0:10100 as open


Additional info: Installed 2.9.1 from source and had the same problem, but version 3.5 from source works.

Comment 1 Fedora Update System 2018-01-18 20:25:19 UTC

ser2net-3.5-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-ab190168b9

Comment 2 Fedora Update System 2018-01-18 20:25:26 UTC

ser2net-3.5-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-166b733bc0

Comment 3 Fedora Update System 2018-01-19 16:34:54 UTC

ser2net-3.5-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-ab190168b9

Comment 4 Ben B 2018-01-19 16:40:43 UTC

I tested the ser2net-3.5-1 rpm from the epel-testing-candidate/epel-testing-pending https://koji.fedoraproject.org/koji/buildinfo?buildID=1018568. It worked successfully on my system, both from cmdline with -C and through systemd.

I did notice the /etc/ser2net.conf had many uncommented examples left in it, should that be cleaned up?

Comment 5 Fedora Update System 2018-01-19 18:47:37 UTC

ser2net-3.5-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-166b733bc0

Comment 6 Ben B 2018-02-08 02:30:36 UTC

Can the updated rpm move from testing to stable?

Comment 7 Ben B 2018-02-26 15:02:56 UTC

Wondering if the rpm can be moved from testing to stable? It has +1 karma and doesn't seem to have any testers other than me.

v/r,
Ben

Comment 8 Fedora Update System 2018-02-27 20:38:54 UTC

ser2net-3.5-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2018-03-22 16:59:31 UTC

ser2net-3.5-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.