IBP ignore 255 exit code from e2fsck
Bug #1452277 reported by
Vladimir Kozhukalov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Sebastian Kalinowski |
Bug Description
Sometimes, when slave nodes aren't synchronized with the master node we can end up with the images built in the future. When you put this image on a hard drive and then run e2fsck it fails with 255 exit code which we probably need to ignore to avoid deployment failing caused by ntp issues.
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Fuel provisioning team (fuel-provisioning) |
Changed in fuel: | |
assignee: | Fuel provisioning team (fuel-provisioning) → Sebastian Kalinowski (prmtl) |
status: | Triaged → In Progress |
To post a comment you must log in.
Ignoring exit code it's probably not the best idea since 255 is not an exit code connected with this issue [1] paste.openstack .org/show/ 220654/
We can try to ignore e2fsck issues regarding to mount times in future using [2] (and [3]) in /etc/e2fsck.conf similar to this: http://
[1] http:// git.kernel. org/cgit/ fs/ext2/ e2fsprogs. git/tree/ e2fsck/ e2fsck. h#n73 git.kernel. org/cgit/ fs/ext2/ e2fsprogs. git/tree/ e2fsck/ problem. c#n338 (PR_0_FUTURE_ SB_LAST_ MOUNT) git.kernel. org/cgit/ fs/ext2/ e2fsprogs. git/tree/ e2fsck/ problem. h#n191 (PR_0_FUTURE_ SB_LAST_ MOUNT)
[2] http://
[3] http://