[Bug 265177] net/cloud-init - fails when attempting to use write_files

From: <bugzilla-noreply_at_freebsd.org>
Date: Tue, 12 Jul 2022 17:34:44 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265177

            Bug ID: 265177
           Summary: net/cloud-init - fails when attempting to use
                    write_files
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: ewan.nisbet@dice.fm
                CC: andrey@bsdnir.info
                CC: andrey@bsdnir.info
             Flags: maintainer-feedback?(andrey@bsdnir.info)

hi,

I've been using py38-cloud-init, and now py39-cloud-init in conjunction with
Xen Orchestra:

https://xen-orchestra.com/docs/installation.html#xoa
https://xoa.io/deploy

Originally with py38-cloud-init, and now py39-cloud-init, I'm applying the
following change:

sed -i '' -e 's/            gid = grp.getgrnam(group).gr_gid/            pass
#20220224 this comment added in packer builder. bug?: gid =
grp.getgrnam(group).gr_gid/g'
/usr/local/lib/python3.9/site-packages/cloudinit/util.py


Unless I make that change, a corresponding cloud_init with eg:

write_files:
- content: |
   some-script-here
  path: /root/some-script.sh

or

write_files:
- content: |
   some-script-here
  permissions: 0744
  path: /root/some-script.sh

write_files:
- content: |
   some-script-here
  permissions: "0744"
  path: /root/some-script.sh

doesn't appear to be handled correctly. Example error message: from
/var/log/cloud-init-output.log is:

util.py[WARNING]: Running module write-files (<module
'cloudinit.config.cc_write_files' from
'/usr/local/lib/python3.9/site-packages/cloudinit/config/cc_write_files.py'>)
failed

I am successfully using cloud-init with the same xen/xen-orchestra & other
operating systems, for example alma linux, without needing to apply this
change. 

Please let me know if there is further information I can provide.
Alternatively, also let me know if you believe this issue should be submitted
upstream with cloud-init team directly.

Many thanks

-- 
You are receiving this mail because:
You are the assignee for the bug.