Activity log for bug #1466101

Date Who What changed Old value New value Message
2015-06-17 14:07:02 Ksenia Svechnikova bug added bug
2015-06-17 14:30:11 Ksenia Svechnikova mos: importance Undecided Medium
2015-06-17 14:48:17 Alexey Khivin tags customer-found customer-found swift
2015-06-19 12:26:55 Dmitry Mescheryakov mos: status New Confirmed
2015-06-19 12:27:02 Dmitry Mescheryakov nominated for series mos/6.1.x
2015-06-19 12:27:02 Dmitry Mescheryakov bug task added mos/6.1.x
2015-06-19 12:27:02 Dmitry Mescheryakov nominated for series mos/7.0.x
2015-06-19 12:27:02 Dmitry Mescheryakov bug task added mos/7.0.x
2015-06-19 12:27:06 Dmitry Mescheryakov mos/6.1.x: status New Confirmed
2015-06-19 12:27:08 Dmitry Mescheryakov mos/6.1.x: importance Undecided Medium
2015-06-19 12:27:15 Dmitry Mescheryakov mos/6.1.x: assignee MOS Deployment Team (mos-deployment)
2015-06-19 12:27:22 Dmitry Mescheryakov mos/7.0.x: assignee MOS Swift (mos-swift) MOS Deployment Team (mos-deployment)
2015-06-19 12:27:25 Dmitry Mescheryakov mos/7.0.x: milestone 6.1 7.0
2015-06-19 12:27:28 Dmitry Mescheryakov mos/6.1.x: milestone 6.1-updates
2015-06-19 13:17:21 Ksenia Svechnikova description Version: 6.1, #521 Steps to reproduce: 1. Install environment with Swift (3 controllers and 2 compute nodes) 2. Check swift-object-replicator is running in swift-init: root@node-4:~# swift-init all status | grep replicat object-replicator running (8320 - /etc/swift/object-server.conf) container-replicator running (8321 - /etc/swift/container-server.conf) account-replicator running (8311 - /etc/swift/account-server.conf) 3. Check the process is running: root@node-4:~# ps aux | grep swift-object-replicator root 6809 0.0 0.0 10460 944 pts/3 S+ 12:59 0:00 grep --color=auto swift-object-replicator swift 8320 0.2 0.0 1554688 26088 ? Ssl Jun16 3:08 /usr/bin/python /usr/bin/swift-object-replicator /etc/swift/object-server.conf root@node-4:~# service swift-object-replicator status swift-object-replicator start/running 4. Kill the process and confirm it is killed: root@node-4:~# kill -9 8320 root@node-4:~# ps aux | grep swift-object-replicator root 13225 0.0 0.0 10460 940 pts/3 S+ 13:02 0:00 grep --color=auto swift-object-replicator Then you can see not appropriate behavior of upstart mechanism: 1. The "service swift-xxx start/stop/status" doesn't have valid information about the process status after the process is killed: root@node-4:~# service swift-object-replicator status swift-object-replicator start/running root@node-4:~# ps aux | grep swift-object-replicator root 13225 0.0 0.0 10460 940 pts/3 S+ 13:02 0:00 grep --color=auto swift-object-replicator root@node-4:~# service swift-object-replicator start start: Job is already running: swift-object-replicator 2. The pid file is still there, while it should be removed, when process is killed: root@node-4:~# ps -ef | grep object-replicator swift 11609 1 0 13:22 ? 00:00:01 /usr/bin/python /usr/bin/swift-object-replicator /etc/swift/object-server.conf root 22261 24310 0 13:29 pts/3 00:00:00 grep --color=auto object-replicator root@node-4:~# kill -9 11609 root@node-4:~# cat /var/run/swift/object-replicator.pid 11609 Meanwhile, if after the process is killed you will run "service stop", it will give a message "Job failed while stopping", but it will delete the pid and "service status" will work fine: root@node-4:~# kill -9 11609 root@node4: service swift-object-replicator stop stop: Job failed while stopping root@node-4:~# service swift-object-replicator status swift-object-replicator stop/waiting root@node-4:~# cat /var/run/swift/object-replicator.pid cat: /var/run/swift/object-replicator.pid: No such file or directory Version: 6.1, #521 Steps to reproduce: 1. Install environment with Swift (3 controllers and 2 compute nodes) 2. Check swift-object-replicator is running in swift-init: root@node-4:~# swift-init all status | grep replicat object-replicator running (8320 - /etc/swift/object-server.conf) container-replicator running (8321 - /etc/swift/container-server.conf) account-replicator running (8311 - /etc/swift/account-server.conf) 3. Check the process is running: root@node-4:~# ps aux | grep swift-object-replicator root 6809 0.0 0.0 10460 944 pts/3 S+ 12:59 0:00 grep --color=auto swift-object-replicator swift 8320 0.2 0.0 1554688 26088 ? Ssl Jun16 3:08 /usr/bin/python /usr/bin/swift-object-replicator /etc/swift/object-server.conf root@node-4:~# service swift-object-replicator status swift-object-replicator start/running 4. Kill the process and confirm it is killed: root@node-4:~# kill 8320 root@node-4:~# ps aux | grep swift-object-replicator root 13225 0.0 0.0 10460 940 pts/3 S+ 13:02 0:00 grep --color=auto swift-object-replicator Then you can see not appropriate behavior of upstart mechanism: 1. The "service swift-xxx start/stop/status" doesn't have valid information about the process status after the process is killed: root@node-4:~# service swift-object-replicator status swift-object-replicator start/running root@node-4:~# ps aux | grep swift-object-replicator root 13225 0.0 0.0 10460 940 pts/3 S+ 13:02 0:00 grep --color=auto swift-object-replicator root@node-4:~# service swift-object-replicator start start: Job is already running: swift-object-replicator 2. The pid file is still there, while it should be removed, when process is killed: root@node-4:~# ps -ef | grep object-replicator swift 11609 1 0 13:22 ? 00:00:01 /usr/bin/python /usr/bin/swift-object-replicator /etc/swift/object-server.conf root 22261 24310 0 13:29 pts/3 00:00:00 grep --color=auto object-replicator root@node-4:~# kill 11609 root@node-4:~# cat /var/run/swift/object-replicator.pid 11609 Meanwhile, if after the process is killed you will run "service stop", it will give a message "Job failed while stopping", but it will delete the pid and "service status" will work fine: root@node-4:~# kill 11609 root@node4: service swift-object-replicator stop stop: Job failed while stopping root@node-4:~# service swift-object-replicator status swift-object-replicator stop/waiting root@node-4:~# cat /var/run/swift/object-replicator.pid cat: /var/run/swift/object-replicator.pid: No such file or directory
2015-06-24 12:28:44 Alexander Rubtsov bug added subscriber Alexander Rubtsov
2015-06-24 12:51:21 Alexey Khivin nominated for series mos/5.1.1-updates
2015-06-24 12:51:21 Alexey Khivin bug task added mos/5.1.1-updates
2015-06-24 12:51:34 Alexey Khivin mos/5.1.1-updates: importance Undecided Medium
2015-06-24 12:51:56 Alexey Khivin mos/5.1.1-updates: assignee MOS Sustaining (mos-sustaining)
2015-06-24 12:52:06 Alexey Khivin mos/5.1.1-updates: milestone 5.1.1-updates
2015-06-24 12:53:17 Alexey Khivin mos/5.1.1-updates: status New Confirmed
2015-07-17 14:32:26 Ivan Udovichenko mos/7.0.x: assignee MOS Deployment Team (mos-deployment) MOS Packaging Team (mos-packaging)
2015-07-17 14:32:32 Ivan Udovichenko mos/7.0.x: status Confirmed Fix Committed
2015-07-20 21:13:27 Vitaly Sedelnik nominated for series mos/5.1-updates
2015-07-20 21:13:27 Vitaly Sedelnik bug task added mos/5.1-updates
2015-07-20 21:13:32 Vitaly Sedelnik mos/5.1-updates: status New Confirmed
2015-07-20 21:13:43 Vitaly Sedelnik mos/5.1-updates: importance Undecided High
2015-07-20 21:13:46 Vitaly Sedelnik mos/5.1.1-updates: importance Medium High
2015-07-20 21:13:53 Vitaly Sedelnik mos/5.1-updates: assignee Alex Khivin (akhivin)
2015-07-20 21:14:01 Vitaly Sedelnik mos/5.1.1-updates: assignee MOS Sustaining (mos-sustaining) Alex Khivin (akhivin)
2015-07-20 21:14:08 Vitaly Sedelnik mos/5.1.1-updates: milestone 5.1.1-updates 5.1.1-mu-2
2015-07-20 21:14:15 Vitaly Sedelnik mos/5.1-updates: milestone 5.1-mu-2
2015-07-24 14:14:23 Vitaly Sedelnik mos/5.1-updates: status Confirmed In Progress
2015-07-24 14:14:25 Vitaly Sedelnik mos/5.1.1-updates: status Confirmed In Progress
2015-07-24 14:14:37 Vitaly Sedelnik mos/5.1-updates: assignee Alexey Khivin (akhivin) Alexander Nevenchannyy (anevenchannyy)
2015-07-24 14:14:45 Vitaly Sedelnik mos/5.1.1-updates: assignee Alexey Khivin (akhivin) Alexander Nevenchannyy (anevenchannyy)
2015-07-24 16:23:54 Alexander Nevenchannyy mos/5.1.1-updates: status In Progress Fix Committed
2015-07-24 17:13:41 Vitaly Sedelnik mos/5.1-updates: status In Progress Fix Committed
2015-07-27 13:56:33 Sergey Novikov mos/5.1-updates: status Fix Committed Confirmed
2015-07-27 13:56:36 Sergey Novikov mos/5.1.1-updates: status Fix Committed Confirmed
2015-07-31 13:51:35 Alexander Nevenchannyy mos/5.1.1-updates: status Confirmed Fix Committed
2015-07-31 15:13:26 Alexander Nevenchannyy mos/6.1.x: assignee MOS Deployment Automation Team (mos-da) Alexander Nevenchannyy (anevenchannyy)
2015-07-31 15:13:32 Alexander Nevenchannyy mos/5.1-updates: status Confirmed Fix Committed
2015-07-31 15:16:02 Alexander Nevenchannyy nominated for series mos/6.0-updates
2015-07-31 15:16:02 Alexander Nevenchannyy bug task added mos/6.0-updates
2015-07-31 15:16:08 Alexander Nevenchannyy mos/6.0-updates: status New Confirmed
2015-07-31 15:16:11 Alexander Nevenchannyy mos/6.0-updates: importance Undecided High
2015-07-31 15:16:14 Alexander Nevenchannyy mos/6.0-updates: assignee Alexander Nevenchannyy (anevenchannyy)
2015-07-31 15:16:19 Alexander Nevenchannyy mos/6.0-updates: milestone 6.0-mu-5
2015-08-03 13:30:18 Alexander Nevenchannyy mos/6.0-updates: status Confirmed In Progress
2015-08-04 11:38:54 Alexander Nevenchannyy mos/6.0-updates: status In Progress Fix Committed
2015-08-06 13:48:56 Vadim Rovachev mos/6.0-updates: status Fix Committed Fix Released
2015-08-06 16:40:53 Sergey Novikov mos/5.1-updates: status Fix Committed Fix Released
2015-08-06 16:40:56 Sergey Novikov mos/5.1.1-updates: status Fix Committed Fix Released
2015-08-11 16:29:01 Olena Logvinova tags customer-found swift 6.0-mu-5 customer-found done release-notes swift
2015-08-17 08:27:37 Vitaly Sedelnik mos/6.1.x: milestone 6.1-updates 6.1-mu-2
2015-08-18 09:25:17 Vitaly Sedelnik mos/6.1.x: milestone 6.1-mu-2 6.1-mu-3
2015-08-24 12:36:08 Ivan Ponomarev mos/7.0.x: status Fix Committed Fix Released
2015-09-14 11:27:14 Olena Logvinova tags 6.0-mu-5 customer-found done release-notes swift 6.0-mu-5 customer-found release-notes-done-7.0 swift
2015-09-14 16:12:15 Olena Logvinova tags 6.0-mu-5 customer-found release-notes-done-7.0 swift customer-found release-notes-done rn6.0-mu-5 rn7.0 swift
2015-09-17 00:06:35 Roman Rufanov tags customer-found release-notes-done rn6.0-mu-5 rn7.0 swift customer-found release-notes-done rn6.0-mu-5 rn7.0 support swift
2015-09-26 09:44:07 Vitaly Sedelnik nominated for series mos/5.1.x
2015-09-26 09:44:07 Vitaly Sedelnik bug task added mos/5.1.x
2015-09-26 09:44:23 Vitaly Sedelnik mos/5.1.x: status New In Progress
2015-09-26 09:44:26 Vitaly Sedelnik mos/5.1.x: importance Undecided High
2015-09-26 09:44:34 Vitaly Sedelnik mos/5.1.x: assignee Alexander Nevenchannyy (anevenchannyy)
2015-09-26 09:44:40 Vitaly Sedelnik mos/5.1.x: milestone 5.1.1-mu-2
2015-09-26 13:32:15 Vitaly Sedelnik nominated for series mos/6.0.x
2015-09-26 13:32:15 Vitaly Sedelnik bug task added mos/6.0.x
2015-09-26 13:32:21 Vitaly Sedelnik mos/6.0.x: status New Fix Released
2015-09-26 13:32:23 Vitaly Sedelnik mos/6.0.x: importance Undecided High
2015-09-26 13:32:31 Vitaly Sedelnik mos/6.0.x: assignee Alexander Nevenchannyy (anevenchannyy)
2015-09-26 13:32:34 Vitaly Sedelnik mos/6.0.x: milestone 6.0-mu-5
2015-10-05 12:08:16 Alexander Nevenchannyy mos/6.1.x: status Confirmed In Progress
2015-10-09 10:36:18 Vitaly Sedelnik mos/6.1.x: status In Progress Fix Committed
2015-10-10 19:46:43 Alexander Nevenchannyy mos/5.1.x: status In Progress Fix Released
2015-10-15 16:26:36 Vadim Rovachev mos/6.1.x: status Fix Committed Confirmed
2015-10-15 21:05:41 Vitaly Sedelnik mos/6.1.x: status Confirmed Fix Committed
2015-10-28 15:15:49 Vitaly Sedelnik mos/6.1.x: status Fix Committed Fix Released