problems after upgrade from 0.10.3 to 1.0.1

528 views
Skip to first unread message

Khusro Jaleel

unread,
Dec 18, 2018, 10:49:53 AM12/18/18
to Vault
Hi, I am running Vault in an HA setup with 3 VMs. I upgraded it from 0.10.3 to 0.11.5 first, and I was able to do:

"$ vault login -method=ldap username=khusro.jaleel"

And this was working fine.

I have now upgraded my instances from 0.11.5 to 1.0.1 using the Linux AMD64 binary from [1] but I now get the following error when trying to login:

* error performing token check: failed to look up namespace from the token: no namespace

Isn't namespaces an enterprise only feature? Have I accidentally downloaded an Enterprise version of Vault? I tried going back to version "0.11.6" of the client side binary and also running a "0.11.5" server against the exact same data set, but I still get the exact same error. Is this fixable?

I also noticed that 1.0.1 isn't available on the main Downloads link, is there a reason for that?




Jeff Mitchell

unread,
Dec 18, 2018, 2:55:15 PM12/18/18
to Vault
Hi,

Can you try using the -token-only flag to "vault login" and, if it's successful, can you paste an example token? (You can send it to me directly at jeff at the company I work for dot com). I don't really see a path for this to happen on a fresh authentication and nobody else has been reporting this kind of issue so it'd be useful to see if the format you're getting is something odd.

As for the version, our website changed recently and I think it broke the automatic version fetching. I'll get it updated.

Thanks,
Jeff

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/vault-tool/167d5bec-b74c-4bec-a9e6-e659c4cae5d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Khusro Jaleel

unread,
Jan 9, 2019, 6:13:10 AM1/9/19
to Vault
Hi Jeff,

Apologies for the late reply. In the end I decided to restore the data from an older backup we had lying around. When doing the upgrades, I was upgrading the standby nodes first, and then the primary as the upgrade guide mentions. But could this have caused an issue, because of the mixture of versions accessing the same backend? Maybe it would have been better to shut them all down when doing the upgrade?

Thanks,
Khusro
Reply all
Reply to author
Forward
0 new messages