Skip to content

account assertion not obtained, hard to debug #225

@knitzsche

Description

@knitzsche

Hi,

A customer installed SV Version: 2.4-6 and could not get it to provide the signed serial despite everything else seeming to be OK (gadget, SV Model config, etc. ) I found that their Account (for the brand account) in the SV did not have an account assertion. I was able to obtain the assertion from CLI, and they deleted the Account in SV and created it again, this time pasting the assertion in. And it worked. There were a couple confusing parts to this:

  1. On the Accounts page of the SV, it showed for the account key: "No account key assertion found". And I think (but I am not totally sure) that it showed the Account "Assertion Status" with a check. But the root cause was, as I said, no account assertion.

  2. Not sure why the SV cannot/did not simply get the Account assertion, since, even for brand accounts, this is publicly available like so: snap known --remote account account-id=ACCOUNT_ID

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions