Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't query for stats if the node is down and handle the errors #1844

Merged
merged 2 commits into from
Oct 25, 2016

Conversation

dadgar
Copy link
Contributor

@dadgar dadgar commented Oct 21, 2016

No description provided.

Copy link
Member

@schmichael schmichael left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -8,6 +8,12 @@ import (
"github.com/hashicorp/go-cleanhttp"
)

var (
// NodeDownErr marks an operational as not able to complete since the node
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

an opertational -> an operation

@@ -233,8 +233,10 @@ func (c *AllocStatusCommand) Run(args []string) int {
var stats *api.AllocResourceUsage
stats, statsErr = client.Allocations().Stats(alloc, nil)
if statsErr != nil {
c.Ui.Output("")
c.Ui.Error(fmt.Sprintf("couldn't retrieve stats (HINT: ensure Client.Advertise.HTTP is set): %v", statsErr))
if statsErr != api.NodeDownErr {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wonder if we should show a message that the node is down if statsErr == api.NodeDownErr ?

@dadgar dadgar merged commit 772c04e into master Oct 25, 2016
@dadgar dadgar deleted the b-alloc-stats branch October 25, 2016 18:31
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants