February 2021 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[Bug 1182525] New: --drop-if-no-change not working
by bugzilla_noreply＠suse.com 22 Feb '21

22 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182525 Bug ID: 1182525 Summary: --drop-if-no-change not working Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: dev.dorrejo(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, i am using microOS with podman, and found that this option come without the needed package "inotify-tools" need to be include on the list of packages require and at the same time need to be compile when preparing the ISO. Now when i install and reboot the system tried to start a transactional-update shell and exit (ctrl + D) of the new instance, but found that the snapshot is not remove. transactional-update shell -d -c Checking for newer version. transactional-update 3.1.4 started Options: shell -d -c Separate /var detected. Opening chroot in snapshot 4, continue with 'exit' 2021-02-20 19:57:50 tukit 3.1.4 started 2021-02-20 19:57:50 Options: call 4 bash 2021-02-20 19:57:50 Executing `bash`: ��transactional update # exit �� 2021-02-20 19:57:53 Application returned with exit status 0. 2021-02-20 19:57:53 Transaction completed. 2021-02-20 19:57:54 tukit 3.1.4 started 2021-02-20 19:57:54 Options: close 4 2021-02-20 19:57:55 New default snapshot is #4 (/.snapshots/4/snapshot). 2021-02-20 19:57:55 Transaction completed. Please reboot your machine to activate the changes and avoid data loss. New default snapshot is #4 (/.snapshots/4/snapshot/). transactional-update finished microos-labs:~ # transactional-update -d shell -c Checking for newer version. transactional-update 3.1.4 started Options: -d shell -c Separate /var detected. WARNING: You are creating a snapshot from a different base (3) than the current default snapshot (4). If you want to continue a previous snapshot use the --continue option, otherwise the previous changes will be discarded. Opening chroot in snapshot 5, continue with 'exit' 2021-02-20 19:58:08 tukit 3.1.4 started 2021-02-20 19:58:08 Options: call 5 bash 2021-02-20 19:58:08 Executing `bash`: ��transactional update # exit �� 2021-02-20 19:58:11 Application returned with exit status 0. 2021-02-20 19:58:11 Transaction completed. 2021-02-20 19:58:12 tukit 3.1.4 started 2021-02-20 19:58:12 Options: close 5 2021-02-20 19:58:13 New default snapshot is #5 (/.snapshots/5/snapshot). 2021-02-20 19:58:13 Transaction completed. Please reboot your machine to activate the changes and avoid data loss. New default snapshot is #5 (/.snapshots/5/snapshot/). transactional-update finished microos-labs:~ # transactional-update shell -d -c Checking for newer version. transactional-update 3.1.4 started Options: shell -d -c Separate /var detected. Opening chroot in snapshot 6, continue with 'exit' 2021-02-20 19:58:37 tukit 3.1.4 started 2021-02-20 19:58:37 Options: call 6 bash 2021-02-20 19:58:37 Executing `bash`: ��transactional update # exit �� 2021-02-20 19:58:40 Application returned with exit status 0. 2021-02-20 19:58:41 Transaction completed. 2021-02-20 19:58:41 tukit 3.1.4 started 2021-02-20 19:58:41 Options: close 6 2021-02-20 19:58:41 New default snapshot is #6 (/.snapshots/6/snapshot). 2021-02-20 19:58:41 Transaction completed. Please reboot your machine to activate the changes and avoid data loss. New default snapshot is #6 (/.snapshots/6/snapshot/). transactional-update finished microos-labs:~ # snapper list # | Type | Pre # | Date | User | Used Space | Cleanup | Description | Userdata ---+--------+-------+--------------------------+------+------------+---------+-----------------------+-------------- 0 | single | | | root | | | current | 1 | single | | s��b 20 feb 2021 16:25:49 | root | 32.00 KiB | | first root filesystem | 2 | single | | s��b 20 feb 2021 16:32:42 | root | 48.00 KiB | number | after installation | important=yes 3- | single | | s��b 20 feb 2021 17:05:48 | root | 9.73 MiB | | Snapshot Update of #1 | 4 | single | | s��b 20 feb 2021 19:57:48 | root | 22.00 MiB | | Snapshot Update of #3 | 5 | single | | s��b 20 feb 2021 19:58:07 | root | 160.00 KiB | | Snapshot Update of #3 | 6+ | single | | s��b 20 feb 2021 19:58:36 | root | 160.00 KiB | | Snapshot Update of #5 | microos-labs:~ # transactional-update --drop-if-no-change shell -c Checking for newer version. transactional-update 3.1.4 started Options: --drop-if-no-change shell -c Separate /var detected. WARNING: You are creating a snapshot from a different base (3) than the current default snapshot (6). If you want to continue a previous snapshot use the --continue option, otherwise the previous changes will be discarded. Opening chroot in snapshot 7, continue with 'exit' 2021-02-20 19:59:17 tukit 3.1.4 started 2021-02-20 19:59:17 Options: call 7 bash 2021-02-20 19:59:17 Executing `bash`: ��transactional update # exit exit �� 2021-02-20 19:59:25 Application returned with exit status 0. 2021-02-20 19:59:25 Transaction completed. 2021-02-20 19:59:26 tukit 3.1.4 started 2021-02-20 19:59:26 Options: close 7 2021-02-20 19:59:27 New default snapshot is #7 (/.snapshots/7/snapshot). 2021-02-20 19:59:27 Transaction completed. Please reboot your machine to activate the changes and avoid data loss. New default snapshot is #7 (/.snapshots/7/snapshot/). transactional-update finished microos-labs:~ # tukit 2021-02-20 19:59:31 tukit 3.1.4 started 2021-02-20 19:59:31 Options: ERROR: basic_string::_M_construct null not valid microos-labs:~ # tukit --help Syntax: tukit [option...] command Manage transactions ... microos-labs:~ # transactional-update --no-selfupdate --drop-if-no-change shell -c transactional-update 3.1.4 started Options: --no-selfupdate --drop-if-no-change shell -c Separate /var detected. WARNING: You are creating a snapshot from a different base (3) than the current default snapshot (7). If you want to continue a previous snapshot use the --continue option, otherwise the previous changes will be discarded. Opening chroot in snapshot 8, continue with 'exit' 2021-02-20 20:01:25 tukit 3.1.4 started 2021-02-20 20:01:25 Options: call 8 bash 2021-02-20 20:01:25 Executing `bash`: ��transactional update # exit �� 2021-02-20 20:01:26 Application returned with exit status 0. 2021-02-20 20:01:26 Transaction completed. 2021-02-20 20:01:27 tukit 3.1.4 started 2021-02-20 20:01:27 Options: close 8 2021-02-20 20:01:28 New default snapshot is #8 (/.snapshots/8/snapshot). 2021-02-20 20:01:28 Transaction completed. Please reboot your machine to activate the changes and avoid data loss. New default snapshot is #8 (/.snapshots/8/snapshot/). transactional-update finished microos-labs:~ # transactional-update shell --no-selfupdate --drop-if-no-change -c transactional-update 3.1.4 started Options: shell --no-selfupdate --drop-if-no-change -c Separate /var detected. Opening chroot in snapshot 9, continue with 'exit' 2021-02-20 20:01:39 tukit 3.1.4 started 2021-02-20 20:01:39 Options: call 9 bash 2021-02-20 20:01:39 Executing `bash`: ��transactional update # exit �� 2021-02-20 20:01:40 Application returned with exit status 0. 2021-02-20 20:01:41 Transaction completed. 2021-02-20 20:01:41 tukit 3.1.4 started 2021-02-20 20:01:41 Options: close 9 2021-02-20 20:01:42 New default snapshot is #9 (/.snapshots/9/snapshot). 2021-02-20 20:01:42 Transaction completed. Please reboot your machine to activate the changes and avoid data loss. New default snapshot is #9 (/.snapshots/9/snapshot/). transactional-update finished So this will p -- You are receiving this mail because: You are the assignee for the bug.

1 1

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 21 Feb '21

21 Feb '21

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! security enhancement: no setuid -> http://bugzilla.suse.com/show_bug.cgi?id=1171174 live-add-yast-repos: uses openSUSE-release -> http://bugzilla.suse.com/show_bug.cgi?id=1172100 transactional-update: warn about reboot etc. -> http://bugzilla.suse.com/show_bug.cgi?id=1173261 transactional-update: Notification on failing update -> http://bugzilla.suse.com/show_bug.cgi?id=1176882 cockpit-ws image is unusable -> http://bugzilla.suse.com/show_bug.cgi?id=1177487 [Build 51.1_15.3][MicroOS] Unknown group 'render' in 50-udev-default.rules -> http://bugzilla.suse.com/show_bug.cgi?id=1179453 KDE: Flatpack Chromium not starting via x-scheme-handler/https -> http://bugzilla.suse.com/show_bug.cgi?id=1182199

1 0

[Bug 1182227] combustion [# combustion: network] does not work
by bugzilla_noreply＠suse.com 15 Feb '21

15 Feb '21

https://bugzilla.suse.com/show_bug.cgi?id=1182227 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kubic-bugs(a)opensuse.org |fvogt(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 14 Feb '21

14 Feb '21

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! security enhancement: no setuid -> http://bugzilla.suse.com/show_bug.cgi?id=1171174 live-add-yast-repos: uses openSUSE-release -> http://bugzilla.suse.com/show_bug.cgi?id=1172100 transactional-update: warn about reboot etc. -> http://bugzilla.suse.com/show_bug.cgi?id=1173261 transactional-update: Notification on failing update -> http://bugzilla.suse.com/show_bug.cgi?id=1176882 cockpit-ws image is unusable -> http://bugzilla.suse.com/show_bug.cgi?id=1177487 [Build 51.1_15.3][MicroOS] Unknown group 'render' in 50-udev-default.rules -> http://bugzilla.suse.com/show_bug.cgi?id=1179453 [Build 20210128] openQA test fails in journal_check -> http://bugzilla.suse.com/show_bug.cgi?id=1181547

1 0

[Bug 1182227] New: combustion [# combustion: network] does not work
by bugzilla_noreply＠suse.com 14 Feb '21

14 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182227 Bug ID: 1182227 Summary: combustion [# combustion: network] does not work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: syuta.hashimoto(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 846101 --> http://bugzilla.opensuse.org/attachment.cgi?id=846101&action=edit combustion/script file [# combustion: network] comment occur error. combustion logged: sh: line 5: /lib/dracut/hooks/pre-udev/60-net-genrules.sh: No such file or directory I used openSUSE-MicroOS.x86_64-16.0.0-Kubic-kubeadm-kvm-and-xen-Snapshot20210210.qcow2. Combustion succeeded without [# combustion: network] comment. What am I wrong? -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1087891] no python3 mysql module available which works with salt.
by bugzilla_noreply＠suse.com 08 Feb '21

08 Feb '21

https://bugzilla.suse.com/show_bug.cgi?id=1087891 https://bugzilla.suse.com/show_bug.cgi?id=1087891#c78 --- Comment #78 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:0316-1: An update that solves 14 vulnerabilities and has 218 fixes is now available. Category: security (moderate) Bug References: 1002529,1004047,1004260,1004723,1008933,1011304,1011800,1012398,1012999,1017078,1019386,1020831,1022562,1022841,1023535,1025896,1027044,1027240,1027722,1030009,1030073,1032213,1032452,1032931,1035914,1036125,1038855,1039370,1040886,1041993,1042749,1043111,1050003,1051948,1052264,1053376,1053955,1057635,1059291,1059758,1060230,1061407,1062462,1062464,1063419,1064520,1065792,1068446,1068566,1071322,1072599,1075950,1079048,1081592,1083110,1087055,1087278,1087581,1087891,1088888,1089112,1089362,1089526,1091371,1092161,1092373,1094055,1095507,1095651,1095942,1096514,1097174,1097413,1098394,1099323,1099460,1099887,1099945,1100142,1100225,1100697,1101780,1101812,1101880,1102013,1102218,1102248,1102265,1102819,1103530,1104154,1104491,1106164,1107333,1108557,1108834,1108969,1108995,1109893,1110938,1112874,1113698,1113699,1113784,1114029,1114197,1114474,1114824,1116343,1116837,1117995,1121091,1121439,1122663,1122680,1123044,1123512,1123865,1124277,1125015,1128061,1128554,1129079,1130588,113078 4,1131114,1132076,1133523,1133647,1134860,1135360,1135507,1135567,1135656,1135732,1137642,1138952,1139761,1140193,1140912,1143301,1146192,1146382,1148714,1150447,1151650,1151947,1152366,1153611,1154620,1157465,1157479,1158441,1158940,1159118,1159284,1159670,1160931,1162327,1162504,1165425,1165572,1167437,1167556,1168340,1169604,1169800,1170042,1170104,1170288,1170595,1171461,1171906,1172075,1172211,1173072,1173909,1173911,1173936,1174165,1175549,1175987,1176024,1176294,1176397,1176480,1177867,1178319,1178361,1178362,1178485,849184,849204,849205,955373,958350,959572,963322,965403,967803,969320,970669,971372,972311,972490,975093,975303,975306,975733,975757,976148,978150,978833,979448,979676,980313,983017,983512,985112,985661,986019,988506,989193,989798,990029,990439,990440,991048,993039,993549,996455,999852 CVE References: CVE-2016-1866,CVE-2016-9639,CVE-2017-12791,CVE-2017-14695,CVE-2017-14696,CVE-2018-15750,CVE-2018-15751,CVE-2019-17361,CVE-2019-18897,CVE-2020-11651,CVE-2020-11652,CVE-2020-16846,CVE-2020-17490,CVE-2020-25592 JIRA References: Sources used: 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.

1 0

[Bug 1087891] no python3 mysql module available which works with salt.
by bugzilla_noreply＠suse.com 08 Feb '21

08 Feb '21

https://bugzilla.suse.com/show_bug.cgi?id=1087891 https://bugzilla.suse.com/show_bug.cgi?id=1087891#c77 --- Comment #77 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:0315-1: An update that solves 14 vulnerabilities and has 218 fixes is now available. Category: security (moderate) Bug References: 1002529,1004047,1004260,1004723,1008933,1011304,1011800,1012398,1012999,1017078,1019386,1020831,1022562,1022841,1023535,1025896,1027044,1027240,1027722,1030009,1030073,1032213,1032452,1032931,1035914,1036125,1038855,1039370,1040886,1041993,1042749,1043111,1050003,1051948,1052264,1053376,1053955,1057635,1059291,1059758,1060230,1061407,1062462,1062464,1063419,1064520,1065792,1068446,1068566,1071322,1072599,1075950,1079048,1081592,1083110,1087055,1087278,1087581,1087891,1088888,1089112,1089362,1089526,1091371,1092161,1092373,1094055,1095507,1095651,1095942,1096514,1097174,1097413,1098394,1099323,1099460,1099887,1099945,1100142,1100225,1100697,1101780,1101812,1101880,1102013,1102218,1102248,1102265,1102819,1103530,1104154,1104491,1106164,1107333,1108557,1108834,1108969,1108995,1109893,1110938,1112874,1113698,1113699,1113784,1114029,1114197,1114474,1114824,1116343,1116837,1117995,1121091,1121439,1122663,1122680,1123044,1123512,1123865,1124277,1125015,1128061,1128554,1129079,1130588,113078 4,1131114,1132076,1133523,1133647,1134860,1135360,1135507,1135567,1135656,1135732,1137642,1138952,1139761,1140193,1140912,1143301,1146192,1146382,1148714,1150447,1151650,1151947,1152366,1153611,1154620,1157465,1157479,1158441,1158940,1159118,1159284,1159670,1160931,1162327,1162504,1165425,1165572,1167437,1167556,1168340,1169604,1169800,1170042,1170104,1170288,1170595,1171461,1171906,1172075,1172211,1173072,1173909,1173911,1173936,1174165,1175549,1175987,1176024,1176294,1176397,1176480,1177867,1178319,1178361,1178362,1178485,849184,849204,849205,955373,958350,959572,963322,965403,967803,969320,970669,971372,972311,972490,975093,975303,975306,975733,975757,976148,978150,978833,979448,979676,980313,983017,983512,985112,985661,986019,988506,989193,989798,990029,990439,990440,991048,993039,993549,996455,999852 CVE References: CVE-2016-1866,CVE-2016-9639,CVE-2017-12791,CVE-2017-14695,CVE-2017-14696,CVE-2018-15750,CVE-2018-15751,CVE-2019-17361,CVE-2019-18897,CVE-2020-11651,CVE-2020-11652,CVE-2020-16846,CVE-2020-17490,CVE-2020-25592 JIRA References: Sources used: 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.

1 0

[Bug 1181934] New: [Build 20210207] Interaction t-u vs combustion failing with t-u 3.1
by bugzilla_noreply＠suse.com 08 Feb '21

08 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1181934 Bug ID: 1181934 Summary: [Build 20210207] Interaction t-u vs combustion failing with t-u 3.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1622310/modules/imag e_checks/steps/13 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-x86_64-microos@64bit fails in [image_checks](https://openqa.opensuse.org/tests/1622310/modules/image_check… ## Test suite description ## Reproducible Fails since (at least) Build [20210207](https://openqa.opensuse.org/tests/1622004) ## Expected result Last good: [20210205](https://openqa.opensuse.org/tests/1620535) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos… -- You are receiving this mail because: You are the assignee for the bug.

1 1

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 07 Feb '21

07 Feb '21

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! security enhancement: no setuid -> http://bugzilla.suse.com/show_bug.cgi?id=1171174 live-add-yast-repos: uses openSUSE-release -> http://bugzilla.suse.com/show_bug.cgi?id=1172100 transactional-update: warn about reboot etc. -> http://bugzilla.suse.com/show_bug.cgi?id=1173261 transactional-update: Notification on failing update -> http://bugzilla.suse.com/show_bug.cgi?id=1176882 cockpit-ws image is unusable -> http://bugzilla.suse.com/show_bug.cgi?id=1177487 [Build 51.1_15.3][MicroOS] Unknown group 'render' in 50-udev-default.rules -> http://bugzilla.suse.com/show_bug.cgi?id=1179453 [Build 20210128] openQA test fails in journal_check -> http://bugzilla.suse.com/show_bug.cgi?id=1181547

1 0

[Bug 1181842] New: RKE: ip forwarding disabled
by bugzilla_noreply＠suse.com 05 Feb '21

05 Feb '21

https://bugzilla.suse.com/show_bug.cgi?id=1181842 Bug ID: 1181842 Summary: RKE: ip forwarding disabled Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying to run RKE on MicroOS: On Tumbleweed and Tumbleweed transactional-server, ip forwarding is enabled (sysctl -a), even if the sysctl.d/70-yast.conf file disables it. On MicroOS and Kubic ip forwarding is enabled for all and default, but disabled for eth0 and lo. Same sysctl.d/70-yast.conf file, which disabled it. RKE only works if you manually enables ip forwarding for eth0 and lo. -- You are receiving this mail because: You are the assignee for the bug.

1 1