Skip to content

Sled Agent service launching should cope with U.2s that might not be ready yet #2973

@smklein

Description

@smklein
  • RSS / Nexus both tell sled agent to launch services
  • If we succeed when starting a service, the sled agent stores "here are the services I should launch on cold boot" in the M.2 configuration dataset
  • On reboot, we read this list of services from the M.2 and try to start 'em.

RIGHT NOW if we fail to start those services, we don't try again.

This is a bummer! Especially with the dependencies on U.2s - which might take a sec to load - we should add a retry-with-backoff to service launching, kinda like we already do for the NTP and Switch zones.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions