[Bug 1175714] New: autoyast network interface node fails to parse
https://bugzilla.suse.com/show_bug.cgi?id=1175714 Bug ID: 1175714 Summary: autoyast network interface node fails to parse Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST Assignee: yast2-maintainers@suse.de Reporter: ohering@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- This used to work, but with current TW snapshot: ==> /proc/cmdline <== BOOT_IMAGE=(hd0,gpt1)/EFI/install/TMBLWEED/linux console=ttyS0,115200 i8042.noaux quiet sysrq_always_enabled panic=9 ignore_loglevel net.ifnames=0 linemode=1 vnc=1 vncpassword=password usessh=1 sshpassword=suse nosshkey net.ifnames=0 brokenmodules=floppy,edd autoyast2=hd:/EFI/install/TMBLWEED/autoyast.xml ifcfg=b4:96:91:67:e1:84=dhcp udev.rule=mac=b4:96:91:67:e1:84,name=uplink hostname=virt152 install=http://download.opensuse.org/history/20200823/tumbleweed/repo/oss ==> /var/log/YaST2/y2log <== 2020-08-25 05:15:15 <1> virt152(5571) [Ruby] transfer/file_from_url.rb:198 Copy profile: /bin/cp /download/autoinst.xml /tmp/YaST2-05571-OcyaYp/autoinst.xml 2020-08-25 05:15:15 <1> virt152(5571) [Ruby] modules/ProfileLocation.rb:168 Dir=/download/ 2020-08-25 05:15:15 <1> virt152(5571) [Ruby] modules/ProfileLocation.rb:169 Fetching Rules File 2020-08-25 05:15:15 <1> virt152(5571) [agent-system] SystemAgent.cc(Execute):1156 mkdir /tmp/YaST2-05571-OcyaYp/rules 2020-08-25 05:15:15 <1> virt152(5571) [Ruby] autoinstall/xml_validator.rb:62 Validating /tmp/YaST2-05571-OcyaYp/autoinst.xml against /usr/share/YaST2/schema/autoyast/rng/profile.rng... 2020-08-25 05:15:15 <3> virt152(5571) [Ruby] autoinstall/xml_validator.rb:68 XML validation errors: ["ERROR: Extra element networking in interleave", "47:0: ERROR: Element profile failed to validate content"] 2020-08-25 05:15:15 <1> virt152(5571) [qt-ui] YQApplication.cc(headingFont):377 Loaded 14 pixel bold font: Sans Serif,-1,14,5,75,0,0,0,0,0 2020-08-25 05:15:15 <1> virt152(5571) [ui] YPushButton.cc(setFunctionKey):202 Guessing button role YOKButton for YPushButton "Continue" at 0x7f1bf8360ad0 from function key F10 2020-08-25 05:15:15 <1> virt152(5571) [ui] YPushButton.cc(setFunctionKey):202 Guessing button role YCancelButton for YPushButton "Cancel" at 0x7f1bf8361400 from function key F9 2020-08-25 05:15:15 <1> virt152(5571) [ui] YCPDialogParser.cc(parseButtonBox):1171 Relaxed sanity check for YButtonBox at 0x7f1bf8360930 <networking> <dhcp_options> <dhclient_additional_options></dhclient_additional_options> <dhclient_client_id></dhclient_client_id> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain/> <hostname>virt152</hostname> </dns> <interfaces config:type="list"> <interface> <device>uplink</device> <startmode>auto</startmode> <bootproto>none</bootproto> </interface> <interface> <device>br0</device> <startmode>auto</startmode> <bootproto>dhcp</bootproto> <bridge>yes</bridge> <bridge_ports>uplink</bridge_ports> <bridge_forwarddelay>0</bridge_forwarddelay> <bridge_stp>off</bridge_stp> </interface> </interfaces> <net-udev config:type="list"> <rule> <name>uplink</name> <rule>ATTR{address}</rule> <value>b4:96:91:67:e1:84</value> </rule> </net-udev> <managed config:type="boolean">false</managed> </networking> -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c1 --- Comment #1 from Olaf Hering <ohering@suse.com> --- autoyast is also broken in other areas. Let me know when it is supposed to work again. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c2 Imobach Gonzalez Sosa <igonzalezsosa@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |igonzalezsosa@suse.com --- Comment #2 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- Hi Olaf, Recently, we added a feature to perform the profile validation at runtime. If you continue the autoinstallation, everything should work as it did before. Basically, the problem is that the profile does not validate at all. libxml2 error messages might be confusing, but jing usually does a better job. The real problem is: error: element "dhcp_resolv" not allowed here; expected the element end-tag or element "domain", "hostname", "nameservers", "resolv_conf_policy", "searchlist" or "write_hostname" At first sight, I would say that the "dhcp_resolv" is unknown to AutoYaST. Simply removing it should do the trick. On the other hand, if you are not happy with the runtime validation, you can disable it by setting specifying YAST_SKIP_XML_VALIDATION=1 as a kernel option. I hope it helps. Regards, Imo -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c3 --- Comment #3 from Olaf Hering <ohering@suse.com> --- Oh, thanks. I will check why 'dhcp_resolv' is used in my code. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c4 Olaf Hering <ohering@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from Olaf Hering <ohering@suse.com> --- It was known in SLE11, and seems to be valid for early SLE12. https://www.suse.com/de-de/support/kb/doc/?id=000018702 I will adjust my code. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c5 Olaf Hering <ohering@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #5 from Olaf Hering <ohering@suse.com> --- I fixed the autoyast.xml generator, a few extra elements are not added anymore. jing and xmllint find no errors: virt152:~ # xmllint --noout --relaxng /usr/share/YaST2/schema/autoyast/rng/profile.rng /boot/efi/EFI/install/TMBLWEED/autoyast.xml /boot/efi/EFI/install/TMBLWEED/autoyast.xml validates virt152:~ # jing /usr/share/YaST2/schema/autoyast/rng/profile.rng /boot/efi/EFI/install/TMBLWEED/autoyast.xml virt152:~ # But yast still finds errors: ["ERROR: Extra element scripts in interleave", "165:0: ERROR: Element profile failed to validate content"] Does yast use a third method for validation? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c6 David Diaz <dgonzalez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dgonzalez@suse.com, | |ohering@suse.com Flags| |needinfo?(ohering@suse.com) --- Comment #6 from David Diaz <dgonzalez@suse.com> --- Hi Olaf, Could you please attach the logs and AutoYaST profile? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 Olaf Hering <ohering@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ohering@suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c8 --- Comment #8 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- Hi all, It looks like AutoYaST is not complaining about the initial profile (which is OK). The real problem is that the profile gets modified at runtime (probably as a side effect of running one of those scripts). And that's the profile which is wrong. These are the errors: failed.xml:547:26: error: element "listentry" not allowed here; expected element "script" failed.xml:549:22: error: element "interpreter" not allowed here; expected the element end-tag or element "arbitrator", "authfile", "port", "site", "ticket" or "transport" failed.xml:550:17: error: element "source" not allowed here; expected the element end-tag or element "arbitrator", "authfile", "port", "site", "ticket" or "transport" failed.xml:599:26: error: element "listentry" not allowed here; expected element "script" failed.xml:601:22: error: element "interpreter" not allowed here; expected the element end-tag or element "arbitrator", "authfile", "port", "site", "ticket" or "transport" failed.xml:602:17: error: element "source" not allowed here; expected the element end-tag or element "arbitrator", "authfile", "port", "site", "ticket" or "transport" failed.xml:624:32: error: element "postpartitioning-scripts" incomplete; missing required element "script" Having said this, I would say that we need to improve the UX experience because it is pretty hard to find out the real problem. I will keep this bug report open anyway to discuss about it with the team. Regards, Imo -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c9 --- Comment #9 from Olaf Hering <ohering@suse.com> --- Which component modifies the profile? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c10 Imobach Gonzalez Sosa <igonzalezsosa@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |CONFIRMED Assignee|yast2-maintainers@suse.de |igonzalezsosa@suse.com --- Comment #10 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- Oh, I have found the problem. It looks like AutoYaST itself is producing a wrong profile when processing the given profile. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c14 Imobach Gonzalez Sosa <igonzalezsosa@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #14 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- I have fixed the problem (which was present since SLE 12 times). Now the postpartitioning-scripts section should be exported properly and the validation problem should not happen. * https://github.com/yast/yast-autoinstallation/pull/681 Fixed in SLE-12-SP5, SLE-15-GA, SLE-15-SP1, SLE-15-SP2 and master (TW and to be SLE-15-SP3). Obviously, in previous versions the problem was not that visible because the profile was not validated at runtime. However, using the AutoYaST UI to create the profile could produce an invalid one. Thanks for reporting! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c16 --- Comment #16 from Olaf Hering <ohering@suse.com> --- Is this supposed to be fixed in 20200902? Still the same error. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c18 Olaf Hering <ohering@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED --- Comment #18 from Olaf Hering <ohering@suse.com> --- (In reply to Olaf Hering from comment #16)
Is this supposed to be fixed in 20200902? Still the same error.
This appears to work with 20200906. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c22 --- Comment #22 from Swamp Workflow Management <swamp@suse.de> --- SUSE-RU-2020:2868-1: An update that has 5 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1110413,1145269,1172026,1175714,1175725 CVE References: JIRA References: Sources used: SUSE Linux Enterprise Module for Basesystem 15-SP1 (src): autoyast2-4.1.21-3.22.1 SUSE Linux Enterprise Installer 15-SP1 (src): autoyast2-4.1.21-3.22.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c23 --- Comment #23 from Swamp Workflow Management <swamp@suse.de> --- SUSE-RU-2020:2940-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1175624,1175714 CVE References: JIRA References: Sources used: SUSE Linux Enterprise Server Installer 12-SP5 (src): autoyast2-3.2.47-3.19.2 SUSE Linux Enterprise Server 12-SP5 (src): autoyast2-3.2.47-3.19.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c24 --- Comment #24 from Swamp Workflow Management <swamp@suse.de> --- SUSE-RU-2020:3079-1: An update that has three recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1172817,1175714,1175725 CVE References: JIRA References: Sources used: SUSE Linux Enterprise Module for Basesystem 15-SP2 (src): autoyast2-4.2.45-3.6.1 SUSE Linux Enterprise Installer 15-SP2 (src): autoyast2-4.2.45-3.6.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c25 --- Comment #25 from Swamp Workflow Management <swamp@suse.de> --- openSUSE-RU-2020:1807-1: An update that has 5 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1110413,1145269,1172026,1175714,1175725 CVE References: JIRA References: Sources used: openSUSE Leap 15.1 (src): autoyast2-4.1.21-lp151.2.18.1 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1175714 https://bugzilla.suse.com/show_bug.cgi?id=1175714#c26 --- Comment #26 from Swamp Workflow Management <swamp@suse.de> --- openSUSE-RU-2020:1815-1: An update that has three recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1172817,1175714,1175725 CVE References: JIRA References: Sources used: openSUSE Leap 15.2 (src): autoyast2-4.2.45-lp152.2.6.1 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com