Please provide your feedback in this short Flings' survey.
Nov 24, 2019

hi, i have deployed the ova today but when it boots it only seems to show the ipv6 ip in vcenter and no ipv4.
the console displays https://[IP]/status

any ideas pls.

Nov 25, 2019

1) Did you confirm the Appliance is on a network that can connect to the Internet?
2) You can login via the console and take a look at /var/log/bootstrap.log to see if there's any errors. If you don't see anything, please re-deploy and toggle the "debug" option at the very bottom and then take a look at /var/log/bootstrap-debug.log which will have more verbose logging

Nov 25, 2019

the log shows the below:-
removed /etc/systemd/system/
w1125 07:10:53.699529 712 common.go:140] warning: could not obtain a bind address for the api server: no default routes found in "/proc/net/route" or "/proc/net/ipv6_route"; using:
I1125 07:10:53.704723 712 verion.go:96] could not fetch a kubernetes version from the internet: unable to get url "": get dial tcp: lookup on server misbehaving
I1125 07:10:53.704747 712 version.go:97] falling back to the local client version: v1.14.6 cannot use "" as the bind address for the api server.

when i try to ping anything from the cli i get "network is unreachable"

Nov 25, 2019


It looks like the networking wasn't setup correctly and/or it can't reach the internet. Can you please double check all your input settings? You should be able to ping the appliance from your desktop as well as being able to ping say

I'm working on a version of the appliance that doesn't need internet and will have the containers pre-downloaded, but in your case, it looks like networking just isn't setup correctly which is all based on you input during deployment. Please check that first and we can then provide you with an early build which doesn't require internet connectivity if you're interested in testing that out

Nov 26, 2019

Hi, the networking inputs are all correct - I have tried to deploy several times with different networks i know has internet access.
I would be interested in getting an early build version to see how that fairs.

Dec 02, 2019

hi, this has now worked for me :) thankyou

Nov 17, 2019

Thank you for the awesome project. I noticed that vcconfig.toml file, vCenter section should be pointed to vCenter instead of VEBA and probably be in the quote marks, i.e server = "vCenter_FQDN/IP".

Nov 18, 2019

Good catch! You're right, this should be the vCenter Server FQDN/IP and it should be in quotes. We'll get this fixed

Nov 25, 2019

Looks like this is fixed, thx!

Nov 12, 2019

Thanks to release that cool fling!
I quickly followed your guideline, but the event doesn't seem to be triggered.
When checking the appliance log kubectl -n openfaas logs deploy/vcenter-connector -f I see all events including the poweron of my test vm, but no tag is added.

The tag is created correctly and I changed the urn in the vcconfig.toml before deploying. Stack.yml also deployed.

When checking faas-cli logs pytag-fn --follow --tls-no-verify I only receive the following output:
2019-11-12T19:34:20Z 2019/11/12 19:34:20 Version: 0.18.0 SHA: 137b63e61fe55e0aea7df466931198c37817f743
2019-11-12T19:34:20Z 2019/11/12 19:34:20 Timeouts: read: 5s, write: 5s hard: 0s.
2019-11-12T19:34:20Z 2019/11/12 19:34:20 Listening on port: 8080
2019-11-12T19:34:20Z 2019/11/12 19:34:20 Writing lock-file to: /tmp/.lock
2019-11-12T19:34:20Z 2019/11/12 19:34:20 Metrics listening on port: 8081

Any idea what to check next?



Nov 12, 2019

when writing it down I noticed it myself. Cluster is a drs cluster, so drs.vm.powered.on instead of vm.powered.on

Works like a charm now!

Nov 12, 2019

Excellent to hear you got it working Dennis!

Nov 11, 2019

When I try to deploy I get either:

Invalid value 'true' specified for property guestinfo.debug.
Invalid value 'false' specified for property guestinfo.debug.

Nov 12, 2019

Hi Simon,

Thanks for trying out VEBA. Sorry to hear you ran into some issues. Could you provide a bit more details on your environment and how you went to deploy the OVA? What version of vCenter Server were you using and was this using the Flash or HTML5 based client? What version was your ESXi hosts that VEBA was being deployed to? I vaguely recall seeing this type of an error before on something un-related and it maybe due to the Client used to deploy the OVA

Nov 12, 2019

Hi Simon,

I've just pushed an updated version of the OVA w/fix, can you please give that a try? The version will still be 0.1.0 as nothing has changed except the stale entry in OVF

Nov 20, 2019

Thanks Will. Of interest, it deployed fine in flash so must have been a HTML5 - VCSA 6.5 issue. Will pull the new image though as I'm seeng nvram errors now...

Nov 20, 2019

The "relaxing" of missing NVRAM was fixed in vSphere 6.7, so you should hit the same problem regardless of the UI you deploy to. It may succeed but it'll fail to power on. The updating OVA shouldn't have this problem but let me know