Looking at machines run up in Joyent, the cloud init log clearly shows the package update/upgrade attributes are being correctly set:
<snip>
output:
all: '| tee -a /var/log/cloud-init-output.log'
package_update: true
package_upgrade: true
packages:
<snip>
So juju is behaving correctly. There may be an upstream cloud-init change. The apt history shows a dist-upgrade is being done. But the cloud init output log does imply an apt update/upgrade is being done also.
Looking at machines run up in Joyent, the cloud init log clearly shows the package update/upgrade attributes are being correctly set:
<snip> cloud-init- output. log'
output:
all: '| tee -a /var/log/
package_update: true
package_upgrade: true
packages:
<snip>
So juju is behaving correctly. There may be an upstream cloud-init change. The apt history shows a dist-upgrade is being done. But the cloud init output log does imply an apt update/upgrade is being done also.