Re: [Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)

[Neil Wilson]

It may be more useful to generate a synthetic replacement definition from
the go file, and then `apparmor_parser -r` the definition if the definition
exists.


On Fri, 14 Jun 2024 at 21:30, Andreas Hasenack <2040...@bugs.launchpad.net>
wrote:

> ** Also affects: libpod (Ubuntu Oracular)
>Importance: Undecided
>Status: Confirmed
>
> ** Also affects: golang-github-containers-common (Ubuntu Oracular)
>Importance: Undecided
>Status: Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2040483
>
> Title:
>   AppArmor denies crun sending signals to containers (stop, kill)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions
>
>

-- 
Neil Wilson

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)

[Neil Wilson]

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:
  AppArmor denies crun sending signals to containers (stop, kill)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)

[Neil Wilson]

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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065685] Re: aa-logprof fails with 'runbindable' error

[Neil Wilson]

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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065685

Title:
  aa-logprof fails with 'runbindable' error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2065685/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)

[Neil Wilson]

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 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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)

[Neil Wilson]

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
comm="conmon" requested_mask="receive" denied_mask="receive" signal=term
peer="podman"

It's trying to kill conmon in some scenarios, which means your policy
changes so far are deficient in that regard. We can tighten the signal
set there to term and kill, which is certainly no worse than the
pre-4.0.0 situation.

I note the point about the signal set on the runtimes, and that should
be removed. The stop signals can be set to anything within the
container.

I would suggest extending the AARE to cover the binaries as well as the
policy name.

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)

[Neil Wilson]

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 Ubuntu.
https://bugs.launchpad.net/bugs/2040483

Title:
  AppArmor denies crun sending signals to containers (stop, kill)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)

[Neil Wilson]

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.
https://bugs.launchpad.net/bugs/2040483

Title:
  AppArmor denies crun sending signals to containers (stop, kill)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)

[Neil Wilson]

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 (receive) set=(int, quit, kill, term) 
peer={/usr/bin/,/usr/sbin/,}runc,
signal (receive) set=(int, quit, kill, term) 
peer={/usr/bin/,/usr/sbin/,}crun,
signal (receive) set=(int, quit, kill, term) 
peer={/usr/bin/,/usr/sbin/,}podman,


Upstream have said they have no apparmor experience, so I suspect they
will take a PR. See https://github.com/containers/common/issues/1898


** Bug watch added: github.com/containers/common/issues #1898
   https://github.com/containers/common/issues/1898

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)

[Neil Wilson]

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" requested_mask="receive" 
denied_mask="receive" signal=term peer="crun" 
May 14 11:13:06 srv-omzr6 kernel: audit: type=1400 audit(1715685186.318:113): 
apparmor="DENIED" operation="signal" class="signal" 
profile="containers-default-0.57.4" pid=8033 comm="3" requested_mask="receive" 
denied_mask="receive" signal=term peer="crun" 
May 14 11:13:16 srv-omzr6 kernel: audit: type=1400 audit(1715685196.340:114): 
apparmor="DENIED" operation="signal" class="signal" 
profile="containers-default-0.57.4" pid=8035 comm="3" requested_mask="receive" 
denied_mask="receive" signal=kill peer="crun" 
May 14 11:13:21 srv-omzr6 kernel: audit: type=1400 audit(1715685201.413:115): 
apparmor="DENIED" operation="signal" class="signal" 
profile="containers-default-0.57.4" pid=7664 comm="conmon" 
requested_mask="receive" denied_mask="receive" signal=term peer="podman" 
May 14 11:14:31 srv-omzr6 kernel: audit: type=1400 audit(1715685271.577:116): 
apparmor="DENIED" operation="signal" class="signal" 
profile="containers-default-0.57.4" pid=8049 comm="3" requested_mask="receive" 
denied_mask="receive" signal=term peer="crun" 
May 14 11:14:36 srv-omzr6 kernel: audit: type=1400 audit(1715685276.326:117): 
apparmor="DENIED" operation="signal" class="signal" 
profile="containers-default-0.57.4" pid=8052 comm="3" requested_mask="receive" 
denied_mask="receive" signal=kill peer="crun" 
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 comm="conmon" 
requested_mask="receive" denied_mask="receive" signal=term peer="podman" 
May 14 11:14:41 srv-omzr6 kernel: audit: type=1400 audit(1715685281.604:119): 
apparmor="DENIED" operation="signal" class="signal" 
profile="containers-default-0.57.4" pid=8055 comm="3" requested_mask="receive" 
denied_mask="receive" signal=kill peer="crun"

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2065685] [NEW] aa-logprof fails with 'runbindable' error

[Neil Wilson]

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 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApparmorStatusOutput:
 Error: command ['/usr/sbin/apparmor_status'] failed with exit code 4: You do 
not have enough privilege to read the profile set.
 apparmor module is loaded.
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudBuildName: server
CloudID: brightbox
CloudName: brightbox
CloudPlatform: ec2
CloudRegion: gb1s-
CloudSerial: 20240423
CloudSubPlatform: metadata (http://169.254.169.254)
Date: Tue May 14 12:29:17 2024
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-6.8.0-31-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
SourcePackage: apparmor
Syslog:
 2024-05-13T10:19:58.724594+00:00 srv-9vqc0 dbus-daemon[838]: [system] AppArmor 
D-Bus mediation is enabled
 2024-05-13T10:22:32.966857+00:00 srv-9vqc0 dbus-daemon[666]: [system] AppArmor 
D-Bus mediation is enabled
 2024-05-13T10:25:00.210572+00:00 srv-9vqc0 dbus-daemon[1044]: [session 
uid=1000 pid=1044] AppArmor D-Bus mediation is enabled
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apparmor (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cloud-image noble

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065685

Title:
  aa-logprof fails with 'runbindable' error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2065685/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)

[Neil Wilson]

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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040483

Title:
  AppArmor denies crun sending signals to containers (stop, kill)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)

[Neil Wilson]

** 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.
https://bugs.launchpad.net/bugs/2040483

Title:
  AppArmor denies crun sending signals to containers (stop, kill)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1913567] Re: Sync puppet 5.5.22-1 (universe) from Debian unstable (main)

[Neil Wilson]

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
> report.
> https://bugs.launchpad.net/bugs/1913567
> 
> Title:
>  Sync puppet 5.5.22-1 (universe) from Debian unstable (main)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913567/+subscriptions

-- 
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 Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913567/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913567] Re: Sync puppet 5.5.22-1 (universe) from Debian unstable (main)

[Neil Wilson]

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-
aldur/ubuntu/+source/puppet/+git/puppet/+ref/ubuntu/devel

-- 
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 Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913567/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913557] Re: Please merge 5.5.22-1 into hirsute

[Neil Wilson]

** 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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913557/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913567] Re: Sync puppet 5.5.22-1 (universe) from Debian unstable (main)

[Neil Wilson]

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 command4: ---]
autopkgtest [10:55:16]: test command4:  - - - - - - - - - - results - - - - - - 
- - - -
command4 PASS
autopkgtest [10:55:17]:  summary
command1 PASS
command2 PASS
command3 PASS
command4 PASS
qemu-system-x86_64: terminating on signal 15 from pid 17892 (/usr/bin/python3)

Is this is the correct test command to be using locally?

-- 
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 Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913567/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913567] Re: Sync puppet 5.5.22-1 (universe) from Debian unstable (main)

[Neil Wilson]

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 Ubuntu.
https://bugs.launchpad.net/bugs/1913567

Title:
  Sync puppet 5.5.22-1 (universe) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913567/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913567] Re: Sync puppet 5.5.22-1 (universe) from Debian unstable (main)

[Neil Wilson]

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 Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913567/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913567] [NEW] Sync puppet 5.5.22-1 (universe) from Debian unstable (main)

[Neil Wilson]

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
deprecation warning
  * 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
deprecation warning
  * d/p/fix-ruby27-warning.patch: Add patch to fix a warning when executed
with Ruby 2.7. It fixes an autopkgtest regression in ruby-puppet-syntax.
  * d/t/control: Add allow-stderr restriction to puppet master and puppet
master passenger tests.
  * d/t/control: add 'puppet' to $no_proxy variable in puppet-master-passenger
