-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4.1 image is really slow with Heketi and fails Install on OKD #128
Comments
@jocelynthode I have cherrypicked that patch and also triggered the build.. Lets see how it goes. |
@jocelynthode you have new image with the fix. please let me know if it helps! |
@humblec Uh, I thought this PR would fix my issue. However reading the Bug reports I see that there is also a bug in LVM which I seem to hit with the unitialized udev:
This is a bit out of my comfort zone. Is there a workaround for this or do we need to wait for a patched LVM version ? |
@humblec To note, I did not encounter any of these issue while using an old version of the container which had gluster 4.1.6 in it |
@humblec : Here's what I noticed between the two builds that encountered the problem: The lvm2 packages are slightly different on 4.1.6 we had lvm2-libs-2.02.180-10.el7_6.2.x86_64 and lvm2-2.02.180-10.el7_6.2.x86_64 and on 4.1.7 we have lvm2-libs-2.02.180-10.el7_6.3.x86_64 and lvm2-2.02.180-10.el7_6.3.x86_64 4.1.6
4.1.7
|
@humblec RedHat has downgraded their lvm packages (https://bugzilla.redhat.com/show_bug.cgi?id=1676921). Can we please do the same in gluster image so that it starts working again ? I could try and submit a PR if you want |
I've also faced this issue with version 4.1.7, is there any eta on fixing it? |
@alibo : As I still did not get an answer from @humblec to rebuild the 4.1 image and setup dockerhub automated builds, I have rebuilt from source the 4.1 image and pushed it to my dockerhub repository if you don't want to rebuild it: |
The change is already included with #134. Unfortunately there was no new image build and pushed to Docher Hub?! The latest gluster4u1_centos7 was build on 18 February... https://hub.docker.com/r/gluster/gluster-centos/tags @humblec could you check why automated image builds fail again? |
[offtopic] |
I just wanted to add that after a failed installation the |
Deploying okd recently and catch same error. |
Hey, I noticed that using the image tagged for 4.1, I cannot install GlusterFS in OKD due to the error fixed by #126
Can we please cherry-pick #126 to 4.1 branch and rebuild images ?
@humblec @mcquinne
The text was updated successfully, but these errors were encountered: