| minimal | Quark: try changing "primary-group" to "primary_group"? Also try validating the user-data in cloud-init to see what it says? | 15:16 |
|---|---|---|
| Quark | Data validation passes. | 15:17 |
| minimal | also did the cloud-init.log show anything? | 15:17 |
| Quark | No, just the cloud-init-output.log had the error. | 15:18 |
| minimal | strange, check the cloud-init.log for when it does user creation to see what it shows | 15:18 |
| Quark | Let me try changing that primary-group (that's a typo there). | 15:18 |
| minimal | it its a Subiquity issue, rather than cloud-init, then the best place to discuss it would be the #ubuntu-server channel | 15:20 |
| bahamat | Is it possible to create a directory with cloud-init? | 22:20 |
| meena | bahamat: not with write_files; so runcmd it has to be; or if it needs to happen very early, bootcmd | 22:34 |
| bahamat | meena: Ok, thanks. I'm trying to do an nfs mount and the directory I want to use doesn't exist. | 22:37 |
| meena | bahamat: according to the documentation, cc_mount creates directories that don't exist first | 23:31 |
| meena | bahamat: so, if it doesn't, I'd call that a bug | 23:33 |
| bahamat | Hmm. Well, my nfs mount isn't being configured. | 23:33 |
| bahamat | Here's the cloud config I'm using: https://gist.github.com/bahamat/01db41644b3885c3f1fdc3b0be1241b1 | 23:34 |
| Quark | Can you provide a pastie with a snipped? | 23:34 |
| Quark | Ops, we typed at the same time. :-D | 23:35 |
| bahamat | :-D | 23:35 |
| bahamat | Running the mount command manually mounts the share, so that part is working. | 23:36 |
| Quark | Running `cloud-init schema --config-file=user-data --annotate` renders `E1: Additional properties are not allowed ('mount' was unexpected)` | 23:38 |
| bahamat | Oh, mounts. | 23:40 |
| bahamat | Damn. | 23:40 |
| bahamat | OK, let's give this another shot. | 23:41 |
| meena | *most* directives are in plural… except runcmd and bootcmd… and, let's not get into details about consistency | 23:47 |
| minimal | bahamat: your cloud-config content is not valid | 23:50 |
| minimal | it is "mounts:", not "mount:" | 23:51 |
| minimal | ah, ok, you noticed ;-) | 23:52 |
| bahamat | Yeah, thanks though :-) | 23:52 |
| minimal | you could validate the YAML to check via "cloud-init schema" command | 23:52 |
| bahamat | I don't use cloud-init a lot myself, but I have a lot of users who do, so I provide examples for them. Hopefully working ones :-) | 23:52 |
| bahamat | The weird thing is that I thought I had, and it returned no errors. | 23:54 |
| bahamat | But later validating it again showed both that "mount" should be "mounts", and that fields 4 and 5 need to be strings, not numbers (which, that one is kind of annoying, because they *are* numbers) | 23:55 |
| minimal | also "mounts" runs in cloud-init "init" stage whereas "packages:" runs in cloud-init "final" stage and so the mount will be attempted BEFORE the nfs-common package is installed | 23:55 |
| bahamat | So there's no way to do this then... | 23:56 |
| bahamat | unless I install the package via bootcmd or something. | 23:56 |
| minimal | runcmd as meena suggested? | 23:56 |
| minimal | bahamat: "fields 4 and 5 need to be strings, not numbers" - you mean fields 5 & 6? the cloud-init is YAML and that's why they need to be quoted as otherwise a number "0" or beginning with "0" will not be treated as a decimal 0 | 23:58 |
| bahamat | Oh, that's right, it's octal. | 23:59 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!