Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • emulab-devel emulab-devel
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 164
    • Issues 164
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • emulabemulab
  • emulab-develemulab-devel
  • Merge requests
  • !5

AMv3 Status bugfix

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Wim Van de Meerssche requested to merge wvdemeer/emulab-devel:amv3-sliver-status-bugfix into master Apr 11, 2016
  • Overview 0
  • Commits 3
  • Changes 1

Occasionally, geni_ready was returned as reply to an AMv3 Status call, while the sliver was not at all ready yet. (This issue does not occur in AMv2.) That's bad for clients like jFed, which then stop periodically calling Status, and report to the user that everything is ready.

The cause was a bad fallback AMv3 status in case of an unknown internal status (geni_ready was the fallback). This fix just returns "unknown" in that case, which fixes the problem. (Because the "unknown" status seems to be only intermediary anyway.)

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: amv3-sliver-status-bugfix