swift_rsync exited in 2/3 controllers after hard reboot
Bug #1896605 reported by
Giulio Fidente
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Giulio Fidente |
Bug Description
While testing reboots, swift_rsync is only running on controller-1; it has status "exited(11)" on controller-0 and controller-2
This is a known issue [1] in handling stale pid files in rsyncd
1. https://<email address hidden>
Changed in tripleo: | |
assignee: | nobody → Giulio Fidente (gfidente) |
status: | Triaged → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/739859 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=43b5b0875d0 7bd3db29e83661a a32742dbef3544
Committed: https:/
Submitter: Zuul
Branch: master
commit 43b5b0875d07bd3 db29e83661aa327 42dbef3544
Author: Giulio Fidente <email address hidden>
Date: Tue Jul 7 23:47:12 2020 +0200
Configure rsyncd without pid file for Swift
There are known issues with stale pid file handling in rsyncd [1],
which by consequence cause Swift to not start.
This change disables use of pid file completely when deployed by
the swift-storage conainer and depends on the addition of such
a feature in the puppetlabs-rsync module [2]
1. https://<email address hidden> /msg32735. html /github. com/puppetlabs/ puppetlabs- rsync/pull/ 120
2. https:/
Closes-Bug: 1896605 5c046a678f4b2cc 51d1014e3b6
Change-Id: I81ad92793b8f11