test to let tests make requests to puppet master running locally
(LP: #1869265).
  * d/p/fix-ruby27-warning.patch: Add patch to fix a warning when executed
with Ruby 2.7. It fixes an autopkgtest regression in ruby-puppet-syntax.
  * d/t/control: Add allow-stderr restriction to puppet master and puppet
master passenger tests.
  * d/t/control: add 'puppet' to $no_proxy variable in puppet-master-passenger
test to let tests make requests to puppet master running locally
(LP: #1869265).
  * Revert:
- Revert the Ubuntu delta. No changes left.
  + DEP8 tests fail in the Ubuntu autopkgtest environment without
the delta.
  * d/t/control: fix incorrect merge in 5.4.0-2ubuntu1:
- Wrong test was generating the certificate.
- Wrong tests were being run for puppet-master-passenger.
  * Revert:
- Revert the Ubuntu delta. No changes left.
  + DEP8 tests fail in the Ubuntu autopkgtest environment without
the delta.
  * d/t/control: fix incorrect merge in 5.4.0-2ubuntu1:
- Wrong test was generating the certificate.
- Wrong tests were being run for puppet-master-passenger.
  * Revert:
- Revert the Ubuntu delta. No changes left.
  + DEP8 tests fail in the Ubuntu autopkgtest environment without
the delta.
  * d/t/control: fix incorrect merge in 5.4.0-2ubuntu1:
- Wrong test was generating the certificate.
- Wrong tests were being run for puppet-master-passenger.
  * Revert:
- Revert the Ubuntu delta. No changes left.
  + DEP8 tests fail in the Ubuntu autopkgtest environment without
the delta.
  * d/t/control: fix incorrect merge in 5.4.0-2ubuntu1:
- Wrong test was generating the certificate.
- Wrong tests were being run for puppet-master-passenger.
  * Revert:
- Revert the Ubuntu delta. No changes left.
  + DEP8 tests fail in the Ubuntu autopkgtest environment without
the delta.
  * d/t/control: fix incorrect merge in 5.4.0-2ubuntu1:
- Wrong test was generating the certificate.
- Wrong tests were being run for puppet-master-passenger.
  * Revert:
- Revert the Ubuntu delta. No changes left.
  + DEP8 tests fail in the Ubuntu autopkgtest environment without
the delta.
  * d/t/control: fix incorrect merge in 5.4.0-2ubuntu1:
- Wrong test was generating the certificate.
- Wrong tests were being run for puppet-master-passenger.
  * Fix duplicate oids, cherrypick upstream patch for OpenSSL 1.1 compat.
  * debian/patches/ruby2.3.6_compat.patch: SSL behavior changed in ruby
2.3.6.
  * Merge with Debian unstable (LP: #1702578). Remaining changes:
- d/t/control: disable sysv-init tests as it does not exist on
  Ubuntu.
- d/t/spec/puppet-master-passenger/zz_puppet3_compat_spec.rb:
  specify to curl that 'puppet' should not be proxied.
- d/t/control: generate a certificate for puppet master if it does
  not already exist, as it is needed by the tests.
  * Drop:
- d/p/0005-use-systemd-as-the-default-service-provider.path: also
  make systemd the default provider on Ubuntu.
  [ Fixed in Debian 4.10.4-1 ]
  * Merge with Debian unstable (LP: #1702578). Remaining changes:
- d/t/control: disable sysv-init tests as it does not exist on
  Ubuntu.
- d/t/spec/puppet-master-passenger/zz_puppet3_compat_spec.rb:
  specify to curl that 'puppet' should not be proxied.
- d/t/control: generate a certificate for puppet master if it does
  not already exist, as it is needed by the tests.
  * Drop:
- d/p/0005-use-systemd-as-the-default-service-provider.path: also
  make systemd the default provider on Ubuntu.
  [ Fixed in Debian 4.10.4-1 ]
  * Merge with Debian unstable. Remaining changes:
- d/p/0005-use-systemd-as-the-default-service-provider.path: also
  make systemd the default provider on Ubuntu.
- d/t/control: disable sysv-init tests as it does not exist on
  Ubuntu.
- d/t/spec/puppet-master-passenger/zz_puppet3_compat_spec.rb:
  specify to curl that 'puppet' should not be proxied.
- d/t/control: generate a certificate for puppet master if it does
  not already exist, as it is needed by the 

[Bug 1913557] Re: Please merge 5.5.22-1 into hirsute

[Neil Wilson]

** 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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913557/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913557] [NEW] Please merge 5.5.22-1 into hirsute

[Neil Wilson]

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 into hirsute

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913557/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913466] Re: puppet gem provider fails in Focal

[Neil Wilson]

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
PackageArchitecture: all
SourcePackage: puppet
UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913466

Title:
  puppet gem provider fails in Focal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913466/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913467] [NEW] puppet throws numerous ruby warnings on Focal

[Neil Wilson]

*** 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: warning: URI.escape is 
obsolete
remote: /usr/lib/ruby/vendor_ruby/puppet/file_system/uniquefile.rb:126: 
warning: $SAFE will become a normal global variable in Ruby 3.0
remote: /usr/lib/ruby/vendor_ruby/puppet/util.rb:315: warning: deprecated 
Object#=~ is called on Puppet::Transaction::Report; it always returns nil
emote: /usr/lib/ruby/vendor_ruby/puppet/type/cron.rb:160: warning: deprecated 
Object#=~ is called on Integer; it always returns nil

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
PackageArchitecture: all
SourcePackage: puppet
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: puppet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal uec-images

** This bug has been marked a duplicate of bug 1875848
   Ruby warnings on puppet run on Focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913467

Title:
  puppet throws numerous ruby warnings on Focal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913467/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913466] [NEW] puppet gem provider fails in Focal

[Neil Wilson]

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: /Stage[main]/Mys_service/Package[uricp]/ensure: change 
from 'absent' to 'present' failed: 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


The puppet 5.5 version available in the Focal archives tries to use '--no-rdoc' 
on a gem install, which is not supported by the Ruby 2.7 gem program installed 
by Focal.

** 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/1913466

Title:
  puppet gem provider fails in Focal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913466/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873794] Re: Unattended upgrades fixes missing from security repo

[Neil Wilson]

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 directory is missing in the 
resulting image.

Under the Debian file system layout /var is supposed to be volatile. You
can't rely on anything being there.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1873794

Title:
  Unattended upgrades fixes missing from security repo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1873794/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1866367] [NEW] NetworkManager can't disable IPv6 properly

[Neil Wilson]

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 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  6 15:24:21 2020
InstallationDate: Installed on 2020-03-06 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304)
IpRoute:
 default via 192.168.1.254 dev ens33 proto dhcp metric 100 
 169.254.0.0/16 dev ens33 scope link metric 1000 
 192.168.1.0/24 dev ens33 proto kernel scope link src 192.168.1.86 metric 100
IwConfig:
 lono wireless extensions.
 
 ens33 no wireless extensions.
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE  TIMESTAMP  
 TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 
  
 Wired connection 1  9f785e0c-8a0d-310a-8a14-c603fd38083c  ethernet  1583508227 
 Fri 06 Mar 2020 15:23:47 GMT  yes  -999  no
/org/freedesktop/NetworkManager/Settings/1  yes ens33   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/Wired connection 1.nmconnection
nmcli-dev:
 DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH 
 CONNECTION  CON-UUID   
   CON-PATH   
 ens33   ethernet  connected  full  limited   
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
9f785e0c-8a0d-310a-8a14-c603fd38083c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.22.8   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866367

Title:
  NetworkManager can't disable IPv6 properly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1866367/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial

[Neil Wilson]

"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 Session 27 of user ubuntu.
Nov 15 14:17:30 srv-ywz63 sudo[12484]:   ubuntu : TTY=pts/2 ; PWD=/home/ubuntu 
; USER=root ; COMMAND=/sbin/dhclient eth0
Nov 15 14:17:30 srv-ywz63 sudo[12484]: pam_unix(sudo:session): session opened 
for user root by ubuntu(uid=0)
Nov 15 14:17:30 srv-ywz63 dhclient[12485]: DHCPREQUEST of 10.241.196.178 on 
eth0 to 255.255.255.255 port 67 (xid=0x511efd40)
Nov 15 14:17:30 srv-ywz63 dhclient[12485]: DHCPACK of 10.241.196.178 from 
10.241.196.177
Nov 15 14:17:30 srv-ywz63 dhclient[12485]: bound to 10.241.196.178 -- renewal 
in 1421 seconds.
Nov 15 14:17:30 srv-ywz63 sudo[12484]: pam_unix(sudo:session): session closed 
for user root

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805183

Title:
  systemd-resolved constantly restarts on Bionic upgraded from Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial

[Neil Wilson]

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 srv-ywz63 systemd[1]: Started Network Name Resolution.
ubuntu@srv-ywz63:~$ sudo dhclient eth0
RTNETLINK answers: File exists
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 srv-ywz63 systemd[1]: Started Network Name Resolution.
ubuntu@srv-ywz63:~$


** 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/1805183

Title:
  systemd-resolved constantly restarts on Bionic upgraded from Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

[Neil Wilson]

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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832138

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1832138/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1832320] [NEW] Login screen hang after June 10 package upgrades

[Neil Wilson]

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: Linux 4.15.0-51-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 11 09:56:56 2019
DistUpgraded: 2018-08-19 11:49:41,331 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2016-04-28 (1138 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=5701a684-d599-4319-b6ee-89d8ef7a11db ro quiet splash
SourcePackage: xorg-server
UpgradeStatus: Upgraded to bionic on 2018-08-19 (295 days ago)
dmi.bios.date: 04/13/2018
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832320

Title:
  Login screen hang after June 10 package upgrades

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1832320/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827502] Re: Simplestreams

[Neil Wilson]

** 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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1827502/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827502] Re: Simplestreams is missing a dependency on gpg

[Neil Wilson]

** 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()
-   File "/usr/bin/sstream-sync", line 161, in main
- tmirror.sync(smirror, cfg['path'])
-   File "/usr/lib/python3/dist-packages/simplestreams/mirrors/__init__.py", 
line 85, in sync
- content, payload = reader.read_json(path)
-   File "/usr/lib/python3/dist-packages/simplestreams/mirrors/__init__.py", 
line 43, in read_json
- return raw, self.policy(content=raw, path=path)
-   File "/usr/bin/sstream-sync", line 154, in policy
- checked=cmdargs.verify)
-   File "/usr/lib/python3/dist-packages/simplestreams/util.py", line 290, in 
read_signed
- raise e
-   File "/usr/lib/python3/dist-packages/simplestreams/util.py", line 286, in 
read_signed
- subp(cmd, data=content)
-   File "/usr/lib/python3/dist-packages/simplestreams/util.py", line 458, in 
subp
- raise subprocess.CalledProcessError(rc, args, output=(out, err))
- subprocess.CalledProcessError: Command '['gpg', '--batch', '--verify', '-']' 
returned non-zero exit status 2.
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
- Package: simplestreams 0.1.0~bzr460-0ubuntu1
- ProcVersionSignature: User Name 4.15.0-48.51-generic 4.15.18
- Uname: Linux 4.15.0-48-generic i686
- ApportVersion: 2.20.9-0ubuntu7.6
- Architecture: i386
- Date: Fri May  3 12:05:24 2019
- PackageArchitecture: all
- SourcePackage: simplestreams
- UpgradeStatus: Upgraded to bionic on 2019-04-15 (17 days ago)
+ .

-- 
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 is missing a dependency on gpg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1827502/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827502] [NEW] Simplestreams is missing a dependency on gpg

[Neil Wilson]

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, cfg['path'])
  File "/usr/lib/python3/dist-packages/simplestreams/mirrors/__init__.py", line 
85, in sync
content, payload = reader.read_json(path)
  File "/usr/lib/python3/dist-packages/simplestreams/mirrors/__init__.py", line 
43, in read_json
return raw, self.policy(content=raw, path=path)
  File "/usr/bin/sstream-sync", line 154, in policy
checked=cmdargs.verify)
  File "/usr/lib/python3/dist-packages/simplestreams/util.py", line 290, in 
