XenServer Tools is unable to report CoreOS' VM IP address to parent XenServer

[TheGammelgalopper]

Bug

Cannot see CoreOS's IP in XenCenter under Networking. I have seen this issue: https://github.com/coreos/bugs/issues/1563, which is just the same here.

Container Linux Version

NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1409.7.0
VERSION_ID=1409.7.0
BUILD_ID=2017-07-19-0005
PRETTY_NAME="Container Linux by CoreOS 1409.7.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"

Environment

XenServer 7.2 build date 2017-05-11

[nitso]

Same problem with latest version:

NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1465.8.0
VERSION_ID=1465.8.0
BUILD_ID=2017-09-20-2237
PRETTY_NAME="Container Linux by CoreOS 1465.8.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"

However renaming etcd.service to etcd2.service (https://github.com/coreos/bugs/issues/2123#issuecomment-327365370) fixes problem. Looks like it is an issue in XenCenter CoreOS template.

[TheGammelgalopper]

Yes, I can second this!

I have tried to comment out the following lines in the cloud config in Xen Orchestra:

# - name: etcd.service
# command: start

# etcd:
# name: %VMNAMETOHOSTNAME%

This kind of worked. But I see it as a workaround and not a solution...

What is the correct place to file this issue for XenServer/XenOrchestra?

[nitso]

There is a merged patch (https://github.com/xenserver/xscontainer/pull/45) to xscontainer already. Hope it ever arrives to supplemental pack iso :)

[TheGammelgalopper]

@nitso What does that mean? Is there something I can do to get it running smoothly?

[nitso]

@TheGammelgalopper just replace etcd with etcd2 in cloud config. Like here: https://github.com/xenserver/xscontainer/pull/45/files

[bgilbert]

Since the xscontainer fix was merged, I'll close.