This change intentionally won't change the permissions of already
existing files. As long as the file is root readable and writable,
manually updating the permissions for existing instances shouldn't cause
any problems.
--
You received this bug notification because you are a member of Ubuntu
Hello Dan, @Dan Watkins
I have a question about the permission of cloud-init-output.log when cloud-init
upgrade to the version which contains this bug fix. I found that before
upgrade, the permission of cloud-init-output.log is 644 and user:group is
root:root, while after upgrade, the
This bug is believed to be fixed in cloud-init in version 21.2. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug was fixed in the package cloud-init -
21.1-19-gbad84ad4-0ubuntu1~16.04.1
---
cloud-init (21.1-19-gbad84ad4-0ubuntu1~16.04.1) xenial; urgency=medium
* d/cloud-init.postinst: Change output log permissions on upgrade
(LP: #1918303)
* d/cloud-init.manpages: include
This bug was fixed in the package cloud-init -
21.1-19-gbad84ad4-0ubuntu1~18.04.1
---
cloud-init (21.1-19-gbad84ad4-0ubuntu1~18.04.1) bionic; urgency=medium
* d/cloud-init.postinst: Change output log permissions on upgrade
(LP: #1918303)
* d/cloud-init.manpages: include
This bug was fixed in the package cloud-init -
21.1-19-gbad84ad4-0ubuntu1~20.04.1
---
cloud-init (21.1-19-gbad84ad4-0ubuntu1~20.04.1) focal; urgency=medium
* d/cloud-init.postinst: Change output log permissions on upgrade
(LP: #1918303)
* d/cloud-init.manpages: include
This bug was fixed in the package cloud-init -
21.1-19-gbad84ad4-0ubuntu1~20.10.1
---
cloud-init (21.1-19-gbad84ad4-0ubuntu1~20.10.1) groovy; urgency=medium
* d/cloud-init.postinst: Change output log permissions on upgrade
(LP: #1918303)
* d/cloud-init.manpages: include
xenial-proposed, bionic-proposed, focal-proposed, and groovy-proposed were all
tested here:
https://github.com/cloud-init/ubuntu-sru/blob/main/bugs/lp-1918303.txt
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-groovy
Hello all,
I tested the focal-proposed package on a new install of Ubuntu Server
and was unable to replicate the issue. The random passwords did not
appear written in the cloud-init-output.log file and the output file's
permissions were restricted. Near as I can tell it appears to be fixed.
--
Hello Carl, or anyone else affected,
Accepted cloud-init into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/21.1-19-gbad84ad4-0ubuntu1~18.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Hello Carl, or anyone else affected,
Accepted cloud-init into groovy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/21.1-19-gbad84ad4-0ubuntu1~20.10.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
cloud-init (21.1-19-gbad84ad4-0ubuntu1) hirsute; urgency=medium
* d/cloud-init.postinst: Change output log permissions on upgrade
(LP: #1918303)
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix
12 matches
Mail list logo
