Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 277
    • Issues 277
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 25
    • Merge requests 25
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • storkstork
  • Issues
  • #360
Closed
Open
Issue created Aug 04, 2020 by Tomek Mrugalski@tomek🛰Owner

UI can't retrieve data (server side events broken?)

On the latest master (8fa94508), I have clean stork running, using rake docker_up.

I've observed a plethora of problems:

  1. added agent-kea, which initially worked ok, but later (after couple mins) reported comm problem with the dhcpv4 and ca daemons ("There is observed issue in communication with the daemon.", see screenshot 1)
  2. added agent-kea-ha1, agent-kea-ha2, they report losing communication. ha1 becomes unreachable, ha2 reports partner down (see screenshot 2)
  3. the RPS and pool utilization is not updated anymore (clicking refresh buttons in the ui, pressing ctrl-r doesn't change a thing, see screenshot 3)
  4. the daemons status is broken (shows all as grey no-entry sign, but when you hover your cursor over it, some say the communication is ok, see screenshot 4)

I'm reporting all of those in a single issue, because I believe most of them (maybe except the log viewer) can be explained with a problem with server side events. More on this in the first comment.

SCREENSHOT 1 (lost comm with dhcpv4 and ca running on agent-kea) Screenshot_2020-08-04_at_19.10.28

SCREENSHOT 2 (ha1 lost comm with its partner) Screenshot_2020-08-04_at_19.13.27

SCREENSHOT 3 (dashboard not updated) Screenshot_2020-08-04_at_19.17.15

SCREENSHOT 4 (broken app status update) Screenshot_2020-08-04_at_19.18.54

Edited Aug 10, 2020 by Michal Nowikowski
Assignee
Assign to
Time tracking