read_signed
raise e
  File "/usr/lib/python3/dist-packages/simplestreams/util.py", line 286, in 
read_signed
subp(cmd, data=content)
  File "/usr/lib/python3/dist-packages/simplestreams/util.py", line 458, in subp
raise subprocess.CalledProcessError(rc, args, output=(out, err))
subprocess.CalledProcessError: Command '['gpg', '--batch', '--verify', '-']' 
returned non-zero exit status 2.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: simplestreams 0.1.0~bzr460-0ubuntu1
ProcVersionSignature: User Name 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic i686
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
Date: Fri May  3 12:05:24 2019
PackageArchitecture: all
SourcePackage: simplestreams
UpgradeStatus: Upgraded to bionic on 2019-04-15 (17 days ago)

** Affects: simplestreams (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug bionic i386 uec-images

** Summary changed:

- Simplestreams is missing a dependency on gig
+ Simplestreams is missing a dependency on gpg

-- 
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 is missing a dependency on gpg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1827502/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial

[Neil Wilson]

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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805183

Title:
  systemd-resolved constantly restarts on Bionic upgraded from Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1805183] [NEW] systemd-resolved constantly restarts on Bionic upgraded from Xenial

[Neil Wilson]

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 port 67 (xid=0x2bd41d7d)
Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 
10.226.209.105
Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution...
Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution.
Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution...
Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors:
Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1
Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 
'srv-qvjhx'.
Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution.
Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting 
resolvconf-pull-resolved.service...
Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal in 
1466 seconds.
Nov 26 16:59:41 srv-qvjhx systemd[1]: Started resolvconf-pull-resolved.service.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.25
ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
Uname: Linux 4.4.0-139-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CrashDB: ubuntu
Date: Mon Nov 26 16:17:52 2018
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade uec-images xenial

** Summary changed:

- systems-resolved constantly restarts on Bionic upgraded from Xenial
+ systemd-resolved constantly restarts on Bionic upgraded from Xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805183

Title:
  systemd-resolved constantly restarts on Bionic upgraded from Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1805183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1804803] [NEW] do-release-upgrade fails due to lack of inodes

[Neil Wilson]

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 does, but checking for
sufficient inodes as well as disk space (plus checking if the apt cache
is ok like unattended upgrades does) might be worth doing.

In the meantime back to trying to recover the corrupted server... :-)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.10
ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39
Uname: Linux 3.13.0-147-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
CrashDB: ubuntu
Date: Fri Nov 23 11:06:35 2018
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade trusty uec-images

** Description changed:

  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 does, but checking for
  sufficient inodes as well as disk space (plus checking if the apt cache
  is ok like unattended upgrades does) might be worth doing.
  
- In the meantime back to trying to recover this server... :-)
+ In the meantime back to trying to recover the corrupted server... :-)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.10
  ProcVersionSignature: Ubuntu 3.13.0-147.196-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-147-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CrashDB: ubuntu
  Date: Fri Nov 23 11:06:35 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804803

Title:
  do-release-upgrade fails due to lack of inodes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1804803/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1800676] Re: Ubuntu swift packages lack systemd unit files

[Neil Wilson]

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: man:systemd-sysv-generator(8)
Tasks: 3 (limit: 2362)
   CGroup: /system.slice/swift-proxy.service
   ├─9718 /usr/bin/python /usr/bin/swift-proxy-server 
/etc/swift/proxy-server.conf
   ├─9728 /usr/bin/python /usr/bin/swift-proxy-server 
/etc/swift/proxy-server.conf
   └─9729 /usr/bin/python /usr/bin/swift-proxy-server 
/etc/swift/proxy-server.conf

Similarly if you look at the package file list of any of the swift built
packages in ubuntu you will see SysV scripts, Upstart conf files, but no
native systemd unit files.

https://packages.ubuntu.com/bionic/all/swift-account/filelist
https://packages.ubuntu.com/bionic/all/swift-proxy/filelist
https://packages.ubuntu.com/bionic/all/swift-container/filelist
https://packages.ubuntu.com/bionic/all/swift-object/filelist
https://packages.ubuntu.com/bionic/all/swift-object-expirer/filelist

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800676

Title:
  Ubuntu swift packages lack systemd unit files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/swift/+bug/1800676/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1800676] [NEW] Ubuntu swift packages lack systemd unit files

[Neil Wilson]

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 to same version of swift package.
  * Changed shell of "swift" user to /bin/false.
  * Add user "swift" to group "adm", not replace group list.
  * Standards-Version is 3.9.7 now (no change).
  * Fixed Vcs URL.

but none of that appears to have made it past the merge process into the
Ubuntu versions. We are now in the situation where the Bionic and Cosmic
packages are still relying upon dated init scripts, and contain obsolete
Upstart init files.

Is there a case for dropping the diff completely?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: swift-container (not installed)
ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Tue Oct 30 15:29:16 2018
SourcePackage: swift
UpgradeStatus: Upgraded to bionic on 2018-10-30 (0 days ago)

** Affects: swift (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800676

Title:
  Ubuntu swift packages lack systemd unit files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/swift/+bug/1800676/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776927] Re: RTNL assertion failure on ipvlan

[Neil Wilson]

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 failure on ipvlan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776927/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1782189] [NEW] Sync conntrack-tools 1:1.4.5-1 (main) from Debian sid (main)

[Neil Wilson]

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: #1761994).
  * d/p/enable-runtime-systemd.patch: Enable systemd runtime support by
default since the package is compiled with --enable-systemd
(LP: #1761994).
  * Fix FTBFS, IFNAMSIZ no longer declared, replaced with IF_NAMESIZE.

Package backports to Cosmic and builds cleanly. Runtime-systemd patch
incorporated upstream here:
https://git.netfilter.org/conntrack-tools/commit/?id=f75fcf21e17c8f490e34bed45d935bd1e13c9b7f

Changelog entries since current cosmic version
1:1.4.4+snapshot20161117-6ubuntu2:

conntrack-tools (1:1.4.5-1) unstable; urgency=medium

  * [9fa49d0] d/control: point VCS-* to salsa.debian.org
  * [912cd2c] d/t/control: create a ct helper requires isolation machine
  * [29d5b29] New upstream version 1.4.5
  * [ee52723] src:conntrack-tools: bump std-version to 4.1.4
  * [5d914c7] d/patches: drop all patches
  * [dce3f46] d/control: bump build-dep on libnetfilter-conntrack
  * [409804e] d/rules: delete special case for autogen.sh
  * [84af1f3] d/control: bump compat to 11
  * [dda40ee] d/conntrack.examples: drop file

 -- Arturo Borrero Gonzalez   Tue, 01 May 2018
12:59:52 +0200

** Affects: conntrack-tools (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/1782189

Title:
  Sync conntrack-tools 1:1.4.5-1 (main) from Debian sid (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/conntrack-tools/+bug/1782189/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776927] Re: RTNL assertion failure on ipvlan

[Neil Wilson]

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" name="cri-containerd.apparmor.d" 
pid=2039 comm="apparmor_parser"
[  335.794651] eth0: renamed from veth1d773317
[  336.205408] IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
[  336.205570] IPVS: Connection hash table configured (size=4096, 
memory=64Kbytes)
[  336.593750] IPVS: ipvs loaded.
[  336.600809] IPVS: [rr] scheduler registered.
[  336.609316] IPVS: [wrr] scheduler registered.
[  336.616999] IPVS: [sh] scheduler registered.
[  336.766386] Netfilter messages via NETLINK v0.30.
[  336.780403] ip_set: protocol 6

-- 
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 failure on ipvlan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776927/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776927] Re: RTNL assertion failure on ipvlan

[Neil Wilson]

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 assertion failure on ipvlan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776927/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1776927] [NEW] RTNL assertion failure on ipvlan

