Bug 1528809
Summary: | glusterd blocks DNF on install | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | customercare |
Component: | glusterd | Assignee: | bugs <bugs> |
Status: | CLOSED EOL | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.10 | CC: | bugs, customercare, humble.devassy, jonathansteffan, kkeithle, matthias, ndevos, ramkrsna |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-06-20 18:27:12 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
customercare
2017-12-24 10:23:59 UTC
Verified on a second server, it stucks here: glusterd --xlator-option *.upgrade=on -N Is this actually an update? I could be mean and close this as WORKSFORME because I don't get this ever when I do a fresh _installs_. It would be helpful if you could run the install in, e.g., the C locale. While the majority of our devs are multi-lingual, German isn't common. (Hint, Gluster Inc. is/was a company in India.) I speak some German, but would not claim to be fluent. It would be helpful even for me. Thanks No, it was an install, BUT.. maybe not a clean one. Those servers had have had gluster on it in 2016. Because of some nasty bugs, like the famous port iteration bug or the SSL bug, the "i take ages on an os upgrade" (bug), i removed the rpms in 2016. The data got removed later, so besides (maybe) /var/lib/glusterd/, there was no data left over. I created my test volumes from scratch again. BTW: Merry chrismas :D I have set up two pairs of systems: one pair of f26, and one pair of f27. I have tried multiple combinations of: + install glusterfs-3.10.8, create+start a volume, stop volume, remove gluster, install glusterfs-3.10.9. + install glusterfs-3.10.8, create+start a volume, stop volume, remove gluster, install glusterfs-3.12.4. + etc. I've done the second install with both nodes up and running, and also with one node shut off (in case glusterd was trying to communicate with the other node's glusterd. I am not able to reproduce the long delay after installing glusterfs-server. I'm changing the product and components to GlusterFS and glusterd in case those developers can think of anything that could be going on. This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained. As a result this bug is being closed. If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately. This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained. As a result this bug is being closed. If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately. |