Failed to mount cubbyhole, 0.6.5 to 0.7.0 upgrade

[broamski]

Upon attempted upgrade from 0.6.5 to 0.7.0 I'm receiving the following in the log:

failed to mount entry: path=cubbyhole/ error=cannot mount under existing mount 'cubbyhole/'

Enabling trace level logging provides no further detail. I'm using the postgresql backend and no HA.

[Brian Nuszkowski]

I failed to mention I also receive this:

post-unseal setup failed: error=failed to setup mount table

Here's the entire block:

[ERROR] core: failed to mount entry: path=cubbyhole/ error=cannot mount under existing mount 'cubbyhole/'

[INFO ] core: pre-seal teardown starting

[TRACE] core: clustering disabled, not stopping listeners

[INFO ] core: pre-seal teardown complete

[ERROR] core: post-unseal setup failed: error=failed to setup mount table

[WARN ] core: vault is sealed

Thanks.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/vault/issues
IRC: #vault-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Vault" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vault-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vault-tool/6f8f1d79-fad8-4d0a-af81-172f9bd88372%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jeff Mitchell]

Hi Brian,

I just tried this upgrade on a fresh install with the 'file' backend and can't replicate this behavior. Did you go straight from 0.6.5 to 0.7.0 or did you hit a beta along the way? Also, can you share (privately if you want) the output of 'vault mounts' from the 0.7.0 binary against your 0.6.5 server?

Best,

Jeff

To view this discussion on the web visit https://groups.google.com/d/msgid/vault-tool/CAFHTOcdZAPnpjct7s2yMjbmQ6QTFsnT5UBthAZM-3%3D_sbCaOvQ%40mail.gmail.com.

[Jeff Mitchell]

Actually as a follow-up: are you sure you got the final 0.7 binary on the server rather than the beta? Stupid question I know, but please indulge me in checking!

Best,

Jeff

[Gobin]

Hi Brian,

Were you able to upgrade to 0.7.0 release? We are facing a similar issue, it'd be good to know if and how you got the issue sorted.

Thanks,

Gobin

To unsubscribe from this group and stop receiving emails from it, send an email to vault-tool+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vault-tool/6f8f1d79-fad8-4d0a-af81-172f9bd88372%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/vault/issues
IRC: #vault-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Vault" group.

To unsubscribe from this group and stop receiving emails from it, send an email to vault-tool+...@googlegroups.com.

[Jeff Mitchell]

Hi Gobin,

Brian's issue got sorted, but there, and in all other cases, this has
been caused by a downgrade of Vault against a data store that was
upgraded to 0.7. When you are going through your upgrade procedure,
somewhere along the way you're having a 0.7 Vault take over, then a
0.6.5 Vault is taking over.

Best,
Jeff

> https://groups.google.com/d/msgid/vault-tool/98420aa1-8b98-4431-a07f-77755cf2cb0d%40googlegroups.com.

[Gobin]

Thanks Jeff.

Linking our github response and the fix to our issue:

https://github.com/hashicorp/vault/issues/2520#issuecomment-303552618

Regards,

Gobin