[Neil Wilson]

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 (110)
Jun 14 15:16:37 srv-x3w2q kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 
4.15.0-23-generic #25-Ubuntu
Jun 14 15:16:37 srv-x3w2q kernel: Hardware name: Red Hat KVM, BIOS 
1.10.2-3.el7_4.1 04/01/2014
Jun 14 15:16:37 srv-x3w2q kernel: Call Trace:
Jun 14 15:16:37 srv-x3w2q kernel:  
Jun 14 15:16:37 srv-x3w2q kernel:  dump_stack+0x63/0x8b
Jun 14 15:16:37 srv-x3w2q kernel:  ipvlan_addr_busy+0x96/0xa0 [ipvlan]
Jun 14 15:16:37 srv-x3w2q kernel:  ipvlan_addr6_event+0x77/0xd0 [ipvlan]
Jun 14 15:16:37 srv-x3w2q kernel:  notifier_call_chain+0x4c/0x70
Jun 14 15:16:37 srv-x3w2q kernel:  atomic_notifier_call_chain+0x1a/0x20
Jun 14 15:16:37 srv-x3w2q kernel:  inet6addr_notifier_call_chain+0x1b/0x20
Jun 14 15:16:37 srv-x3w2q kernel:  ipv6_add_addr+0x43d/0x5c0
Jun 14 15:16:37 srv-x3w2q kernel:  ? addrconf_prefix_route+0xd7/0x120
Jun 14 15:16:37 srv-x3w2q kernel:  addrconf_prefix_rcv_add_addr+0xb9/0x250
Jun 14 15:16:37 srv-x3w2q kernel:  ? addrconf_prefix_rcv_add_addr+0xb9/0x250
Jun 14 15:16:37 srv-x3w2q kernel:  addrconf_prefix_rcv+0x26c/0x740
Jun 14 15:16:37 srv-x3w2q kernel:  ndisc_router_discovery+0x683/0xbe0
Jun 14 15:16:37 srv-x3w2q kernel:  ? ndisc_router_discovery+0x683/0xbe0
Jun 14 15:16:37 srv-x3w2q kernel:  ndisc_rcv+0xe9/0x100
Jun 14 15:16:37 srv-x3w2q kernel:  icmpv6_rcv+0x408/0x540
Jun 14 15:16:37 srv-x3w2q kernel:  ip6_input_finish+0xcc/0x460
Jun 14 15:16:37 srv-x3w2q kernel:  ip6_input+0x3f/0xb0
Jun 14 15:16:37 srv-x3w2q kernel:  ip6_rcv_finish+0x92/0x100
Jun 14 15:16:37 srv-x3w2q kernel:  ipv6_rcv+0x346/0x550
Jun 14 15:16:37 srv-x3w2q kernel:  ? ipvlan_handle_frame+0xbd/0x1c0 [ipvlan]
Jun 14 15:16:37 srv-x3w2q kernel:  __netif_receive_skb_core+0x432/0xb40
Jun 14 15:16:37 srv-x3w2q kernel:  ? ipv6_gro_receive+0x22b/0x390
Jun 14 15:16:37 srv-x3w2q kernel:  __netif_receive_skb+0x18/0x60
Jun 14 15:16:37 srv-x3w2q kernel:  ? __netif_receive_skb+0x18/0x60
Jun 14 15:16:37 srv-x3w2q kernel:  netif_receive_skb_internal+0x37/0xd0
Jun 14 15:16:37 srv-x3w2q kernel:  napi_gro_receive+0xc5/0xf0
Jun 14 15:16:37 srv-x3w2q kernel:  receive_buf+0x275/0x1180 [virtio_net]
Jun 14 15:16:37 srv-x3w2q kernel:  ? vring_unmap_one+0x1b/0x80
Jun 14 15:16:37 srv-x3w2q kernel:  virtnet_poll+0xc4/0x289 [virtio_net]
Jun 14 15:16:37 srv-x3w2q kernel:  net_rx_action+0x140/0x3a0
Jun 14 15:16:37 srv-x3w2q kernel:  __do_softirq+0xdf/0x2b2
Jun 14 15:16:37 srv-x3w2q kernel:  irq_exit+0xb6/0xc0
Jun 14 15:16:37 srv-x3w2q kernel:  do_IRQ+0x82/0xd0
Jun 14 15:16:37 srv-x3w2q kernel:  common_interrupt+0x84/0x84
Jun 14 15:16:37 srv-x3w2q kernel:  
Jun 14 15:16:37 srv-x3w2q kernel: RIP: 0010:native_safe_halt+0x6/0x10
Jun 14 15:16:37 srv-x3w2q kernel: RSP: 0018:ac5ec0377e80 EFLAGS: 0246 
ORIG_RAX: ffd9
Jun 14 15:16:37 srv-x3w2q kernel: RAX: a4196060 RBX: 0001 
RCX: 
Jun 14 15:16:37 srv-x3w2q kernel: RDX:  RSI:  
RDI: 
Jun 14 15:16:37 srv-x3w2q kernel: RBP: ac5ec0377e80 R08:  
R09: a4c08528
Jun 14 15:16:37 srv-x3w2q kernel: R10: 91d27ffb1ca8 R11:  
R12: 0001
Jun 14 15:16:37 srv-x3w2q kernel: R13:  R14:  
R15: 

Fix is apparently at https://www.spinics.net/lists/netdev/msg485566.html

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-23-generic 4.15.0-23.25
ProcVersionSignature: User Name 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jun 14 10:00 seq
 crw-rw 1 root audio 116, 33 Jun 14 10:00 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Date: Thu Jun 14 15:20:04 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Red Hat KVM
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-23-generic N/A
 linux-backports-modules-4.15.0-23-generic  N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

[Bug 1748210] [NEW] Sync haproxy 1.8.3-1 (main) from Debian experimental (main)

[Neil Wilson]

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 adding
" stats socket  expose-fd listeners
  stats bind-process 1 "
to the global section of your haproxy config, and
setting HAPROXY_STATS_SOCKET in the haproxy.service unit file.
(LP: #1712925)
  * Backport of -x option from upstream haproxy to enable seamless
reloading of haproxy without dropping connections.  This is enabled
by adding
" stats socket  expose-fd listeners
  stats bind-process 1 "
to the global section of your haproxy config, and
setting HAPROXY_STATS_SOCKET in the haproxy.service unit file.
(LP: #1712925)

1.8 version includes this backported change, is a the current stable
haproxy version and will be mainline throughout the bionic release
cycle. It should be in the LTS version, rather than maintaining the
current delta for five years.

Changelog entries since current bionic version 1.7.9-1ubuntu2:

haproxy (1.8.3-1) experimental; urgency=medium

  * New upstream stable release.
  * Change default configuration of stats socket to support hitless
reload.

 -- Vincent Bernat   Tue, 02 Jan 2018 18:48:24 +0100

haproxy (1.8.2-1) experimental; urgency=medium

  * New upstream stable release
  * Refresh patches
  * Bump Standards-Version to 4.1.2; no changes needed

 -- Apollon Oikonomopoulos   Sun, 24 Dec 2017
14:28:28 +0200

haproxy (1.8.1-1) experimental; urgency=medium

  * New upstream stable release.
  * Enable PCRE JIT.
  * systemd: replace Wants/After=syslog.service with After=rsyslog.service
(Closes: #882610)

 -- Apollon Oikonomopoulos   Sun, 03 Dec 2017
23:59:03 +0200

haproxy (1.8.0-2) experimental; urgency=medium

  * Use libatomic on platforms without 64-bit atomics. Fixes FTBFS on armel,
mips, mipsel, powerpc, powerpcspe, sh4 and m68k.
  * d/rules: use variables defined in architecture.mk and buildflags.mk
  * d/rules: drop unreachable else case.

 -- Apollon Oikonomopoulos   Wed, 29 Nov 2017
01:21:40 +0200

haproxy (1.8.0-1) experimental; urgency=medium

  * New upstream stable series. Notable new features include:
+ HTTP/2 support
+ Support for multiple worker threads to allow scalability across CPUs
  (e.g. for SSL termination)
+ Seamless reloads
+ HTTP small object caching
+ Dynamic backend server configuration
See https://www.haproxy.com/blog/whats-new-haproxy-1-8/ and
https://www.mail-archive.com/haproxy@formilux.org/msg28004.html for more
detailed descriptions of the new features.
  * Upload to experimental
  * Refresh all patches.
  * d/watch: switch to the 1.8.x upstream stable series
  * Bump Standards to 4.1.1
+ Switch haproxy-doc to Priority: optional from extra.
  * Bump compat to 10:
+ B-D on debhelper (>= 10)
+ Drop explicit dh-systemd dependency and invocation
+ Replace --no-restart-on-upgrade with --no-restart-after-upgrade
  --no-stop-on-upgrade to make up for DH 10 defaults.
  * B-D on libsystemd-dev and enable sd_notify() support on Linux.
  * B-D on python3-sphinx instead of python-sphinx.
  * d/rules: do not call dpkg-parsechangelog directly.
  * d/copyright: drop obsolete section.
  * Drop obsolete lintian overrides.
  * Do a full-service restart when upgrading from pre-1.8 versions and running
under systemd, to migrate to the new process model and service type.
+ Document this in d/NEWS as well.

 -- Apollon Oikonomopoulos   Tue, 28 Nov 2017
22:25:11 +0200

** Affects: haproxy (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/1748210

Title:
  Sync haproxy 1.8.3-1 (main) from Debian experimental (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1748210/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1725633] [NEW] package tcpdump 4.9.2-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2

[Neil Wilson]

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 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 tcpdump: Purge
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Oct 21 11:41:49 2017
DpkgTerminalLog:
 Removing tcpdump (4.9.0-1ubuntu1~ubuntu16.04.1) ...
 /var/lib/dpkg/info/tcpdump.postrm: 1: /var/lib/dpkg/info/tcpdump.postrm: 
Syntax error: word unexpected (expecting ")")
 dpkg: error processing package tcpdump (--purge):
  subprocess installed post-removal script returned error exit status 2
DuplicateSignature:
 package:tcpdump:4.9.2-0ubuntu0.16.04.1
 Removing tcpdump (4.9.0-1ubuntu1~ubuntu16.04.1) ...
 /var/lib/dpkg/info/tcpdump.postrm: 1: /var/lib/dpkg/info/tcpdump.postrm: 
Syntax error: word unexpected (expecting ")")
 dpkg: error processing package tcpdump (--purge):
  subprocess installed post-removal script returned error exit status 2
ErrorMessage: subprocess installed post-removal script returned error exit 
status 2
InstallationDate: Installed on 2016-04-28 (540 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: tcpdump
Title: package tcpdump 4.9.2-0ubuntu0.16.04.1 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: tcpdump (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725633

Title:
  package tcpdump 4.9.2-0ubuntu0.16.04.1 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tcpdump/+bug/1725633/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1691979] [NEW] etcd in gateway/grpc_proxy mode hangs on startup

[Neil Wilson]

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: activating (start) since Fri 2017-05-19 09:22:09 UTC; 1min 25s ago
 Docs: https://github.com/coreos/etcd
   man:etcd
 Main PID: 24451 (etcd)
Tasks: 7 (limit: 4915)
   Memory: 8.1M
  CPU: 32ms
   CGroup: /system.slice/etcd.service
   └─24451 /usr/bin/etcd gateway start --endpoints=grp-ux6nb.gb1s.bright


Presumable the type of daemon is different in normal mode, from when it is 
running as the newer proxy modes.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: etcd 3.1.0-1
ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Fri May 19 09:22:57 2017
SourcePackage: etcd
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.etcd:
  Daemon parameters:
 DAEMON_ARGS="gateway start --endpoints=grp-ux6nb.gb1s.brightbox.com:2379 
--listen-addr=127.0.0.1:2379"
mtime.conffile..etc.default.etcd: 2017-05-19T09:22:55.238937

** Affects: etcd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug uec-images zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691979

Title:
  etcd in gateway/grpc_proxy mode hangs on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/etcd/+bug/1691979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1691979] Re: etcd in gateway/grpc_proxy mode hangs on startup

[Neil Wilson]

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 sd_notify behaviors in gateway, grpc-proxy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691979

Title:
  etcd in gateway/grpc_proxy mode hangs on startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/etcd/+bug/1691979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1635192] Re: package depends on pep8 tool instead of python-pep8 library

[Neil Wilson]

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 instead of python-pep8 library

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopep8/+bug/1635192/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1661693] Re: identify brightbox platform to enable Ec2 datasource

[Neil Wilson]

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

Title:
  identify brightbox platform to enable Ec2 datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1661693/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1649288] [NEW] Unified ping doesn't support IPv4-mapped IPv6 addresses

[Neil Wilson]

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 have expected this to use the IPv6 API to send an ICMP packet
over the v4 Internet on a dual stack machine in accordance with RFC4038.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: iputils-ping 3:20150815-2ubuntu3
ProcVersionSignature: User Name 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Mon Dec 12 14:27:34 2016
SourcePackage: iputils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: iputils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug uec-images zesty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649288

Title:
  Unified ping doesn't support IPv4-mapped IPv6 addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1649288/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645323] Re: Openvswitch-ipsec daemon fails to start

[Neil Wilson]

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:
  Openvswitch-ipsec daemon fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1645323/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1645323] [NEW] Openvswitch-ipsec daemon fails to start

