Standalone deployment immediately fails when removing the install directory fails because of EBUSY
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Low
|
Takashi Kajinami |
Bug Description
Description
===========
Standalone jobs failed sometimes because of EBUSY while cleaning up the install directory, even after deployment succeeds.
https:/
https:/
~~~
2022-08-16 21:15:41Z [standalone.
2022-08-16 21:15:41Z [standalone]: CREATE_COMPLETE Stack CREATE completed successfully
Stack standalone/
Generating default ansible config file /home/zuul/
Exception: [Errno 17] File exists: '/home/
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
shutil.
File "/usr/lib64/
onerror(
File "/usr/lib64/
os.rmdir(path)
OSError: [Errno 16] Device or resource busy: '/home/
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
shutil.
File "/usr/lib64/
return _copytree(
File "/usr/lib64/
os.
File "/usr/lib64/
mkdir(name, mode)
FileExistsError: [Errno 17] File exists: '/home/
None
[Errno 17] File exists: '/home/
~~~
The command output does not indicate failure in umount, I suspect EBUSY was returned because rmdir was executed right after umount and there were still remaining reference caused left by mount.
We better introduce retry mechanism to avoid immediate failure, because deployment has passed without failure and the error affects only cleanup process.
Changed in tripleo: | |
importance: | Undecided → Low |
assignee: | nobody → Takashi Kajinami (kajinamit) |
milestone: | none → zed-1 |
Fix proposed to branch: master /review. opendev. org/c/openstack /python- tripleoclient/ +/853381
Review: https:/