Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 214
    • Issues 214
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 15
    • Merge requests 15
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • storkstork
  • Issues
  • #528

Closed
Open
Created Apr 09, 2021 by Tomek Mrugalski@tomek🛰Owner

Restarting agent service triggers re-registration (sanity checks)

This was reported by @marcin during 0.15 sanity checks:

When the user restarts the agent service:

$ systemctl service restart isc-agent-service

the registration starts over. The agent which used to be authorized is now back to unauthorized agents and again requires an approval. This is not right. We should have a way to determine that the agent has been already registered and do not re-register. Maybe simply trying to ping itself via the server would be sufficient to see that the connection can be established.

Assignee
Assign to
Time tracking