lp:~raharper/curtin/trunk.fix-raid-over-iscsi
- Get this branch:
- bzr branch lp:~raharper/curtin/trunk.fix-raid-over-iscsi
Branch merges
- Server Team CI bot: Approve (continuous-integration)
- Scott Moser (community): Approve
-
Diff: 154 lines (+95/-5)5 files modifiedcurtin/block/iscsi.py (+9/-0)
curtin/commands/install.py (+17/-5)
curtin/util.py (+14/-0)
tests/unittests/test_util.py (+51/-0)
tests/vmtests/test_mdadm_iscsi.py (+4/-0)
Branch information
Recent revisions
- 525. By Ryan Harper
-
Instead of forcing a disconnect; ensure iscsi service is running which handles disconnect already
- 524. By Joshua Powers
-
vmtest: catch exceptions in curtin-log-print
Wraps the calling of curtin-log-print to catch any exceptions
that result. Was causing large image files to be left behind as
an exception generated by the curtin-log-print prevented proper
cleanup.LP: #1714592
- 523. By Ryan Harper
-
iscsi: use curtin storage config to disconnect iscsi targets
When curtin disconnects from iscsi targets after an install, it does so
after unmounting the targets, however it passed the target dir into the
iscsi disconnect code which then silently failed to find any
session configurations.We've been lucky as the existing shutdown iscsi service has been
logging out of sessions defined on the host; however on recent
Artful systems, the open-iscsi service is not restarted after
populating /etc/iscsi/nodes directory and since it is not running
in the ephemeral environment the service will not automatically
stop the iscsi devices, causing a hang on shutdown.To resolve this parse the curtin storage config for iscsi disks,
construct IscsiDisk objects and then call their disconnect() method.
In addition to this logic fix, this branch contains:- adds a missing Artful LVM Iscsi vmtest class
- Updated logging messages in iscsi paths, including
a message when iscsi_disconnect doesn't find the
/etc/iscsi/nodes directory.
- Updated IscsiDisk disconnect with similar logging - 521. By Scott Moser
-
vmtest: get info about collected symlinks and then delete them.
Some of the 'collect' scripts collect files with 'cp -a' or other
means that would collect a symbolic link. Since none of our
scripts yet handle properly resolving absolute symlinks we just
remove all symlinks and write a file 'symlinks.txt' with info about them.At a later date we might need to also clean out sockets or other content.
The primary motivation for this is to
a.) make sure tests don't inadvertantly read the target of the symlink
and thus "verify" files on the host
b.) jenkins can produce a zip file of the artifacts, and we suspect that
it is bothered by the symbolic links.
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