When in a network there's the dns_resolver_configuration sub element the
current network is not parsed correctly and the following networks will
not be correctly collected
I have added a couple of tests to the #206.
What I have seen is that starting to parse the dns_resolver_configuration the parser finds the name_servers and after that it misses the closing xml element for the dns_resolver_configuration trying to parse all the following elements (like mtu and others) from a wrong level of nesting.
The effect is that for the current network all parameters after the dns_resolver_configuration are not correctly added and the following networks are not collected.
I think it's a problem in the readers generator (am I wrong?) but right now I don't clearly see a way to fix it.
Can someone give me some hints to help me in fixing it?
Thanks
The problem
When in a network there's the dns_resolver_configuration sub element the current network is not parsed correctly and the following networks will not be correctly collected
I have added a couple of tests to the #206.
What I have seen is that starting to parse the dns_resolver_configuration the parser finds the name_servers and after that it misses the closing xml element for the dns_resolver_configuration trying to parse all the following elements (like mtu and others) from a wrong level of nesting.
The effect is that for the current network all parameters after the dns_resolver_configuration are not correctly added and the following networks are not collected.
This is related to a problem reported in BZ https://bugzilla.redhat.com/show_bug.cgi?id=1841556
I think it's a problem in the readers generator (am I wrong?) but right now I don't clearly see a way to fix it. Can someone give me some hints to help me in fixing it? Thanks