Labels not showing up when using faasd on Multipass

[kadern0]

Labels not showing up when running faas-cli describe function

Steps to Reproduce

1. Followed this guide to get faasd running locally with multipass -> https://gist.github.com/alexellis/6d297e678c9243d326c151028a3ad7b9

(I've tried faasd versions: 0.7.7 and 0.7.8)

2. Deploy function with labels:

WARNING! Communication is not secure, please consider using HTTPS. Letsencrypt.org offers free SSL/TLS certificates.

Deployed. 200 OK.
URL: http://127.0.0.1:8080/function/figlet

3. Describe deployed function:

Name:                figlet
Status:              Ready
Replicas:            1
Available replicas:  1
Invocations:         4
Image:               
Function process:    
URL:                 http://127.0.0.1:8080/function/figlet
Async URL:           http://127.0.0.1:8080/async-function/figlet

4. Labels are present on server:

[
  {
    "name": "figlet",
    "image": "docker.io/functions/figlet:0.13.0",
    "invocationCount": 4,
    "replicas": 1,
    "envProcess": "",
    "availableReplicas": 0,
    "labels": {
      "testing": "true"
    },
    "annotations": null,
    "namespace": "openfaas-fn"
  }
]

Environment

go version go1.13.4 linux/amd64
containerd -version
containerd containerd.io 1.2.6 894b81a4b802e4eb2a91d1ce216b8817763c29fb
 uname -a
Linux kaderno-XPS-13-9360 5.3.0-40-generic #32-Ubuntu SMP Fri Jan 31 20:24:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
 cat /etc/os-release
NAME="Ubuntu"
VERSION="19.10 (Eoan Ermine)"

[martindekov]

I think this might be more faas-cli related rather than faasd. I will take a better look later today. If the labels appear on the server then the problem is in the client in our case faas-cli.

[martindekov]

By the way thank you for opening this @kadern0 💪

[kadern0]

My initial impression was same as yours, that this issue belongs to faas-cli but after talking to @alexellis and verifying he was getting results with same faas-cli version leaded to the idea that the problem is within the provider.

[martindekov]

The problem is now resolved, thanks for the feedback 👍