This bug was fixed in the package cloud-init - 0.6.3-0ubuntu1.10
---
cloud-init (0.6.3-0ubuntu1.10) precise-proposed; urgency=low
* debian/patches/lp-1272115-fix_smartos_compliance.patch: Fix compliance for
SmartOS data handling (LP: #1272115):
- cloud-init user-data is now
This bug was fixed in the package cloud-init - 0.7.3-0ubuntu2.1
---
cloud-init (0.7.3-0ubuntu2.1) saucy-proposed; urgency=low
* debian/patches/lp-1272115-fix_smartos_compliance.patch: Fix compliance for
SmartOS data handling (LP: #1272115):
- straight backport from 14.04
Verified on saucy with success. Attaching cloud-init.log for saucy.
** Attachment added: cloud-init.log for saucy verification
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1272115/+attachment/3976186/+files/cloud-init_saucy.log
--
You received this bug notification because you
Log file and notes from verification on precise.
- Testing was successful on a host with plain text in the cloud-init:user-data
metadata field.
- Testing failed on a host which had base64 data in the cloud-init:user-data
metadata field.
I also saw that the user-script ran twice, producing two
@rcj: this is as expected. The cloud-init user-data needs to have a
metadata key of base64_keys=cloud-init:user-data in order for it to
work.
The logs indicate that the instance your on is lacking a ubuntu user.
Can you re-run the test, but create the ubuntu user before running the
test?
--
You
Marking as verification-done. The logs from comment #8, actually
indicate that the test cases succeeded, however, it was failing due to
using a non-official Ubuntu image.
I verified the test cases. This SRU is good to go for release.
** Tags removed: verification-needed
** Tags added:
Hm. In “Regression potential” you say “will only affect users who are
relying on the broken behavior”.
What effect will this have on users who *are* relying on the current
behaviour? Do you have any estimate of how many users might be relying
on it? There's a high bar to clear for an SRU that
What effect will this have on users who *are* relying on the current
behaviour?
The effect will be minimial, if any. SmartOS has the concept of user-
data, which is a channel for sending raw data. In the case of cloud-
init, users would be more likely to be confused by something acting on
the
Hello Ben, or anyone else affected,
Accepted cloud-init into saucy-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/cloud-
init/0.7.3-0ubuntu2.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
** Summary changed:
- cloud-init SmartOS datasource provider is not compliant to datadictionary
+ [SRU] cloud-init SmartOS datasource provider is not compliant to
datadictionary
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Description changed:
+ [IMPACT]
+ Cloud-init provisioning on SmartOS is not compliant per the DataDictionary
published on 25 September. The result is that cloud-init provisioned Ubuntu on
SmartOS hosts will not behave as user expect. This SRU makes cloud-init's
SmartOS datasource compliant
11 matches
Mail list logo
