Bugzilla – Bug 1202748
[Build E.662.1] yast forcibly calls netconfig update
Last modified: 2022-10-19 09:38:15 UTC
In light of ALP, we are trying to eliminate netconfig wrappers.
To this end, we changed one of the last packages depending on sysconfig-netconfig to no longer do so (NetworkManager)
This results in a system installation error:
"Cannot update the dynamic configuration policy"
As netconfig is no longer mandatory, YaST should cope with its absence
openQA test in scenario opensuse-Staging:E-Staging-DVD-x86_64-RAID0_gpt@64bit fails in
## Test suite description
Fails since (at least) Build [E.662.1](https://openqa.opensuse.org/tests/2550590) (current job)
## Expected result
Last good: [E.661.1](https://openqa.opensuse.org/tests/2538496) (or more recent)
## Further details
Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=Staging-DVD&machine=64bit&test=RAID0_gpt&version=Staging%3AE)
The error seems to track back to:
# Writes sysconfig ntp policy and calls netconfig to update ntp. Report an
# error if some of the call fails.
success = write_policy && update_netconfig
Report.Error(_("Cannot update the dynamic configuration policy.")) unless success
This looks like a duplicate of https://bugzilla.suse.com/show_bug.cgi?id=1198066, although not crashing in case of netconfig is more generic and we need to adapt several modules but for that we have the Jira request.
At least the installation should work fine with the fix introduced by yast2-ntp-client-4.5.1 but there are other modules that needs to be adapted like yast2-samba (see https://bugzilla.suse.com/show_bug.cgi?id=1198066)
As for removing completely netconfig we already have a jira entry, do we want to maintain this bug open or can we close it already once the installation should works now fine with yast2-ntp-client fixes?
changing assignment as it is already being handled in yast kanban queue
(In reply to Knut Alejandro Anderssen González from comment #5)
> At least the installation should work fine with the fix introduced by
> yast2-ntp-client-4.5.1 but there are other modules that needs to be adapted
> like yast2-samba (see https://bugzilla.suse.com/show_bug.cgi?id=1198066)
> As for removing completely netconfig we already have a jira entry, do we
> want to maintain this bug open or can we close it already once the
> installation should works now fine with yast2-ntp-client fixes?
I'd say we can close the bug - as the immediate issue reported here is fixed and the remaining pieces are part of the jira ticket