[Neil Wilson]

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  | ovs-monitor-ipsec | ERR | 
traceback
 Traceback (most recent call last):
   File 
"/usr/share/openvswitch/scripts/ovs-monitor-ipsec", line 489, in 
 main()
   File 
"/usr/share/openvswitch/scripts/ovs-monitor-ipsec", line 410, in main
 schema_helper = 
ovs.db.idl.SchemaHelper()
   File 
"/usr/lib/python2.7/dist-packages/ovs/db/idl.py", line 1696, in __init__
 schema_json = 
ovs.json.from_file(location)
   File 
"/usr/lib/python2.7/dist-packages/ovs/json.py", line 60, in from_file
 stream = open(name, "r")
 IOError: [Errno 2] No such file or 
directory: '/usr/local/share/openvswitch/vswitch.ovsschema'
Nov 28 13:15:58 srv-yz20n openvswitch-ipsec[18332]: 2016-11-28T13:15:58Z |  0  
| ovs-monitor-ipsec | ERR | traceback
Nov 28 13:15:58 srv-yz20n openvswitch-ipsec[18332]: Traceback (most recent call 
last):
Nov 28 13:15:58 srv-yz20n openvswitch-ipsec[18332]:   File 
"/usr/share/openvswitch/scripts/ovs-monitor-ipsec", line 489, in 
Nov 28 13:15:58 srv-yz20n openvswitch-ipsec[18332]: main()
Nov 28 13:15:58 srv-yz20n openvswitch-ipsec[18332]:   File 
"/usr/share/openvswitch/scripts/ovs-monitor-ipsec", line 410, in main
Nov 28 13:15:58 srv-yz20n openvswitch-ipsec[18332]: schema_helper = 
ovs.db.idl.SchemaHelper()
Nov 28 13:15:58 srv-yz20n openvswitch-ipsec[18332]:   File 
"/usr/lib/python2.7/dist-packages/ovs/db/idl.py", line 1696, in __init__
Nov 28 13:15:58 srv-yz20n openvswitch-ipsec[18332]: schema_json = 
ovs.json.from_file(location)
Nov 28 13:15:58 srv-yz20n openvswitch-ipsec[18332]:   File 
"/usr/lib/python2.7/dist-packages/ovs/json.py", line 60, in from_file
Nov 28 13:15:58 srv-yz20n openvswitch-ipsec[18332]: stream = open(name, "r")
Nov 28 13:15:58 srv-yz20n openvswitch-ipsec[18332]: IOError: [Errno 2] No such 
file or directory: '/usr/local/share/openvswitch/vswitch.ovsschema'
Nov 28 13:15:58 srv-yz20n openvswitch-ipsec[18332]:...fail!
Nov 28 13:15:58 srv-yz20n systemd[1]: openvswitch-ipsec.service: Control 
process exited, code=exited status=1
Nov 28 13:15:58 srv-yz20n systemd[1]: Failed to start LSB: Open vSwitch 
GRE-over-IPsec daemon.
Nov 28 13:15:58 srv-yz20n systemd[1]: openvswitch-ipsec.service: Unit entered 
failed state.
Nov 28 13:15:58 srv-yz20n systemd[1]: openvswitch-ipsec.service: Failed with 
result 'exit-code'.


It's looking in /usr/local/share rather than /usr/share

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: openvswitch-ipsec 2.6.0-0ubuntu2
ProcVersionSignature: User Name 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Mon Nov 28 13:42:06 2016
SourcePackage: openvswitch
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openvswitch (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug uec-images yakkety

-- 
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:
  Openvswitch-ipsec daemon fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1645323/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576692] Re: fully support package installation in systemd

[Neil Wilson]

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 server and snapshotted the image.

Rebuilt a new server from the snapshotted image using the previously
failing postgresql user data and all is well. The new packages correct
my problem - bug 1611973

-- 
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 installation in systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1576692/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576692] Re: fully support package installation in systemd

[Neil Wilson]

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 installation in systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1576692/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576692] Re: fully support package installation in systemd

[Neil Wilson]

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 cloud-init, and cloud events delay the
start event until the boot is complete, then the configurator that
expects things to happen in sequence will break.

It looks to me that large chunks of cloud-init need to be moved so it
runs after 'multi-user.target' has been reached, not just package
installation.

-- 
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 installation in systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1576692/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1613320] [NEW] Missing dependency on libfile-copy-recursive-perl in Xenial

[Neil Wilson]

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 /usr/lib/x86_64
-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at /usr/bin/mylvmbackup line 25.

this is corrected by manualling installing the package libfile-copy-
recursive-perl

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mylvmbackup 0.15-1
ProcVersionSignature: User Name 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Aug 15 15:04:10 2016
PackageArchitecture: all
SourcePackage: mylvmbackup
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.mylvmbackup.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/mylvmbackup.conf']

** Affects: mylvmbackup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug uec-images xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613320

Title:
  Missing dependency on libfile-copy-recursive-perl in Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mylvmbackup/+bug/1613320/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1521302] Re: gnome-terminal maximize than un-maximize behaves odd

[Neil Wilson]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1521302/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1521302] Re: gnome-terminal maximize than un-maximize behaves odd

[Neil Wilson]

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 bug go to:
https://bugs.launchpad.net/unity/+bug/1521302/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1482644] [NEW] Can't deploy charm directly after bootstrap

[Neil Wilson]

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
Starting new instance for initial state server
Installing Juju agent on bootstrap instance
Logging to /var/log/cloud-init-output.log on remote host
Running apt-get update
Installing package: curl
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: rsyslog-gnutls
Installing package: cloud-utils
Installing package: cloud-image-utils
Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP 
%{http_code}; time %{time_total}s; size %{size_download} bytes; speed 
%{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz 
[https://streams.canonical.com/juju/tools/releases/juju-1.22.6-trusty-amd64.tgz]
Bootstrapping Juju machine agent
Starting Juju machine agent (jujud-machine-0)
Bootstrap complete
ERROR cannot add charm to storage: cannot clean up after failed storage 
operation because: EOF: cannot clean up after failed storage operation because: 
EOF: unexpected deletion of resource catalog entry with id 
2246ebfe399809b5a748f93c22e3979c9f88770fcff5dd1bb262ecc8ce958e59c820873f300fcc26c0c638a10cdba22a:
 EOF

adding a 'sleep 5' works around the issue.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: juju (not installed)
ProcVersionSignature: User Name 3.13.0-61.100-generic 3.13.11-ckt22
Uname: Linux 3.13.0-61-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Fri Aug  7 13:26:06 2015
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1482644

Title:
  Can't deploy charm directly after bootstrap

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1482644/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1482644] [NEW] Can't deploy charm directly after bootstrap

[Neil Wilson]

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
Starting new instance for initial state server
Installing Juju agent on bootstrap instance
Logging to /var/log/cloud-init-output.log on remote host
Running apt-get update
Installing package: curl
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: rsyslog-gnutls
Installing package: cloud-utils
Installing package: cloud-image-utils
Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP 
%{http_code}; time %{time_total}s; size %{size_download} bytes; speed 
%{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz 
[https://streams.canonical.com/juju/tools/releases/juju-1.22.6-trusty-amd64.tgz]
Bootstrapping Juju machine agent
Starting Juju machine agent (jujud-machine-0)
Bootstrap complete
ERROR cannot add charm to storage: cannot clean up after failed storage 
operation because: EOF: cannot clean up after failed storage operation because: 
EOF: unexpected deletion of resource catalog entry with id 
2246ebfe399809b5a748f93c22e3979c9f88770fcff5dd1bb262ecc8ce958e59c820873f300fcc26c0c638a10cdba22a:
 EOF

adding a 'sleep 5' works around the issue.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: juju (not installed)
ProcVersionSignature: User Name 3.13.0-61.100-generic 3.13.11-ckt22
Uname: Linux 3.13.0-61-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Fri Aug  7 13:26:06 2015
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1482644

Title:
  Can't deploy charm directly after bootstrap

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1482644/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1482226] [NEW] juju status with 'prefer-ipv6' shows address, not DNS name.

[Neil Wilson]

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
Package: juju-core 1.22.6-0ubuntu1~14.04.1
ProcVersionSignature: User Name 3.13.0-61.100-generic 3.13.11-ckt22
Uname: Linux 3.13.0-61-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Thu Aug  6 13:42:49 2015
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1482226

Title:
  juju status with 'prefer-ipv6' shows address, not DNS name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1482226/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1482226] [NEW] juju status with 'prefer-ipv6' shows address, not DNS name.

[Neil Wilson]

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
Package: juju-core 1.22.6-0ubuntu1~14.04.1
ProcVersionSignature: User Name 3.13.0-61.100-generic 3.13.11-ckt22
Uname: Linux 3.13.0-61-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Thu Aug  6 13:42:49 2015
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1482226

Title:
  juju status with 'prefer-ipv6' shows address, not DNS name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1482226/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1481683] [NEW] juju-core version out of sync with tools stream - bootstrap fails

[Neil Wilson]

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

