[Bug 1636322] [NEW] [SRU] upstart: ceph-all service starts before networks up

Launchpad Bug Tracker 1636322 at bugs.launchpad.net
Tue Mar 28 09:22:49 UTC 2017


You have been subscribed to a public bug by Edward Hope-Morley (hopem):

As reported in upstream bug http://tracker.ceph.com/issues/17689, the
ceph-all service starts at runlevels [2345] and introduces a race
condition which allows the ceph service (e.g. ceph-mon) to start prior
to the network the service binds to is up on the server. This causes the
service to fail on start because it was unable to bind to the specific
network the service is configured to listen on.

A work around is to provide a post-up directive to the network stanza
configuring the network device in the /etc/network/interfaces file which
restarts the necessary ceph service.

[Impact]

 * Ceph service fails to start on reboot of machine/container when
networking takes some time to come up.

 * The provided patch to the upstart service configuration adds the
static-network-up event as a dependency for the start on service
directive. The static-network-up event is started after all the network
stanzas have been processed in the necessary config files.

[Test Case]

* Configure multiple network interfaces and have the ceph service bind
to one of the last configured network devices to introduce a delayed
start of the network interface.

[Regression Potential]

* Upstream previously had the directive to start the service after any
network-device-up for a network which is not the loopback interface.
This caused some "weirdness" to be seen when the multiple network
interfaces were configured. This was likely due the events that it keyed
on being the local filesystems being available and a single network
interface being available. This would add the change to start only after
all the network interface stanzas are processed in the /e/n/i
configuration files.

* Additionally, this will cause some ceph services to start later than
they previously would have since this change causes additional start
dependencies. However, the results should be that the interfaces have
always had a chance to be started prior to the attempt to start the ceph
service.

** Affects: cloud-archive
     Importance: High
         Status: Triaged

** Affects: cloud-archive/icehouse
     Importance: High
         Status: Triaged

** Affects: cloud-archive/kilo
     Importance: High
         Status: Triaged

** Affects: cloud-archive/liberty
     Importance: High
         Status: Triaged

** Affects: cloud-archive/mitaka
     Importance: High
         Status: Triaged

** Affects: ceph (Ubuntu)
     Importance: High
     Assignee: Billy Olsen (billy-olsen)
         Status: Fix Released

** Affects: ceph (Ubuntu Trusty)
     Importance: Undecided
         Status: New

** Affects: ceph (Ubuntu Xenial)
     Importance: Undecided
         Status: New

** Affects: ceph (Ubuntu Yakkety)
     Importance: Undecided
         Status: New

** Affects: ceph (Ubuntu Zesty)
     Importance: High
     Assignee: Billy Olsen (billy-olsen)
         Status: Fix Released


** Tags: patch sts sts-sponsor sts-sru-needed
-- 
[SRU] upstart: ceph-all service starts before networks up
https://bugs.launchpad.net/bugs/1636322
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list