Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

lava-docker: backup/restore should handle devices and device-types

Fixed

Description

When doing a backup/restore, the device and device-type files are not saved.  This is OK if the remote workers are also stopped and restarted, but if doing a trivial update of the master (e.g. adding a user or a token) it should not be a requirement to restart the remote workers.

 

Environment

None

Activity

Show:

Kevin Hilman 
December 13, 2018 at 3:18 PM

OK, so since any new device-types would be in the database, they are already part of the backup anyways.  So, the new feature is just to be sure that device files need to be saved, because they are on the filesystem, not in the db.

 

Corentin Labbe 
December 13, 2018 at 11:03 AM

Note that the patch adds backup of devices files only.

This is because lava-slave does not add "new device-types", it only prevent the master that it uses it.

But this information is in the database and not on the filesystem.

Kevin Hilman 
December 12, 2018 at 3:50 AM

Support merged into upstream lava-docker project: https://github.com/kernelci/lava-docker/pull/80

 

Kevin Hilman 
December 12, 2018 at 3:48 AM

Corentin confirmed that with the current backup/restore procedure, a restart of the remote worker(s) is required to restore devices and device-types.

We will fix that in the backup/restore process.

Details

Assignee

Reporter

Labels

Contract ID

Components

Priority

Parent

Created December 12, 2018 at 3:47 AM
Updated January 23, 2019 at 3:31 AM
Resolved December 19, 2018 at 6:10 PM