Traceback of the nm-update-client-ids.py

[oamg]

Traceback of the nm-update-client-ids.py

[bengal]

client = NM.Client.new(None)

creates a new client object by connecting to NM via D-Bus. The error "Could not connect" comes from Glib gsocketclient.c and indicates that the connection to a socket failed so perhaps the unix socket for the system bus in /run/dbus is missing.

[bocekm]

@bengal, do you think try/catch block and handling this error gracefully could suffice? Or you think that this error may indicate a more serious issue?

[bengal]

As far as I remember, the actor is supposed to be run after NM (which depends on D-Bus) and so it seems unexpected that the D-Bus socket is missing at that point. In my opinion this indicates a more serious issue.

[pirat89]

For the record, in the past we added service dependencies to ensure the leapp will be processed after network is up, but it looks that it is still processed to early maybe? If it is the issue, retry could help here. If not, ...

Here is the unit file: https://github.com/oamg/leapp-repository/blob/master/repos/system_upgrade/el7toel8/actors/createresumeservice/files/leapp_resume.service