com.ubuntu.juju:15.10:amd64: {
version: 1.24.2,
arch: amd64,
versions: {
20150728: {
items: {
1.24.2-wily-amd64: {
release: wily,
version: 1.24.2,
arch: amd64,
size: 14129911,
path: releases/juju-1.24.2-wily-amd64.tgz,
ftype: tar.gz,
sha256: 
f250d8e90ff512e5f278c062de15ebbd9ffcd6525801f1f0ef9d798c64e7a7b1
},
1.24.3-wily-amd64: {
release: wily,
version: 1.24.3,
arch: amd64,
size: 14183032,
path: releases/juju-1.24.3-wily-amd64.tgz,
ftype: tar.gz,
sha256: 
b27e1e4e1906cb5fe1550840009fdc558faa0a3a1f902e68dfc0bf112fca4862
}
}
}


so bootstrap on manual fails.

2015-08-05 10:06:16 DEBUG juju.utils.ssh ssh.go:249 using OpenSSH ssh client
2015-08-05 10:06:18 INFO juju.environs.manual init.go:122 series: wily, 
characteristics: arch=amd64 cpu-cores=2 mem=3952M
2015-08-05 10:06:18 ERROR juju.cmd supercommand.go:430 failed to bootstrap 
environment: no matching tools available

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: juju-core 1.22.6-0ubuntu1
ProcVersionSignature: User Name 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
Date: Wed Aug  5 09:59:25 2015
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug uec-images wily

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1481683

Title:
  juju-core version out of sync with tools stream - bootstrap fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1481683/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1481683] [NEW] juju-core version out of sync with tools stream - bootstrap fails

[Neil Wilson]

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

com.ubuntu.juju:15.10:amd64: {
version: 1.24.2,
arch: amd64,
versions: {
20150728: {
items: {
1.24.2-wily-amd64: {
release: wily,
version: 1.24.2,
arch: amd64,
size: 14129911,
path: releases/juju-1.24.2-wily-amd64.tgz,
ftype: tar.gz,
sha256: 
f250d8e90ff512e5f278c062de15ebbd9ffcd6525801f1f0ef9d798c64e7a7b1
},
1.24.3-wily-amd64: {
release: wily,
version: 1.24.3,
arch: amd64,
size: 14183032,
path: releases/juju-1.24.3-wily-amd64.tgz,
ftype: tar.gz,
sha256: 
b27e1e4e1906cb5fe1550840009fdc558faa0a3a1f902e68dfc0bf112fca4862
}
}
}


so bootstrap on manual fails.

2015-08-05 10:06:16 DEBUG juju.utils.ssh ssh.go:249 using OpenSSH ssh client
2015-08-05 10:06:18 INFO juju.environs.manual init.go:122 series: wily, 
characteristics: arch=amd64 cpu-cores=2 mem=3952M
2015-08-05 10:06:18 ERROR juju.cmd supercommand.go:430 failed to bootstrap 
environment: no matching tools available

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: juju-core 1.22.6-0ubuntu1
ProcVersionSignature: User Name 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
Date: Wed Aug  5 09:59:25 2015
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug uec-images wily

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481683

Title:
  juju-core version out of sync with tools stream - bootstrap fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1481683/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1410288] Re: qemu-img conversion to qcow2 hangs with blank image less than 100kiB

[Neil Wilson]

** 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 less than 100kiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1410288/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1410288] Re: qemu-img conversion to qcow2 hangs with blank image less than 100kiB

[Neil Wilson]

** 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1410288/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1410288] [NEW] qemu-img conversion to qcow2 hangs with blank image less than 100kiB

[Neil Wilson]

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 v2.

strace shows a seek loop.

ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0
ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0
ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0
ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0
ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0
ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0
ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0
ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: qemu-utils 2.0.0+dfsg-2ubuntu1.10
ProcVersionSignature: User Name 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
Date: Tue Jan 13 14:30:39 2015
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qemu (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: apport-bug i386 trusty uec-images

-- 
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 less than 100kiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1410288/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1410288] [NEW] qemu-img conversion to qcow2 hangs with blank image less than 100kiB

[Neil Wilson]

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 v2.

strace shows a seek loop.

ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0
ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0
ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0
ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0
ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0
ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0
ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0
ioctl(6, FS_IOC_FIEMAP, 0xb5e68dc4) = 0
_llseek(6, 0, [10], SEEK_END)   = 0

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: qemu-utils 2.0.0+dfsg-2ubuntu1.10
ProcVersionSignature: User Name 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
Date: Tue Jan 13 14:30:39 2015
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qemu (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: apport-bug i386 trusty uec-images

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1410288/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1410288] Re: qemu-img conversion to qcow2 hangs with blank image less than 100kiB

[Neil Wilson]

Workaround is to 'fallocate'. Problem seems to be linked to files with
sparse holes in them.

-- 
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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1410288/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1410288] Re: qemu-img conversion to qcow2 hangs with blank image less than 100kiB

[Neil Wilson]

Workaround is to 'fallocate'. Problem seems to be linked to files with
sparse holes in them.

-- 
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 less than 100kiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1410288/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1388036] Re: qemu-img segmentation fault when asking for options

[Neil Wilson]

ubuntu@srv-puxvl:~$ uname -a
Linux srv-puxvl 3.2.0-70-virtual #105-Ubuntu SMP Wed Sep 24 20:06:46 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

ubuntu@srv-puxvl:~$ dpkg -s qemu-utils | grep Version
Version: 1.0+noroms-0ubuntu14.20
ubuntu@srv-puxvl:~$ qemu-img convert -O qcow2 -o ? a b
Supported options:
size Virtual disk size
backing_file File name of a base image
backing_fmt  Image format of the base image
encryption   Encrypt the image
cluster_size qcow2 cluster size
preallocationPreallocation mode (allowed values: off, metadata)
ubuntu@srv-puxvl:~$ sudo qemu-img convert -O qcow2 -o ? a b
Supported options:
size Virtual disk size
backing_file File name of a base image
backing_fmt  Image format of the base image
encryption   Encrypt the image
cluster_size qcow2 cluster size
preallocationPreallocation mode (allowed values: off, metadata)


The fix corrects the segmentation fault.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1388036

Title:
  qemu-img segmentation fault when asking for options

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1388036/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1388036] Re: qemu-img segmentation fault when asking for options

[Neil Wilson]

ubuntu@srv-3wzed:~$ uname -a
Linux srv-3wzed 3.2.0-69-virtual #103-Ubuntu SMP Tue Sep 2 05:28:41 UTC 2014 
i686 i686 i386 GNU/Linux

ubuntu@srv-3wzed:~$ dpkg -s qemu-utils | grep Version
Version: 1.0+noroms-0ubuntu14.20
ubuntu@srv-3wzed:~$ qemu-img convert -O qcow2 -o ? a b
Supported options:
size Virtual disk size
backing_file File name of a base image
backing_fmt  Image format of the base image
encryption   Encrypt the image
cluster_size qcow2 cluster size
preallocationPreallocation mode (allowed values: off, metadata)
ubuntu@srv-3wzed:~$ sudo qemu-img convert -O qcow2 -o ? a b
Supported options:
size Virtual disk size
backing_file File name of a base image
backing_fmt  Image format of the base image
encryption   Encrypt the image
cluster_size qcow2 cluster size
preallocationPreallocation mode (allowed values: off, metadata)


Also fixed on i686 version.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1388036

Title:
  qemu-img segmentation fault when asking for options

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1388036/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1388036] Re: qemu-img segmentation fault when asking for options

[Neil Wilson]

ubuntu@srv-puxvl:~$ uname -a
Linux srv-puxvl 3.2.0-70-virtual #105-Ubuntu SMP Wed Sep 24 20:06:46 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

ubuntu@srv-puxvl:~$ dpkg -s qemu-utils | grep Version
Version: 1.0+noroms-0ubuntu14.20
ubuntu@srv-puxvl:~$ qemu-img convert -O qcow2 -o ? a b
Supported options:
size Virtual disk size
backing_file File name of a base image
backing_fmt  Image format of the base image
encryption   Encrypt the image
cluster_size qcow2 cluster size
preallocationPreallocation mode (allowed values: off, metadata)
ubuntu@srv-puxvl:~$ sudo qemu-img convert -O qcow2 -o ? a b
Supported options:
size Virtual disk size
backing_file File name of a base image
backing_fmt  Image format of the base image
encryption   Encrypt the image
cluster_size qcow2 cluster size
preallocationPreallocation mode (allowed values: off, metadata)


The fix corrects the segmentation fault.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388036

Title:
  qemu-img segmentation fault when asking for options

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1388036/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1388036] Re: qemu-img segmentation fault when asking for options

[Neil Wilson]

ubuntu@srv-3wzed:~$ uname -a
Linux srv-3wzed 3.2.0-69-virtual #103-Ubuntu SMP Tue Sep 2 05:28:41 UTC 2014 
i686 i686 i386 GNU/Linux

ubuntu@srv-3wzed:~$ dpkg -s qemu-utils | grep Version
Version: 1.0+noroms-0ubuntu14.20
ubuntu@srv-3wzed:~$ qemu-img convert -O qcow2 -o ? a b
Supported options:
size Virtual disk size
backing_file File name of a base image
backing_fmt  Image format of the base image
encryption   Encrypt the image
cluster_size qcow2 cluster size
preallocationPreallocation mode (allowed values: off, metadata)
ubuntu@srv-3wzed:~$ sudo qemu-img convert -O qcow2 -o ? a b
Supported options:
size Virtual disk size
backing_file File name of a base image
backing_fmt  Image format of the base image
encryption   Encrypt the image
cluster_size qcow2 cluster size
preallocationPreallocation mode (allowed values: off, metadata)


Also fixed on i686 version.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388036

Title:
  qemu-img segmentation fault when asking for options

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1388036/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1388036] [NEW] qemu-img segmentation fault when asking for options

[Neil Wilson]

Build from current-cloud image

com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:12.04:i386/20140927/disk1.img
com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:12.04:amd64/20140927/disk1.img

sudo apt-get update
sudo apt-get install language-pack-en qemu-utils
qemu-img convert -O qcow2 -o ? a b

(Note, not as root).


On 3 November 2014 16:01, Serge Hallyn 1388...@bugs.launchpad.net
wrote:

 Hi,

 I can't actually reproduce this on my precise server.  Could you please
 show the full, precise set of commands you used starting with an empty
 directory?

  status: incomplete


 ** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1388036

 Title:
   qemu-img segmentation fault when asking for options

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1388036/+subscriptions



-- 
Neil Wilson

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1388036

Title:
  qemu-img segmentation fault when asking for options

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1388036/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1388036] [NEW] qemu-img segmentation fault when asking for options

