Bug 604681

Summary: error message appear - error: unspecified error
Product: Red Hat Enterprise Linux 6 Reporter: Jan Ščotka <jscotka>
Component: netcfAssignee: Laine Stump <laine>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: low    
Version: 6.0   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-22 12:24:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 584893    

Description Jan Ščotka 2010-06-16 13:41:37 UTC
Description of problem:
was found problem of SElinux was discovered and repaired by new build of selinux
There appeared second problem. That necf doesn't work as expected
it shows
error: unspecified error
Is it big problem, or only smaller one (some of my mistake)
I expected some interactive console of netcf tool.
strace of command attached there:

How reproducible:

Steps to Reproduce:
1. ncftool
Actual results:
Failed to initialize netcf
error: unspecified error

Expected results:
interactive console of netcftool

Comment 2 RHEL Product and Program Management 2010-06-16 14:12:54 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 3 Laine Stump 2010-06-17 11:47:39 UTC
Can you post the contents of /etc/sysconfig/iptables? (is it 0 length? If so, is there an "iptables.old" file? What happens if you mv that file to /etc/sysconfig/iptables?)

Comment 5 Jan Ščotka 2010-06-18 06:57:53 UTC
or at least it should show some better error, than unspecified error.

Comment 6 Laine Stump 2010-06-22 12:24:11 UTC
Agreed. I will try to make the handling of a missing/0 length iptables file more graceful.

Since this is the same issue as Bug 582905, I'm marking it as a duplicate.

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