@Prakesh or others.
Based on last comment #12, I have set this to 'Incomplete'.
Please provide some more information and set the bug back to "New" when you're
done.
Thanks.
Scott
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
An upstream commit landed for this bug.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=9d0e557e
** Changed in: curtin
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
An upstream commit landed for this bug.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=1bc868b4
** Changed in: curtin
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
There is a bug in extract_root_fsimage_url that causes stack trace when
attempting to extract a local filesystem image.
The stack trace looks like below.
The bug is fairly clear in the following:
def extract_root_fsimage_url(url, target):
path =
** Also affects: curtin
Importance: Undecided
Status: New
** Changed in: curtin
Status: New => Confirmed
** Changed in: curtin (Ubuntu)
Status: New => Confirmed
** Changed in: curtin
Importance: Undecided => Medium
** Changed in: curtin (Ubuntu)
Importance:
Public bug reported:
Subiquity provides /target as in config like:
install: {target: /target}
if /target already exists, then WorkingDir will fail and stack trace.
stack trace looks something like this:
Running command ['tar', '-cvf', '/var/log/curtin/curtin-error-logs.tar',
Just a comment...
'apt' indicates that its cli is unstable and should not be relied upon by
scripts.
So fixing this general problem in 'apt' (and not apt-get) means you fix it
possibly for humans who are typing things, but all non-human package
installations needlessly have to 'apt-get update'.
@Tianon,
You are correct that a user then would inevitably get an out of date
package.
However, removing the release pocket content
a.) means every user in every image has to download that data which does not
change.
b.) only defers the potential problem until later.
Essentially, the problem
@vijaya.h,
If you're having issues, please file a bug with 'ubuntu-bug' in your system and
follow the prompts.
That should collect enough information for us to determine what is going wrong.
Thanks!.
Scott
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Prakash,
>From your logs it appears that you are booting under kvm and are using
the Ec2 Datasource. The metadata in that datasource is invalid. It
describes network information (as seen in /var/log/cloud-init.log and
cleaner in /run/cloud-init/instance-data.json) like this:
"network": {
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init (Ubuntu Bionic)
Importance: Undecided
** Description changed:
With trusty, /bin/ping relies on having extended attributes and kernel
capabilities to gain the cap_net_raw+p capability. This allows removing
the suid bit.
However, the tarball cloud images do not preserve the extended
attributes, and thus /bin/ping does not
** Description changed:
Ping is not longer setuid root and I have to ping as root:
[~]$ ping kubuntu.org
ping: icmp open socket: Operation not permitted
[~]$ sudo ping kubuntu.org
PING kubuntu.org (91.189.94.156) 56(84) bytes of data.
64 bytes from vostok.canonical.com
I think this was user-error... I think the serial console was just messing with
me.
I'll re-open if I see it again.
** Changed in: apport (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I believe that this change has broken cosmic cloud-images.
there is 'journalctl -o short-precise' output of a 20180530 image booted in kvm
at
http://paste.ubuntu.com/p/xhzxNc4QtR/
>From that you will see:
May 31 15:54:35.838996 ubuntu systemd[1]: sysinit.target: Found ordering
cycle on
Public bug reported:
ubuntu-bug is now producing links that do not work.
using 'ubuntu-bug' in xenial produces links that look like:
https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/0f274d36-64f2-11e8-b34a-002481e7f48a?
but the cosmic version produces links like:
** Summary changed:
- SRU pollinate 4.32
+ SRU pollinate 4.33
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761240
Title:
SRU pollinate 4.33
To manage notifications about this bug go to:
This is fixed in upstream at revision 372.
It affects only systems that are booted without systemd. In Ubuntu, that means
only trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774043
Title:
** Description changed:
if running on xen and not using systemd (such as in trusty)
pollinate will report its virt as
- virt/xen/xen
+ virt/virt/xen
rather than
- virt/xen
+ virt/xen
** Summary changed:
- non-systemd path reports virt/xen/xen when inside xen.
+ non-systemd path
Public bug reported:
if running on xen and not using systemd (such as in trusty)
pollinate will report its virt as
virt/xen/xen
rather than
virt/xen
** Affects: pollinate (Ubuntu)
Importance: Medium
Status: Confirmed
** Changed in: pollinate (Ubuntu)
Status: New =>
@Martin,
Can you file this upstream with 'tuned' ? or is it not a problem with upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774000
Title:
Fails to boot cirros QEMU image with tuned
n: pollinate (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: pollinate (Ubuntu Cosmic)
Assignee: (unassigned) => Scott Moser (smoser)
** Changed in: pollinate (Ubuntu Trusty)
Assignee: (unassigned) => Chad Smith (chad.smith)
** Changed in: pollinate (Ubuntu Xenial)
** Description changed:
ubuntu-server has a hard dependency on open-iscsi, which means there is
a daemon running (iscsid), and the package cannot be removed. All
unnecessary daemons are a cause of concern when auditing a system.
Propose moving this to "Recommends" instead, which
** Description changed:
In bionic, the open-iscsi systemd unit has the following guards to keep
it from running on systems with no iscsi targets configured:
# Must have some pre-defined targets to login to
ConditionDirectoryNotEmpty=|/etc/iscsi/nodes
# or have a session to use via
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576351
Title:
include cloud-init in ubuntu-server disable by default in
@Christian,
Well, the intended goal is that ubuntu-server == cloud-image.
we did fairly significant work to get as close as we are.
Currently cloud-image [1] differs from ubuntu-server [2] only by
presense of cloud-init and openssh-server.
The goal was to ultimately drop those also, and
** Changed in: ssh-import-id (Ubuntu Xenial)
Status: Fix Committed => Triaged
** Tags removed: verification-failed-xenial verification-needed
verification-needed-bionic xenial
** Tags added: verification-done verification-done-bionic
** Attachment added: "verification log for bionic"
** Description changed:
=== Begin SRU Template ===
- [Impact]
+ [Impact]
Running ssh-import-id without environment variable HOME set
will fail and print an error message like:
TypeError: join() argument must be str or bytes, not 'NoneType'
[Test Case]
$ name="my-x"
- $
** Changed in: curtin (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772037
Title:
lintian warnings on source package
To manage notifications about this
@Suraj,
Hi, I don't think the problem you're seeing is at all related to this bug.
If you are still having the problem file a new bug
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+filebug/
Please attach to it
a.) /var/log/cloud-init.log
b.) /var/log/cloud-init-output.log
c.) the cloud
Public bug reported:
current ubuntu/devel build shows the following warnings (in cosmic)
W: curtin source: package-uses-deprecated-debhelper-compat-version 7
W: curtin source: ancient-python-version-field x-python3-version 3.2
W: curtin source: ancient-standards-version 3.9.6 (released
I've marked as 'verification-done' based on comment 7 and 8 above.
** Tags removed: verification-need-bionic verification-needed
** Tags added: verification-done verification-done-bionic
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new
An upstream commit landed for this bug.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=d5374bba
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi,
I believe you're suggesting that cloud-init fails handle config-drive
data that you've provided it. From what I can understand, this config-
drive data is from a locally modified OpenStack.
Cloud-init does not support all possible things that look remotely like
a Config Drive from
** Also affects: ssh-import-id (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ssh-import-id (Ubuntu)
Status: New => Confirmed
** Changed in: ssh-import-id (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of
** Also affects: ssh-import-id (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ssh-import-id (Ubuntu)
Status: New => Confirmed
** Changed in: ssh-import-id (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
** Merge proposal linked:
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/345365
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767131
Title:
Pre-seeded snaps are not
Full verification log attached, the gist is:
## look for iproute2 in the new package
root@b1:~# apt-cache show cloud-init=18.2-27-g6ef92c98-0ubuntu1~18.04.1 | grep
iproute2 || echo not-there
Depends: cloud-guest-utils | cloud-utils, isc-dhcp-client, iproute2, nplan |
ifupdown, procps, python3,
Hi,
please run as root 'cloud-init collect-logs' and get the cloud-init.tar.gz
it collects many things other than just the cloud-init-output.log.
the output log doens't give us enough info.
thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Ivan,
Thanks for taking the time to report a bug.
Could you please run:
cloud-init collect-logs
and then attach the 'cloud-init.tar.gz' that it produces ?
Without more information we can't really help much.
When you've done so, set the status of this bug back to 'New'.
Thanks.
Scott
**
This is at least related to commit
4bd5870f62df771f2a346b0003fd03e44d7fac19
https://git.launchpad.net/cloud-init/commit/?id=4bd5870f62df77
right ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Corey,
Thanks for finding this bug, reporting it and even finding the fix.
If you'd like to have your name in the cloud-init changelog for the fix,
please:
a.) sign the merge canonical contributors agreement
b.) submit a merge proposal
there is information on how to do each at
Marking verification-done for artful.
IBM Cloud only provides Ubuntu at LTS versions, so there is no
artful image that we can launch. Thus, this test is a bit contrived
and the bug is quite unlikely to affect a user there.
To test anyway, we launch an Ubuntu 16.04, and manually upgrade it to
marked verification-done-xenial based on comment 13 above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766401
Title:
full config file wiped after apt-upgrade issued
To manage notifications
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Low
** Changed in: cloud-init (Ubuntu)
Importance: Low => Medium
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Scott Moser (smos
The snap module, which processes 'snap' configuration [1] currently runs
just about as early as it can run. The snapd daemon is not available until
cloud_config_modules time frame [2], so use of 'snap' or any provided
commands is not possible before that.
This means that bootcmd cannot use snap
** Description changed:
- When IBMCloud deploys from a template, artifacts from the
+ === Begin SRU Template ===
+ [Impact]
+ Cloud-init is disabled in the provisioning state. If provisioning
+ artifacts are left around after debug mode, cloud-init remains disabled
+ and doesn't properly
** Description changed:
- file: 50-cloud-init.cfg wiped of it's initial (working) configuration
- after a standard apt-upgrade was issued.
+ === Begin SRU Template ===
+ [Impact]
+ Upgrades of cloud-init on official Ubuntu 16.04 and 17.10 images
+ running on IBM public cloud will be unreachable
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Cc-series)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Bionic)
Importance: Medium
Status: Confirmed
** Also affects:
Hi David,
Thank you for the information.
Its not clear to me what the problem is.
Please answer:
Which OS did you ugprade from artful to bionic? The host? the container?
both?
I just successfully attempted a upgrade from an artful lxd container to
bionic lxd container (my host is bionic,
cloud-init collect-logs
writes output to the current working directory named 'cloud-
init.tar.gz'.
Can you please attach that?
thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768118
David,
After you've provided the information requested, please set the bug back to
'New' status.
Thanks,
Scott
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768118
Title:
Hi David,
Thank you for filing the bug.
Could you please run 'cloud-init collect-logs' and attach the output?
We're interested also in knowing what platform you are running on.
Is cloud-init installed on your container host ? Is that running on a cloud
platform?
Or, are you only having
I'm marking verification-done for xenial and artful based on my attached
logs and xenial based on Jared's comment above.
** Tags removed: verification-needed verification-needed-artful
verification-needed-xenial
** Tags added: verification-done verification-done-artful
verification-done-xenial
** Attachment added: "verification log of xenial via vm boot"
https://bugs.launchpad.net/cloud-utils/+bug/1762748/+attachment/5130962/+files/notes-xenial-boot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "verification log of artful via vm boot"
https://bugs.launchpad.net/cloud-utils/+bug/1762748/+attachment/5130963/+files/notes-artful-boot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
=== Begin SRU Template ===
[Impact]
Growpart will not grow a partition past the 2TB mark.
The code to do this is present by design for MBR partitioned disks but
was active both for MBR and for GPT.
The primary impact is that guests with very large root disks
** Attachment added: "verification log of artful via test-script"
https://bugs.launchpad.net/cloud-utils/+bug/1762748/+attachment/5130945/+files/notes-artful-testscript.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "verification log of xenial via test-script"
https://bugs.launchpad.net/cloud-utils/+bug/1762748/+attachment/5130947/+files/notes-xenial-testscript.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking verification-done-xenial based on Jared's comment.
George, get-proposed-cloudimg can download and update a cloud-image for you.
see more info in the test example above.
get-proposed-cloudimg --proposed --upgrade=cloud-guest-utils \
xenial xenial-proposed.img
--
You received this bug
Public bug reported:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. Notable changes for Ubuntu stable releases are:
* debian/control: add missing dependency
An upstream commit landed for this bug.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=4731c8da
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Merge proposal linked:
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344546
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767166
Title:
IBMCloud datasource does not
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Status: New => In Progress
** Changed in: cloud-init
Assignee: (unassigned) => Ryan Harper (raharper)
--
Public bug reported:
When IBMCloud deploys from a template, artifacts from the
provisioning stage are normally cleaned up. Cloud-init relied'
on that behavior to determine the provisioning boot from the subsequent
post-provisioning boot.
However, when testing, the provisioning stage will leave
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766714
Title:
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-init
Ugh.
the merge proposal at
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/342214
put a build-depends on isc-dhcp-client
not a runtime depends.
i've opened bug 1766714 to address.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
bug 1759307 incorrectly added a build-depends rather than a Depends.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cloud-init 18.2-14-g6d48d265-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion:
Public bug reported:
cloud-init is not marking a dependency on iproute2.
It needs iproute2 or nettools to rename devices.
It was assumed that cloud-init would have dependencies of 'ubuntu-
minimal', but some official ubuntu-minimal images do not have ubuntu-
minimal.
ProblemType: Bug
this came from
https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2018-April/017967.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762724
Title:
Exec slaves and controlling TTY
To
Hi,
I've marked this verification-failed as we had found some issues and forgotten
that there was an upload in the xenial queue.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-failed verification-failed-xenial
--
You received this bug notification
Public bug reported:
The changes in commit 6d48d265a05 made netdevinfo.netdev_pformat() stop
showing information about network devices that do not have an address.
see below:
$ git checkout --quiet 6d48d265a05^
$ git rev-parse HEAD
4c573d0e0173d2b1e99a383c54a0a6c957aa1cbb
$ python3 -c 'from
/ubuntu/+source/cloud-utils/log/?h=bug/1762748-artful-growpart-past-2TB-disks
** Changed in: cloud-utils (Ubuntu Xenial)
Assignee: (unassigned) => Scott Moser (smoser)
** Changed in: cloud-utils (Ubuntu Artful)
Assignee: (unassigned) => Scott Moser (smoser)
** Changed in: cloud
An upstream commit landed for this bug.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=4c573d0e
** Changed in: cloud-init
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
An upstream commit landed for this bug.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=025ddc03
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763511
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu)
Status: New => Confirmed
** Changed in: curtin (Ubuntu)
Importance: Undecided => Medium
** Changed in: curtin (Ubuntu)
Status: Confirmed => In Progress
--
You received
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu)
Status: New => Confirmed
** Changed in: curtin (Ubuntu)
Importance: Undecided => Medium
** Changed in: curtin (Ubuntu)
Status: Confirmed => In Progress
--
You received
** Changed in: cloud-init (Ubuntu)
Status: New => In Progress
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763511
** Description changed:
=== Begin SRU Template ===
[Impact]
Growpart will not grow a partition past the 2TB mark.
The code to do this is present by design for MBR partitioned disks but
was active both for MBR and for GPT.
The primary impact is that guests with very large root disks
marked this fix-released.
I dont see the problem any more.
It is possible it still affects 4.4 series, but bionic is fine for sure.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This was a stock lxc launch.
$ lxc launch ubuntu-daily:bionic b4
$ lxc exec b4 /bin/bash
root@b4:~# cat /etc/cloud/build.info
build_name: server
serial: 20180411
root@b4:~# ubuntu-bug systemd
*** Collecting problem information
The collected information can be sent to the developers to
False", I'm guessing that whether gpt or mbr is specified makes no
> difference.
>
> Mike
>
> On Thu, Apr 12, 2018 at 8:41 PM, Scott Moser <ssmoser2+ubu...@gmail.com>
> wrote:
>
> > You probably need to change table_type mbr to gpt too if the point is
> > big dis
** Description changed:
=== Begin SRU Template ===
[Impact]
Growpart will not grow a partition past the 2TB mark.
The code to do this is present by design for MBR partitioned disks but
was active both for MBR and for GPT.
The primary impact is that guests with very large root disks
** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+ Growpart will not grow a partition past the 2TB mark.
+ The code to do this is present by design for MBR partitioned disks but
+ was active both for MBR and for GPT.
+
+ The primary impact is that guests with very large root disks
** Also affects: cloud-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-utils (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-utils (Ubuntu)
Importance: Undecided => Medium
** Changed in: cloud-utils
Status: Confirmed => Fix Committed
**
You probably need to change table_type mbr to gpt too if the point is
big disks. In fact it might just be the mbr table that is limiting you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763511
fwiw, I think you could send vendor-data to with cloud-config to set the
fs_setup like you wanted (assuming 'you' here are the cloud platform).
The point of vendor data is so that the vendor could make changes like
this without changing cloud-init.
But the 1 byte change is also acceptable.
An upstream commit landed for this bug.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=c6dff581
** Changed in: cloud-init
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Branch linked: lp:~thedac/simplestreams/lp1611987
** Also affects: simplestreams
Importance: Undecided
Status: New
** Also affects: simplestreams (Ubuntu)
Importance: Undecided
Status: New
** Changed in: simplestreams (Ubuntu)
Status: New => Confirmed
** Changed
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these improvements.
The notable ones are:
* zfs/zpool version=28 by default, allow users to
** Also affects: simplestreams (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: simplestreams (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: simplestreams (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: simplestreams (Ubuntu
** Changed in: cloud-init (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762773
Title:
IBM Cloud datasource not enabled by default.
To manage
** Changed in: cloud-init (Ubuntu)
Status: New => In Progress
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug notification because you are
cture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: cloud-init (Ubuntu)
Importance: High
Assignee: Scott Moser (smoser)
Status: I
** Description changed:
'openstack server list' does an obscene number of HTTP requests (228 in
my case) and as a result is very slow compared to 'nova list'.
By comparison, the 'nova list' command does 6.
$ openstack --debug server list > openstack.log 2>&1
real 1m48.731s
The upstream commit didnt' actually fix the issue, as there are 2
occurences that use HOME.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-failed-xeniall
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
When trying to test my changes for bug 1686086, I was unable to auth
to keystone, which means glance image sync just doesn't work with
a v3 keystone.
Related bugs:
* bug 1719879: swift client needs to use v1 auth prior to ocata
* bug 1728982: openstack
501 - 600 of 11836 matches
Mail list logo
