Backup/restore master node failed. Docker containers logs: Socket service systemd-udevd.service not loaded, refusing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
High
|
Ivan Suzdal | ||
8.0.x |
In Progress
|
High
|
Ivan Suzdal | ||
Mitaka |
Confirmed
|
High
|
Ivan Suzdal |
Bug Description
Sometimes Backup/restore master node failed. Docker containers logs: Socket service systemd-
Scenario:
1. Setup master node
2. Create new environment
3. Choose Neutron, TUN
4. Add 3 controller
5. Add 2 compute
6. Verify networks
7. Deploy the environment
8. Verify networks
9. Run OSTF tests
10. Backup master node with default path for archive(#dockerctl backup)
11. Verify networks
12. Run OSTF tests
13. Add 1 compute node
14. Restore master node with default path for archive(#dockerctl restore)
The majority container logs contain:
#dockerctl logs nginx
...
Socket service systemd-
VERSION:
feature_groups:
- mirantis
production: "docker"
release: "8.0"
api: "1.0"
build_number: "478"
build_id: "478"
fuel-nailgun_sha: "ae949905142507
python-
fuel-agent_sha: "481ed135de2cb5
fuel-
astute_sha: "b81577a5b7857c
fuel-library_sha: "420c6fa5f8cb51
fuel-ostf_sha: "ab5fd151fc6c1a
fuel-mirror_sha: "b62f3cce5321fd
fuelmenu_sha: "fac143f4dfa757
shotgun_sha: "63645dea384a37
network-
fuel-upgrade_sha: "616a7490ec7199
fuelmain_sha: "6c6b088a3d52dd
Snapshot:
https:/
tags: | added: area-python |
Workaround is to reboot Fuel Master and verify that containers started okay. It will go in Known Issues of Fuel 8.0 release notes.