Description of problem: The network bridge errors page in the RHEL 5 Virtualization guide has the following errors: In the script, the line case ${op} in Should be: case ${OP} in The lines that read: .. ,, Should actually be semi-colons: ;; Version-Release number of selected component (if applicable): http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Virtualization-en-US/ch-virt-bridge-errors.html How reproducible: N/A Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
reassigning to Brian Cleary Brian, once the changes are in cvs, please build on docbot (html) and reassign to mhideo for staging into docs page. thanks!
Don, I have corrected the error in the source. However, I cannot generate a new build of the Virt docs. Strange thing is I can do builds of other things but not Virt docs. I will notify Mike H Smith.
sounds like something jfearn can help us with. reassigning to him for inspection. adding mhideo to this bug as CC
Does it work on DocBot?
Very strange. I do a Docbot build, I recieve no errors. I go to the respective repository, and see if it built, and the html file remains unchanged, so DocBot is not getting the job done (and no errors reported in the log).
Section 19.6 needs updating too. The example shows one thing, but the ensuing text is talking about something else: "The sync_console can help determine a problem that causes hangs with asynchronous hypervisor console output, and the "pnpacpi=off" works around a problem that breaks input on the serial console. The parameters "console=ttyS0" and "console=tty" means that kernel errors get logged with on both the normal VGA console and on the serial console." Not shown in the example: 'sync_console', 'pnpacpi=off', "console=ttyS0". Looks like one part was changed and the other was not.
link to the log would be handy.
Here the link to the Docbot Virt log. Hope it comes up for you. https://engineering.redhat.com/docbot/logs/virtualizaiton.log
Build log looks fine to me, maybe you where caught up in the recent outage?
Asside from the missing image this looks fine to me.
closing this bug out as per previous comment
Why was this bug closed? I do not see the corrections I listed on the webpage.
reassigning to bcleary for processing
User bcleary's account has been closed
already corrected in link. closing as CLOSEDCURRENTRELEASE. (In reply to comment #12) > Why was this bug closed? I do not see the corrections I listed on the webpage.