0e79e1a46e
Keep stream and logs in sync for detecting closed pipe
2018-05-09 11:22:52 -07:00
71ad33fb26
Add link to privacy policy in website footer
...
Added link to updated privacy policy in footer of `layout.erb` for the OSS website.
2018-05-09 12:13:55 -06:00
62f99cc629
Addressed review comments
2018-05-09 13:21:35 -04:00
74f3263073
Merge pull request #4265 from hashicorp/b-fix-cpu-fingerprinter-error-msg
...
Fix the CPU Information error message
2018-05-09 13:15:07 -04:00
ef531b0f34
Add unit tests for forced rescheduling
2018-05-09 11:30:42 -05:00
d51611040f
Add driver health information to node list stub
2018-05-09 11:21:54 -04:00
1b8d8b2186
Fix logic inversion in force rescheduling
2018-05-08 20:00:06 -05:00
c1b92c284e
Work in progress - force rescheduling of failed allocs
2018-05-08 17:26:57 -05:00
1dc39a1d4c
update CHANGELOG
2018-05-08 17:07:10 -05:00
210d520a94
changelog
2018-05-08 14:57:10 -07:00
e7ae6e98d9
Merge pull request #4259 from hashicorp/f-deployment-improvements
2018-05-08 16:37:10 -05:00
d64b02f07d
Override 3 sec. WMI timeout in gopsutil
...
The default timeout is too short for some overburdened or resource
constrained machines to complete the WMI query before the context
deadline expires. This causes them to be unable to fingerprint the CPU
properly.
2018-05-08 17:00:31 -04:00
3598925ca4
client/driver: use correct repo address when using docker-credential helper
2018-05-08 15:17:28 -04:00
893b01158c
Fix the CPU Information error message
...
The new version of gopsutil introduces a 3 second timeout that could come up as an error here; however, we are outputting the wrong variable and eating the error.
2018-05-08 14:11:29 -04:00
c42340ca48
Merge pull request #4179 from hashicorp/f-retry-join
...
Cloud Auto Join
2018-05-08 13:00:02 -04:00
9ee8e248d3
Merge pull request #4262 from hashicorp/b-3720-optional-meta
...
client/driver/env: interpolate empty optional meta params as empty strings
2018-05-07 20:44:02 -04:00
54c86a0292
client/driver/env: interpolate empty optional meta params as empty strings
2018-05-07 20:19:51 -04:00
136635f04d
only write error log line on error
2018-05-07 16:57:07 -04:00
30584639b5
remove log line for empty addresses which could confuse on initalization
2018-05-07 16:57:07 -04:00
24ff40df01
retry until all options are exhausted
2018-05-07 16:57:07 -04:00
ec4be4f871
ensure provider= is always the string prefix
2018-05-07 16:57:07 -04:00
5422b1b088
update test for more realistic IP address from go-discover
2018-05-07 16:57:07 -04:00
8d3c739832
remove unused dependencies
2018-05-07 16:57:07 -04:00
d215326de7
update go-discover
2018-05-07 16:57:07 -04:00
a6aa2f6bfa
vendor go-discover
2018-05-07 16:57:07 -04:00
7e4d4f8088
comments and other fixups
2018-05-07 16:57:06 -04:00
8f584f6474
add go-discover
2018-05-07 16:57:06 -04:00
25ad6eaf96
refactor to retryJoiner interface
2018-05-07 16:57:06 -04:00
00930a4f88
Merge pull request #4261 from hashicorp/f-docker-progress-detection
...
client/driver: remove unused const 'dockerPullProgressEmitInterval'
2018-05-07 16:27:19 -04:00
016ab7a105
client/driver: remove unused const 'dockerPullProgressEmitInterval'
2018-05-07 16:24:48 -04:00
c7edbd5f41
newlines in test
2018-05-07 14:55:01 -05:00
4e75456beb
Fix deadlock in deadline timer logic when progress deadline is passed and the deployment is updated.
2018-05-07 14:55:01 -05:00
cba13e4ec5
Fix test set up to set ModifyTime for alloc
2018-05-07 14:55:01 -05:00
19b096d203
Set modify time for allocs in unit test, and define current time in one spot
2018-05-07 14:55:01 -05:00
4c377b112e
Fix panic in deployment watcher when deployment is not in the state store due to a gc
2018-05-07 14:55:01 -05:00
02d63432b4
Fix typo
2018-05-07 14:55:01 -05:00
6c09379bd7
Update end to end tests to use shorter progress deadlines
2018-05-07 14:55:01 -05:00
738056634e
Fix the initial progress deadline calculation when the alloc is inplace updated to be part of a new deployment
2018-05-07 14:55:01 -05:00
b2e89d69d8
More e2e test fixes after changes to rescheduling during deployments
2018-05-07 14:55:01 -05:00
02567ade71
Some test fixes to e2e rescheduling tests
2018-05-07 14:55:01 -05:00
e90d051c43
consul: change hashed canary bytes
2018-05-07 14:55:01 -05:00
555d14fd92
Add test
2018-05-07 14:55:01 -05:00
cf44670d56
Make sure that task group has a deployment state before using it
2018-05-07 14:55:01 -05:00
c6478d9469
clarify comment
2018-05-07 14:55:01 -05:00
768fec8505
Allow healthy canary deployment to skip progress deadline
2018-05-07 14:55:01 -05:00
8626c1b94a
Reschedule when we have canaries properly
2018-05-07 14:55:01 -05:00
f1d13683e6
consul: remove services with/without canary tags
...
Guard against Canary being set to false at the same time as an
allocation is being stopped: this could cause RemoveTask to be called
with the wrong Canary value and leaking a service.
Deleting both Canary values is the safest route.
2018-05-07 14:55:01 -05:00
50e04c976e
consul: support canary tags for services
...
Also refactor Consul ServiceClient to take a struct instead of a massive
set of arguments. Meant updating a lot of code but it should be far
easier to extend in the future as you will only need to update a single
struct instead of every single call site.
Adds an e2e test for canary tags.
2018-05-07 14:55:01 -05:00
a3038cefb4
typo: transistion -> transition
2018-05-07 14:50:01 -05:00
8dee3ab068
canary reschedule test
2018-05-07 14:50:01 -05:00
Alex Dadgar