[Bug 1013047] New: Autoyast profile does not validate
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Bug ID: 1013047 Summary: Autoyast profile does not validate Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST Assignee: autoyast-maintainers@suse.de Reporter: mkravec@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 704429 --> http://bugzilla.suse.com/attachment.cgi?id=704429&action=edit autoinst.xml Generated profile fails to validate with: xmllint: - Element profile has extra content: add-on jing: - element "copy_on_write" not allowed here; expected the element end-tag or text - element "path" not allowed here; expected the element end-tag or text OpenQA link: http://dhcp91.suse.cz/tests/3181#step/yast2_clone_system/7 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Martin Kravec <mkravec@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |igonzalezsosa@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Imobach Gonzalez Sosa <igonzalezsosa@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|autoyast-maintainers@suse.d |igonzalezsosa@suse.com |e | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Michel Normand <normand@linux.vnet.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |normand@linux.vnet.ibm.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c4 --- Comment #4 from Stephan Kulow <coolo@suse.com> --- perhaps this is better tracked as SP3 bug - to actually get attention -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c5 Oliver Kurz <okurz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |okurz@suse.com Severity|Normal |Major --- Comment #5 from Oliver Kurz <okurz@suse.com> --- (In reply to Stephan Kulow from comment #4)
perhaps this is better tracked as SP3 bug - to actually get attention
yes, good idea. I can write a script to clone every openSUSE bug to SLE tomorrow ;-) Honestly, I don't consider cloning bugs with no further information just to raise attention is not a sustainable workflow. Leap bug reports by default in components like "basesystem" or "kernel" should also be tracked for SLE and also Tumbleweed should be crosschecked for issues which have been "backported" already or do apply nevertheless. recent example on openSUSE Leap 42.3: https://openqa.opensuse.org/tests/379388#step/yast2_clone_system/13 recent example on SUSE Linux Enterprise Server 12 SP3 build 0313: https://openqa.suse.de/tests/855580#step/yast2_clone_system/13 At least with the previously auto-generated comments the bug can be found with queries like https://bugzilla.suse.com/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=REOPENED&bug_status=RESOLVED&chfieldfrom=3w&chfieldto=Now&f1=longdesc&f2=bug_status&known_name=open%2Bosd_referenced%2Bchange-3w&list_id=6202124&o1=regexp&o2=notsubstring&query_based_on=open%2Bosd_referenced%2Bchange-3w&query_format=advanced&v1=This%20bug%20is%20still%20referenced%20in%20a%20failing%20openQA%20test.%2Aopenqa.suse.de already -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c6 --- Comment #6 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- A PR is under review: https://github.com/yast/yast-autoinstallation/pull/296 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c7 Imobach Gonzalez Sosa <igonzalezsosa@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS --- Comment #7 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- * SR for CaaSP: https://build.suse.de/request/show/130457 * SR for SLE 12 SP3: https://build.suse.de/request/show/130456 * SR for Factory: http://build.opensuse.org/request/show/486121 Let's keep the bug open until yast2-schema gets rebuilt and the problem goes away. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c8 Imobach Gonzalez Sosa <igonzalezsosa@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #8 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- This bug was already fixed and, according to openQA is working again: https://openqa.suse.de/tests/996126. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c9 Oliver Kurz <okurz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED --- Comment #9 from Oliver Kurz <okurz@suse.com> --- verified working in build 0319 and later: https://openqa.suse.de/tests/867580 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c10 Michel Normand <normand@linux.vnet.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |okurth@vmware.com Flags| |needinfo?(okurth@vmware.com | |) --- Comment #10 from Michel Normand <normand@linux.vnet.ibm.com> --- While this bug is supposed to be solved as per previous comment, there is still an openQA test flagged with its reference with last TW snapshot 20170629 ppc64le (1) Should I create a new bug for that ? (1) https://openqa.opensuse.org/tests/434752#step/yast2_clone_system/14 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c11 Oliver Kurz <okurz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|VERIFIED |REOPENED Resolution|FIXED |--- Flags|needinfo?(okurth@vmware.com |needinfo?(igonzalezsosa@sus |) |e.com) --- Comment #11 from Oliver Kurz <okurz@suse.com> --- I assume you meant me (okurz@suse.com), not okurth@vmware.com :-) As you stated, maybe the problem is not yet fixed for ppc64le: https://openqa.opensuse.org/tests/434752#step/yast2_clone_system/13 It shows the same problem as in the original description: Element profile has extra content: add-on so I'm reopening. I'm not sure about how the packages should be provided for ppc64le as the repos stating ppc64le in https://build.opensuse.org/package/show/openSUSE:Factory/autoyast2 are disabled. Imobach, the SR for Factory was accepted. The file _packages.root in https://openqa.opensuse.org/tests/434752/file/install_and_reboot-y2logs.tar.... mentions "autoyast2 [3.2.16-1.1.noarch]" so it seems to be an up-to-date version but maybe the packages in the installed system differ or it's yet another problem. Could you check please? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c14 --- Comment #14 from Michel Normand <normand@linux.vnet.ibm.com> --- Imobach, FYI there was another transient failure (1) this night for same test new snapshot but failed differently with: === "Internal error ... undefined method 'description' for nil:NilClass" === Should I create a new bug ? I consider it as transient because two retries did not failed the same way (2) (1) https://openqa.opensuse.org/tests/442248#step/yast2_clone_system/6 (2) https://openqa.opensuse.org/tests/442556 https://openqa.opensuse.org/tests/442571 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |ibs:running:5388:low -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:5388:low |ibs:running:5388:moderate -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Jozef Pupava <jpupava@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jpupava@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Stefan Behlert <behlert@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c24 Imobach Gonzalez Sosa <igonzalezsosa@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://trello.com/c/o6xMc6 | |sL Assignee|igonzalezsosa@suse.com |yast-internal@suse.de --- Comment #24 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- We have introduced several changes in the AutoYaST schema definition (firewalld, chrony, etc.). We would need to review this issue again. Now tracked at https://trello.com/c/o6xMc6sL -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c25 Stefan Schubert <schubi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |schubi@suse.com Assignee|yast-internal@suse.de |schubi@suse.com --- Comment #25 from Stefan Schubert <schubi@suse.com> --- https://github.com/yast/yast-firewall/pull/51/files -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c26 Stefan Schubert <schubi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #26 from Stefan Schubert <schubi@suse.com> --- xmllint works fine now the the fix and the current build. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c27 --- Comment #27 from Oliver Kurz <okurz@suse.com> --- Hi, good news! Can you check https://openqa.opensuse.org/tests/613307#step/yast2_clone_system/13 then? Seems like we still get some error reports in the "current build" of openSUSE Tumbleweed or maybe you mean a different build? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Stefan Behlert <behlert@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|schubi@suse.com |yast-internal@suse.de -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Knut Alejandro Anderssen González <knut.anderssen@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |knut.anderssen@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c31 --- Comment #31 from Oliver Kurz <okurz@suse.com> --- Actually it's possible to check yourself. Take a look at the last comment stating an openQA scenario failing on this, click on "Link to latest" and you should be able to find https://openqa.suse.de/tests/1560510#step/yast2_clone_system/14 which shows that the profile validation is not passed yet. https://openqa.suse.de/tests/1560509/file/logs_from_installation_system-y2lo... are the logfiles from the corresponding qcow image creation job showing that the package version in that installation is already "yast2-firewall [4.0.19-1.2.noarch]". -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c33 Rodion Iafarov <riafarov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |riafarov@suse.com --- Comment #33 from Rodion Iafarov <riafarov@suse.com> --- (In reply to Oliver Kurz from comment #31) I guess it's not only about version included, but if bug is really fixed by that change, as we don't use the ay profile from Martin in any of automated tests.
Actually it's possible to check yourself. Take a look at the last comment stating an openQA scenario failing on this, click on "Link to latest" and you should be able to find https://openqa.suse.de/tests/1560510#step/yast2_clone_system/14 which shows that the profile validation is not passed yet. https://openqa.suse.de/tests/1560509/file/logs_from_installation_system- y2logs.tar.bz2 are the logfiles from the corresponding qcow image creation job showing that the package version in that installation is already "yast2-firewall [4.0.19-1.2.noarch]".
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c34 --- Comment #34 from Knut Alejandro Anderssen González <knut.anderssen@suse.com> --- (In reply to Oliver Kurz from comment #31)
Actually it's possible to check yourself. Take a look at the last comment stating an openQA scenario failing on this, click on "Link to latest" and you should be able to find https://openqa.suse.de/tests/1560510#step/yast2_clone_system/14 which shows that the profile validation is not passed yet. https://openqa.suse.de/tests/1560509/file/logs_from_installation_system- y2logs.tar.bz2 are the logfiles from the corresponding qcow image creation job showing that the package version in that installation is already "yast2-firewall [4.0.19-1.2.noarch]".
I was mentioning the firewall part https://openqa.suse.de/tests/1520139#step/yast2_clone_system/13 https://openqa.suse.de/tests/1560510#step/yast2_clone_system/13 And comparing both tests seems it is already fixed, so it is still not passing because the add-on tag. I will check what is wrong there. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c35 --- Comment #35 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- The problem with yast2-schema is that we need to rebuild it everytime a YaST2 package changes. I've tried to rebuild the package today and I got the following list of errors: 90:49: error: element "partition_alignment" not allowed here; expected the element end-tag or element "btrfs_set_default_subvolume_name" or "start_multipath" 632:31: error: element "peers" not allowed here; expected the element end-tag or element "ntp_servers" or "ntp_sync" 720:35: error: element "restricts" not allowed here; expected the element end-tag or element "ntp_servers" or "ntp_sync" 802:42: error: element "start_at_boot" not allowed here; expected the element end-tag or element "ntp_servers" or "ntp_sync" 803:44: error: element "start_in_chroot" not allowed here; expected the element end-tag or element "ntp_servers" or "ntp_sync" 804:42: error: element "sync_interval" not allowed here; expected the element end-tag or element "ntp_servers" or "ntp_sync" 805:45: error: element "synchronize_time" not allowed here; expected the element end-tag or element "ntp_servers" or "ntp_sync" The partition_alignment element is not used anymore. And about the rest of errors, they are related to the ntp-client configuration, that has changed. Perhaps we should bump the yast2-schema version to make sure that it gets properly rebuild. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c36 Imobach Gonzalez Sosa <igonzalezsosa@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS --- Comment #36 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- About my previous comment, I was trying the profile attached by Martin. Trying https://openqa.suse.de/assets/other/01560510-autoinst.xml looks much worse (especially some problems with listentries). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c37 --- Comment #37 from Lukas Ocilka <locilka@suse.com> --- But then it shows another problem: Schema is rebuilt anytime when related YaST have some new version, but it's not automatically submitted to SLE/TW/... We thought it would be rebuilt directly in SLE/TW/... but it somehow does not work now. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c38 --- Comment #38 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- There are a bunch of listentry elements that: 1) should be exported with a better name (https://github.com/yast/yast-autoinstallation/blob/master/src/include/autoin...). 2) should be allowed when validating. Knut is already working on that. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast-internal@suse.de |knut.anderssen@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Stefan Behlert <behlert@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |behlert@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c39 --- Comment #39 from Imobach Gonzalez Sosa <igonzalezsosa@suse.com> --- autoyast2 4.0.44 will prevent from exporting the internal index (_id) in the partitioning section: PR: https://github.com/yast/yast-autoinstallation/pull/417 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c40 Knut Alejandro Anderssen González <knut.anderssen@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #40 from Knut Alejandro Anderssen González <knut.anderssen@suse.com> --- Fixed all the issues we have found and described below: We have added more entries to be exported with proper name tags instead of just listentry in this PR: - https://github.com/yast/yast-autoinstallation/pull/414 But we also will support the listentry tag in firewall and software list entry sections: - https://github.com/yast/yast-firewall/pull/56 - https://github.com/yast/yast-autoinstallation/pull/415 Added the zone element in /networking/interfaces/interface XML node: - https://github.com/yast/yast-network/pull/618 Permit an empty ntp_server list and allowed the use of listentry: - https://github.com/yast/yast-ntp-client/pull/109 Documented the drop of partition_alignment - https://github.com/SUSE/doc-sle/pull/275 (documentation about partition_alignment being dropped) After that the cloned profile is validating correctly with jing. So, should be fixed with: yast2-ntp-client-4.0.10 yast2-network-4.0.23 yast2-autoinstallation-4.0.44 yast2-firewall-4.0.20 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Matthias Griessmeier <mgriessmeier@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1103712 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Jeffrey Cheung <jcheung@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jcheung@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Maintenance Robot <maint-coord+maintenance_robot@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:5388:moderate |ibs:running:5388:important -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c49 Ednilson Miura <emiura@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emiura@suse.com --- Comment #49 from Ednilson Miura <emiura@suse.com> --- Issue still happening after update SUSE:Maintenance:5388:215540: autoyast2 : 3.1.172-36.30.1 autoyast2-installation : 3.1.172-36.30.1 yast2-storage : 3.1.110-28.7.141 # yast clone_system # xmllint --noout --relaxng /usr/share/YaST2/schema/autoyast/rng/profile.rng autoinst.xml autoinst.xml:4: element add-on: Relax-NG validity error : Element profile has extra content: add-on autoinst.xml fails to validate -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 Maintenance Robot <maint-coord+maintenance_robot@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:5388:important | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1013047 http://bugzilla.suse.com/show_bug.cgi?id=1013047#c50 --- Comment #50 from Swamp Workflow Management <swamp@suse.de> --- SUSE-RU-2020:1036-1: An update that has 18 recommended fixes can now be installed. Category: recommended (important) Bug References: 1011541,1013047,1019652,1026027,1039528,1040154,1044250,1044434,1049108,1049473,1051762,1052145,1054969,1057597,1059617,1077292,1156567,1167596 CVE References: Sources used: SUSE OpenStack Cloud 7 (src): autoyast2-3.1.172-36.30.1, yast2-storage-3.1.110-28.7.141 SUSE Linux Enterprise Server for SAP 12-SP2 (src): autoyast2-3.1.172-36.30.1, yast2-storage-3.1.110-28.7.141 SUSE Linux Enterprise Server 12-SP2-LTSS (src): autoyast2-3.1.172-36.30.1, yast2-storage-3.1.110-28.7.141 SUSE Linux Enterprise Server 12-SP2-BCL (src): autoyast2-3.1.172-36.30.1, yast2-storage-3.1.110-28.7.141 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.
participants (1)
-
bugzilla_noreply＠novell.com