You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Epicli: offline installation fails with error yum lockfile is held by another process on Azure/RHEL environment.
Reproduced on version 0.5.x and develop, so probably it also applies to all other versions. The problem occurs unpredictably in various tasks.
To Reproduce
Run offline installation on Azure RedHat:
sk4zuzu
changed the title
[BUG] Epicli: offline installation fails with error 'yum lockfile is held by another process' (Azure/RHEL)
[BUG] offline installation fails with error 'yum lockfile is held by another process' (Azure/RHEL)
Nov 30, 2020
Well, I created a workaround for this issue (only partial solution) in a PR, but I didn't like what I did. If we'd upgrade ansible to at least 2.9 (we use 2.8) this code would simplify greatly. On top of it this issue is not something critical, I believe it can wait. We can do 2 things: I could revisit latest changes in develop and adjust the PR then we merge it now or we could upgrade ansible and refine it.
Describe the bug
Epicli: offline installation fails with error
yum lockfile is held by another process
on Azure/RHEL environment.Reproduced on version 0.5.x and develop, so probably it also applies to all other versions. The problem occurs unpredictably in various tasks.
To Reproduce
Run offline installation on Azure RedHat:
epicli prepare --os redhat-7
/tmp/offline_requirements_rhel/prepare_scripts_rhel/download-requirements.sh /tmp/offline_requirements_rhel/downloads
epicli/data/azure/defaults/infrastructure/virtual-machine.yml
epicli apply -f /shared/05offazurrhelflannel/05offazurrhelflannel.yml --offline-requirements /shared/build/offline_requirements_rhel
Expected behavior
The cluster has been deployed successfully with no Internet access.
Config files
Sample configuration for 0.5:
OS (please complete the following information):
Cloud Environment (please complete the following information):
Additional context
Different installation:
I think people install Epiphany in offline mode as 'on prem' and not in the cloud, but still something is not working here.
The text was updated successfully, but these errors were encountered: