After upgrade from 1.7/stable to 1.8/stable: failed to look up namespace from the token: no namespace

Bug #2008760 reported by Diko Parvanov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vault-charm
New
High
Unassigned

Bug Description

After charm upgrade from 1.7/stable to 1.8/stable with vault snap refresh from 1.7/stable to 1.8/stable as well services can't communicate to vault with:

unit-nova-compute-kvm-sriov-0: 07:11:32 WARNING unit.nova-compute-kvm-sriov/0.post-series-upgrade hvac.exceptions.InternalServerError: error performing token check: failed to look up namespace from the token: no namespace, on post http://vault.pc1.canonical.com:8200/v1/sys/wrapping/unwrap

trying manually to create a token fails as well:

vault token create -ttl=10m
Error creating token: Error making API request.

URL: POST http://127.0.0.1:8200/v1/auth/token/create
Code: 500. Errors:

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

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

I've noticed an issue with config for the snap set to the default and it failing during the upgrade-charm hook as well.

Changed in vault-charm:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Liam Young (gnuoy) wrote :

When you say "with vault snap refresh from 1.7/stable to 1.8/stable as well" do you mean you manually issued the snap refresh to the 1.8 channel?

Do you have the steps you went through to do the upgrade?

Can you provide juju logs and vault logs from the vault units please ?

NOTE: From what I can tell namespaces are an enterprise feature which is strange.

Changed in vault-charm:
status: Triaged → Incomplete
Revision history for this message
Diko Parvanov (dparv) wrote :

The vault snap was refreshed by the charm, nothing manual. Unfortunately this was partner cloud and it was re-deployed couple of times since, so no logs.

It is a single step: juju upgrade-charm vault --channel 1.8/stable

Changed in vault-charm:
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.