IBP ignore 255 exit code from e2fsck

[Vladimir Kozhukalov]

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.

[Sebastian Kalinowski (prmtl)]

Ignoring exit code it's probably not the best idea since 255 is not an exit code connected with this issue [1]
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://paste.openstack.org/show/220654/

[1] http://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/tree/e2fsck/e2fsck.h#n73
[2] http://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/tree/e2fsck/problem.c#n338 (PR_0_FUTURE_SB_LAST_MOUNT)
[3] http://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/tree/e2fsck/problem.h#n191 (PR_0_FUTURE_SB_LAST_MOUNT)

[Vladimir Kozhukalov (kozhukalov)]

Sebastian,

Great findings. It sounds much more rational to have this in the config rather than somewhere in the code.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/182587

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/182587
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=b1df628b0d8d77d6baf8dad1fead812b6e26f0e7
Submitter: Jenkins
Branch: master

commit b1df628b0d8d77d6baf8dad1fead812b6e26f0e7
Author: Sebastian Kalinowski <email address hidden>
Date: Wed May 13 11:08:52 2015 +0200

    Ignore time shifts in e2fsck on bootstrap

    Added /etc/e2fsck.conf with ignoring of problems related with
    time shifts between Fuel Master and bootstraped nodes.

    Ignoring two problems:
     * PR_0_FUTURE_SB_LAST_WRITE (0x000032) - Last write time is in the future
     * PR_0_FUTURE_SB_LAST_MOUNT (0x000031) - Last mount time is in the future

    Change-Id: Ie75538b92af9fdda0078a0a35799da5cde313fa5
    Closes-Bug: #1452277