| 2016-09-07 17:15:52 |
Scott Moser |
bug |
|
|
added bug |
| 2016-09-07 17:16:03 |
Scott Moser |
bug task added |
|
cloud-init |
|
| 2016-09-07 17:16:10 |
Scott Moser |
cloud-init: status |
New |
Confirmed |
|
| 2016-09-07 17:16:13 |
Scott Moser |
cloud-init (Ubuntu): status |
New |
Confirmed |
|
| 2016-09-07 17:16:15 |
Scott Moser |
cloud-init: importance |
Undecided |
Medium |
|
| 2016-09-07 17:16:17 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
Medium |
|
| 2016-09-07 17:16:25 |
Scott Moser |
bug task added |
|
juju (Ubuntu) |
|
| 2016-09-07 18:44:31 |
Scott Moser |
affects |
juju (Ubuntu) |
juju-core (Ubuntu) |
|
| 2016-09-07 18:44:52 |
Scott Moser |
bug task added |
|
curtin |
|
| 2016-09-07 19:25:07 |
Scott Moser |
merge proposal linked |
|
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/305137 |
|
| 2016-09-07 19:27:59 |
Scott Moser |
bug task deleted |
curtin |
|
|
| 2016-09-08 16:00:37 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2016-09-12 20:51:05 |
Scott Moser |
cloud-init: status |
Confirmed |
Fix Released |
|
| 2016-09-12 21:07:27 |
Scott Moser |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-09-12 21:07:27 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Xenial) |
|
| 2016-09-12 21:07:27 |
Scott Moser |
bug task added |
|
juju-core (Ubuntu Xenial) |
|
| 2016-09-13 20:18:51 |
Chris J Arges |
cloud-init (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2016-09-13 20:18:54 |
Chris J Arges |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-09-13 20:18:56 |
Chris J Arges |
bug |
|
|
added subscriber SRU Verification |
| 2016-09-13 20:18:59 |
Chris J Arges |
tags |
amd64 apport-bug uec-images yakkety |
amd64 apport-bug uec-images verification-needed yakkety |
|
| 2016-09-13 20:23:42 |
Scott Moser |
description |
$ cat /tmp/foo.ud
#cloud-config
apt_mirror: ''
$ lxc launch ubuntu-daily:yakkety sm-y0 "--config=user.user-data=$(cat /tmp/foo.ud)"
$ sleep 10
$ lxc exec sm-y0 grep yakkety /etc/apt/sources.list | head -n 3
deb yakkety main restricted
deb-src yakkety main restricted
deb yakkety-updates main restricted
basically if you provide an empty apt_mirror in the old format, then it is taken as providing an apt mirror. This non-true value should just be the same as not providing it.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: cloud-init 0.7.7-22-g763f403-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Wed Sep 7 17:12:11 2016
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
==== Begin SRU Template ====
[Impact]
This is a bug that existed only in development time in cloud-init and was exposed during uploads to yakkety. It has never existed in xenial, but we do need to make sure that the function is still present.
The impact was that if a user (juju) started an instance with:
apt_mirror: ''
that was taken as the apt mirror and /etc/apt/sources.list would have empty entries where a mirror should be.
[Test Case]
$ cat /tmp/foo.ud
#cloud-config
apt_mirror: ''
$ lxc launch ubuntu-daily:xenial sm-x0 "--config=user.user-data=$(cat /tmp/foo.ud)"
$ sleep 10
$ lxc exec sm-x0 grep yakkety /etc/apt/sources.list | head -n 3
deb yakkety main restricted
deb-src yakkety main restricted
deb yakkety-updates main restricted
Expected behavior is to see http://archive.ubuntu.com/ubuntu.
[Regression Potential]
Over all, the apt configuration feature could have other regressions
similar to this, but this specific change has very little chance for regresion.
==== End SRU Template ====
$ cat /tmp/foo.ud
#cloud-config
apt_mirror: ''
$ lxc launch ubuntu-daily:yakkety sm-y0 "--config=user.user-data=$(cat /tmp/foo.ud)"
$ sleep 10
$ lxc exec sm-y0 grep yakkety /etc/apt/sources.list | head -n 3
deb yakkety main restricted
deb-src yakkety main restricted
deb yakkety-updates main restricted
basically if you provide an empty apt_mirror in the old format, then it is taken as providing an apt mirror. This non-true value should just be the same as not providing it.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: cloud-init 0.7.7-22-g763f403-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Wed Sep 7 17:12:11 2016
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2016-09-14 20:05:02 |
Scott Moser |
description |
==== Begin SRU Template ====
[Impact]
This is a bug that existed only in development time in cloud-init and was exposed during uploads to yakkety. It has never existed in xenial, but we do need to make sure that the function is still present.
The impact was that if a user (juju) started an instance with:
apt_mirror: ''
that was taken as the apt mirror and /etc/apt/sources.list would have empty entries where a mirror should be.
[Test Case]
$ cat /tmp/foo.ud
#cloud-config
apt_mirror: ''
$ lxc launch ubuntu-daily:xenial sm-x0 "--config=user.user-data=$(cat /tmp/foo.ud)"
$ sleep 10
$ lxc exec sm-x0 grep yakkety /etc/apt/sources.list | head -n 3
deb yakkety main restricted
deb-src yakkety main restricted
deb yakkety-updates main restricted
Expected behavior is to see http://archive.ubuntu.com/ubuntu.
[Regression Potential]
Over all, the apt configuration feature could have other regressions
similar to this, but this specific change has very little chance for regresion.
==== End SRU Template ====
$ cat /tmp/foo.ud
#cloud-config
apt_mirror: ''
$ lxc launch ubuntu-daily:yakkety sm-y0 "--config=user.user-data=$(cat /tmp/foo.ud)"
$ sleep 10
$ lxc exec sm-y0 grep yakkety /etc/apt/sources.list | head -n 3
deb yakkety main restricted
deb-src yakkety main restricted
deb yakkety-updates main restricted
basically if you provide an empty apt_mirror in the old format, then it is taken as providing an apt mirror. This non-true value should just be the same as not providing it.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: cloud-init 0.7.7-22-g763f403-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Wed Sep 7 17:12:11 2016
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
==== Begin SRU Template ====
[Impact]
This is a bug that existed only in development time in cloud-init and was exposed during uploads to yakkety. It has never existed in xenial, but we do need to make sure that the function is still present.
The impact was that if a user (juju) started an instance with:
apt_mirror: ''
that was taken as the apt mirror and /etc/apt/sources.list would have empty entries where a mirror should be.
[Test Case]
$ cat /tmp/foo.ud
#cloud-config
apt_mirror: ''
$ lxc launch ubuntu-daily:xenial sm-x0 "--config=user.user-data=$(cat /tmp/foo.ud)"
$ sleep 10
$ lxc exec sm-x0 grep yakkety /etc/apt/sources.list | head -n 3
deb yakkety main restricted
deb-src yakkety main restricted
deb yakkety-updates main restricted
Expected behavior is to see http://archive.ubuntu.com/ubuntu.
[Regression Potential]
Over all, the apt configuration feature could have other regressions
similar to this, but this specific change has very little chance for regresion.
==== End SRU Template ====
$ cat /tmp/foo.ud
#cloud-config
apt_mirror: ''
$ lxc launch ubuntu-daily:yakkety sm-y0 "--config=user.user-data=$(cat /tmp/foo.ud)"
$ sleep 10
$ lxc exec sm-y0 grep ^deb /etc/apt/sources.list | head -n 3
deb yakkety main restricted
deb-src yakkety main restricted
deb yakkety-updates main restricted
basically if you provide an empty apt_mirror in the old format, then it is taken as providing an apt mirror. This non-true value should just be the same as not providing it.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: cloud-init 0.7.7-22-g763f403-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Wed Sep 7 17:12:11 2016
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2016-09-14 20:09:03 |
Scott Moser |
tags |
amd64 apport-bug uec-images verification-needed yakkety |
amd64 apport-bug uec-images verification-done yakkety |
|
| 2016-09-14 20:10:10 |
Scott Moser |
description |
==== Begin SRU Template ====
[Impact]
This is a bug that existed only in development time in cloud-init and was exposed during uploads to yakkety. It has never existed in xenial, but we do need to make sure that the function is still present.
The impact was that if a user (juju) started an instance with:
apt_mirror: ''
that was taken as the apt mirror and /etc/apt/sources.list would have empty entries where a mirror should be.
[Test Case]
$ cat /tmp/foo.ud
#cloud-config
apt_mirror: ''
$ lxc launch ubuntu-daily:xenial sm-x0 "--config=user.user-data=$(cat /tmp/foo.ud)"
$ sleep 10
$ lxc exec sm-x0 grep yakkety /etc/apt/sources.list | head -n 3
deb yakkety main restricted
deb-src yakkety main restricted
deb yakkety-updates main restricted
Expected behavior is to see http://archive.ubuntu.com/ubuntu.
[Regression Potential]
Over all, the apt configuration feature could have other regressions
similar to this, but this specific change has very little chance for regresion.
==== End SRU Template ====
$ cat /tmp/foo.ud
#cloud-config
apt_mirror: ''
$ lxc launch ubuntu-daily:yakkety sm-y0 "--config=user.user-data=$(cat /tmp/foo.ud)"
$ sleep 10
$ lxc exec sm-y0 grep ^deb /etc/apt/sources.list | head -n 3
deb yakkety main restricted
deb-src yakkety main restricted
deb yakkety-updates main restricted
basically if you provide an empty apt_mirror in the old format, then it is taken as providing an apt mirror. This non-true value should just be the same as not providing it.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: cloud-init 0.7.7-22-g763f403-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Wed Sep 7 17:12:11 2016
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
==== Begin SRU Template ====
[Impact]
This is a bug that existed only in development time in cloud-init and was exposed during uploads to yakkety. It has never existed in xenial, but we do need to make sure that the function is still present.
The impact was that if a user (juju) started an instance with:
apt_mirror: ''
that was taken as the apt mirror and /etc/apt/sources.list would have empty entries where a mirror should be.
[Test Case]
$ cat /tmp/foo.ud
#cloud-config
apt_mirror: ''
$ lxc launch ubuntu-daily:xenial sm-x0 "--config=user.user-data=$(cat /tmp/foo.ud)"
$ sleep 10
$ lxc exec sm-x0 grep yakkety /etc/apt/sources.list | head -n 3
deb yakkety main restricted
deb-src yakkety main restricted
deb yakkety-updates main restricted
Expected behavior is to see http://archive.ubuntu.com/ubuntu.
[Regression Potential]
Over all, the apt configuration feature could have other regressions
similar to this, but this specific change has very little chance for regresion.
==== End SRU Template ====
$ cat /tmp/foo.ud
#cloud-config
apt_mirror: ''
$ lxc launch ubuntu-daily:yakkety sm-y0 "--config=user.user-data=$(cat /tmp/foo.ud)"
$ sleep 10
$ lxc exec sm-y0 grep ^deb /etc/apt/sources.list | head -n 3
deb yakkety main restricted
deb-src yakkety main restricted
deb yakkety-updates main restricted
## Now get -proposed version.
$ lxc exec sm-x0 -- sh -c '
p=/etc/apt/sources.list.d/proposed.list
echo deb http://archive.ubuntu.com/ubuntu xenial-proposed main > "$p" &&
apt-get update -q && apt-get -qy install cloud-init'
## cleanup so it thinks its fresh
$ lxc exec sm-x0 -- sh -c '
cd /var/lib/cloud && for d in *; do [ "$d" = "seed" ] || rm -Rf "$d"; done
rm -Rf /var/log/cloud-init*'
$ lxc exec sm-x0 reboot
$ lxc exec sm-x0 grep ^deb /etc/apt/sources.list | head -n 3
deb http://archive.ubuntu.com/ubuntu xenial main restricted
deb-src http://archive.ubuntu.com/ubuntu xenial main restricted
deb http://archive.ubuntu.com/ubuntu xenial-updates main restricted
basically if you provide an empty apt_mirror in the old format, then it is taken as providing an apt mirror. This non-true value should just be the same as not providing it.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: cloud-init 0.7.7-22-g763f403-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Wed Sep 7 17:12:11 2016
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2016-09-15 14:31:14 |
Martin Pitt |
tags |
amd64 apport-bug uec-images verification-done yakkety |
amd64 apport-bug uec-images yakkety |
|
| 2016-09-15 14:31:16 |
Martin Pitt |
tags |
amd64 apport-bug uec-images yakkety |
amd64 apport-bug uec-images verification-needed yakkety |
|
| 2016-09-17 02:19:46 |
Scott Moser |
tags |
amd64 apport-bug uec-images verification-needed yakkety |
amd64 apport-bug uec-images verification-done yakkety |
|
| 2016-09-22 17:34:08 |
Launchpad Janitor |
cloud-init (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-09-22 17:35:47 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2023-05-10 16:28:05 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2723 |
|
