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.

Sign up for GitHub

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

Jump to bottom

"Failed to read seal configuration" errors after upgrading to 0.10.2 #4721

Closed
mjacksonw opened this issue Jun 7, 2018 · 7 comments
Closed

"Failed to read seal configuration" errors after upgrading to 0.10.2 #4721

mjacksonw opened this issue Jun 7, 2018 · 7 comments
Milestone
0.10.3

Comments

@mjacksonw
Copy link

Describe the bug
After upgrading from 0.10.1 (or 0.10.0) to 0.10.2, vault produces the following errors:

[ERROR] core: failed to read seal configuration: error="UnmarshalTypeError: cannot unmarshal string into Go value of type []uint8"
[INFO ] core: security barrier not initialized

Environment:

  • Vault Server Version (retrieve with vault status): 0.10.2
  • Vault CLI Version (retrieve with vault version): 0.10.2
  • Server Operating System/Architecture: Alpine Linux 3.6 / Docker

Vault server configuration file(s):

listener "tcp" {
  address     = "0.0.0.0:8200"
  tls_disable = "true"
  proxy_protocol_behavior = "use_always"
  proxy_protocol_authorized_addrs = "REDACTED"
}

storage "dynamodb" {
  ha_enabled      = "true"
  region          = "us-east-1"
  table           = "REDACTED"
  advertise_addr  = "REDACTED"
  recovery_mode   = 1
}

disable_mlock = "true"
ui = "true"
@jefferai
Copy link
Member

jefferai commented Jun 7, 2018

Can you build a branch if I put in some debug?

@mjacksonw
Copy link
Author

mjacksonw commented Jun 7, 2018 •
edited
Loading

I can give it a try! Also, I just spun up a local version of 0.10.2 (on MacOS, against the same dynamodb table) and got the same error, so it's not likely related to the environment.

@mjacksonw
Copy link
Author

Yup, got a build env going, and confirmed I get the same issue against master (which is likely unsurprising).

@mjacksonw
Copy link
Author

Did a git bisect against the diff between 0.10.1 and 0.10.2 and came up against this seemingly-relevant commit:

39f2d66

@kalafut
Copy link
Contributor

kalafut commented Jun 7, 2018 •
edited
Loading

I landed at that same commit too through other means. I ran a forked version of our tests using the old write, but the new read, and get the error you reported. We're discussing next steps now.

Related PR: #4534

@kalafut kalafut mentioned this issue Jun 8, 2018
Merged
@jefferai jefferai added this to the 0.10.3 milestone Jun 11, 2018
@jefferai
Copy link
Member

This will be fixed in 0.10.3.

kalafut pushed a commit that referenced this issue Jun 12, 2018
Update aws-sdk-go deps
2a3756a 
Fixes #4721
Fixes #4742
@kalafut kalafut mentioned this issue Jun 12, 2018
Closed
kalafut pushed a commit that referenced this issue Jun 12, 2018
Update aws-sdk-go/service/dynamodb/dynamodbattribute
9b214f7 
Fixes #4721, Fixes #4742
@kalafut kalafut mentioned this issue Jun 12, 2018
Merged
kalafut added a commit that referenced this issue Jun 12, 2018
@kalafut
Update aws-sdk-go/service/dynamodb/dynamodbattribute (#4744)
d360428 
Fixes #4721, Fixes #4742
@kalafut
Copy link
Contributor

kalafut commented Jun 12, 2018

@mjacksonw Now that this is merged, if you get a chance to retest with master it would be a very useful confirmation that this fully fixed your issue.

@MattSurabian MattSurabian mentioned this issue Jun 15, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.10.3
Development

No branches or pull requests
3 participants
@jefferai @mjacksonw @kalafut