@Merlie,
could you please test the attached merge proposal and report if it works?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784713
Title:
cloud-init profile.d files use bash-specific builtin
** Also affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** Changed in: software-properties (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can you test if this works?
http://paste.ubuntu.com/p/wyPPhjRRzP/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784713
Title:
cloud-init profile.d files use bash-specific builtin "local"
To
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (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/1784713
Title:
fixed in cosmic at 18.3-18-g3cee0bf8-0ubuntu1
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug
Please make sure that you end up with the same content that exists in the cloud
images.
We don't want arbitrary differences among ways of installing Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-init (Ubuntu Zesty)
Status: Confirmed => Won't Fix
** Changed in: cloud-init (Ubuntu Artful)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Right.
So we think this was actually just lack of external connection from the system.
This is still an issue though. There is no requirement on internet
connectivity for running a container ('lxc launch ubuntu-daily:bionic').
--
You received this bug notification because you are a member of
Public bug reported:
This is a default container (bionic) launched from a ppc64el host
inside I see:
$ lxc launch ubuntu-daily:bionic sstest-616
$ lxc exec sstest-616 /bin/bash
root@sstest-616:~# systemd-analyze critical-chain
The time after the unit is active or started is printed after the
possibly some relevant info, from journalctl -o short-monotonic
[ 540.929982] sstest-616 systemd[1]: snapd.seeded.service: Failed to reset
devices.list: Operation not permitted
[ 540.930083] sstest-616 sshd[257]: Server listening on 0.0.0.0 port 22.
[ 540.931309] sstest-616 sshd[257]: Server
** Attachment added: "output of journalctl -o short-monotonic -xb"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782616/+attachment/5165355/+files/journal-short-monotonic-xb.txt
** Description changed:
This is a default container (bionic) launched from a ppc64el host
inside I
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Bionic)
Importance: Undecided =>
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Invalid
** Changed in: cloud-init (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm marking this incomplete now.
If we sort out what needs to happen, and that bug 1771858 does not fix this
issue, please set back to 'Confirmed'.
I'd much rather not deal with knowledge in cloud-init of how to set up snap
path. That should all "just work" in the system.
I'd be willing to
this was fixed under
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1760173
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Ivan,
I'm sorry, can you please run 'cloud-init collect-logs' ? It collects
more informmation than the cloud-init-output.log.
then set back to New.
Thanks.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Hi,
I think the correct fix for you is to just get rid of grub-legacy-ec2.
It is not generally a apckage you'd want on a system with a touchpad.
(the error you see is also not likely related to the touchpad).
if this is still a problem for you, please update the bug. and move it
back to "New"
I think these comments are just noise at this piont.
I do not believe you will see them on subsequent updates.
there was a fix that went in that moved the directory from '/etc/kernel/kernel'
to '/etc/kernel' (bug 1581416).
i believe the messages are just a result of that.
if you continued to
cloud-init can collect relevant logs with 'cloud-init collect-logs'
that is what we tell people to run (and what gets done with 'ubuntu-bug
cloud-init').
I know that is not exactly what you're after.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** 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/1724626
Title:
** Description changed:
This issue keeps cropping up. It shows itself in open-iscsi autopkg tests.
I think it might just be "really slow system". It seems the timeout is only
- 1 minute 30 seconds for the disk to appear, and in a happy run you
+ 1 minute 30 seconds for the disk to appear,
i attached as reference
https://hackmd.io/E0ydu7Y7QEe-kroPb6-OOA
at some point we can improve the doc in the debian/tests directory with that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732028
Hi,
thanks for taking the time to file a bug.
Could you please attach the output of:
cloud-init collect-logs
(it will create a .tar.gz file in the local dir).
Then, set the bug state back to 'New'
Thanks.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received
I've marked verification-done-artful based on logs above and content at
https://github.com/cloud-init/ubuntu-sru/tree/master/20180620
We are waiting on lts results for
* TODO: attach Solutions Testing team test results for each LTS
sru-artifact-solutions-qa-xenial
* TODO: attach MAAS Team test
*** This bug is a duplicate of bug 1486113 ***
https://bugs.launchpad.net/bugs/1486113
** This bug has been marked a duplicate of bug 1486113
write_files runs before users/groups, renders "owner" useless
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi,
This bug is belived to be fixed in the version of cloud-init in -proposed of
16.04, 17.10 and 18.04 under SRU bug 1777912.
It would be good if someone could report back on that bug as to whether
or not this is now working for them.
--
You received this bug notification because you are a
** Attachment added: "manual run on joyent. update, clean, reboot,
collect-logs"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1777912/+attachment/5162909/+files/joyent-xenial.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Attach file softlayer-bionic.tar.gz.
** Attachment added: "manual results for softlayer-bionic"
https://bugs.launchpad.net/bugs/1777912/+attachment/5162884/+files/softlayer-bionic.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Attach file softlayer-xenial.tar.gz.
** Attachment added: "manual results for softlayer-xenial"
https://bugs.launchpad.net/bugs/1777912/+attachment/5162883/+files/softlayer-xenial.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Attach integration tests results from
https://jenkins.ubuntu.com/server/view/cloud-
init,%20curtin,%20streams/job/cloud-init-integration-proposed-b/28/.
** Attachment added: "bionic integration test results [jenkins
cloud-init-integration-proposed-b/28] console log."
Attach integration tests results from
https://jenkins.ubuntu.com/server/view/cloud-
init,%20curtin,%20streams/job/cloud-init-integration-proposed-x/23/.
** Attachment added: "xenial integration test results [jenkins
cloud-init-integration-proposed-x/23] console log."
Attach integration tests results from
https://jenkins.ubuntu.com/server/view/cloud-
init,%20curtin,%20streams/job/cloud-init-integration-proposed-b/28/.
** Attachment added: "bionic integration test results [jenkins
cloud-init-integration-proposed-b/28] artifacts"
Attach integration tests results from
https://jenkins.ubuntu.com/server/view/cloud-
init,%20curtin,%20streams/job/cloud-init-integration-proposed-x/23/.
** Attachment added: "xenial integration test results [jenkins
cloud-init-integration-proposed-x/23] artifacts"
Attach integration tests results from
https://jenkins.ubuntu.com/server/view/cloud-
init,%20curtin,%20streams/job/cloud-init-integration-proposed-a/26/.
** Attachment added: "artful integration test results [jenkins
cloud-init-integration-proposed-a/26] console log."
Note that the artful results attachment in comment 19 did actually fail.
However, the failure is a result of bug 1779302.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777912
Title:
sru cloud-init
Attach integration tests results from
https://jenkins.ubuntu.com/server/view/cloud-
init,%20curtin,%20streams/job/cloud-init-integration-proposed-a/26/.
** Attachment added: "artful integration test results [jenkins
cloud-init-integration-proposed-a/26] artifacts"
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix Released
** Changed in: cloud-init
Importance: Undecided => Low
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in:
** Description changed:
UPDATE: SRU regression found during -proposed validation. fix is queued
for xenial, artful and bionic for the following -proposed regression
bug:
https://bugs.launchpad.net/cloud-init/+bug/1780481
Updated description of changes for minor SRU-update to 18.3
** Description changed:
+ [Test Case]
+ # We should see specific version and patch information
+ $ packaged_version=$(dpkg-query --show -f '${version}' cloud-init)
+ $ grep $packaged_version /var/log/cloud-init.log # Expect to stage header
logs
+ ...
+ 2018-07-10 19:33:16,406 - util.py[DEBUG]:
Thanks,
I think the right thing to do here is to just copy the 'noauto' from
underlay/backing partition to the overlay fstab entry.
Could you try this patch?
Thanks.
** Patch added: "suggested fix"
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Invalid
** Changed in: cloud-init (Ubuntu Bionic)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-initramfs-tools (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi, can you please provide your original fstab file and also the one
written by overlayfs ?
** Changed in: cloud-initramfs-tools (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I saw this "in the wild" with /var/log/cloud-init.log showing:
2018-07-09 15:20:22,666 - util.py[DEBUG]: Running command
['add-apt-repository', 'cloud-archive:ocata'] with allowed return codes [0]
(shell=False, capture=True)
2018-07-09 15:20:24,907 - cc_apt_configure.py[ERROR]:
Public bug reported:
Per Adam in #ubuntu-devel:
18:45 smoser: curtin's btrfs-tools dep is muy obsolete. Can
you update it to either btrfs-progs or "brtfs-progs | btrfs-tools" if
you're aiming for backportability?
In addition to debian/control we need to fix any in-target fixes.
package
** Description changed:
Updated description of changes for minor SRU-update to 18.3 targets
Xenial, Artful and Bionic.
18.2.4 -> 18.3 changeset contains
- OpenStack now runs at local time frame network config can be rendered from
network_data.json if configured
Attach integration tests results from
https://jenkins.ubuntu.com/server/view/cloud-
init,%20curtin,%20streams/job/cloud-init-integration-proposed-x/12/.
** Attachment added: "xenial integration test results [jenkins
cloud-init-integration-proposed-x/12] console log."
Attach integration tests results from
https://jenkins.ubuntu.com/server/view/cloud-
init,%20curtin,%20streams/job/cloud-init-integration-proposed-x/12/.
** Attachment added: "xenial integration test results [jenkins
cloud-init-integration-proposed-x/12] artifacts"
Attach integration tests results from
https://jenkins.ubuntu.com/server/view/cloud-
init,%20curtin,%20streams/job/cloud-init-integration-proposed-b/17/.
** Attachment added: "bionic integration test results [jenkins
cloud-init-integration-proposed-b/17] console log."
Attach integration tests results from
https://jenkins.ubuntu.com/server/view/cloud-
init,%20curtin,%20streams/job/cloud-init-integration-proposed-b/17/.
** Attachment added: "bionic integration test results [jenkins
cloud-init-integration-proposed-b/17] artifacts"
Attach integration tests results from
https://jenkins.ubuntu.com/server/view/cloud-
init,%20curtin,%20streams/job/cloud-init-integration-proposed-a/16/.
** Attachment added: "artful integration test results [jenkins
cloud-init-integration-proposed-a/16] console log."
Attach integration tests results from
https://jenkins.ubuntu.com/server/view/cloud-
init,%20curtin,%20streams/job/cloud-init-integration-proposed-a/16/.
** Attachment added: "artful integration test results [jenkins
cloud-init-integration-proposed-a/16] artifacts"
set this as 'High' at least per ubuntu guidelines, there isn't really a
workaround other than "use python2". :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425575
Title:
[py3] corrupts binary
I've poked at this some, originally assuming there was some silly
decode() in a python3 path that was losing data, but I did not see it.
In both python2 and python3 we get to Http._request (in httplib2/__init__.py).
with the same body (minus python3 bytes, python2 string).
To break there, add
Attach integration tests results from
https://jenkins.ubuntu.com/server/view/cloud-
init,%20curtin,%20streams/job/cloud-init-integration-proposed-a/16/.
** Attachment added: "artful integration test results [jenkins
cloud-init-integration-proposed-a/16] artifacts"
Attach integration tests results from
https://jenkins.ubuntu.com/server/view/cloud-
init,%20curtin,%20streams/job/cloud-init-integration-proposed-a/16/.
** Attachment added: "artful integration test results [jenkins
cloud-init-integration-proposed-a/16] console log."
Public bug reported:
Some recent events have made keyservers less reliable than they were
previously:
https://bitbucket.org/skskeyserver/sks-keyserver/issues/57
https://bitbucket.org/skskeyserver/sks-keyserver/issues/60
We have seen a greatly increased failure rate of retreiving keys
Public bug reported:
I'm not sure exactly what got me into this state, but I have several lxc
containers that cannot be deleted.
$ lxc info
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
addresses: []
architectures:
- x86_64
- i686
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in simplestreams in version 0.1.0. If
this is still a problem for you, please make a comment and set the state
back to New
Thank you.
** Changed in: simplestreams
Status: Fix Committed => Fix Released
--
You received this bug notification because you are
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
other workaround is openstack client
openstack console log show xenial-20180617-135556
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777482
Title:
console-log ERROR (TypeError): write() argument
** Description changed:
- $ sstack nova --debug console-log xenial-20180617-135556
+ $ nova --debug console-log xenial-20180617-135556
DEBUG (shell:791) write() argument must be str, not bytes
Traceback (most recent call last):
- File "/usr/lib/python3/dist-packages/novaclient/shell.py",
Public bug reported:
$ sstack nova --debug console-log xenial-20180617-135556
DEBUG (shell:791) write() argument must be str, not bytes
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/novaclient/shell.py", line 789, in main
OpenStackComputeShell().main(argv)
File
I've linked a merge proposal. Please review that if you are interested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1134036
Title:
Failure when using ssh with a locale that is not configured on
Public bug reported:
$ cat > my.yaml <) failed
cloudinit.util.ProcessExecutionError: Unexpected error while running command.
Stderr: Error: The network already exists
** Affects: cloud-init
Importance: Medium
Status: Confirmed
** Affects: cloud-init (Ubuntu)
Importance:
The change in behavior of lxd init was filed as an upstream issue at
https://github.com/lxc/lxd/issues/4649 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776958
Title:
error creating lxdbr0.
To
** Attachment added: "verification log for bionic"
https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1761240/+attachment/5152176/+files/verify-bionic.log
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You
401 - 500 of 11836 matches
Mail list logo
