Bug 769473 - sample config file from tutorial contains errors.
Summary: sample config file from tutorial contains errors.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: cfengine
Version: 15
Hardware: noarch
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Jeff Sheltren
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-20 23:25 UTC by Mark Lamourine
Modified: 2012-08-07 20:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 20:22:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mark Lamourine 2011-12-20 23:25:18 UTC
Description of problem:

This file contains a sample configuration and instructions to run cf-promise.
The version presented has errors and does not behave as the documentation indicates.

Mark Burgess provided an updated text for the sample file in a bug report:


/usr/share/doc/cfengine-doc-3.0.5p1/cf3.html

cfengine bug report:
  http://www.mail-archive.com/bug-cfengine@cfengine.org/msg00685.html

Updated file content:
  http://www.mail-archive.com/bug-cfengine@cfengine.org/msg00688.html

Version-Release number of selected component (if applicable):
  cfengine-doc-3.0.5p1-2.fc15.noarch

How reproducible:
Copy the sample text from /usr/share/doc/cfengine-doc-3.0.5p1/cf3.html to
a file and run cf-promise to parse it.

Steps to Reproduce:
1. Extract the test file:

sed '1,/<pre>/ d;/<\/pre>/,$d' /usr/share/doc/cfengine-doc-3.0.5p1/cf3.html > /tmp/test.cf

2. limit write to the user.

chmod 644 /tmp/test/cf

3. check the test file

cf-promises -f /tmp/test.cf

  
Actual results:
cf3:/tmp/test.cf:57,27: Constraint lvalue on_change is not allowed in 'classes' constraint body, near token '}'
cf3:/tmp/test.cf:58,28: Constraint lvalue on_failure is not allowed in 'classes' constraint body, near token '}'
Summarizing promises as text to /tmp/test.cf.txt
Summarizing promises as html to /tmp/test.cf.html


Expected results:

no output

or with 

$ cf-promises -v -f /tmp/test.cf | tail -1
cf3  -> Inputs are valid



Additional info:

I'm not sure if this is also still broken in the files provided by cfengine themselves.

Comment 1 Fedora Update System 2012-04-25 18:17:21 UTC
cfengine-3.3.0-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/cfengine-3.3.0-1.fc17

Comment 2 Fedora Update System 2012-05-04 23:06:46 UTC
cfengine-3.3.0-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 3 Fedora End Of Life 2012-08-07 20:22:29 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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