Bug 1352355
Summary: | Corosync fails to start after upgrading package to 2.3.4-7.el7_2.3 | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Sam McLeod <mailinglists> | ||||
Component: | corosync | Assignee: | Jan Friesse <jfriesse> | ||||
Status: | CLOSED UPSTREAM | QA Contact: | cluster-qe <cluster-qe> | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 7.2 | CC: | akarlsso, ccaulfie, cfeist, cluster-maint, mailinglists | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | corosync-2.4.0-1.el7 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-07-04 08:00:35 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: | |||||||
Attachments: |
|
Description
Sam McLeod
2016-07-04 01:22:13 UTC
Note, downgrading corosync and corosync-lib to the previous version fixes the issue and it starts as expected: root@s1-san8:~ # yum downgrade corosync corosynclib ... corosync.x86_64 0:2.3.4-7.el7_2.1 corosynclib.x86_64 0:2.3.4-7.el7_2.1 root@s1-san8:~ # systemctl start corosync Already reported in upstream as https://github.com/corosync/corosync/issues/137 (+ fixed). This bug is not fatal because it has simple workaround and pcs generated clusters are unaffected (pcs doesn't allow creating of corosync.conf without cluster_name) so no need for Z stream. Bug is already fixed in upstream (https://github.com/corosync/corosync/commit/44df76a7ee6c10468d87f1e0888d6ce5b558d565). Interesting and thank you for the link, I'm sorry I didn't actually spot that myself. We don't use PCS (yet) due to some limitations when automating cluster bootstraipping / configuration hence why we noticed it. Again, sorry for not spotting this upstream first. Thanks, Sam. (In reply to Sam McLeod from comment #4) > Interesting and thank you for the link, I'm sorry I didn't actually spot > that myself. No problem, actually it's quite useful to have also BZ for anybody who hits same problem. > > We don't use PCS (yet) due to some limitations when automating cluster > bootstraipping / configuration hence why we noticed it. Yep, so for a quick workaround just follow github issue (setting cluster_name is generally recommended and it's needed for new qdevice feature). RHEL is going to get this BZ fixed with 7.3. > > Again, sorry for not spotting this upstream first. I would like to thank you for high quality report. Regards, Honza > > Thanks, > Sam. |