You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 7, 2020. It is now read-only.
"Issue Request" button should be disabled for keepalive check result.
Current Behavior
"Issue Request" button is enabled for keepalive check result. Using the "Issue Request" button for this check result will always return an error.
Possible Solution
Disable the "Issue Request" button for keepalive check on any client
Steps to Reproduce (for bugs)
Locate any non-proxy client in an Uchiwa instance
Click through to the keepalive check result view
Click "Issue Request"
Observe error notification
Context
As keepalive events are a special case (created by server on behalf of an AWOL client), specifying the keepalive check as part of a call to the /requests API endpoint will always fail.
Per sensu/sensu#1902, the option to "issue request" for keepalive check results is misleading.
Your Environment
Uchiwa version used: 1.3.1
Sensu version used: Sensu Enterprise 3.1
Operating System and version (e.g. Ubuntu 14.04): Ubuntu 16.04
The text was updated successfully, but these errors were encountered:
Expected Behavior
"Issue Request" button should be disabled for
keepalive
check result.Current Behavior
"Issue Request" button is enabled for
keepalive
check result. Using the "Issue Request" button for this check result will always return an error.Possible Solution
Disable the "Issue Request" button for
keepalive
check on any clientSteps to Reproduce (for bugs)
keepalive
check result viewContext
As
keepalive
events are a special case (created by server on behalf of an AWOL client), specifying thekeepalive
check as part of a call to the/requests
API endpoint will always fail.Per sensu/sensu#1902, the option to "issue request" for keepalive check results is misleading.
Your Environment
The text was updated successfully, but these errors were encountered: