Description of problem: Swift services started using swift-init cannot be managed with systemctl and vice versa. Version-Release number of selected component (if applicable): RDO Juno / RHEL7 How reproducible: 100% Steps to Reproduce for object-server, same for all swift service files: 1. run "swift-init start object" 2. run "systemctl status openstack-swift-object.service" 3. The object-server started by swift-init is not detected by "systemctl status" command. It must be stopped using "swift-init stop object" 4. run "systemctl start openstack-swift-object.service" 5. run "swift-init status object" 6. The object server started by systemctl is not detected by "swift-init status" command. Additional info: swift-init relies on pid file being created in /var/run/swift. The swift service files do not result in pid files being created. The two service management interfaces should be integrated better or should swift-init should be deprecated?
We always discouraged swift-init, because launching with swift-init makes processes run with the wrong SElinux context. It was the case even in RHEL 6, where you had to run service openstack-swift-blah start, despite the two using the same PID-based accounting. There should be no mention of swift-init in any of RDO, RHOS, or RHEL OSP documentation.
This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.