You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by "weizhouapache (via GitHub)" <gi...@apache.org> on 2023/08/29 08:27:40 UTC
[GitHub] [cloudstack] weizhouapache commented on issue #7918: [4.19] UserData must have a header
weizhouapache commented on issue #7918:
URL: https://github.com/apache/cloudstack/issues/7918#issuecomment-1696996302
> I thought the header requirement only applied if the underlying template had userdata linked to it.
>
@mlsorensen
you are right. If there are joint userdata, both should have a header.
In some scenarios, plain-text userdata still works, for example
- only template has linked userdata, but no vm userdata
- only vm has userdata (template does not have linked userdata)
Assume there are two userdata
```
#!/bin/bash
echo "acs-1"
```
and
```
echo "acs-2"
```
If we use the first as template userdata and the second as manual entry, it works in 4.18 but not in 4.19
> This could be an issue, as there are appliances that read config from userdata that is in proprietary (or at least non-cloud-init) formats. For example, vASA "Day 0 configuration" has been shown to work with CloudStack by reading day 0 config from config drive.
>
> If it is only an issue for underlying templates linked with userdata, it is probably OK, as the admin of the template has done this, we enforce the VM's additional userdata is compatible with the template's userdata. However, we probably don't want to require header for all userdata.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org