Assignee: James Page (james-page)
Status: New
** Affects: software-properties (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: software-properties (Ubuntu Utopic)
Importance: Undecided
Assignee: James Page (james-page)
Status: New
** Also affects
Requested apport data from impacted users - may still be a problem on
12.04 - it would be nice if anyone who saw the issue over 2 years ago
could confirm whether this has been resolved.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 412011
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the
Looking at the kernels we have in supported releases, I think this
problem was fixed in 2011:
https://lkml.org/lkml/2011/10/1/28
Marking Fix Released.
** Changed in: pm-utils (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
** Changed in: pm-utils (Ubuntu)
Status: New = Triaged
** Changed in: pm-utils (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Fixed in version pm-utils/1.4.1-10
** Changed in: pm-utils (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/648832
Title:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
** Changed in: pm-utils (Ubuntu)
Status: New = Opinion
** Changed in: pm-utils (Ubuntu)
Importance: Undecided = Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
** Changed in: heimdal (Ubuntu)
Status: New = Opinion
** Changed in: heimdal (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to heimdal in Ubuntu.
Something is definitely not consistent:
ubuntu@churel:~$ sudo mii-tool -v eth0
eth0: negotiated 1000baseT-FD flow-control, link ok
product info: vendor 00:d8:97, model 34 rev 0
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 1000baseT-HD
Looks like:
printf(\n advertising: %s, media_list(advert, lpa2 2, 0));
if (lkpar MII_AN_ABILITY_MASK)
printf(\n link partner:%s, media_list(lkpar, bmcr2, 0));
should be
printf(\n advertising: %s, media_list(advert, bmcr2, 0));
if (lkpar LPA_ABILITY_MASK)
Appears to be resolved in upstream trunk codebase; looking at commits.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to net-tools in Ubuntu.
https://bugs.launchpad.net/bugs/860064
Title:
mii-tool in displays advertising and
*** This bug is a duplicate of bug 602049 ***
https://bugs.launchpad.net/bugs/602049
** This bug has been marked a duplicate of bug 602049
Suspend to RAM fails due to tpm_tis kernel module (regression)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
Public bug reported:
Context:
juju + MAAS deployed OpenStack environment, misc services deployed under
LXC on the bootstrap node, interfaces configured for jumbo frames - note
that I had to manually set the LXC container interfaces to mtu 9000
before the bridge would do the same.
Action:
Trusty)
Importance: Undecided = High
** Changed in: software-properties (Ubuntu Trusty)
Status: Confirmed = In Progress
** Changed in: software-properties (Ubuntu Trusty)
Assignee: (unassigned) = James Page (james-page)
--
You received this bug notification because you
why is this bug incomplete? as far as I can see there is sufficient
information to triage this...
Yes - you have to set the mtu on the lxc container interfaces to match
the bridge, otherwise it drops to the lowest MTU of any attached veth.
For now I've patched the config files to set the mtu
Public bug reported:
Context: Neutron gateway north/south routing server which manages a
large number of network namespaces; also hosts a few LXC containers for
misc lightweight control plane services.
Problem: If I restart one of the lxc containers, all of the namespaces
get corrupted in
Confirmed on utopic as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1401148
Title:
Re/starting an lxc container corrupts all network namespaces on the
same physical
Confirmed on vivid as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1401148
Title:
Re/starting an lxc container corrupts all network namespaces on the
same physical
sudo ip netns exec test ip addr
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1401148
Title:
Re/starting an lxc container corrupts all network namespaces on the
same
Public bug reported:
LXC containers configured with lxc.network.mtu = 9000
On start/restart using lxc-* commands, the mtu on the host and in
container interface is correctly set to 9000.
However, if the container is rebooted internally, the mtu of the veth on
the host resets to 1500, whilst the
** Tags added: landscape smoosh
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1401658
Title:
Host veth mtu not preserved during container reboot
Status in lxc package in
** Tags added: smoosh
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1350947
Title:
apparmor: no working rule to allow making a mount private
Status in AppArmor Linux
I think I see what the problem is; the containers on these hosts where
created with mtu 1500; i then updated the configuration files to set the
mtu to 9000 + set the veth mtu's to 9000 using:
ip link set veth mtu 9000
This means that the container was started using an mtu of 1500 not
Bumped priority for this bug as this is part of priority activity for
reference OpenStack deployments for the vivid cycle .
** Changed in: lxc (Ubuntu)
Importance: Medium = High
** Changed in: linux (Ubuntu)
Importance: Medium = High
** Tags added: landscape
--
You received this bug
I've re-titled this bug to be about effective interface MTU management
across MAAS and Juju; enabling Jumbo frames is something that we should
support in our core tooling and is critical for the successful operation
of a Neutron based OpenStack Cloud.
Combine this with LXC container spread across
Public bug reported:
There's a lot of supposition in the title of this bug but its currently
my best guess.
In this deployment, I have a number of services running in LXC
containers across multiple physical hosts; each service is clustered
across three units, all on separate physical hosts,
Looks like this is not actually fixed release - setting back to new.
** Changed in: python2.7 (Ubuntu Precise)
Status: Fix Released = New
** Changed in: python2.7 (Ubuntu Precise)
Importance: Undecided = High
** Tags added: mos
--
You received this bug notification because you are a
** Description changed:
+ [Impact]
+ Restarting rsyslog causing logging from python based daemons to lockup.
+
+ [Test Case]
+ == script
+ #!/usr/bin/env python
+
+ import eventlet
+ from logging.handlers import SysLogHandler
+ import time
+ import logging
+
+
** Description changed:
[Impact]
Restarting rsyslog causing logging from python based daemons to lockup.
[Test Case]
- == script
+ sudo apt-get install python-eventlet
+ == run this script script
#!/usr/bin/env python
import eventlet
from logging.handlers import SysLogHandler
I've done a bit more testing, and here are my observations:
1) rebooting a container internally/stop-start externally using lxc-*
Works OK - container re-joins the corosync cluster just fine.
2) rebooting the physical host
Fails - containers never re-join the corosync cluster and perform the
Things appear to be somewhat random; however setting the
multicast_querier flag to 1 resulted in all my clustered spring back to
life:
for i in `seq 0 10`; do juju ssh $i echo -n 1 | sudo tee
/sys/devices/virtual/net/juju-br0/bridge/multicast_querier; done
Juju creates a bridge where this is not
For context:
http://en.wikipedia.org/wiki/IGMP_snooping#IGMP_querier
** Also affects: juju-core
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Invalid = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1402763
Title:
Multicast traffic not propating correctly over
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282667/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282666/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
I enabled the multicast_querier using a udev rule for juju-br0; however
physical host reboots are still resulting in impact lxc containers not
re-joining the cluster; toggling the querier off/on again resolves the
issue so I'm guessing some sort of race.
** Tags added: apparmor apport-collected
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282669/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282668/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282671/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282672/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: KernLog.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282670/+files/KernLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282675/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282676/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282677/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: lxc-net.default.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282681/+files/lxc-net.default.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282679/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282678/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282674/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282673/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: lxcsyslog.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282683/+files/lxcsyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: lxc.default.txt
https://bugs.launchpad.net/bugs/1402763/+attachment/4282682/+files/lxc.default.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Even post toggling the querier off/no, multicast is still unreliable,
with cluster members failing to transmit data successfully to each
other.
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Just to fill in a bit more detail, the physical hosts have multiple lxc
containers (~3 each), any of which will be participating in a different
multicast group; containers in the same group are spread across
different physical hosts.
--
You received this bug notification because you are a member
Stephane
The network itself is pretty stock; the mtu on the switches is set to
9000; other than that its pretty much the standard cisco configuration
for the switch model.
I have the full details (but can't put them here :-)).
--
You received this bug notification because you are a member of
$ ip link help
Usage: ip link add [link DEV] [ name ] NAME
[ txqueuelen PACKETS ]
[ address LLADDR ]
[ broadcast LLADDR ]
[ mtu MTU ] [index IDX ]
[ numtxqueues QUEUE_COUNT ]
[
Suspicious commit:
http://anonscm.debian.org/cgit/collab-maint/pkg-
iproute.git/commit/ip/iplink.c?id=9a02651a87d0fd56e2e7eedd63921a050a42b3ec
** Bug watch added: Debian Bug tracker #757644
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757644
** Also affects: iproute2 (Debian) via
Confirmed neutron functional again with updated iproute2 package.
** Changed in: neutron (Ubuntu Utopic)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
** Changed in: ceph (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1413321
Title:
ceph-disk commands fail due to unset cluster
Public bug reported:
This appears to be a regression in the argparse package in python; under
trusty ceph-disk works just fine, however in vivid, the cluster
attribute remains unset (despite having a default of 'ceph').
Attached python demonstrates the problem.
ProblemType: Bug
DistroRelease:
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: software-properties (Ubuntu)
Importance: High
Assignee: James Page (james-page)
Status: In Progress
** Affects: software-properties (Ubuntu Trusty)
Importance: High
Assignee: James Page (james-page
Public bug reported:
dh_pythonX appears to go through the following series of checks when
generating dependencies for python packages:
1) check package specific pydist overrides
2) check for package in dh-python fallback files
3) check for package using dpkg -S
these last two steps appear the
Piotr - thanks for the pointer!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/1422433
Title:
installed packages should be checked first when generating
dependencies
Piotr
distro-info provides ubuntu-distro-info --devel which would give you
the name of the current devel release of Ubuntu, which is probably the
right source for most re-generations - full URL:
http://archive.ubuntu.com/ubuntu/dists/vivid/Contents-amd64.gz
Does that work for you?
--
You
Proposed patch attached for supporting Ubuntu fallback generation.
Piotr - can you let me know what you think?
** Patch added: pydist-ubuntu-support.patch
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1422433/+attachment/4322470/+files/pydist-ubuntu-support.patch
--
You received
Tested OK from proposed on trusty.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1412465
** Also affects: juju-core
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's Option interface-mtu 9000 is
** Changed in: cinder (Ubuntu)
Status: New = Fix Committed
** Changed in: cinder (Ubuntu)
Importance: Undecided = High
** Changed in: cinder (Ubuntu)
Assignee: (unassigned) = James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
We're seeing this error with the new kilo-3 milestone:
==
FAIL:
cinder.tests.test_utils.GetBlkdevMajorMinorTestCase.test_get_blkdev_major_minor_file
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Pacemaker unable to communicate with corosync on restart
+ Pacemaker unable to communicate with corosync on restart under lxc
--
You received this bug notification because you are a member of Ubuntu
I've being trying to reproduce this under KVM and on hardware (no LXC)
but I'm unable to reproduce the problem, so this appears isolated to
LXC.
The pacemaker - corosync communication occurs over IPC implemented
using shared memory. I'm wondering whether this is managing to get into
an
: James Page (james-page)
Status: In Progress
** Affects: dh-python (Ubuntu Wily)
Importance: Medium
Status: Fix Released
** Also affects: dh-python (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: dh-python (Ubuntu Wily)
Importance: Undecided
Confirm this resolved python3 related install ability issues with
argparse dependencies.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in
Updates for trusty, utopic and vivid uploaded to proposed for SRU team
review.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1401141
Title:
DHCP server does not work
Public bug reported:
[Impact]
python dependency definitions which declare != generate broken binary
dependencies (trailing -).
[Test Case]
[Regression Potential]
Minimal - in later releases; only impacts on 14.04 (backporting for Cloud
Archive).
Debian Bug:
)
Assignee: (unassigned) = James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/1475375
Title:
dh-python fails to parse != relationship
Status in dh
$ dpkg -I python-designate_1.0.0~b1-0ubuntu3_all.deb
new debian package, version 2.0.
size 236918 bytes: control archive=14338 bytes.
1901 bytes,21 lines control
56024 bytes, 492 lines md5sums
164 bytes, 9 lines * postinst
Public bug reported:
Please add support for:
cloud-archive:liberty
cloud-archive:liberty-proposed
This will also need to be SRU'ed back to trusty.
** Affects: software-properties (Ubuntu)
Importance: Undecided
Assignee: Corey Bryant (corey.bryant)
Status: New
**
LGTM +1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1472586
Title:
[SRU] Add support for liberty cloud-archive
Status in software-properties package in
(trusty-amd64)root@armstrong:~# add-apt-repository cloud-archive:liberty
Ubuntu Cloud Archive for OpenStack Liberty
More info: https://wiki.ubuntu.com/ServerTeam/CloudArchive
Press [ENTER] to continue or ctrl-c to cancel adding it
Reading package lists...
Building dependency tree...
Reading
Its the OpenStack Newton release archive for Ubuntu 16.04; it contains
backports of all the packages required to run OpenStack Newton from the
Yakkety release
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The command:
update-rc.d lvm2 defaults
in the maintainer script is throwing the error; the mountdevsubfs is
showing as masked by systemd:
$ systemctl status mountdevsubfs
● mountdevsubfs.service
Loaded: masked (/dev/null; bad)
Active: inactive (dead)
but lvm2 is as well - so not quite
Public bug reported:
Logging this bug as I don't think we should be doing this for Xenial -
the output of the net-tools tooling is quite different with the new
snapshot which I think as the potential to regress anything parsing the
output of net-tools tooling:
Current output:
$ ifconfig -a
** Summary changed:
- Merge net-tools 1.60+git20150829.73cef8a-2 from unstable
+ (Don't) Merge net-tools 1.60+git20150829.73cef8a-2 from unstable
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to net-tools in Ubuntu.
Public bug reported:
/e/n/i:
auto lo
iface lo inet loopback
dns-nameservers 10.245.168.2
dns-search dellstack
auto eth0
iface eth0 inet static
gateway 10.245.168.1
address 10.245.168.17/21
dns-nameservers 10.245.168.2
mtu 1500
auto eth1
iface eth1 inet manual
mtu
Turned out it was the mtu setting directly on the vlan interface that
causes the problem:
auto eth1.2667
iface eth1.2667 inet static
address 10.245.184.20/24
vlan-raw-device eth1
mtu 9000
vlan_id 2667
mtu needs to be set on the underlying network device (eth1 in this
case).
--
correction - the mismatch between the underlying network device and the
vlan interface causes the error:
Apr 04 14:15:23 reflecting-attraction ifup[5936]: run-parts: executing
/etc/network/if-pre-up.d/vlan
Apr 04 14:15:23 reflecting-attraction ifup[5936]: Set name-type for VLAN
subsystem.
Public bug reported:
Some updates to requirements for openstack projects (glance and keystone
specifically) is causing dh-python to incorrectly generate a != version
dependency; this is the requires.txt entry:
cryptography!=1.3.0,>=1.0
which causes (utimately):
dpkg-gencontrol: warning: can't
1 - 100 of 203 matches
Mail list logo