[Neil Wilson]

Build from current-cloud image

com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:12.04:i386/20140927/disk1.img
com.ubuntu.cloud:released:download/com.ubuntu.cloud:server:12.04:amd64/20140927/disk1.img

sudo apt-get update
sudo apt-get install language-pack-en qemu-utils
qemu-img convert -O qcow2 -o ? a b

(Note, not as root).


On 3 November 2014 16:01, Serge Hallyn 1388...@bugs.launchpad.net
wrote:

 Hi,

 I can't actually reproduce this on my precise server.  Could you please
 show the full, precise set of commands you used starting with an empty
 directory?

  status: incomplete


 ** Changed in: qemu-kvm (Ubuntu)
Status: New = Incomplete

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1388036

 Title:
   qemu-img segmentation fault when asking for options

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1388036/+subscriptions



-- 
Neil Wilson

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388036

Title:
  qemu-img segmentation fault when asking for options

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1388036/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1383704] Re: Can't switch off SSLv3 cipher groups in haproxy

[Neil Wilson]

From RH Bug list:

It appears the cause was identified and fixed in the latest haproxy upstream
release, 1.5.7. From the release announcement on the haproxy mailing list:

  - John Leach reported an interesting bug in the way SSL certificates were
loaded : if a certificate with an invalid subject (no parsable CN) is
loaded as the first in the list, its context will not be updated with the
bind line arguments, resulting in such a certificate to accept SSLv3
despite the no-sslv3 keyword. That was diagnosed and fixed by Emeric.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1383704

Title:
  Can't switch off SSLv3 cipher groups in haproxy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1383704/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1388036] [NEW] qemu-img segmentation fault when asking for options

[Neil Wilson]

Public bug reported:

When you ask for options for a command on the precise version of qemu-
img

qemu-img convert -O qcow2 -o ? a b

The tool seg faults:

Supported options:
size Virtual disk size
backing_file File name of a base image
backing_fmt  Image format of the base image
encryption   Encrypt the image
cluster_size qcow2 cluster size
preallocationPreallocation mode (allowed values: off, metadata)
Segmentation fault (core dumped)

This is fixed upstream in later versions, but may be worth backporting
to precise.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: qemu-utils 1.0+noroms-0ubuntu14.18
ProcVersionSignature: Ubuntu 3.2.0-65.98-generic 3.2.60
Uname: Linux 3.2.0-65-generic i686
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
Date: Fri Oct 31 10:41:52 2014
MarkForUpload: True
SourcePackage: qemu-kvm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qemu-kvm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 precise

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1388036

Title:
  qemu-img segmentation fault when asking for options

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1388036/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1383704] Re: Can't switch off SSLv3 cipher groups in haproxy

[Neil Wilson]

From RH Bug list:

It appears the cause was identified and fixed in the latest haproxy upstream
release, 1.5.7. From the release announcement on the haproxy mailing list:

  - John Leach reported an interesting bug in the way SSL certificates were
loaded : if a certificate with an invalid subject (no parsable CN) is
loaded as the first in the list, its context will not be updated with the
bind line arguments, resulting in such a certificate to accept SSLv3
despite the no-sslv3 keyword. That was diagnosed and fixed by Emeric.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1383704

Title:
  Can't switch off SSLv3 cipher groups in haproxy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1383704/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1388036] [NEW] qemu-img segmentation fault when asking for options

[Neil Wilson]

Public bug reported:

When you ask for options for a command on the precise version of qemu-
img

qemu-img convert -O qcow2 -o ? a b

The tool seg faults:

Supported options:
size Virtual disk size
backing_file File name of a base image
backing_fmt  Image format of the base image
encryption   Encrypt the image
cluster_size qcow2 cluster size
preallocationPreallocation mode (allowed values: off, metadata)
Segmentation fault (core dumped)

This is fixed upstream in later versions, but may be worth backporting
to precise.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: qemu-utils 1.0+noroms-0ubuntu14.18
ProcVersionSignature: Ubuntu 3.2.0-65.98-generic 3.2.60
Uname: Linux 3.2.0-65-generic i686
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
Date: Fri Oct 31 10:41:52 2014
MarkForUpload: True
SourcePackage: qemu-kvm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qemu-kvm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 precise

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1388036

Title:
  qemu-img segmentation fault when asking for options

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1388036/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1383704] Re: Can't switch off SSLv3 cipher groups in haproxy

[Neil Wilson]

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1383704

Title:
  Can't switch off SSLv3 cipher groups in haproxy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1383704/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1383704] Re: Can't switch off SSLv3 cipher groups in haproxy

[Neil Wilson]

The issue seems to be caused by a self-signed cert we're using. A cert
from a CA seems to work as expected.


** Attachment added: ssl_cert.pem.orig.fixed
   
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1383704/+attachment/4241193/+files/ssl_cert.pem.orig.fixed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1383704

Title:
  Can't switch off SSLv3 cipher groups in haproxy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1383704/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1383704] Re: Can't switch off SSLv3 cipher groups in haproxy

[Neil Wilson]

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1383704

Title:
  Can't switch off SSLv3 cipher groups in haproxy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1383704/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1383704] Re: Can't switch off SSLv3 cipher groups in haproxy

[Neil Wilson]

The issue seems to be caused by a self-signed cert we're using. A cert
from a CA seems to work as expected.


** Attachment added: ssl_cert.pem.orig.fixed
   
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1383704/+attachment/4241193/+files/ssl_cert.pem.orig.fixed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1383704

Title:
  Can't switch off SSLv3 cipher groups in haproxy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1383704/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1068756] Re: IPv6 Privacy Extensions enabled on Ubuntu Server by default

[Neil Wilson]

There's no problem with using it in an IPv6 environment if you use
IPv6 prefix mechanisms as designed

If you've tied down your cloud environment too tight (and technically
contra the spec - IPv6 is prefix based, not address based) then you
have to expect to make alterations to the standard equipment.

I have no problem with the temporary addresses as I scope my machines
on /64 boundaries - which is what everything pretty much expects and
RFC 5375 recommends. Note that RFC 3177 strongly prescribes 64-bit
subnets for general usage, and that stateless autoconfiguration on
most link layers (including Ethernet) is only defined for 64-bit
subnets.



On 4 June 2014 11:57, Alex Bligh ubu...@alex.org.uk wrote:
 Neil: the metadata is just one example (though that's not happening).

 The firewall rule thing applies irrespective of the metadata. The cloud
 environment created requires only /128 addresses it knows about to be
 accessible, and firewalls everything else out. Reasons for this include
 prevention of spoofing of IP addresses on outbound traffic. We want each
 UEC image to come up with the IPv6 address(es) we have assigned, and not
 a random one in the same /64. This is not an unreasonable requirement.
 We would use DHCPv6 for this if it weren't for the fact that DHCPv6 is
 broken in different ways and has little support.

 IPv6 *as designed* says RFC4941 SHOULD (RFC capitalisation) be turned
 off by default. So the argument that applications should be using it 'as
 designed' is bogus, as if it was deployed *as designed* (i.e. per the
 RFC) it would work. There would be no problem with (e.g.) Network
 Manager turning this on in a desktop environment.

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1068756

 Title:
   IPv6 Privacy Extensions enabled on Ubuntu Server by default

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1068756/+subscriptions


-- 
Neil Wilson

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1068756

Title:
  IPv6 Privacy Extensions enabled on Ubuntu Server by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1068756/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1068756] Re: IPv6 Privacy Extensions enabled on Ubuntu Server by default

[Neil Wilson]

I would suggest that is a design flaw in your network - which is
working in an IPv4 manner, not an IPv6 one. You should have used a
prefix smaller than /64

The problem here is with the network design, not the image.

On 4 June 2014 14:40, Alex Bligh ubu...@alex.org.uk wrote:
 That doesn't work if (for instance) you have 2 machines on the same SDN
 virtual LAN, which is a /64, and you want to prevent source spoofing
 between them. For avoidance of doubt, we do use /64s.

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1068756

 Title:
   IPv6 Privacy Extensions enabled on Ubuntu Server by default

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1068756/+subscriptions


-- 
Neil Wilson

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1068756

Title:
  IPv6 Privacy Extensions enabled on Ubuntu Server by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1068756/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1068756] Re: IPv6 Privacy Extensions enabled on Ubuntu Server by default

[Neil Wilson]

The metadata request on IPv6 should ask to use the global address on
outgoing connection. If it did, then the firewall rule would work, the
metadata obtained and that can turn off the temporary address
mechanism if that is what you want.

Badly coded applications should be fixed to work properly with IPv6
*as IPv6 is designed*, and then temporary addresses would work quite
happily.

The problem here is primarily coding applications to use IPv6 as
though it is IPv4.

There is no need to cripple the UEC images. There is a need to fix the
software so it works with IPv6 properly.


On 4 June 2014 11:13, Alex Bligh ubu...@alex.org.uk wrote:
 In my view this is NOT a software bug, its an OS bug.

 Here's a completely different why this causes problems.

 We use Ubuntu UEC images. There are no meaningful privacy considerations
 here because we generate both the MAC address and the IP address of the
 servers concerned. IE, if the machine is mobile and changes IP address,
 it changes MAC address too.

 We build firewall rules automatically for the machine. These are applied
 outside of the machine (on the router). In order to write the rules
 correctly, we need to know the IPv6 address the machine will have, and
 use EUI-64 addressing to do this.

 Equally, for the server to get metadata on a boot, both the IP address
 needs to be correct (and no, that's not the only thing that is checked).
 On UEC randomisation of addresses thus prevents getting metadata over
 IPv6. This is only 'not a killer problem' as most people have IPv4 too.

 In a server environment (particularly on cloud images) there is no need
 whatsoever to have RFC4941 turned on by default.

 As Brian Candler wrote, the RFC says this should be disabled by default.
 It also says:

Devices implementing this specification MUST provide a way for the
end user to explicitly enable or disable the use of temporary
addresses.  In addition, a site might wish to disable the use of
temporary addresses in order to simplify network debugging and
operations.  Consequently, implementations SHOULD provide a way for
trusted system administrators to enable or disable the use of
temporary addresses.

 On a cloud image, the user can't even administer his own machine until
 it has booted, which in a full IPv6 environment requires it to get
 metadata. For the reasons above, this prevents that from working.
 Therefore at least on UEC images, RFC4941 should be turned off by
 default and EUI-64 addresses only should be used.

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1068756

 Title:
   IPv6 Privacy Extensions enabled on Ubuntu Server by default

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1068756/+subscriptions


-- 
Neil Wilson

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068756

Title:
  IPv6 Privacy Extensions enabled on Ubuntu Server by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1068756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1068756] Re: IPv6 Privacy Extensions enabled on Ubuntu Server by default

