Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • S slapos.core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slapos.core
  • Merge requests
  • !251

Merged
Created Sep 16, 2020 by Jérome Perrin@jeromeOwner

grid: Keep using the previous socket path name if it still exists

  • Overview 18
  • Commits 2
  • Pipelines 5
  • Changes 5

In 58fbaabf (svcbackend/standalone: use shorter names for supervisor sockets , 2020-07-17) we changed the socket path from supervisord.sock to a shorter sv.sock, but this caused issues when updating running slapos node instances, because this was trying to start a new supervisord process using the new socket path, while the old one was still running.

To keep services running after upgrade, introduce a compatibility layer in this socket path - if we still have a supervisord running with a socket at this previous path, keep using this old socket name.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: fix/supervisor_socket_path_change
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7