On Mon, Apr 15, 2019 at 9:21 AM Pengzhen(Peter) Cao
wrote:
> Hi Ryan,
>
> As you said, "cloudinit/sources/helpers/vmware/imc/config_nic.py" now
> generates v1 network_state dictionary. Should I just add a "DHCPFROMDNS:
> true/false" key as V1 format or should I update the output to v2
> together
Hi Ryan,
As you said, "cloudinit/sources/helpers/vmware/imc/config_nic.py" now
generates v1 network_state dictionary. Should I just add a "DHCPFROMDNS:
true/false" key as V1 format or should I update the output to v2
together with other fields?
--
You received this bug notification because you
Hi,
For now, the version from dpkg is the best way. Netplan does have plans
for querying feature-flags/--version.
https://trello.com/c/ls9KUQuV/42-feature-availability-documentation-
introspection-feature-flags
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Ryan,
Is there any reliable way to detect netplan version in Ubuntu? Could netplan
add "-v/--version" option so that cloud-init or VMware own perl customization
engine could know which netplan pkg is installed in the system.
We need to check if the Netplan installed could support this "use-dns:
We have internal VMware PR2319097 to track the progress.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776452
Title:
Fail to set DNS server and search domain when customize Ubuntu18.04 to
DHCP
I will fix it in cloud-init. Once it is done, we should backport the fix
to ubuntu 18.04.1/18.04.2 as their netplan package is being updated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776452
Netplan in disco has support for dhcp overrides[A], and this is
available in Disco now. Netplan 0.95 is being backported to bionic
which will include this functionality.
Once present, for cloud-init; we will need a few things.
1) cloudinit/sources/helpers/vmware/imc/config_nic.py current
Can this be prioritized higher as this is a bad regression in >= bionic
releases?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776452
Title:
Fail to set DNS server and search domain when
Also tried the following:
network:
version: 1
config:
- type: nameserver
address:
- 172.29.248.2
This version is picked up, but is broken for the same reason xenial is
broken:
2018-11-07 14:33:06,581 - util.py[DEBUG]: Read 18 bytes from
/sys/class/net/eth0/address
Trying to upgrade from Xenial to Bionic we think we've hit this bug.
Previously in xenial we used resolvconf from bootcmd to override the DNS
server. This no longer works in Bionic.
We switched to using the "network" section in cloud init as below:
network:
version: 1
config:
- type:
This is an important user scenario for VMware customer.
And the fix not only affects ubuntu18.04, but also all other linux distros that
are using cloud-init.
The fix needs to be done on a per distro basis, every distro has their
specific way to control the behavior if to override dhcp offered
We're looking to support this use-case in netplan in the near future.
I'll update this bug with some details on what changes we'll need to
cloud-init to support this use-case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached the cust.cfg, Thanks Christian.
** Attachment added: "cust.cfg"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+attachment/5154229/+files/cust.cfg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There isn't yet a way to allow DNS overrides and DHCP on the same
interface. That is, the DHCP response from the server may include DNS
entries so the custom nameserver values are not automatically appended
to an existing DHCP configuration.
Generally adding/overriding DHCP response values isn't
Hi,
it would be nice to see the full /var/run/vmware-imc/cust.cfg that you are
using to configure it.
Just as an FYI - There are plenty of special-case network config sources
[1], I see that you fortunately use the generic one, but still on V1. If
you code up something new I'd recommend to
50-cloud-init.yaml file
** Attachment added: "50-cloud-init.yaml"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+attachment/5151696/+files/50-cloud-init.yaml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
cloud-init logs
** Attachment added: "cloud-init.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1776452/+attachment/5151695/+files/cloud-init.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
17 matches
Mail list logo
