Bug 1031053 - XML error: bridge stp should be on or off got yes
Summary: XML error: bridge stp should be on or off got yes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: netcf
Version: 19
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Laine Stump
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-15 14:32 UTC by Martin Wilck
Modified: 2014-05-16 10:05 UTC (History)
12 users (show)

Fixed In Version: netcf-0.2.3-5.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1060076 (view as bug list)
Environment:
Last Closed: 2014-05-16 10:05:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
proposed patch (1.08 KB, patch)
2013-11-15 14:41 UTC, Martin Wilck
no flags Details | Diff
[PATCH] redhat-put.xsl: transform STP value to "on/off" (1.54 KB, patch)
2013-11-18 08:48 UTC, Martin Wilck
no flags Details | Diff

Description Martin Wilck 2013-11-15 14:32:47 UTC
Description of problem:
The above error message is displayed after configuring a bridge interface with NetworkManager

Version-Release number of selected component (if applicable):
libvirt-1.0.5.6-3.fc19.x86_64
netcf-libs-0.2.3-4.fc19.x86_64
NetworkManager-0.9.8.8-1.fc19.x86_64

How reproducible:
always

Steps to Reproduce:
1. create bridge configuration with NetworkManager
2. run virt-manager and open "Network Interfaces" tab in localhost connection details, or run virt-install

Actual results:
"XML error: bridge stp shold be on or off got yes"

Expected results:
No error message

Additional info:
NM puts "yes" or "no" in the ifcfg file depending on the user STP setting:

# grep STP /etc/sysconfig/network-scripts/ifcfg-br0
STP=no

the brctl tool accepts both "on"/"off" and "yes"/"no". But libvirt handles only "on" and "off".

Comment 1 Martin Wilck 2013-11-15 14:41:36 UTC
Created attachment 824571 [details]
proposed patch

Comment 2 Martin Wilck 2013-11-15 14:43:36 UTC
Confirmed - the patch from comment #1 solves this problem.

Comment 3 Eric Blake 2013-11-15 15:06:29 UTC
Can you please post this patch upstream to libvir-list?  It will get reviewed faster, and it is easier for upstream to apply patches that go through the list than patches that require firing up a web browser.

Comment 4 Martin Wilck 2013-11-15 17:45:33 UTC
I sent the mail in the hope the list does't require subscription.

Comment 5 Eric Blake 2013-11-15 20:43:50 UTC
(In reply to Martin Wilck from comment #4)
> I sent the mail in the hope the list does't require subscription.

Thanks; it came through just fine:
https://www.redhat.com/archives/libvir-list/2013-November/msg00581.html

List policy is to reply-all, so that you need not subscribe.  Hopefully you get a response soon.

Comment 6 Cole Robinson 2013-11-17 23:01:06 UTC
As Dan mentioned in reply to that message, at its root this sounds like a netcf issue, reassigning.

Comment 7 Martin Wilck 2013-11-18 08:43:32 UTC
Comment from Mailing list:

"The XML schema does not care what values the brctl tool
exposes. It standardizes on on & off for values. Whatever
tool is creating this XML (netcf I guess) should translate
from the values brctl uses to what the XML requires."

Comment 8 Martin Wilck 2013-11-18 08:48:11 UTC
Created attachment 825430 [details]
[PATCH] redhat-put.xsl: transform STP value to "on/off"

Another proposed patch, for netcf this time.

(wrt Daniel's comment, I haven't seen a schema file that would specify the netcf output in that detail. However I really don't care if the fix is applied in netcf or libvirt. I want this to get fixed either way).

Comment 9 Martin Wilck 2013-11-18 08:51:07 UTC
> (wrt Daniel's comment, I haven't seen a schema file that would specify the
> netcf output in that detail. 

Found it now. It's in interface.rng:

          <attribute name="stp">
            <ref name="on-or-off"/>
          </attribute>

Comment 10 Laine Stump 2013-11-18 09:18:58 UTC
(In reply to Martin Wilck from comment #8)
> Created attachment 825430 [details]
> [PATCH] redhat-put.xsl: transform STP value to "on/off"
> 
> Another proposed patch, for netcf this time.


Thanks for taking the time to make these patches. Sorry to keep doing this to you, but if you could send this netcf patch to

   netcf-devel.org

I can more easily push it into git with proper attribution to you. (you should be able to post without subscribing - it will just queue up the mail to wait for an admin (me) to clear it.

Comment 11 Martin Wilck 2013-11-18 09:23:16 UTC
Sent the email.
Subject: [PATCH] redhat-put.xsl: transform STP value to "on/off"

Comment 12 Martin Wilck 2013-11-18 09:24:15 UTC
Hmm, I got this:

You are not allowed to post to this mailing list, and your message has
been automatically rejected.  If you think that your messages are
being rejected in error, contact the mailing list owner at
netcf-devel-owner.org.

Comment 13 Laine Stump 2013-11-18 11:10:04 UTC
(In reply to Martin Wilck from comment #12)
> You are not allowed to post to this mailing list, and your message has
> been automatically rejected.

Oops. I had thought the netcf mailing list was configured similarly to libvir-list. I just changed it to hold-for-moderation messages from non-subscribers rahter than deleting them. Can you make one more try to that address? If that doesn't work, just email the patch to my email directly, and I'll forward it on to the list. (BTW, I'm assuming that you're making the patch with git send-email.)

Comment 14 Laine Stump 2014-01-31 11:51:44 UTC
This has been fixed upstream. Do you need a fix in F19? F20?

commit 048d13afcc91f4a16a80012aa34b9a024d95368e
Author: Martin Wilck <martin.wilck.com>
Date:   Mon Nov 18 12:35:15 2013 +0100

    transform STP value from "yes/no" to "on/off" in redhat-put.xsl
    
    Some tools (e.g. NetworkManager) use "yes"/"no" in config files
    rather than "on/off". netcf needs to transform this in order to conform
    with the schema.

Comment 15 Martin Wilck 2014-01-31 12:04:19 UTC
I'm still using F19, but I could live with the fix being in F20 is the first place.

RHEL7 might also be considered I guess.

Comment 16 Fedora Update System 2014-05-03 20:34:37 UTC
netcf-0.2.3-5.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/netcf-0.2.3-5.fc19

Comment 17 Fedora Update System 2014-05-06 03:35:07 UTC
Package netcf-0.2.3-5.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing netcf-0.2.3-5.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-6011/netcf-0.2.3-5.fc19
then log in and leave karma (feedback).

Comment 18 Fedora Update System 2014-05-16 10:05:58 UTC
netcf-0.2.3-5.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


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