vmware customization only writes ENI network config
Bug #1675063 reported by
Scott Moser
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-init |
Fix Released
|
Medium
|
Sankar Tanguturi | ||
Bug Description
the vmware code that configures networking currently only supports writing etc/network/
It would be better for it to use the renderers for ENI and sysconfig, and then it will gain new backends as cloud-init does.
Related branches
~sankaraditya/cloud-init:topic-stanguturi-vmware-curtin-changes
- Scott Moser: Approve
- Server Team CI bot: Approve (continuous-integration)
- Chad Smith: Approve
-
Diff: 808 lines (+418/-103)4 files modifiedcloudinit/sources/DataSourceOVF.py (+64/-27)
cloudinit/sources/helpers/vmware/imc/config_nic.py (+130/-71)
cloudinit/sources/helpers/vmware/imc/guestcust_util.py (+7/-5)
tests/unittests/test_vmware_config_file.py (+217/-0)
| Changed in cloud-init: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| assignee: | nobody → Sankar Tanguturi (sankaraditya) |
Revision history for this message
| Scott Moser (smoser) wrote Fixed in Cloud-init 17.1 | #1 |
| Changed in cloud-init: | |
| status: | Confirmed → Fix Released |
Revision history for this message
| James Falcon (falcojr) wrote | #2 |
To post a comment you must log in.
This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New
Thank you.