Bug 1121527
Summary: | augeas aug lens bug for /etc/services currently doesn't handle colon in service_name | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Dominic Cleal <dcleal> |
Component: | augeas | Assignee: | Dominic Cleal <dcleal> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | ayadav, cww, dsulliva, lkong, virt-bugs |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | augeas-1.1.0-13.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1121263 | Environment: | |
Last Closed: | 2015-03-05 09:25:36 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: | |||
Bug Depends On: | 1121263 | ||
Bug Blocks: | 1064025 |
Description
Dominic Cleal
2014-07-21 07:20:43 UTC
Can reproduce with augeas-1.1.0-12.el7: Steps to reproduce: 1. Add the following line to /etc/services SWRPC.ACCESS.BSS:BS_rmq 48102/tcp # SWIFTAlliance_SWRPC ACCESS (the new line is11177 ) 2. # augtool print /augeas//error /augeas/files/etc/services/error = "parse_failed" /augeas/files/etc/services/error/pos = "670293" /augeas/files/etc/services/error/line = "11177" /augeas/files/etc/services/error/char = "0" /augeas/files/etc/services/error/lens = "/usr/share/augeas/lenses/dist/services.aug:87.10-.39:" /augeas/files/etc/services/error/message = "Iterated lens matched less than it should" Verify with augeas-1.1.0-13.el7 Steps to verify: 1. Add the following line to /etc/services SWRPC.ACCESS.BSS:BS_rmq 48102/tcp # SWIFTAlliance_SWRPC ACCESS 2. # augtool print /augeas//error no errors like: /augeas/files/etc/services/error = "parse_failed" Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0399.html |