[Bug 1560487] Re: local provider fails to create lxc container from template
** Changed in: juju-core/1.25 Status: In Progress => Invalid ** Changed in: juju-core/1.25 Importance: Critical => Undecided ** Changed in: juju-core/1.25 Assignee: Dimiter Naydenov (dimitern) => (unassigned) ** Changed in: juju-core/1.25 Milestone: 1.25.7 => None ** Changed in: opnfv Status: New => Invalid ** Changed in: juju-core Status: Won't Fix => Triaged ** Changed in: juju-core Milestone: None => 1.25.7 ** Changed in: juju-core Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560487 Title: local provider fails to create lxc container from template To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1560487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560487] Re: local provider fails to create lxc container from template
I got the expected error:
$ juju bootstrap
Bootstrap failed, cleaning up the environment.
ERROR there was an issue examining the environment: failed verification of
local provider prerequisites:
juju-local must be installed to enable the local provider:
sudo apt-get install juju-local
However, if I install both juju-local and lxc from trusty-backports:
sudo apt-get install juju-local -t trusty-backports lxc
apt-cache policy lxc
lxc:
Installed: 2.0.4-0ubuntu1~ubuntu14.04.1
Candidate: 2.0.4-0ubuntu1~ubuntu14.04.1
Version table:
*** 2.0.4-0ubuntu1~ubuntu14.04.1 0
100 http://us.archive.ubuntu.com/ubuntu/ trusty-backports/main amd64
Packages
100 /var/lib/dpkg/status
1.0.8-0ubuntu0.3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
1.0.7-0ubuntu0.7 0
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64
Packages
1.0.3-0ubuntu3 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
Then bootstrapped and added 1 trusty and 1 xenial container, juju status shows
no issues:
environment: local
machines:
"0":
agent-state: started
agent-version: 1.25.6.1
dns-name: localhost
instance-id: localhost
series: trusty
state-server-member-status: has-vote
"1":
agent-state: started
agent-version: 1.25.6.1
dns-name: 10.0.3.95
instance-id: ubuntu-local-machine-1
series: trusty
hardware: arch=amd64
"2":
agent-state: started
agent-version: 1.25.6.1
dns-name: 10.0.3.47
instance-id: ubuntu-local-machine-2
series: xenial
hardware: arch=amd64
services: {}
So the root cause is the juju-core source package (in trusty/updates):
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/juju-core/trusty-updates/view/head:/debian/control
The binary juju-local package has Depends: lxc (>=1.0.0~alpha1-0ubuntu14),
but it really should be depending on lxc (>=2.0.4...).
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1560487
Title:
local provider fails to create lxc container from template
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1560487/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590689] Re: MAAS 1.9.3 + Juju 1.25.5 - on the Juju controller node eth0 and juju-br0 interfaces have the same IP address at the same time
Closing this, as the LACP bonding issue on trusty is now tracked separately: https://bugs.launchpad.net/juju-core/+bug/1594855 ** Changed in: juju-core/1.25 Status: In Progress => Won't Fix ** Changed in: juju-core/1.25 Milestone: 1.25.6 => None ** Changed in: juju-core/1.25 Assignee: Dimiter Naydenov (dimitern) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590689 Title: MAAS 1.9.3 + Juju 1.25.5 - on the Juju controller node eth0 and juju- br0 interfaces have the same IP address at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1590689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592365] Re: Juju 2.0 crashes on bootstrap with datacentred.co.uk OpenStack cloud
** Package changed: juju-core (Ubuntu) => juju-core -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592365 Title: Juju 2.0 crashes on bootstrap with datacentred.co.uk OpenStack cloud To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1592365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584692] Re: fanatic does not use the user-specified underlay, but 192.168.0.0/16
Filed a separate bug 1584775 for the issue in comment #4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584692 Title: fanatic does not use the user-specified underlay, but 192.168.0.0/16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584775] [NEW] fanatic does not use the correct LXD command to import image for fanatic-test container
Public bug reported: Something I noticed while trying to use fanatic (see related bug 1584692): /usr/sbin/fanatic: 808: /usr/sbin/fanatic: lxd-images: not found Because of this the lxd test cannot spin up the test container, as it can't import the image. I managed to get it to work by patching fanatic like this: --- # Check if we have images already... lxc image show fanatic-test >/dev/null 2>&1 if [ "$?" -ne 0 ]; then echo "local lxd test: pulling container images ..." lxc image copy ubuntu:xenial local: --alias fanatic-test local rc="$?" if [ "$rc" -ne 0 ]; then echo "local lxd test: lxc image import failure, skipping test." return "$rc" fi fi --- There's no lxd-images on my machine and I suspect it used to be one in an earlier version of the LXD package. I'm using lxd 2.0.1-0ubuntu1~16 amd64 ubuntu-fan is 0.9.0 ** Affects: ubuntu-fan (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/1584775 Title: fanatic does not use the correct LXD command to import image for fanatic-test container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584692] Re: fanatic does not use the user-specified underlay, but 192.168.0.0/16
Another thing I noticed: /usr/sbin/fanatic: 808: /usr/sbin/fanatic: lxd-images: not found Because of this the lxd test cannot spin up the test container, as it can't import the image. I managed to get it to work by patching fanatic like this: --- # Check if we have images already... lxc image show fanatic-test >/dev/null 2>&1 if [ "$?" -ne 0 ]; then echo "local lxd test: pulling container images ..." lxc image copy ubuntu:xenial local: --alias fanatic-test local rc="$?" if [ "$rc" -ne 0 ]; then echo "local lxd test: lxc image import failure, skipping test." return "$rc" fi fi --- There's no lxd-images on my machine and I suspect it used to be one in an earlier version of the LXD package. I'm using lxd 2.0.1-0ubuntu1~16 amd64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584692 Title: fanatic does not use the user-specified underlay, but 192.168.0.0/16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584692] Re: fanatic does not use the user-specified underlay, but 192.168.0.0/16
I wasn't aware I needed to use an underlay range already present on my machine :/ (I thought it needs a free range to do the config). Using the defaults (I suspect, 192.168.0.0/16 was auto-detected) worked! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584692 Title: fanatic does not use the user-specified underlay, but 192.168.0.0/16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584692] Re: fanatic does not use the user-specified underlay, but 192.168.0.0/16
Trying to specify both explicitly yields a different error: http://paste.ubuntu.com/16630370/ Same result when I run `fanatic configure -u 10.88.0.0/16 -o 250.0.0.0/8` FWIW. There's a typo in the error message when I at first tried `fanatic -u 10.88.0.0./16 -o 250.0.0.0/8`: Usage: /usr/sbin/fanatic -u: uknown command -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584692 Title: fanatic does not use the user-specified underlay, but 192.168.0.0/16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584692] [NEW] fanatic does not use the user-specified underlay, but 192.168.0.0/16
Public bug reported: On a xenial machine, I tried to use fanatic to configure the fan with underlay 10.88.0.0/16 and the suggested overlay 250.0.0.0/8, but the underlay suggested by fanatic (192.168.0.0/16) was used instead of 10.88.0.0/16 I specified. Here's the paste of the session: http://paste.ubuntu.com/16630235/ ** Affects: ubuntu-fan (Ubuntu) Importance: Undecided Status: New ** Summary changed: - fanatic does not use the user-specific underlay but 192.168.0.0/16 + fanatic does not use the user-specified underlay, but 192.168.0.0/16 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584692 Title: fanatic does not use the user-specified underlay, but 192.168.0.0/16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567744] Re: USB NICs get too long name for ifupdown aliases
Additionally, Juju creates bridges on top of both physical and VLAN interfaces to allow for the same level of addressability for containers as regular machines. The bridges currently use the "br-" prefix and the underlying device name, which if it happens to be "enxxaabbccddeef0.1234" already, obviously won't work. So the length limit on interface names can be even lower than what Mike suggested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547060] Re: cant use -d switch
I'm seeing quite a lot of oom kills with multiple boot images imported in MAAS 2.0.0 (beta3), which depends on tgt via maas-rack-controller package. FWIW this issue causes the workaround suggested in bug 1389811 impossible (passing -t 1 to limit the number of threads to 1, rather than causing oom killer). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547060 Title: cant use -d switch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1547060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address
Related bug #1520199 fixed in 1.25 and master. ** No longer affects: juju-core ** Changed in: juju-core (Ubuntu) Status: New => Invalid ** Package changed: juju-core (Ubuntu) => ubuntu ** Package changed: ubuntu => juju-core ** No longer affects: juju-core -- 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/1519527 Title: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1519527/+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 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address
Related bug #1520199 fixed in 1.25 and master. ** No longer affects: juju-core ** Changed in: juju-core (Ubuntu) Status: New => Invalid ** Package changed: juju-core (Ubuntu) => ubuntu ** Package changed: ubuntu => juju-core ** No longer affects: juju-core -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519527 Title: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1519527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address
Andres, the issue with b2 is "maas device claim-sticky-ip- address " (which juju 1.25.1 uses, after creating a device for the container with parent it's host node) fails to allocate an address for the device, despite having properly configured ranges and available IPs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519527 Title: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1519527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1519527] Re: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address
Andres, the issue with b2 is "maas device claim-sticky-ip- address " (which juju 1.25.1 uses, after creating a device for the container with parent it's host node) fails to allocate an address for the device, despite having properly configured ranges and available IPs. -- 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/1519527 Title: juju 1.25.1: lxc units all have the same IP address - changed to claim_sticky_ip_address To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1519527/+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 1307445] Re: openstack: instances with multiple nics on the same network don't have deterministic private-addresses
** Changed in: juju-core Status: Triaged = Incomplete -- 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/1307445 Title: openstack: instances with multiple nics on the same network don't have deterministic private-addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307445/+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 1307445] Re: openstack: instances with multiple nics on the same network don't have deterministic private-addresses
** Changed in: juju-core Status: Triaged = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307445 Title: openstack: instances with multiple nics on the same network don't have deterministic private-addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403955] Re: DHCP's Option interface-mtu 9000 is being ignored on bridge interface br0
juju-br0 was reintroduced in 1.23.3 as the default behavior in MAAS, unless the address-allocation feature flag is enabled. AIUI the juju-br0 swallows the interface-mtu DHCP setting coming from MAAS. It doesn't happen when eth0 is not bound to juju-br0. So it looks like this is a pre-existing issue since for ever. I'm open to suggestions how Juju can work around the issue (e.g. by generating a slightly different /etc/network/interfaces file with the juju-br0 definition and/or brctl commands). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1403955 Title: DHCP's Option interface-mtu 9000 is being ignored on bridge interface br0 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1403955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403955] Re: DHCP's Option interface-mtu 9000 is being ignored on bridge interface br0
Depending on the version of juju used, one option is to set: lxc-default-mtu: 9000 in environments.yaml for that environment and re-bootstrap. All LXC containers juju creates should use 9000 as MTU for the eth0 of the container. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1403955 Title: DHCP's Option interface-mtu 9000 is being ignored on bridge interface br0 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1403955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1355813] Re: Interface MTU management across MAAS/juju
See also the related bug 1442257 which has a proposed fix. -- 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/1355813 Title: Interface MTU management across MAAS/juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1355813] Re: Interface MTU management across MAAS/juju
See also the related bug 1442257 which has a proposed fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1355813 Title: Interface MTU management across MAAS/juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403955] Re: DHCP's Option interface-mtu 9000 is being ignored on bridge interface br0
Since 1.23 there's no need to create juju-br0 (or as it used to be called before - br0) at initial boot, so this should solve the issue. ** Changed in: juju-core Status: Triaged = Fix Committed ** Changed in: juju-core Milestone: None = 1.23-beta1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1403955 Title: DHCP's Option interface-mtu 9000 is being ignored on bridge interface br0 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1403955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423626] Re: Inconsistent device naming depending on install method - biosdevname/no biosdevname
Blake, yes that's correct - having stable names based on udev rules, especially discoverable via the API will be the proper way to fix this for MAAS. The solution proposed in comment #1 could potentially work for any provider, but relying on networking features (discovery, configuration, even connectivity) during boot is racy and unreliable with current cloud-init support (2.0 will hopefully solve this). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1423626 Title: Inconsistent device naming depending on install method - biosdevname/no biosdevname To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1423626/+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 1423626] Re: Inconsistent device naming depending on install method - biosdevname/no biosdevname
Blake, yes that's correct - having stable names based on udev rules, especially discoverable via the API will be the proper way to fix this for MAAS. The solution proposed in comment #1 could potentially work for any provider, but relying on networking features (discovery, configuration, even connectivity) during boot is racy and unreliable with current cloud-init support (2.0 will hopefully solve this). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423626 Title: Inconsistent device naming depending on install method - biosdevname/no biosdevname To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1423626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307445] Re: openstack: instances with multiple nics on the same network don't have deterministic private-addresses
** Tags added: network -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307445 Title: openstack: instances with multiple nics on the same network don't have deterministic private-addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307445] Re: openstack: instances with multiple nics on the same network don't have deterministic private-addresses
** Tags added: network -- 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/1307445 Title: openstack: instances with multiple nics on the same network don't have deterministic private-addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307445/+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 1417771] Re: juju-core vivid ppc64el fails to build
There's an updated gccgo-go version for vivid - https://launchpad.net/ubuntu/+source/gccgo-go/1.2.1-0ubuntu7 which includes fixes for a number of issues we're seeing (tests failing, builds failing due to duplicate symbols, random instabilities). Why is this 1.2.1-0ubuntu7 not backported to trusty (even precise?). I think it should be to solve those issues and use it on the ppc64 CI jobs among others. Having CI blockers due to a flaky ppc64 compiler version which already has a fixed version is NOT OK. Related bug #1393825, another one - #1381671. ** Changed in: gccgo-go (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417771 Title: juju-core vivid ppc64el fails to build To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1417771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381671] Re: reboot tests fail to build on gccgo
It turns out the vivid package does not yet have the needed patch from https://go-review.googlesource.com/#/c/1840/ we'll have to wait for an upstream release I guess. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381671 Title: reboot tests fail to build on gccgo To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1381671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417771] Re: juju-core vivid ppc64el fails to build
It turns out the vivid package does not yet have the needed patch from https://go-review.googlesource.com/#/c/1840/ we'll have to wait for an upstream release I guess. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417771 Title: juju-core vivid ppc64el fails to build To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1417771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393825] Re: Juju testsuite fails in random ways
It turns out the vivid package does not yet have the needed patch from https://go-review.googlesource.com/#/c/1840/ we'll have to wait for an upstream release I guess. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393825 Title: Juju testsuite fails in random ways To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1393825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393825] Re: Juju testsuite fails in random ways
Related bug 1417771. Let's release an updated version of gccgo-go for trusty at least, if not precise. In vivid, a more recent release (1.2.1-0ubuntu7 ) has the fix. ** Changed in: gccgo-go (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393825 Title: Juju testsuite fails in random ways To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1393825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381671] Re: reboot tests fail to build on gccgo
Related bug 1417771. Let's release an updated version of gccgo-go for trusty at least, if not precise. In vivid, a more recent release (1.2.1-0ubuntu7 ) has the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381671 Title: reboot tests fail to build on gccgo To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1381671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417771] Re: juju-core vivid ppc64el fails to build
OK, jamespage confirmed a port to precise is not happening, as there's no ppc64 support in there. That's fine - let's see what we can do for trusty though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417771 Title: juju-core vivid ppc64el fails to build To manage notifications about this bug go to: https://bugs.launchpad.net/juju-release-tools/+bug/1417771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423626] Re: Inconsistent device naming depending on install method - biosdevname/no biosdevname
The problem in such cases is juju has little control on how the machine's hardware (as seed by lshw) changes between commissioning and deployment, and frankly neither has maas. jamespage suggested that juju could inject a script very early (e.g. a bootcmd) in the cloud-init userdata to try and discover what interface names and MAC addresses the machine has and try to match those from the lshw data juju already gets from maas during node allocation. This nice thing about this solution is that it's not maas specific, but can be used elsewhere (e.g. other distros, with systemd, etc.). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1423626 Title: Inconsistent device naming depending on install method - biosdevname/no biosdevname To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1423626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1423626] Re: Inconsistent device naming depending on install method - biosdevname/no biosdevname
The problem in such cases is juju has little control on how the machine's hardware (as seed by lshw) changes between commissioning and deployment, and frankly neither has maas. jamespage suggested that juju could inject a script very early (e.g. a bootcmd) in the cloud-init userdata to try and discover what interface names and MAC addresses the machine has and try to match those from the lshw data juju already gets from maas during node allocation. This nice thing about this solution is that it's not maas specific, but can be used elsewhere (e.g. other distros, with systemd, etc.). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1423626 Title: Inconsistent device naming depending on install method - biosdevname/no biosdevname To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1423626/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Which version of juju are you using? What's the content of the lshw xml dump for the instance with the p1p1 NIC? The MAAS provider uses that lshw output generated during the node's commissioning to determine which is the primary NIC on that node, so it can be added into the bridge. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Which version of juju are you using? What's the content of the lshw xml dump for the instance with the p1p1 NIC? The MAAS provider uses that lshw output generated during the node's commissioning to determine which is the primary NIC on that node, so it can be added into the bridge. -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1183129] Re: 'juju status' difficult to read and provides unneccessary information
I think we can close this now - juju status --format accepts a number of
new output formats (in addition to the default yaml and optional
json). Excerpt from juju status --help:
There are a number of ways to format the status output:
- {short|line|oneline}: List units and their subordinates. For each
unit, the IP address and agent status are listed.
- summary: Displays the subnet(s) and port(s) the environment utilizes.
Also displays aggregate information about:
- MACHINES: total #, and # in each state.
- UNITS: total #, and # in each state.
- SERVICES: total #, and # exposed of each service.
- tabular: Displays information in a tabular format in these sections:
- Machines: ID, STATE, VERSION, DNS, INS-ID, SERIES, HARDWARE
- Services: NAME, EXPOSED, CHARM
- Units: ID, STATE, VERSION, MACHINE, PORTS, PUBLIC-ADDRESS
- Also displays subordinate units.
- yaml (DEFAULT): Displays information on machines, services, and units
in the yaml format.
** Changed in: juju-core
Status: Triaged = Fix Released
--
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/1183129
Title:
'juju status' difficult to read and provides unneccessary information
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1183129/+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 1183129] Re: 'juju status' difficult to read and provides unneccessary information
I think we can close this now - juju status --format accepts a number of
new output formats (in addition to the default yaml and optional
json). Excerpt from juju status --help:
There are a number of ways to format the status output:
- {short|line|oneline}: List units and their subordinates. For each
unit, the IP address and agent status are listed.
- summary: Displays the subnet(s) and port(s) the environment utilizes.
Also displays aggregate information about:
- MACHINES: total #, and # in each state.
- UNITS: total #, and # in each state.
- SERVICES: total #, and # exposed of each service.
- tabular: Displays information in a tabular format in these sections:
- Machines: ID, STATE, VERSION, DNS, INS-ID, SERIES, HARDWARE
- Services: NAME, EXPOSED, CHARM
- Units: ID, STATE, VERSION, MACHINE, PORTS, PUBLIC-ADDRESS
- Also displays subordinate units.
- yaml (DEFAULT): Displays information on machines, services, and units
in the yaml format.
** Changed in: juju-core
Status: Triaged = 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/1183129
Title:
'juju status' difficult to read and provides unneccessary information
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1183129/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1355813] Re: Interface MTU management across MAAS/juju
Proposed a fix with http://reviews.vapour.ws/r/686/ - before starting a container, the host's primary physical NIC's MTU value is detected and applied to the container's veth device. -- 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/1355813 Title: Interface MTU management across MAAS/juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1355813] Re: Interface MTU management across MAAS/juju
** Changed in: juju-core Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1355813 Title: Interface MTU management across MAAS/juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1355813] Re: Interface MTU management across MAAS/juju
Proposed a fix with http://reviews.vapour.ws/r/686/ - before starting a container, the host's primary physical NIC's MTU value is detected and applied to the container's veth device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1355813 Title: Interface MTU management across MAAS/juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1355813] Re: Interface MTU management across MAAS/juju
** Changed in: juju-core Status: In Progress = Fix Committed -- 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/1355813 Title: Interface MTU management across MAAS/juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1355813] Re: Interface MTU management across MAAS/juju
** Changed in: juju-core Assignee: (unassigned) = Dimiter Naydenov (dimitern) ** Changed in: juju-core Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1355813 Title: Interface MTU management across MAAS/juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1355813] Re: Interface MTU management across MAAS/juju
** Changed in: juju-core Assignee: (unassigned) = Dimiter Naydenov (dimitern) ** Changed in: juju-core Status: Triaged = In Progress -- 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/1355813 Title: Interface MTU management across MAAS/juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Yes, it appears you're having a separate issue. I'd appreciate if you open a new bug for it and we can continue there. -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Yes, it appears you're having a separate issue. I'd appreciate if you open a new bug for it and we can continue there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
@mark-dickie Can you please try to reproduce this with the latest juju- core built from source (master branch) to see if you still have an issue? If you do, please attach the following logs to help us analyze the issue better: Before anything, please add logging-config: root=TRACE to your maas environment config in ~/environments.yaml. The result of running $ juju bootstrap --upload-tools --debug ~/maas-bootstrap.log (you mentioned you're using the latest From the bootstrap node: /var/log/cloud-init.log /var/log/cloud-init-output.log /var/log/juju/machine-0.log /var/log/juju/machine-0-lxc-0.log -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
@mwenning - What's the output of $ juju version? Can you try what I've proposed in comment #46? -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
@mark-dickie - I can't see 1.21-beta3 in https://launchpad.net/~juju/+archive/ubuntu/proposed are you sure you didn't mean https://launchpad.net/~juju/+archive/ubuntu/devel ? Thanks for sharing the workaround - at least it gives me something to look into! :) -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
@mark-dickie: Ok, 1.21-beta3 actually should have the fix - no need to build from source. Can you: 1. Edit your ~/.juju/environments.yaml to include logging-config: root=TRACE for your maas environment. 2. Run $ juju bootstrap --debug ~/maas-bootstrap.log 3. Once the machine is up and you can SSH into it (via juju ssh 0 or otherwise), get /var/log/juju/*.log and /var/log/cloud*.log, zip them and attach them to the bug please. Of course, provided you can reproduce the issue still. Thanks! -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Thanks for the logs! None of them show anything alarming. However something is wrong with your setup. How did you reboot the instance after the bootstrap was done? Once MAAS provisions a machine cloud-init should not run anymore - it's only used to boot the initial OS. Did you recommission or deallocate the node from MAAS? Another request - since the initial bootstrap completes ok, can you please retry the same and attach the contents of /etc/network/interfaces and /etc/network/interfaces.d/*.* ? If the problem happens after reboot something might be wrong with how the interfaces are configured there. -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
@mark-dickie Can you please try to reproduce this with the latest juju- core built from source (master branch) to see if you still have an issue? If you do, please attach the following logs to help us analyze the issue better: Before anything, please add logging-config: root=TRACE to your maas environment config in ~/environments.yaml. The result of running $ juju bootstrap --upload-tools --debug ~/maas-bootstrap.log (you mentioned you're using the latest From the bootstrap node: /var/log/cloud-init.log /var/log/cloud-init-output.log /var/log/juju/machine-0.log /var/log/juju/machine-0-lxc-0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
@mwenning - What's the output of $ juju version? Can you try what I've proposed in comment #46? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
@mark-dickie - I can't see 1.21-beta3 in https://launchpad.net/~juju/+archive/ubuntu/proposed are you sure you didn't mean https://launchpad.net/~juju/+archive/ubuntu/devel ? Thanks for sharing the workaround - at least it gives me something to look into! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
@mark-dickie: Ok, 1.21-beta3 actually should have the fix - no need to build from source. Can you: 1. Edit your ~/.juju/environments.yaml to include logging-config: root=TRACE for your maas environment. 2. Run $ juju bootstrap --debug ~/maas-bootstrap.log 3. Once the machine is up and you can SSH into it (via juju ssh 0 or otherwise), get /var/log/juju/*.log and /var/log/cloud*.log, zip them and attach them to the bug please. Of course, provided you can reproduce the issue still. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Thanks for the logs! None of them show anything alarming. However something is wrong with your setup. How did you reboot the instance after the bootstrap was done? Once MAAS provisions a machine cloud-init should not run anymore - it's only used to boot the initial OS. Did you recommission or deallocate the node from MAAS? Another request - since the initial bootstrap completes ok, can you please retry the same and attach the contents of /etc/network/interfaces and /etc/network/interfaces.d/*.* ? If the problem happens after reboot something might be wrong with how the interfaces are configured there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338675] [NEW] GPU lockup IPEHR: 0x0a080001 IPEHR: 0x01000000
*** This bug is a duplicate of bug 1338673 *** https://bugs.launchpad.net/bugs/1338673 Public bug reported: I've already reported this several times, as it happens multiple times after login or later. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jun 30 20:05:59 2014 DistUpgraded: 2014-06-20 00:25:45,939 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-29-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.15.0-6-generic, x86_64: installed DpkgLog: DuplicateSignature: GPU lockup IPEHR: 0x0a080001 IPEHR: 0x0100 Ubuntu 14.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00fd] InstallationDate: Installed on 2013-06-09 (392 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir5,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=04cb2209-8ab8-4b63-ba31-dac82ab949d3 ro quiet splash libata.force=1:noncq vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libdrm2 2.4.54-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: GPU lockup IPEHR: 0x0a080001 IPEHR: 0x0100 UpgradeStatus: Upgraded to utopic on 2014-06-19 (17 days ago) UserGroups: dmi.bios.date: 11/27/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA51.88Z.00EF.B02.1211271028 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-66F35F19FE2A0D05 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-66F35F19FE2A0D05 dmi.modalias: dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05: dmi.product.name: MacBookAir5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Jul 7 19:36:15 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 40178 vendor APP xserver.version: 2:1.15.1-0ubuntu5 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 freeze ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338675 Title: GPU lockup IPEHR: 0x0a080001 IPEHR: 0x0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1338675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338673] [NEW] GPU lockup IPEHR: 0x0a080001 IPEHR: 0x01000000
Public bug reported: Occurs 5 times after login each time. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jun 30 21:49:51 2014 DistUpgraded: 2014-06-20 00:25:45,939 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-29-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.15.0-6-generic, x86_64: installed DpkgLog: DuplicateSignature: GPU lockup IPEHR: 0x0a080001 IPEHR: 0x0100 Ubuntu 14.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00fd] InstallationDate: Installed on 2013-06-09 (392 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir5,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=04cb2209-8ab8-4b63-ba31-dac82ab949d3 ro quiet splash libata.force=1:noncq vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libdrm2 2.4.54-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: GPU lockup IPEHR: 0x0a080001 IPEHR: 0x0100 UpgradeStatus: Upgraded to utopic on 2014-06-19 (17 days ago) UserGroups: dmi.bios.date: 11/27/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA51.88Z.00EF.B02.1211271028 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-66F35F19FE2A0D05 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-66F35F19FE2A0D05 dmi.modalias: dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05: dmi.product.name: MacBookAir5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Jul 7 19:36:15 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 40178 vendor APP xserver.version: 2:1.15.1-0ubuntu5 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 freeze ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338673 Title: GPU lockup IPEHR: 0x0a080001 IPEHR: 0x0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1338673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335623] [NEW] GPU lockup IPEHR: 0x0a080001 IPEHR: 0x0b140001
Public bug reported: I get the crash report dialog after every login, often more than one. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jun 23 21:51:33 2014 DistUpgraded: 2014-06-20 00:25:45,939 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-29-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.15.0-6-generic, x86_64: installed DuplicateSignature: GPU lockup IPEHR: 0x0a080001 IPEHR: 0x0b140001 Ubuntu 14.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00fd] InstallationDate: Installed on 2013-06-09 (384 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.4 MachineType: Apple Inc. MacBookAir5,1 ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=04cb2209-8ab8-4b63-ba31-dac82ab949d3 ro quiet splash libata.force=1:noncq vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libdrm2 2.4.54-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: GPU lockup IPEHR: 0x0a080001 IPEHR: 0x0b140001 UpgradeStatus: Upgraded to utopic on 2014-06-19 (9 days ago) UserGroups: dmi.bios.date: 11/27/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA51.88Z.00EF.B02.1211271028 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-66F35F19FE2A0D05 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-66F35F19FE2A0D05 dmi.modalias: dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05: dmi.product.name: MacBookAir5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Jun 29 16:38:14 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 40178 vendor APP xserver.version: 2:1.15.1-0ubuntu5 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 freeze need-duplicate-check ubuntu utopic ** Description changed: - I get the e report dialog after every login, often more than one. + I get the crash report dialog after every login, often more than one. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: - + ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jun 23 21:51:33 2014 DistUpgraded: 2014-06-20 00:25:45,939 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: - bcmwl, 6.30.223.141+bdcom, 3.13.0-29-generic, x86_64: installed - bcmwl, 6.30.223.141+bdcom, 3.15.0-6-generic, x86_64: installed + bcmwl, 6.30.223.141+bdcom, 3.13.0-29-generic, x86_64: installed + bcmwl,
[Bug 1284127] Re: juju deploy fails against juju-core 1.17.3 environment with 1.17.2 client
How is this a regression in juju-core when the issue seems to be the slower updating of streams.canonical.com after the release? This is bound to happen at any time we do a release and update streams.c.c some time after. -- 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/1284127 Title: juju deploy fails against juju-core 1.17.3 environment with 1.17.2 client To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1284127/+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 1284127] Re: juju deploy fails against juju-core 1.17.3 environment with 1.17.2 client
How is this a regression in juju-core when the issue seems to be the slower updating of streams.canonical.com after the release? This is bound to happen at any time we do a release and update streams.c.c some time after. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284127 Title: juju deploy fails against juju-core 1.17.3 environment with 1.17.2 client To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1284127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183776] [NEW] bzr diff --old/--new does not report and changes with a lightweight checkout of a native repo
Public bug reported: I'm using a native repo in ~/src/juju-core. I have a lightweight checkout of it in ~/go/src/launchpad.net/juju-core/ (in my $GOPATH). In addition I have a symlink in ~/work/juju-core pointing to the second path above. I have 2 branches: trunk and 041-provisioner-api-calls What happens: $ cd ~/work/juju-core $ bzr diff --old trunk --new 041-provisioner-api-calls state/api bzr: ERROR: Path(s) are not versioned: 041-provisioner-api-calls trunk If instead I do this it works: $ cd ~ $ bzr diff --old ~/src/juju-core/trunk --new ~/src/juju-core/041-provisioner-api-calls/ state/api Or even: $ cd ~/src $ bzr diff --old trunk --new 041-provisioner-api-calls state/api Also works. I'd expect bzr diff working in the lightweight checkout just the same as in the native repo it links to. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: bzr 2.6.0~bzr6571-4ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri May 24 12:49:05 2013 InstallationDate: Installed on 2011-11-17 (553 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True PackageArchitecture: all SourcePackage: bzr UpgradeStatus: Upgraded to raring on 2013-05-03 (20 days ago) ** Affects: bzr (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bzr diff raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183776 Title: bzr diff --old/--new does not report and changes with a lightweight checkout of a native repo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/1183776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177583] Re: lxc-list crash after lxc-destory of a running container
Thanks for investigating this! You can find plan9port and installation instructions from here: http://swtch.com/plan9port/ I forgot to mention, in order to build p9p I also installed wget and build-essential into the container. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1177583 Title: lxc-list crash after lxc-destory of a running container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1177583/+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 1177583] Re: lxc-list crash after lxc-destroy of a running container
So I followed your suggestions for retracing he apport dump and got these results (not much I'm afraid): http://paste.ubuntu.com/5645895/ (1st option); http://paste.ubuntu.com/5645890/ (2nd option). I'll try replicating the same steps I did before from scratch to see if I can reproduce it later today. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1177583 Title: lxc-list crash after lxc-destroy of a running container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1177583/+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 1177583] Re: lxc-list crash after lxc-destory of a running container
Thanks for investigating this! You can find plan9port and installation instructions from here: http://swtch.com/plan9port/ I forgot to mention, in order to build p9p I also installed wget and build-essential into the container. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177583 Title: lxc-list crash after lxc-destory of a running container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1177583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177583] Re: lxc-list crash after lxc-destroy of a running container
So I followed your suggestions for retracing he apport dump and got these results (not much I'm afraid): http://paste.ubuntu.com/5645895/ (1st option); http://paste.ubuntu.com/5645890/ (2nd option). I'll try replicating the same steps I did before from scratch to see if I can reproduce it later today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177583 Title: lxc-list crash after lxc-destroy of a running container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1177583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177583] [NEW] lxc-list crash after lxc-destory of a running container
Public bug reported: I created a container with lxc-create -t ubuntu -n test1; started it (lxc-start -n test1); installed plan9port and some x-related packages (xterm, xdm, xserver-xorg-core, xserver-xorg). Then, while it was still running, logged out and run lxc-destroy -n test1, which hung and I had to break it and then calling lxc-list also hung forever. Trying to remove the container from /var/lib/lxc/test1/ failed with: rm: cannot remove ‘/var/lib/lxc/test1/rootfs/dev/pts’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/dev/ptmx’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/dev/lxc/console’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/dev/lxc/tty1’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/dev/lxc/tty4’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/dev/lxc/tty3’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/dev/lxc/tty2’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/proc’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/sys’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/run’: Device or resource busy Running ps -xa | grep lxc produced: 121 1509 1 0 09:01 ?00:00:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/lxc/dnsmasq.pid --conf-file= --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative root 5604 1 0 14:32 ?00:00:00 sudo lxc-start -n test1 root 5605 5604 0 14:32 ?00:00:00 lxc-start -n test1 root 8977 8771 0 15:12 pts/900:00:00 sudo lxc-destroy -n test1 root 8978 8977 0 15:12 pts/900:00:00 /bin/sh /usr/bin/lxc-destroy -n test1 root 8984 8978 0 15:12 pts/900:00:00 lxc-info -n test1 -P /var/lib/lxc --state-is STOPPED dimitern 8995 8901 0 15:13 pts/10 00:00:00 grep --color=auto lxc Finally, killing -9 the lxc-info with pid 8984 caused the hung lxc- destroy to return and lxc-list afterwards did not hang anymore. Attached the /var/crash/ file. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Attachment added: _usr_bin_lxc-ls.0.crash https://bugs.launchpad.net/bugs/1177583/+attachment/3669265/+files/_usr_bin_lxc-ls.0.crash -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1177583 Title: lxc-list crash after lxc-destory of a running container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1177583/+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 1177583] [NEW] lxc-list crash after lxc-destory of a running container
Public bug reported: I created a container with lxc-create -t ubuntu -n test1; started it (lxc-start -n test1); installed plan9port and some x-related packages (xterm, xdm, xserver-xorg-core, xserver-xorg). Then, while it was still running, logged out and run lxc-destroy -n test1, which hung and I had to break it and then calling lxc-list also hung forever. Trying to remove the container from /var/lib/lxc/test1/ failed with: rm: cannot remove ‘/var/lib/lxc/test1/rootfs/dev/pts’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/dev/ptmx’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/dev/lxc/console’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/dev/lxc/tty1’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/dev/lxc/tty4’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/dev/lxc/tty3’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/dev/lxc/tty2’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/proc’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/sys’: Device or resource busy rm: cannot remove ‘/var/lib/lxc/test1/rootfs/run’: Device or resource busy Running ps -xa | grep lxc produced: 121 1509 1 0 09:01 ?00:00:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/var/run/lxc/dnsmasq.pid --conf-file= --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative root 5604 1 0 14:32 ?00:00:00 sudo lxc-start -n test1 root 5605 5604 0 14:32 ?00:00:00 lxc-start -n test1 root 8977 8771 0 15:12 pts/900:00:00 sudo lxc-destroy -n test1 root 8978 8977 0 15:12 pts/900:00:00 /bin/sh /usr/bin/lxc-destroy -n test1 root 8984 8978 0 15:12 pts/900:00:00 lxc-info -n test1 -P /var/lib/lxc --state-is STOPPED dimitern 8995 8901 0 15:13 pts/10 00:00:00 grep --color=auto lxc Finally, killing -9 the lxc-info with pid 8984 caused the hung lxc- destroy to return and lxc-list afterwards did not hang anymore. Attached the /var/crash/ file. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Attachment added: _usr_bin_lxc-ls.0.crash https://bugs.launchpad.net/bugs/1177583/+attachment/3669265/+files/_usr_bin_lxc-ls.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177583 Title: lxc-list crash after lxc-destory of a running container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1177583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155166] [NEW] HUD keyboard shortcut always reset after an update
Public bug reported: It's really frustrating that every time the update manager runs and applies an update, my keyboard shortcut for showing the HUD (default: Alt L) is reset to the default and I always have to set it back to something else (which I never use, like Shift+Ctrl+Alt+F12). I do this, because I have a xbindkeys mapping of Alt + Left / Alt + Right mapped to my Logitech 10 button mouse's forward/back thumb buttons. I haven't noticed any other shortcuts changing after an update. I never use the HUD and I don't really find it useful. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.12.0-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,gtkloader,opengl,copytex,decor,mousepoll,imgjpeg,commands,resize,place,imgsvg,regex,session,grid,compiztoolbox,imgpng,move,gnomecompat,animation,snap,wall,expo,fade,workarounds,ezoom,scale,unityshell] Date: Thu Mar 14 15:36:14 2013 InstallationDate: Installed on 2011-11-17 (482 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2013-01-05 (68 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hud keyboard-shortcuts quantal running-unity settings unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155166 Title: HUD keyboard shortcut always reset after an update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1155166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1129159] Re: Show Transmission app indicator checkbox not updated when launching from the Launcher
** Attachment added: transmission-2.jpg https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1129159/+attachment/3534868/+files/transmission-2.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1129159 Title: Show Transmission app indicator checkbox not updated when launching from the Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1129159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1129159] [NEW] Show Transmission app indicator checkbox not updated when launching from the Launcher
Public bug reported: This is really, just a minor, trivial thing. When you open the app indicator menu for Transmission, and click Show Transmission, the checkbox gets updated and the main window shows (or hides if it was visible). Now, if you close the window and open it from the Launcher (provided you have it pinned there), the checkbox gets out of sync and is checked when the window is hidden and vice versa. If you show/hide the window only from the app indicator, checkbox works and acts as expected. Attached a screenshots: 1) window not visible (as seen on the desktop and in the launcher), but app indicator menu has the checkbox 2) window visible, checkbox on - as expected (from 1) just click on the launcher icon) 3) window visible, checkbox off - not expected (from 2, close the window and reopen it from the launcher icon) $ lsb_release -rd Description:Ubuntu 12.10 Release:12.10 $ apt-cache policy transmission-gtk transmission-gtk: Installed: 2.61-0ubuntu2.1 Candidate: 2.61-0ubuntu2.1 Version table: *** 2.61-0ubuntu2.1 0 500 http://mt.archive.ubuntu.com/ubuntu/ quantal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.61-0ubuntu2 0 500 http://mt.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages Expected: * app indicator checkbox stays in sync with the visibility of the main window, regardless how the windows is shown (via the app indicator menu or from the launcher) Actual: * checkbox looses sync when the window is opened/closed from the launcher ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: transmission-gtk 2.61-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4 Uname: Linux 3.5.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Mon Feb 18 15:22:45 2013 InstallationDate: Installed on 2011-11-17 (458 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True SourcePackage: transmission UpgradeStatus: Upgraded to quantal on 2013-01-05 (44 days ago) ** Affects: transmission (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed quantal running-unity ** Attachment added: transmission-1.jpg https://bugs.launchpad.net/bugs/1129159/+attachment/3534865/+files/transmission-1.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1129159 Title: Show Transmission app indicator checkbox not updated when launching from the Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1129159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1129159] Re: Show Transmission app indicator checkbox not updated when launching from the Launcher
** Attachment added: transmission-3.jpg https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1129159/+attachment/3534869/+files/transmission-3.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1129159 Title: Show Transmission app indicator checkbox not updated when launching from the Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1129159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1044503] Re: kernel command line is not easily customizable
** Branch linked: lp:~jameinel/maas/1.2-node-get-effective-kernel- options ** Branch linked: lp:~gz/maas/1.2_add_db_kernel_params -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1044503 Title: kernel command line is not easily customizable To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1044503/+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 1044503] Re: kernel command line is not easily customizable
** Branch linked: lp:~jameinel/maas/1.2-node-get-effective-kernel- options ** Branch linked: lp:~gz/maas/1.2_add_db_kernel_params -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1044503 Title: kernel command line is not easily customizable To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1044503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1044503] Re: kernel command line is not easily customizable
** Branch linked: lp:~dimitern/maas/1.2-node-view-shows-kernel-params -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1044503 Title: kernel command line is not easily customizable To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1044503/+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 1075108] [NEW] bzr branch fails on a ssh mount of remove ext4 fs with Error 95 Operation Not Supported
Public bug reported:
I'm using a VM, running 12.10, upgraded from 12.04.1 (server). Using a
bzr checkout dir on the VM and mounting that locally on the host with
SSH from /home/USER/.gvfs/home/VMUSER/work/maas, symlinked to
/home/USER/work/maas, then running bzr branch --switch on the host,
while in the symlink dir. I get an Error 95 Operation not supported. And
looking at the traceback in the log, it seems the fs reports erroneously
supporting fdatasync, but actually fails later when bzr tries to do it.
Running the same command on the VM locally works.
Traceback (most recent call last):
File .../bzrlib/commands.py, line 920, in exception_to_return_code
return the_callable(*args, **kwargs)
File .../bzrlib/commands.py, line 1131, in run_bzr
ret = run(*run_argv)
File .../bzrlib/commands.py, line 673, in run_argv_aliases
return self.run(**all_cmd_args)
File .../bzrlib/commands.py, line 695, in run
return self._operation.run_simple(*args, **kwargs)
File .../bzrlib/cleanup.py, line 136, in run_simple
self.cleanups, self.func, *args, **kwargs)
File .../bzrlib/cleanup.py, line 166, in _do_with_cleanups
result = func(*args, **kwargs)
File .../bzrlib/builtins.py, line 1493, in run
source_branch=br_from)
File .../bzrlib/bzrdir.py, line 366, in sprout
create_tree_if_local=create_tree_if_local)
File .../bzrlib/cleanup.py, line 132, in run
self.cleanups, self.func, self, *args, **kwargs)
File .../bzrlib/cleanup.py, line 166, in _do_with_cleanups
result = func(*args, **kwargs)
File .../bzrlib/bzrdir.py, line 416, in _sprout
result_repo.fetch(source_repository, fetch_spec=fetch_spec)
File .../bzrlib/vf_repository.py, line 1267, in fetch
find_ghosts=find_ghosts, fetch_spec=fetch_spec)
File .../bzrlib/decorators.py, line 218, in write_locked
result = unbound(self, *args, **kwargs)
File .../bzrlib/vf_repository.py, line 2584, in fetch
find_ghosts=find_ghosts)
File .../bzrlib/fetch.py, line 77, in __init__
self.__fetch()
File .../bzrlib/fetch.py, line 104, in __fetch
self._fetch_everything_for_search(search_result)
File .../bzrlib/fetch.py, line 132, in _fetch_everything_for_search
stream, from_format, [])
File .../bzrlib/vf_repository.py, line 2050, in insert_stream
hint = self.target_repo.commit_write_group()
File .../bzrlib/repository.py, line 633, in commit_write_group
result = self._commit_write_group()
File .../bzrlib/repofmt/pack_repo.py, line 1727, in _commit_write_group
hint = self._pack_collection._commit_write_group()
File .../bzrlib/repofmt/pack_repo.py, line 1612, in _commit_write_group
self._new_pack.finish()
File .../bzrlib/repofmt/pack_repo.py, line 496, in finish
want_fdatasync=self._pack_collection.config_stack.get('repository.fdatasync'))
File .../bzrlib/transport/__init__.py, line 237, in close
self.fdatasync()
File .../bzrlib/transport/__init__.py, line 268, in fdatasync
self.file_handle.flush()
IOError: [Errno 95] Operation not supported
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bzr 2.5.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
Uname: Linux 3.2.0-32-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu14
Architecture: amd64
Date: Mon Nov 5 11:16:01 2012
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
PackageArchitecture: all
SourcePackage: bzr
UpgradeStatus: Upgraded to precise on 2012-05-03 (186 days ago)
** Affects: bzr
Importance: High
Status: Confirmed
** Affects: bzr (Ubuntu)
Importance: High
Status: Confirmed
** Tags: amd64 apport-bug precise running-unity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1075108
Title:
bzr branch fails on a ssh mount of remove ext4 fs with Error 95
Operation Not Supported
To manage notifications about this bug go to:
https://bugs.launchpad.net/bzr/+bug/1075108/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075108] Re: bzr branch fails on a ssh mount of remote ext4 fs with Error 95 Operation Not Supported
** Summary changed: - bzr branch fails on a ssh mount of remove ext4 fs with Error 95 Operation Not Supported + bzr branch fails on a ssh mount of remote ext4 fs with Error 95 Operation Not Supported -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075108 Title: bzr branch fails on a ssh mount of remote ext4 fs with Error 95 Operation Not Supported To manage notifications about this bug go to: https://bugs.launchpad.net/bzr/+bug/1075108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1044503] Re: kernel command line is not easily customizable
** Branch linked: lp:~dimitern/maas/1.2-node-view-shows-kernel-params -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1044503 Title: kernel command line is not easily customizable To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1044503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994887] Re: Nodes listing does not support sorting
** Changed in: maas Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/994887 Title: Nodes listing does not support sorting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/994887/+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 994887] Re: Nodes listing does not support sorting
** Changed in: maas Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994887 Title: Nodes listing does not support sorting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/994887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994887] Re: Nodes listing does not support sorting
** Branch linked: lp:~dimitern/maas/bug-994887-alternate-nodes-list- sorting -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/994887 Title: Nodes listing does not support sorting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/994887/+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 994887] Re: Nodes listing does not support sorting
** Branch linked: lp:~dimitern/maas/bug-994887-alternate-nodes-list- sorting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994887 Title: Nodes listing does not support sorting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/994887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994887] Re: Nodes listing does not support sorting
** Changed in: maas Status: Triaged = In Progress ** Changed in: maas Assignee: (unassigned) = Dimiter Naydenov (dimitern) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/994887 Title: Nodes listing does not support sorting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/994887/+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 994887] Re: Nodes listing does not support sorting
** Branch linked: lp:~dimitern/maas/bug-994887-nodes-listing-does-not- support-sorting -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/994887 Title: Nodes listing does not support sorting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/994887/+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 994887] Re: Nodes listing does not support sorting
** Changed in: maas Status: Triaged = In Progress ** Changed in: maas Assignee: (unassigned) = Dimiter Naydenov (dimitern) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994887 Title: Nodes listing does not support sorting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/994887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994887] Re: Nodes listing does not support sorting
** Branch linked: lp:~dimitern/maas/bug-994887-nodes-listing-does-not- support-sorting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994887 Title: Nodes listing does not support sorting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/994887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
