action #135368
closedFix check for NetworkManager in cockpit_service test module
Description
Motivation¶
The cockpit_service
test module has a check for NetworkManager built in that makes the test fail if it runs on a distribution that should have NetworkManager installed by default.
This check will cause problems when cockpit_service
is run in a migration scenario (observed on SLE Micro 5.1->5.5 migration), because the initial version in the migration test had wicked
installed an running and there is not automatic migration from 'wickedto NetworkManager. So after doing
zypper_migrationwe end up in a situation that the upgraded system is still running
wicked` which then will lead to a failure.
ToDo¶
After some discussion on Slack the result was to create an own YAML schedule for migration and don't use cockpit_service
in that since its checks are not really related to migration scenarios.
Acceptance criteria¶
AC1: Migration tests in the SLE Micro/Yast and migraiton
job group will work without cockpit_service
test.
Updated by lmanfredi about 1 year ago
- Status changed from Workable to In Progress
- Assignee set to lmanfredi
Updated by lmanfredi about 1 year ago
Verified in Overall Summary of YaST and Migration
Updated by lmanfredi about 1 year ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100