PR accepted upstream. I've backported the patch the oracular MP above.
What needs to be done now to get this into an SRU for noble?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040483
Title:
PR opened upstream: https://github.com/containers/common/pull/2004
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040483
Title:
AppArmor denies crun sending signals to containers (stop, kill)
To
ubuntu@srv-9vqc0:~$ sudo grep -r "runbindable*/*" /etc/apparmor.d
/etc/apparmor.d/abstractions/passt: mount options=(rw, runbindable) /,
ubuntu@srv-9vqc0:~$ sudo aa-logprof
ERROR: Operation {'runbindable'} cannot have a source. Source =
AARE('/')
HTH
--
You received this bug notification
I've pushed the changes based on your comments to the MP above. I've
left the signal set for podman as (int, quit, term, kill).
Do you think that signal set should be tighter, or is that a good
compromise?
If that seems ok with you, I'll happily handle the PR upstream at
GitHub.
--
You
The debdiff is in the MP above.
Podman does try to kill the container itself, as the error trace above
testifies.
May 14 11:14:41 srv-omzr6 kernel: audit: type=1400
audit(1715685281.392:118): apparmor="DENIED" operation="signal"
class="signal" profile="containers-default-0.57.4" pid=7458
Adding the podman signal line, and building a libpod that overrides the
default packages eliminates the errors I was getting.
All the tests in this ticket pass with the updated packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've built a backported 4.9.4 libpod for noble based on an updated
golang-github-containers-common including the above patch.
It's available from ppa:brightbox/experimental
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The debdiff I've put together for oracular updates the patch to be a bit
more general and cover all the signals I've seen so far in testing. (As
well as dropping the other patch that has been incorporated upstream).
# Allow certain signals from OCI runtimes (podman, runc and crun)
signal
The patch above doesn't work as it stands. We are still getting signal
filters in the audit log
May 14 11:13:06 srv-omzr6 kernel: audit: type=1400 audit(1715685186.296:112):
apparmor="DENIED" operation="signal" class="signal"
profile="containers-default-0.57.4" pid=8031 comm="3"
Public bug reported:
On the latest LTS, aa-logprof does nothing other than fail with the
error
ERROR: Operation {'runbindable'} cannot have a source. Source =
AARE('/')
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: apparmor-utils 4.0.0-beta3-0ubuntu3
ProcVersionSignature: User Name
To move this on a bit more rapidly as it is a blocking issue for me.
It's the same version in Oracular at present. I've pushed the changes as
an MP against ubuntu/devel.
What needs to happen next?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Merge proposal linked:
https://code.launchpad.net/~neil-aldur/ubuntu/+source/golang-github-containers-common/+git/golang-github-containers-common/+merge/465970
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Ubuntu Noble
requestsync has started failing on this version of Ubuntu
$ requestsync mkosi
Traceback (most recent call last):
File "/usr/bin/requestsync", line 402, in
main()
File "/usr/bin/requestsync", line 187, in main
Package: mkosi
Version: 20-1
Severity: normal
Tags: upstream patch
X-Debbugs-Cc: n...@aldur.co.uk
Dear Maintainer,
v20 erroneously removed the copy nspawn settings functionality even
though it continues to be used by 'machinectl pull-tar'. This has been
reversed upstream, and I would if you
Package: mkosi
Version: 20-1
Severity: normal
Tags: upstream patch
X-Debbugs-Cc: n...@aldur.co.uk
Dear Maintainer,
v20 erroneously removed the copy nspawn settings functionality even
though it continues to be used by 'machinectl pull-tar'. This has been
reversed upstream, and I would if you
Package: inetutils-telnetd
Version: 2:2.4-3
Severity: wishlist
Tags: patch
X-Debbugs-Cc: n...@aldur.co.uk
Dear Maintainer,
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-3-cloud-amd64 (SMP
Package: rclone
Version: 1.53.3-4ubuntu1
Severity: normal
Dear Maintainer,
rclone uses TLS to connect to remote repositories, but lacks a Suggests
on ca-certificates. This leads to "x509: certificate signed by unknown
authority" errors.
Adding it in would mirror the Suggests in the 'openssl'
Wonderful. Thank you.
> On 7 Feb 2021, at 18:05, Dmitry Shachnev <1913...@bugs.launchpad.net> wrote:
>
> And finally it migrated.
>
> ** Changed in: puppet (Ubuntu)
> Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
I have prepared a 1ubuntu1 version with what I think is the missing
diff.
https://launchpad.net/~brightbox/+archive/ubuntu/experimental?field.series_filter=hirsute
which has been built from the following branch
https://code.launchpad.net/~neil-
Package: puppet
Version: 5.5.22-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
*** /tmp/tmpcldu3hrj/bug_body
In Ubuntu, the attached patch was applied to achieve the following:
This change allows autopkgtest to complete when run
** Changed in: puppet (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913557
Title:
Please merge 5.5.22-1 into hirsute
To manage notifications about this
Similarly the Debian package passes a local Autopkgtest
Following 4.3 here: https://packaging.ubuntu.com/html/auto-pkg-test.html
#executing-the-test
$ sudo autopkgtest puppet -U --apt-pocket=proposed=src:puppet -- qemu
autopkgtest-hirsute-amd64.img
Gives
autopkgtest [10:55:15]: test
Are there know differences between the Debian CI and the Ubuntu CI?
Because it passes autopkgtest over there.
https://ci.debian.net/data/autopkgtest/testing/amd64/p/puppet/10026148/log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Backport to Focal available at
https://launchpad.net/~brightbox/+archive/ubuntu/experimental
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913567
Title:
Sync puppet 5.5.22-1 (universe) from
Public bug reported:
Please sync puppet 5.5.22-1 (universe) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* d/t/control: fix second dep8 test by telling it to not use a proxy
for the "puppet" hostname, and allow stderr because of a ruby
** Changed in: puppet (Ubuntu)
Status: New => 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/1913557
Title:
Please merge 5.5.22-1 into hirsute
To manage notifications about this
Public bug reported:
tracking bug
** Affects: puppet (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913557
Title:
Please merge 5.5.22-1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: puppet 5.5.10-4ubuntu3
ProcVersionSignature: User Name 5.4.0-62.70-generic 5.4.78
Uname: Linux 5.4.0-62-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jan 27 17:11:14 2021
*** This bug is a duplicate of bug 1875848 ***
https://bugs.launchpad.net/bugs/1875848
Public bug reported:
The puppet 5.5 version available in Focal throws a lot of ruby warnings,
which interferes with the puppet installation traces.
remote: /usr/lib/ruby/vendor_ruby/puppet/util.rb:461:
Public bug reported:
remote: ^[[1;31mError: Execution of '/usr/bin/gem install --no-rdoc --no-ri
uricp' returned 1: ERROR: While executing gem ... (OptionParser::InvalidOption)
remote: invalid option: --no-rdoc
remote: Did you mean? no-force^[[0m
remote: ^[[1;31mError:
This is for an ancient version of QEMU and no doubt a network approach
that is long since obsolete.
Probably best to close it as an edge case. If I run into it again I'll
re-raise.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
If the fix is not in the security pocket, how does it get sorted if the
updates pocket is turned off?
I understood *-updates are only supposed to be recommended.
As I mentioned if you build an image with a tool like 'mkosi' which utilises
debootstrap and then cleans the cache, the partial
If the fix is not in the security pocket, how does it get sorted if the
updates pocket is turned off?
I understood *-updates are only supposed to be recommended.
As I mentioned if you build an image with a tool like 'mkosi' which utilises
debootstrap and then cleans the cache, the partial
Public bug reported:
Clicking 'disable' on the IPv6 tag doesn't appear to remove auto-
configured IPv6 addresses or turn off the IPv6 operations on the
specified interface.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.8-1ubuntu1
ProcVersionSignature: Ubuntu
Public bug reported:
Clicking 'disable' on the IPv6 tag doesn't appear to remove auto-
configured IPv6 addresses or turn off the IPv6 operations on the
specified interface.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.8-1ubuntu1
ProcVersionSignature: Ubuntu
Public bug reported:
Clicking 'disable' on the IPv6 tag doesn't appear to remove auto-
configured IPv6 addresses or turn off the IPv6 operations on the
specified interface.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.8-1ubuntu1
ProcVersionSignature: Ubuntu
"I think you're trying to start dhclient on an interface that's already
setup."
It just triggers a lease refresh on the existing interface, which has
the same issue.
Nov 15 14:17:10 srv-ywz63 systemd-logind[981]: New session 27 of user ubuntu.
Nov 15 14:17:10 srv-ywz63 systemd[1]: Started
"I think you're trying to start dhclient on an interface that's already
setup."
It just triggers a lease refresh on the existing interface, which has
the same issue.
Nov 15 14:17:10 srv-ywz63 systemd-logind[981]: New session 27 of user ubuntu.
Nov 15 14:17:10 srv-ywz63 systemd[1]: Started
LGTM on bionic
ubuntu@srv-ywz63:~$ dpkg -l systemd | grep ii
ii systemd237-3ubuntu10.32 i386 system and service manager
ubuntu@srv-ywz63:~$ journalctl -b -u systemd-resolved | grep Started
Nov 14 17:05:43 srv-ywz63 systemd[1]: Started Network Name Resolution.
Nov 14 17:05:44
LGTM on bionic
ubuntu@srv-ywz63:~$ dpkg -l systemd | grep ii
ii systemd237-3ubuntu10.32 i386 system and service manager
ubuntu@srv-ywz63:~$ journalctl -b -u systemd-resolved | grep Started
Nov 14 17:05:43 srv-ywz63 systemd[1]: Started Network Name Resolution.
Nov 14 17:05:44
The same issue here. There are no hwrandom devices on the VM when it
starts. The hypervisor is configured to supply entropy via the
virtio-rng device, which all works as expected with Ubuntu cloud
images
--
Neil Wilson - Brightbox (Leeds, UK)
The same issue here. There are no hwrandom devices on the VM when it
starts. The hypervisor is configured to supply entropy via the
virtio-rng device, which all works as expected with Ubuntu cloud
images
--
Neil Wilson - Brightbox (Leeds, UK)
For me the login screen hangs as the Ubuntu logo at the bottom of the
screen fades in.
The crashes are here
https://errors.ubuntu.com/user/9918ca952fad5050e5d19cd326c70f270fae7631e330cf3c0c0ee4c728f149c2412b9c7bbdbfed5f6d72b3f62f187ada199b6d5ac8043b4329d0bbe352b51487
--
You received this bug
For me the login screen hangs as the Ubuntu logo at the bottom of the
screen fades in.
The crashes are here
https://errors.ubuntu.com/user/9918ca952fad5050e5d19cd326c70f270fae7631e330cf3c0c0ee4c728f149c2412b9c7bbdbfed5f6d72b3f62f187ada199b6d5ac8043b4329d0bbe352b51487
--
You received this bug
For me the login screen hangs as the Ubuntu logo at the bottom of the
screen fades in.
The crashes are here
https://errors.ubuntu.com/user/9918ca952fad5050e5d19cd326c70f270fae7631e330cf3c0c0ee4c728f149c2412b9c7bbdbfed5f6d72b3f62f187ada199b6d5ac8043b4329d0bbe352b51487
--
You received this bug
Public bug reported:
After package updates on 10/6/19 the login screen froze. Turning Wayland
off in the GDM configuration worked around the issue,
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xwayland 2:1.19.6-1ubuntu4.2
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname:
Public bug reported:
After package updates on 10/6/19 the login screen froze. Turning Wayland
off in the GDM configuration worked around the issue,
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xwayland 2:1.19.6-1ubuntu4.2
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname:
Public bug reported:
After package updates on 10/6/19 the login screen froze. Turning Wayland
off in the GDM configuration worked around the issue,
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xwayland 2:1.19.6-1ubuntu4.2
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname:
** Summary changed:
- Simplestreams is missing a dependency on gpg
+ Simplestreams
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827502
Title:
Simplestreams
To manage notifications about this
** Changed in: simplestreams (Ubuntu)
Status: New => Invalid
** Description changed:
- When installing in docker containers there is no gpg available for use
- by /usr/bin/sstream-sync
-
- Traceback (most recent call last):
- File "/usr/bin/sstream-sync", line 169, in
- main()
-
Public bug reported:
When installing in docker containers there is no gpg available for use
by /usr/bin/sstream-sync
Traceback (most recent call last):
File "/usr/bin/sstream-sync", line 169, in
main()
File "/usr/bin/sstream-sync", line 161, in main
tmirror.sync(smirror,
I think just a delta change process would be fine. It's restarting when
there is no change in lease details, and just clogging up the logs.
btw I am not suggesting leaving dhclient there is a bug - hence the
title of the bug.
--
You received this bug notification because you are a member of
I think just a delta change process would be fine. It's restarting when
there is no change in lease details, and just clogging up the logs.
btw I am not suggesting leaving dhclient there is a bug - hence the
title of the bug.
--
You received this bug notification because you are a member of
Public bug reported:
If a cloud server is upgraded from Xenial to Bionic, the dhclient system
remains in place and any DHCP lease refreshes cause a needless restart
of the system-resolved daemon
Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on ens3
to 10.226.209.105
Public bug reported:
When upgrading from Trusty to Xenial it is possible to have a disk that
is half empty but has run out of inodes due to uncleared kernel updates.
This of course causes the upgrade to fail with catastrophic and
irreversible results
Not sure what pre-flight checks upgrader
For example proxy is LSB generated, not systemd native
$ systemctl status swift-proxy
● swift-proxy.service - LSB: Swift proxy server
Loaded: loaded (/etc/init.d/swift-proxy; generated)
Active: active (running) since Fri 2018-10-26 15:13:07 UTC; 1 weeks 2 days
ago
Docs:
Public bug reported:
The Debian upstream packages for swift have had Systemd unit support
since
swift (2.6.0-2) experimental; urgency=medium
[ Ondřej Nový ]
* Added Debian tests.
* Removed swift-init.
* Systemd support.
* Added container-sync config files.
* Changed all dependencies
Does the trick nicely. Thank you.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776927
Title:
RTNL assertion
Does the trick nicely. Thank you.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776927
Title:
RTNL
Public bug reported:
Please sync conntrack-tools 1:1.4.5-1 (main) from Debian sid (main)
Explanation of the Ubuntu delta and why it can be dropped:
* d/p/enable-runtime-systemd.patch: Enable systemd runtime support by
default since the package is compiled with --enable-systemd
(LP:
Seems to do the trick
ubuntu@srv-uq8mr:~$ uname -a
Linux srv-uq8mr 4.15.0-23-generic #26~lp1776927 SMP Fri Jun 15 17:06:38 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
[ 307.632377] audit: type=1400 audit(1529163746.165:17): apparmor="STATUS"
operation="profile_load" profile="unconfined"
Seems to do the trick
ubuntu@srv-uq8mr:~$ uname -a
Linux srv-uq8mr 4.15.0-23-generic #26~lp1776927 SMP Fri Jun 15 17:06:38 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
[ 307.632377] audit: type=1400 audit(1529163746.165:17): apparmor="STATUS"
operation="profile_load" profile="unconfined"
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/diff/?id=8230819494b3bf284ca7262ac5f877333147b937
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776927
Title:
RTNL
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/diff/?id=8230819494b3bf284ca7262ac5f877333147b937
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1776927
Title:
Public bug reported:
Running up two containers using ipvlan with IPv6 autoconf active
triggers an assertion failure in the kernel (cloud image running on
Brightbox)
Jun 14 15:16:37 srv-x3w2q kernel: RTNL: assertion failed at
/build/linux-uT8zSN/linux-4.15.0/drivers/net/ipvlan/ipvlan_core.c
Public bug reported:
Running up two containers using ipvlan with IPv6 autoconf active
triggers an assertion failure in the kernel (cloud image running on
Brightbox)
Jun 14 15:16:37 srv-x3w2q kernel: RTNL: assertion failed at
/build/linux-uT8zSN/linux-4.15.0/drivers/net/ipvlan/ipvlan_core.c
Public bug reported:
Please sync haproxy 1.8.3-1 (main) from Debian experimental (main)
Explanation of the Ubuntu delta and why it can be dropped:
* Backport of -x option from upstream haproxy to enable seamless
reloading of haproxy without dropping connections. This is enabled
by
Public bug reported:
Please sync haproxy 1.8.3-1 (main) from Debian experimental (main)
Explanation of the Ubuntu delta and why it can be dropped:
* Backport of -x option from upstream haproxy to enable seamless
reloading of haproxy without dropping connections. This is enabled
by
Public bug reported:
Background installation of the package failed and stoppered up dpkg for
a month. There was no indication the update system wasn't work it.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tcpdump 4.9.2-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu
host-model is "The host-model mode is essentially a shortcut to copying host
CPU definition from capabilities XML into domain XML.”
So usually you don’t have any "feature policy=‘require’” statements with it.
What you have are “feature policy=“disable’” to switch things off.
The ‘feature
Public bug reported:
If you set the DAEMON_ARGS of etcd so that it runs in gateway or
grpc_proxy mode, the unit file will hang on startup
● etcd.service - etcd - highly-available key value store
Loaded: loaded (/lib/systemd/system/etcd.service; enabled; vendor preset: ena
Active:
This appears to be fixed in 3.1.3 of etcd where they have fixed the
sd_notify behaviour.
etcd v3.1.3 (2017-03-10)
- use machine default host when advertise URLs are default
values(localhost:2379,2380) AND if listen URL is 0.0.0.0
- fix 'etcd gateway' schema handling in DNS discovery
- fix
This doesn't appear to have hit the main archive. I'm still seeing
0.9.1-2 installed today on 16.04.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1635192
Title:
package depends on pep8 tool
How long does last week's security update remain in the test repo before it
gets moved to release?
Rgs
Neil Wilson
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt
Refactor and improve nat support to allow conntrack to manage IPv6
NAT entries.
Refactor and improve conntrack nat tests to include IPv6 NAT.
Signed-off-by: Neil Wilson <n...@aldur.co.uk>
---
src/conntrack.c| 213 +
tests/con
The serial update is now in production. Latest zesty image we have is
from 15th Feb and is not picking up the network (probably as expected).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661693
Public bug reported:
ping to a mapped address
ping :::216.58.213.68
sends an ICMPv6 packet out onto the Internet with the mapped address in
the destination packet and the IPv6 address as the source. Mapped
addresses shouldn't appear on the public internet according to the RFC.
I would
Public bug reported:
ping to a mapped address
ping :::216.58.213.68
sends an ICMPv6 packet out onto the Internet with the mapped address in
the destination packet and the IPv6 address as the source. Mapped
addresses shouldn't appear on the public internet according to the RFC.
I would
Public bug reported:
ping to a mapped address
ping :::216.58.213.68
sends an ICMPv6 packet out onto the Internet with the mapped address in
the destination packet and the IPv6 address as the source. Mapped
addresses shouldn't appear on the public internet according to the RFC.
I would
Following this recipe
http://costiser.ro/2016/07/07/overlay-tunneling-with-openvswitch-gre-
vxlan-geneve-greoipsec/#.WDwlxXecZmB
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1645323
Title:
Public bug reported:
The Openvswitch IPSEC daemon fails to start
Nov 28 13:15:57 srv-yz20n systemd[1]: Starting LSB: Open vSwitch GRE-over-IPsec
daemon...
Nov 28 13:15:58 srv-yz20n openvswitch-ipsec[18332]: * Starting
ovs-monitor-ipsec
Nov 28 13:15:58 srv-yz20n python[18360]: ovs| 0 |
Added both cloud-ini t and init-system-helpers from proposed to the
standard Xenial cloud image
(com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:16.04:amd64/20160907.1/disk1.img)
on a suitably sized server.
Reset the cloud init with rm -rf /var/lib/cloud/instances/*, shutdown
the
Added both cloud-ini t and init-system-helpers from proposed to the
standard Xenial cloud image
(com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:16.04:amd64/20160907.1/disk1.img)
on a suitably sized server.
Reset the cloud init with rm -rf /var/lib/cloud/instances/*, shutdown
the
Have we back ported the init-system-helpers changes to Xenial?
I'm only seeing 1.29ubuntu2 this morning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576692
Title:
fully support package
Have we back ported the init-system-helpers changes to Xenial?
I'm only seeing 1.29ubuntu2 this morning.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1576692
Martin,
Probably worth noting that this impacts upon the configuration systems
as well. I'm using the PostgreSQL puppet configuration system, and that
will sit in a loop waiting for PostgresQL to come up before moving onto
the next stage of the configuration.
So if you are using puppet within
Public bug reported:
Got the error:
Can't locate File/Copy/Recursive.pm in @INC (you may need to install the
File::Copy::Recursive module) (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1
/usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5
SRU Verification performed. The proposed package corrects the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521302
Title:
gnome-terminal maximize than un-maximize behaves odd
To manage
SRU Verification performed. The proposed package corrects the problem.
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1521302
Title:
gnome-terminal maximize than un-maximize behaves
Has the SRU process been kicked of for Xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521302
Title:
gnome-terminal maximize than un-maximize behaves odd
To manage notifications about this
Public bug reported:
If bootstrapping a machine on a trusty cloud image and then directly
installing the gui:
/usr/bin/juju bootstrap /usr/bin/juju deploy juju-gui --to 0
/usr/bin/juju expose juju-gui
The installation of the charm fails after the bootstrap.
Bootstrapping environment manual
Public bug reported:
If bootstrapping a machine on a trusty cloud image and then directly
installing the gui:
/usr/bin/juju bootstrap /usr/bin/juju deploy juju-gui --to 0
/usr/bin/juju expose juju-gui
The installation of the charm fails after the bootstrap.
Bootstrapping environment manual
Public bug reported:
If I have 'prefer-ipv6' set and bootstrap a manual environment, then
the dns-name and public address entries show the IPv6 address, not the
dns-name for that IPv6 address - even though it is available via a DNS
PTR record.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Public bug reported:
If I have 'prefer-ipv6' set and bootstrap a manual environment, then
the dns-name and public address entries show the IPv6 address, not the
dns-name for that IPv6 address - even though it is available via a DNS
PTR record.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Public bug reported:
The tools stream for juju doesn't have tools for 'wily' that correspond
with the version of the packages in the main repository.
ubuntu@srv-2f16s:~$ juju --version
1.22.6-wily-amd64
From
https://streams.canonical.com/juju/tools/streams/v1/com.ubuntu.juju:released:tools.json
Public bug reported:
The tools stream for juju doesn't have tools for 'wily' that correspond
with the version of the packages in the main repository.
ubuntu@srv-2f16s:~$ juju --version
1.22.6-wily-amd64
From
https://streams.canonical.com/juju/tools/streams/v1/com.ubuntu.juju:released:tools.json
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1410288
Title:
qemu-img conversion to qcow2 hangs with blank image less than 100kiB
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1410288
Title:
qemu-img conversion to qcow2 hangs with blank image
** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410288
Title:
qemu-img conversion to qcow2 hangs with blank image less than 100kiB
Public bug reported:
If you try to convert a blank image to qcow2 that is less than 100kiB in
size then qemu-img hangs trying to seek to the end of the file.
$ truncate --size 102399 /tmp/temp
$ qemu-img convert -p -O qcow2 /tmp/temp /tmp/temp2.qcow2
I'm finding this on all versions of qemu-img
1 - 100 of 1994 matches
Mail list logo
