lp:~raharper/curtin/trunk.fix-iscsi-shutdown
- Get this branch:
- bzr branch lp:~raharper/curtin/trunk.fix-iscsi-shutdown
Branch merges
- Server Team CI bot: Approve (continuous-integration)
- Chad Smith: Approve
- Nish Aravamudan: Pending requested
-
Diff: 298 lines (+227/-5)4 files modifiedcurtin/block/iscsi.py (+35/-3)
curtin/commands/install.py (+7/-2)
tests/unittests/test_block_iscsi.py (+181/-0)
tests/vmtests/test_lvm_iscsi.py (+4/-0)
Related bugs
Bug #1713537: iscsi-targets don't quit session on shutdown | Medium | Fix Released |
Related blueprints
Branch information
Recent revisions
- 530. By Ryan Harper
-
Parse storage config for reconstructing iscsi disk objects for disconnect operations
- 529. By Ryan Harper
-
Don't use iscsi globals, not available across stages
The iscsi global is not available across stages due to use of
subprocess to run curtin commands. Revert back to finding
on-disk sessions that curtin configured to run iscsi disconnects. - 528. By Ryan Harper
-
Switch back to unmounting all paths, and then disconnecting iscsi
In general, the typical cleanup of an in-use of block device involves
unmounting the filesystem/block device, and then perform any block
device specific actions. In this case, curtin will recursively unmount
any devices mounted under the install target directory (iscsi disks included)
And then we query the curtin iscsi layer for any connected iscsi devices it
created and invoke disconnect on each device. This should avoid shutting down
any other sessions which may be active but are not created/owned by curtin.In addition, add some logging to some of the iscsi paths which previously
would silently exit without performing the requested action (disconnect for
example returns if the target iscsi node dir is not present).
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:~curtin-dev/curtin/trunk