To summarize the discussion and close this for now:
- as outlined in comment #16 there are two paths in vmtools
(A) being the new code using cloud-init is NOT affected
(B) being the old code path being affected with own customization code
The problem is that for some customizations this has to run early, and for
some others things
it has to run late - that is the Dilemma here.
- Path (A) does not have a problem and is the way to go in the future
Cloud-init provides all that is needed to configure the system
- (B) is there for compatibility with older setups
- To fix (B) there are two options:
- modify the config (that is what the KB article is about)
That is the least nice option, but the benefit is that it costs no effort
- open-vm-tools could split vmtools customization code into two
(or more) pieces like cloud-init already does
Those pieces could then run early/late as needed
This would be a major dev effort for a code path that is considered
"the old one" and probably not worth the effort.
So from a Ubuntu perspective all is discussed and done.
I'm marking the bug tasks as Invalid.
>From a VMWare perspective the options are:
- keep the KB article up (we can bikeshed about wording)
- spend dev time on (B) to be split
- put time on further deprecating and dropping path (B) (recommended)
** Changed in: open-vm-tools (Ubuntu)
Status: Confirmed => Opinion
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793715
Title:
VMWare Guest OS Customization will fail for Ubuntu 18.04 Server
LiveCD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
