At first install fuel-octane
after that patch octane that add file to it (just for test `touch /usr/lib/python2.7/site-packages/octane/commands/crazy_cmd.py`)
after that remove octane
and than
Why this is the problem?
CI working this way:
in every step it reverts to snapshot with previous finished procedure,
removes octane,
install new and
patches it.
If in previous step octane had been already patched, this file had been added, it would not patched on the next step.
We have problem
At first install fuel-octane python2. 7/site- packages/ octane/ commands/ crazy_cmd. py`)
after that patch octane that add file to it (just for test `touch /usr/lib/
after that remove octane
and than
find /usr/lib/ python2. 7/site- packages/ octane | grep crazy_cmd python2. 7/site- packages/ octane/ commands/ crazy_cmd. py
/usr/lib/
Why this is the problem?
CI working this way:
in every step it reverts to snapshot with previous finished procedure,
removes octane,
install new and
patches it.
If in previous step octane had been already patched, this file had been added, it would not patched on the next step.
This problem fixed by workaround in fuel-qa.