Given that this only happens if there is a Jinja error present, and most
systems will have already upgraded at this point, I don't see much value
in fixing this.
** Changed in: cloud-init
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1983303
Title:
logs mangled
Status in cloud-init:
Won't Fix
Bug description:
The fix of #1978422 mangles logs as `sed` modifies them while they are
still open (at least that's my deduction). Applies to both cloud-
init.log and cloud-init-output.log.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1983303/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