[Neil Wilson]

There's no problem with using it in an IPv6 environment if you use
IPv6 prefix mechanisms as designed

If you've tied down your cloud environment too tight (and technically
contra the spec - IPv6 is prefix based, not address based) then you
have to expect to make alterations to the standard equipment.

I have no problem with the temporary addresses as I scope my machines
on /64 boundaries - which is what everything pretty much expects and
RFC 5375 recommends. Note that RFC 3177 strongly prescribes 64-bit
subnets for general usage, and that stateless autoconfiguration on
most link layers (including Ethernet) is only defined for 64-bit
subnets.



On 4 June 2014 11:57, Alex Bligh ubu...@alex.org.uk wrote:
 Neil: the metadata is just one example (though that's not happening).

 The firewall rule thing applies irrespective of the metadata. The cloud
 environment created requires only /128 addresses it knows about to be
 accessible, and firewalls everything else out. Reasons for this include
 prevention of spoofing of IP addresses on outbound traffic. We want each
 UEC image to come up with the IPv6 address(es) we have assigned, and not
 a random one in the same /64. This is not an unreasonable requirement.
 We would use DHCPv6 for this if it weren't for the fact that DHCPv6 is
 broken in different ways and has little support.

 IPv6 *as designed* says RFC4941 SHOULD (RFC capitalisation) be turned
 off by default. So the argument that applications should be using it 'as
 designed' is bogus, as if it was deployed *as designed* (i.e. per the
 RFC) it would work. There would be no problem with (e.g.) Network
 Manager turning this on in a desktop environment.

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1068756

 Title:
   IPv6 Privacy Extensions enabled on Ubuntu Server by default

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1068756/+subscriptions


-- 
Neil Wilson

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068756

Title:
  IPv6 Privacy Extensions enabled on Ubuntu Server by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1068756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1068756] Re: IPv6 Privacy Extensions enabled on Ubuntu Server by default

[Neil Wilson]

I would suggest that is a design flaw in your network - which is
working in an IPv4 manner, not an IPv6 one. You should have used a
prefix smaller than /64

The problem here is with the network design, not the image.

On 4 June 2014 14:40, Alex Bligh ubu...@alex.org.uk wrote:
 That doesn't work if (for instance) you have 2 machines on the same SDN
 virtual LAN, which is a /64, and you want to prevent source spoofing
 between them. For avoidance of doubt, we do use /64s.

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1068756

 Title:
   IPv6 Privacy Extensions enabled on Ubuntu Server by default

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1068756/+subscriptions


-- 
Neil Wilson

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068756

Title:
  IPv6 Privacy Extensions enabled on Ubuntu Server by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1068756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1073204] Re: ssh-authkey-fingerprints fails on boot

[Neil Wilson]

All looks fine on Trusty.

I've built both with the same user. The current Trusty works and the
current Quantal does not.


On 3 June 2014 16:33, Scott Moser smo...@ubuntu.com wrote:
 Hey, can you verify that this is still a problem on 14.04, and give some info 
 on how you did it ?
 Did the user have no keys?

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1073204

 Title:
   ssh-authkey-fingerprints fails on boot

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1073204/+subscriptions


-- 
Neil Wilson

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1073204

Title:
  ssh-authkey-fingerprints fails on boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1073204/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1073204] Re: ssh-authkey-fingerprints fails on boot

[Neil Wilson]

All looks fine on Trusty.

I've built both with the same user. The current Trusty works and the
current Quantal does not.


On 3 June 2014 16:33, Scott Moser smo...@ubuntu.com wrote:
 Hey, can you verify that this is still a problem on 14.04, and give some info 
 on how you did it ?
 Did the user have no keys?

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1073204

 Title:
   ssh-authkey-fingerprints fails on boot

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1073204/+subscriptions


-- 
Neil Wilson

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073204

Title:
  ssh-authkey-fingerprints fails on boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1073204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1295244] [NEW] TypeError: request() got an unexpected keyword argument 'body'

[Neil Wilson]

Public bug reported:

The version of the requests library on Trusty uses 'data' as the
positional argument.

File /usr/lib/python2.7/dist-packages/ftpcloudfs/fs.py, line 66, in
request_x_forwarded_for#012fn(method, url, body=body,
headers=headers)#012TypeError: request() got an unexpected keyword
argument 'body'

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python-ftp-cloudfs 0.25.2-1 [modified: 
usr/lib/python2.7/dist-packages/ftpcloudfs/fs.py]
ProcVersionSignature: User Name 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
Date: Thu Mar 20 17:06:31 2014
PackageArchitecture: all
SourcePackage: ftp-cloudfs
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ftp-cloudfs (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1295244

Title:
  TypeError: request() got an unexpected keyword argument 'body'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ftp-cloudfs/+bug/1295244/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1157914] Re: time never catches up to reality after VM sleep

[Neil Wilson]

It would be as well to try it out - particularly as the package has been
updated recently.

I tried a fresh install of Trusty and when 'vmtoolsd' is running from
the 'open-vm-tools' package,  the output from 'vmware-toolbox-cmd stat
hosttime' and 'date' are the same after a restore from vmware suspend.

The graphic indicator lags, but caught up within about a minute.

Check 'vmware-toolbox-cmd timesync status' and run 'vmware-toolbox-cmd
timesync enable' if necessary.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157914

Title:
  time never catches up to reality after VM sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157914/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1157914] Re: time never catches up to reality after VM sleep

[Neil Wilson]

I don't see the issue on Windows XP. Only when running Ubuntu.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157914

Title:
  time never catches up to reality after VM sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157914/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1157914] Re: time never catches up to reality after VM sleep

[Neil Wilson]

Barry,

Can you check you VMWare settings for the virtual machine and check that
'synchronise time' is checked in the Advanced Section.

Also do you have the 'open-vm-tools' installed (i.e. is vmtoolsd running
which is what does the time sync to the Host every 60 seconds).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157914

Title:
  time never catches up to reality after VM sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157914/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1241711] [NEW] simplestreams failing on release feed - TypeError

[Neil Wilson]

Public bug reported:

New 13.10 installation, with simplestreams package and a copy of the
'hook-debug' script in bin in the home directory.

When I run

sstream-sync --max 1 --verbose --hook=bin/debug http://cloud-
images.ubuntu.com/releases

I get

Traceback (most recent call last):
  File /usr/bin/sstream-sync, line 163, in module
main()
  File /usr/bin/sstream-sync, line 156, in main
tmirror.sync(smirror, cfg['path'])
  File /usr/lib/python3/dist-packages/simplestreams/mirrors/__init__.py, line 
85, in sync
return self.sync_index(reader, path, data, content)
  File /usr/lib/python3/dist-packages/simplestreams/mirrors/__init__.py, line 
230, in sync_index
self.sync(reader, path=epath)
  File /usr/lib/python3/dist-packages/simplestreams/mirrors/__init__.py, line 
83, in sync
return self.sync_products(reader, path, data, content)
  File /usr/lib/python3/dist-packages/simplestreams/mirrors/__init__.py, line 
358, in sync_products
self.insert_products(path, target, content)
  File /usr/lib/python3/dist-packages/simplestreams/mirrors/command_hook.py, 
line 141, in insert_products
content=content, extra={'path': path})
  File /usr/lib/python3/dist-packages/simplestreams/mirrors/command_hook.py, 
line 201, in call_hook
tfile.write(content)
TypeError: 'str' does not support the buffer interface

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: simplestreams 0.1.0~bzr318-0ubuntu1
ProcVersionSignature: User Name 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Fri Oct 18 16:22:19 2013
MarkForUpload: True
PackageArchitecture: all
SourcePackage: simplestreams
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: simplestreams (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug saucy uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241711

Title:
  simplestreams failing on release feed - TypeError

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1241711/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1195169] [NEW] time and date doesn't update on resume in VM fusion

[Neil Wilson]

Public bug reported:

If you're running ubuntu within VM Fusion and you suspend the Ubuntu VM
using the suspend and resume functions within VM fusion then the time
and date doesn't synchronise when the VM is resumed.

The work around is to switch to manual and them back to automatic to
force an NTP check.

Note this is with 'open-vm-tools' package installed rather than the
proprietary VM ware support tool installation script.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: systemd-services 198-0ubuntu11.1
ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
Uname: Linux 3.8.0-25-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
CheckboxSubmission: 55cafa5b8b82ed224cc59d444cb1fc25
CheckboxSystem: 3e53d3ea5811723345f19eff5070f9ab
Date: Thu Jun 27 08:03:56 2013
InstallationDate: Installed on 2013-06-22 (4 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
MarkForUpload: True
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug raring

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195169

Title:
  time and date doesn't update on resume in VM fusion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1195169/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1195169] Re: time and date doesn't update on resume in VM fusion

[Neil Wilson]

No it's both.

The system date is wrong. Nothing appears to be picking up the resume
event (assuming such a thing exists).

From the help on 'synchronise time' in VM Fusion:

You can configure whether the clock on the guest operating system is 
synchronized with the clock on the host.
If you turn on this advanced setting for time synchronization, the VMware Tools 
service, which runs inside the guest operating system, checks once every minute 
to determine whether the clocks on the guest and host operating systems still 
match. If not, the clock on the guest operating system is synchronized to match 
the clock on the host.

So it may be open-vm-tools hasn't got that facility in the package.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195169

Title:
  time and date doesn't update on resume in VM fusion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1195169/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1195169] Re: time and date doesn't update on resume in VM fusion

[Neil Wilson]

** Changed in: indicator-datetime (Ubuntu)
   Status: Incomplete = New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195169

Title:
  time and date doesn't update on resume in VM fusion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1195169/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs