multipath parent device may need unmapping to release hold on disks
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| curtin |
Undecided
|
Unassigned |
Bug Description
In our vmtest scenario for multipath the removal wiping of the underlying path element would fail if the multipath mapping for the device was present; this causes an installation failure.
Ryan Harper (raharper) wrote : | #2 |
[ 88.709877] cloud-init[809]: Traceback (most recent call last):
[ 88.710852] cloud-init[809]: File "/curtin/
[ 88.714853] cloud-init[809]: ret = args.func(args)
[ 88.715720] cloud-init[809]: File "/curtin/
[ 88.717063] cloud-init[809]: return log_time("TIMED %s: " % msg, func, *args, **kwargs)
[ 88.719463] cloud-init[809]: File "/curtin/
[ 88.722392] cloud-init[809]: return func(*args, **kwargs)
[ 88.723299] cloud-init[809]: File "/curtin/
[ 88.725877] cloud-init[809]: meta_clear(devices, state.get(
[ 88.728655] cloud-init[809]: File "/curtin/
[ 88.733926] cloud-init[809]: clear_holders.
[ 88.734960] cloud-init[809]: File "/curtin/
[ 88.738874] cloud-init[809]: shutdown_
[ 88.739870] cloud-init[809]: File "/curtin/
k
[ 88.741448] cloud-init[809]: _wipe_superbloc
[ 88.744671] cloud-init[809]: File "/curtin/
ck
[ 88.746179] cloud-init[809]: exclusive=
[ 88.748710] cloud-init[809]: File "/curtin/
[ 88.751119] cloud-init[809]: quick_zero(path, partitions=False, exclusive=
[ 88.754240] cloud-init[809]: File "/curtin/
[ 88.755434] cloud-init[809]: exclusive=
[ 88.757729] cloud-init[809]: File "/curtin/
ts
[ 88.760699] cloud-init[809]: with exclusive_
[ 88.763491] cloud-init[809]: File "/usr/lib/
[ 88.764845] cloud-init[809]: return next(self.gen)
[ 88.767372] cloud-init[809]: File "/curtin/
[ 88.770156] cloud-init[809]: fd = os.open(path, flags)
Ryan Harper (raharper) wrote : | #3 |
This commit fixes this issue:
https:/
Changed in curtin: | |
status: | Incomplete → Fix Committed |
Do we have a log, traceback, subiquity bug or jenkins CI job that ran into this?