Ubuntu swift packages lack systemd unit files

Bug #1800676 reported by Neil Wilson on 2018-10-30
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
swift (Ubuntu)
Medium
Sahid Orentino

Bug Description

The Debian upstream packages for swift have had Systemd unit support since

swift (2.6.0-2) experimental; urgency=medium

  [ Ondřej Nový ]
  * Added Debian tests.
  * Removed swift-init.
  * Systemd support.
  * Added container-sync config files.
  * Changed all dependencies to same version of swift package.
  * Changed shell of "swift" user to /bin/false.
  * Add user "swift" to group "adm", not replace group list.
  * Standards-Version is 3.9.7 now (no change).
  * Fixed Vcs URL.

but none of that appears to have made it past the merge process into the Ubuntu versions. We are now in the situation where the Bionic and Cosmic packages are still relying upon dated init scripts, and contain obsolete Upstart init files.

Is there a case for dropping the diff completely?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: swift-container (not installed)
ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Tue Oct 30 15:29:16 2018
SourcePackage: swift
UpgradeStatus: Upgraded to bionic on 2018-10-30 (0 days ago)

Neil Wilson (neil-aldur) wrote :
Corey Bryant (corey.bryant) wrote :

Hi Neil,

Thank you for reporting this and making Ubuntu better. The Ubuntu packages originate in Ubuntu and are not based on the Debian packages. The Ubuntu packages have had systemd unit support since Vivid. Please can you add some details for the missing unit files?

Thanks,
Corey

Changed in swift (Ubuntu):
status: New → Incomplete
Neil Wilson (neil-aldur) wrote :

For example proxy is LSB generated, not systemd native

$ systemctl status swift-proxy
● swift-proxy.service - LSB: Swift proxy server
   Loaded: loaded (/etc/init.d/swift-proxy; generated)
   Active: active (running) since Fri 2018-10-26 15:13:07 UTC; 1 weeks 2 days ago
     Docs: man:systemd-sysv-generator(8)
    Tasks: 3 (limit: 2362)
   CGroup: /system.slice/swift-proxy.service
           ├─9718 /usr/bin/python /usr/bin/swift-proxy-server /etc/swift/proxy-server.conf
           ├─9728 /usr/bin/python /usr/bin/swift-proxy-server /etc/swift/proxy-server.conf
           └─9729 /usr/bin/python /usr/bin/swift-proxy-server /etc/swift/proxy-server.conf

Similarly if you look at the package file list of any of the swift built packages in ubuntu you will see SysV scripts, Upstart conf files, but no native systemd unit files.

https://packages.ubuntu.com/bionic/all/swift-account/filelist
https://packages.ubuntu.com/bionic/all/swift-proxy/filelist
https://packages.ubuntu.com/bionic/all/swift-container/filelist
https://packages.ubuntu.com/bionic/all/swift-object/filelist
https://packages.ubuntu.com/bionic/all/swift-object-expirer/filelist

Corey Bryant (corey.bryant) wrote :

You are right, the packages do in fact lack systemd unit files. While the SysV scripts and generated files work as is, we should stil add systemd unit files and align with the rest of the openstack packages. Also we are overdue for dropping upstart scripts from the packages now that we are no longer backporting openstack releases to the cloud archive for trusty. Note that the upstart scripts shouldn't be causing any issues.

Changed in swift (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
Changed in swift (Ubuntu):
assignee: nobody → Sahid Orentino (sahid-ferdjaoui)
James Page (james-page) on 2019-12-03
Changed in swift (Ubuntu):
milestone: none → ubuntu-19.12
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers