cloud-init - Hosts in softlayer receiving warning
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
High
|
Unassigned | ||
cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Unassigned | ||
Yakkety |
Fix Released
|
Medium
|
Unassigned | ||
Zesty |
Fix Released
|
Medium
|
Unassigned | ||
Artful |
Fix Released
|
Medium
|
Unassigned |
Bug Description
=== Begin cloud-init SRU Template ===
[Impact]
Softlayer user datasource is undetected when only openstack/latest config-drive directory is provided (due to softlayer user-data being provided).
[Test Case]
For cloud-init, the easiest way to demonstrate this is to
create a lxc container and populate it with a '/config-drive' that only contains a openstack/latest path.
wget https:/
chmod 755 lxc-proposed-
wget https:/
chmod 755 make-configdriv
name=test-proposed
for release in xenial yaketty zesty; do
ref=$release-
./lxc-
./lxc init $ref $name;
## populate a /config-drive with attached 'make-configdri
## and push it to the container
d=$(mktemp -d)
./make-
rm -Rf "$d"
lxc file pull $name/etc/
sed 's/NoCloud, //' |
lxc file push - $name/etc/
lxc start $name;
sleep 10;
lxc exec $name -- rm -rf /config-
lxc exec $name -- cp -r /config-drive /var/lib/
lxc exec $name -- sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/
# should produce config drive seeded directory had only 'latest'
done
[Regression Potential]
Minimal as this code is exercised for softlayer
[Other Info]
Related bugs:
* bug 1689890: Unable to identify datasource in IBM Bluemix
=== End cloud-init SRU Template ===
Related branches
- Scott Moser: Approve
- Server Team CI bot: Needs Fixing (continuous-integration)
-
Diff: 21 lines (+3/-2)1 file modifiedtools/ds-identify (+3/-2)
Changed in cloud-init (Ubuntu): | |
status: | New → Fix Committed |
description: | updated |
Changed in cloud-init (Ubuntu Xenial): | |
status: | New → Confirmed |
Changed in cloud-init (Ubuntu Yakkety): | |
status: | New → Confirmed |
Changed in cloud-init (Ubuntu Zesty): | |
status: | New → Confirmed |
Changed in cloud-init (Ubuntu Artful): | |
status: | Fix Committed → Fix Released |
Changed in cloud-init (Ubuntu Xenial): | |
importance: | Undecided → Medium |
Changed in cloud-init (Ubuntu Yakkety): | |
importance: | Undecided → Medium |
Changed in cloud-init (Ubuntu Zesty): | |
importance: | Undecided → Medium |
Changed in cloud-init (Ubuntu Artful): | |
importance: | Undecided → Medium |
Changed in cloud-init: | |
status: | Confirmed → Fix Committed |
description: | updated |
tags: | added: id-58cc1e3bea5b5c7f55e04e65 |
Hi, can you please collect the following from the system:
/var/ log/cloud- init.log
/run/cloud-init/
dmesg > dmesg.txt
journalctl -o short-precise > journal.txt
Then, please run: ds-identify --force
sudo /usr/lib/
And collect the (now updated) files: cloud-init/ cloud.cfg cloud-init/ ds-identify. log
/run/
/run/
Thank you.