[Touch-packages] [Bug 1777512] Re: key retrieval timeouts cause failures
** No longer affects: cdoqa-system-tests -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1777512 Title: key retrieval timeouts cause failures Status in juju: New Status in software-properties package in Ubuntu: New Bug description: We have been seeing keyserver timeouts causing failed runs at an increased rate recently (over the last 6+ months). Here is an example failure: [10.244.40.32] sudo: add-apt-repository -k https://keyserver.ubuntu.com/ --yes "ppa:curtin-dev/proposed" [10.244.40.32] out: Error: retrieving gpg key timed out. One idea is that this needs to be addressed by making the client (software-properties) more robust. We have an RT about this: https://portal.admin.canonical.com/C112309/ To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1777512/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777512] Re: key retrieval timeouts cause failures
** Tags added: cpe-onsite -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1777512 Title: key retrieval timeouts cause failures Status in CDO QA System Tests: Confirmed Status in software-properties package in Ubuntu: New Bug description: We have been seeing keyserver timeouts causing failed runs at an increased rate recently (over the last 6+ months). Here is an example failure: [10.244.40.32] sudo: add-apt-repository -k https://keyserver.ubuntu.com/ --yes "ppa:curtin-dev/proposed" [10.244.40.32] out: Error: retrieving gpg key timed out. One idea is that this needs to be addressed by making the client (software-properties) more robust. We have an RT about this: https://portal.admin.canonical.com/C112309/ To manage notifications about this bug go to: https://bugs.launchpad.net/cdoqa-system-tests/+bug/1777512/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777512] Re: rt #112309: keyserver.ubuntu.com increased failure rates over past few days
Sub'd ~field-high. ** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Summary changed: - rt #112309: keyserver.ubuntu.com increased failure rates over past few days + key retrieval timeouts cause failures ** Description changed: - keyserver failures more often than usual! not just our team experiencing - it - several other teams have reported it too. + We have been seeing keyserver timeouts causing failed runs at an + increased rate recently (over the last 6+ months). Here is an example + failure: + [10.244.40.32] sudo: add-apt-repository -k https://keyserver.ubuntu.com/ --yes "ppa:curtin-dev/proposed" + [10.244.40.32] out: Error: retrieving gpg key timed out. + + One idea is that this needs to be addressed by making the client + (software-properties) more robust. + + + We have an RT about this: https://portal.admin.canonical.com/C112309/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1777512 Title: key retrieval timeouts cause failures Status in CDO QA System Tests: Confirmed Status in software-properties package in Ubuntu: New Bug description: We have been seeing keyserver timeouts causing failed runs at an increased rate recently (over the last 6+ months). Here is an example failure: [10.244.40.32] sudo: add-apt-repository -k https://keyserver.ubuntu.com/ --yes "ppa:curtin-dev/proposed" [10.244.40.32] out: Error: retrieving gpg key timed out. One idea is that this needs to be addressed by making the client (software-properties) more robust. We have an RT about this: https://portal.admin.canonical.com/C112309/ To manage notifications about this bug go to: https://bugs.launchpad.net/cdoqa-system-tests/+bug/1777512/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792978] Re: initscript avahi-daemon, action "start" failed
1) Testing 2) No, it's in baremetal 3) Attached. 4) The machine was deployed with maas - it's a bionic cloud image. We then install/configure maas, run some tests, and remove maas via purge, and repeat. This shows up sometimes on deployments after the initial one - avahi-daemon, or at least its pid file, is left in /var/run/avahi-daemon from a previous run. There are LOTS of commands run. The important ones seem like: 1) apt-get -q install -y avahi-utils maas-region-api maas-dns 2) apt-get -q autoremove --purge maas-common -y 3) apt-get -q autoremove --purge avahi-daemon -y ... repeat until failure ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1792978/+attachment/5247981/+files/syslog ** Changed in: avahi (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1792978 Title: initscript avahi-daemon, action "start" failed Status in avahi package in Ubuntu: New Bug description: When installing maas-region-controller, avahi-deamon failed to install because it was it seemed to already be running. $ apt-get -q install -y maas-region-controller [1invoke-rc.d: initscript avahi-daemon, action "start" failed. [0;1;31m●[0m avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: [0;1;31mfailed[0m (Result: exit-code) since Sat 2018-09-15 19:42:29 UTC; 9ms ago Process: 22726 ExecStart=/usr/sbin/avahi-daemon -s [0;1;31m(code=exited, status=255)[0m Main PID: 22726 (code=exited, status=255) Sep 15 19:42:29 leafeon systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Sep 15 19:42:29 leafeon avahi-daemon[22726]: Daemon already running on PID 21868 Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Main process exit.../a[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;31mFailed to start Avahi mDNS/DNS-SD Stack.[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Unit entered fail...e.[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Failed with resul...'.[0m Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package avahi-daemon (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of avahi-utils: avahi-utils depends on avahi-daemon; however: Package avahi-daemon is not configured yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1792978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792978] Re: initscript avahi-daemon, action "start" failed
Subscribed to field-high as this is causing a lot of failures lately. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1792978 Title: initscript avahi-daemon, action "start" failed Status in avahi package in Ubuntu: New Bug description: When installing maas-region-controller, avahi-deamon failed to install because it was it seemed to already be running. $ apt-get -q install -y maas-region-controller [1invoke-rc.d: initscript avahi-daemon, action "start" failed. [0;1;31m●[0m avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: [0;1;31mfailed[0m (Result: exit-code) since Sat 2018-09-15 19:42:29 UTC; 9ms ago Process: 22726 ExecStart=/usr/sbin/avahi-daemon -s [0;1;31m(code=exited, status=255)[0m Main PID: 22726 (code=exited, status=255) Sep 15 19:42:29 leafeon systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Sep 15 19:42:29 leafeon avahi-daemon[22726]: Daemon already running on PID 21868 Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Main process exit.../a[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;31mFailed to start Avahi mDNS/DNS-SD Stack.[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Unit entered fail...e.[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Failed with resul...'.[0m Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package avahi-daemon (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of avahi-utils: avahi-utils depends on avahi-daemon; however: Package avahi-daemon is not configured yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1792978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792978] Re: initscript avahi-daemon, action "start" failed
In the previous package removal, we are seeing: [10.244.40.30] out: Purging configuration files for avahi-daemon (0.7-3.1ubuntu1.1) ... [10.244.40.30] out: rmdir: failed to remove '/var/run/avahi-daemon': Directory not empty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1792978 Title: initscript avahi-daemon, action "start" failed Status in avahi package in Ubuntu: New Bug description: When installing maas-region-controller, avahi-deamon failed to install because it was it seemed to already be running. $ apt-get -q install -y maas-region-controller [1invoke-rc.d: initscript avahi-daemon, action "start" failed. [0;1;31m●[0m avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled) Active: [0;1;31mfailed[0m (Result: exit-code) since Sat 2018-09-15 19:42:29 UTC; 9ms ago Process: 22726 ExecStart=/usr/sbin/avahi-daemon -s [0;1;31m(code=exited, status=255)[0m Main PID: 22726 (code=exited, status=255) Sep 15 19:42:29 leafeon systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Sep 15 19:42:29 leafeon avahi-daemon[22726]: Daemon already running on PID 21868 Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Main process exit.../a[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;31mFailed to start Avahi mDNS/DNS-SD Stack.[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Unit entered fail...e.[0m Sep 15 19:42:29 leafeon systemd[1]: [0;1;39mavahi-daemon.service: Failed with resul...'.[0m Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package avahi-daemon (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of avahi-utils: avahi-utils depends on avahi-daemon; however: Package avahi-daemon is not configured yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1792978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1802355] Re: systemd-resolve is missing nameservers until interface is bounced
I've configured our test runs to turn debug logging on for networkd and resolvd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1802355 Title: systemd-resolve is missing nameservers until interface is bounced Status in systemd package in Ubuntu: New Bug description: On some deployments of bionic, using maas and juju, my system ends up not being able to resolve hostnames. This happens inconsistently, it seems like a race. systemd-resolve is showing no nameservers https://pastebin.canonical.com/p/tyFw8TfSxk rharper had a look at one reproducing: 17:47 < rharper> jhobbs: ok, I'm not sure how it got into that state; but networkd showed all of the DNS servers as configured in it's setting (networkctl status) but resolved had none. I restarted resolvd, that did not help; then I downed one of the interfaces (ip link set down eth1.2734; ip link set eth1.2734 up) and networkd I guess poked resolved with the list of DNS servers and I can see /run/systemd/resovle/* and they are now 17:47 < rharper> populated with the configs here is the netplan: https://pastebin.ubuntu.com/p/8nGXgNmw9q/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1802355/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1802355] [NEW] systemd-resolve is missing nameservers until interface is bounced
Public bug reported: On some deployments of bionic, using maas and juju, my system ends up not being able to resolve hostnames. This happens inconsistently, it seems like a race. systemd-resolve is showing no nameservers https://pastebin.canonical.com/p/tyFw8TfSxk rharper had a look at one reproducing: 17:47 < rharper> jhobbs: ok, I'm not sure how it got into that state; but networkd showed all of the DNS servers as configured in it's setting (networkctl status) but resolved had none. I restarted resolvd, that did not help; then I downed one of the interfaces (ip link set down eth1.2734; ip link set eth1.2734 up) and networkd I guess poked resolved with the list of DNS servers and I can see /run/systemd/resovle/* and they are now 17:47 < rharper> populated with the configs here is the netplan: https://pastebin.ubuntu.com/p/8nGXgNmw9q/ ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: cdo-qa foundations-engine -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1802355 Title: systemd-resolve is missing nameservers until interface is bounced Status in systemd package in Ubuntu: New Bug description: On some deployments of bionic, using maas and juju, my system ends up not being able to resolve hostnames. This happens inconsistently, it seems like a race. systemd-resolve is showing no nameservers https://pastebin.canonical.com/p/tyFw8TfSxk rharper had a look at one reproducing: 17:47 < rharper> jhobbs: ok, I'm not sure how it got into that state; but networkd showed all of the DNS servers as configured in it's setting (networkctl status) but resolved had none. I restarted resolvd, that did not help; then I downed one of the interfaces (ip link set down eth1.2734; ip link set eth1.2734 up) and networkd I guess poked resolved with the list of DNS servers and I can see /run/systemd/resovle/* and they are now 17:47 < rharper> populated with the configs here is the netplan: https://pastebin.ubuntu.com/p/8nGXgNmw9q/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1802355/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution
Ok, that's not much of a workaround then :).
On Thu, Mar 8, 2018 at 3:52 AM, Dan Watkins
<daniel.watk...@canonical.com> wrote:
> On Wed, Mar 07, 2018 at 11:42:29PM -0000, Jason Hobbs wrote:
>> Is there a workaround for this? I can just rm /etc/resolv.conf and
>> create it with the contents I want, right?
>
> Yep, though you'll need to recreate it every so often as it will be
> replaced.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1750884
>
> Title:
> [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
> leads to no DNS resolution
>
> Status in cloud-init:
> New
> Status in MAAS:
> Triaged
> Status in nplan package in Ubuntu:
> New
> Status in systemd package in Ubuntu:
> New
>
> Bug description:
> When deploying Bionic, /etc/resolv.conf is not configured correctly,
> which leads to no DNS resolution. In the output below, you will see
> that netplan config is correctly to the 10.90.90.1 nameserver, but in
> resolv.conf that's a local address.
>
> Resolv.conf should really be configured to use the provided DNS
> server(s). That said, despite that fact, DNS resolution doesn't work
> with the local address.
>
> Bionic
> --
>
> ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
> # This file is generated from information provided by
> # the datasource. Changes to it will not persist across an instance.
> # To disable cloud-init's network configuration capabilities, write a file
> # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
> # network: {config: disabled}
> network:
> version: 2
> ethernets:
> enp0s25:
> match:
> macaddress: b8:ae:ed:7d:17:d2
> mtu: 1500
> nameservers:
> addresses:
> - 10.90.90.1
> search:
> - maaslab
> - maas
> set-name: enp0s25
> bridges:
> br0:
> addresses:
> - 10.90.90.3/24
> gateway4: 10.90.90.1
> interfaces:
> - enp0s25
> parameters:
> forward-delay: 15
> stp: false
> ubuntu@node01:~$ cat /etc/resolv.conf
> # This file is managed by man:systemd-resolved(8). Do not edit.
> #
> # 127.0.0.53 is the systemd-resolved stub resolver.
> # run "systemd-resolve --status" to see details about the actual
> nameservers.
> nameserver 127.0.0.53
>
> search maaslab maas
> ubuntu@node01:~$ ping google.com
> ping: google.com: Temporary failure in name resolution
>
> [...]
>
> ubuntu@node01:~$ sudo vim /etc/resolv.conf
> ubuntu@node01:~$ cat /etc/resolv.conf
> # This file is managed by man:systemd-resolved(8). Do not edit.
> #
> # 127.0.0.53 is the systemd-resolved stub resolver.
> # run "systemd-resolve --status" to see details about the actual
> nameservers.
> nameserver 10.90.90.1
>
> search maaslab maas
> ubuntu@node01:~$ ping google.com
> PING google.com (172.217.0.174) 56(84) bytes of data.
> 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52
> time=4.46 ms
> 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52
> time=4.38 ms
>
> =
> Xenial
> ==
>
> ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
> # This file is generated from information provided by
> # the datasource. Changes to it will not persist across an instance.
> # To disable cloud-init's network configuration capabilities, write a file
> # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
> # network: {config: disabled}
> auto lo
> iface lo inet loopback
> dns-nameservers 10.90.90.1
> dns-search maaslab maas
>
> auto enp0s25
> iface enp0s25 inet static
> address 10.90.90.162/24
> gateway 10.90.90.1
> mtu 1500
> ubuntu@node05:~$ cat /etc/resolv.conf
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by
> resolvconf(8)
> # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
> nameserver 10.90.90.1
> search maaslab maas
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution
Is there a workaround for this? I can just rm /etc/resolv.conf and
create it with the contents I want, right?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1750884
Title:
[2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
leads to no DNS resolution
Status in cloud-init:
New
Status in MAAS:
Triaged
Status in nplan package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
When deploying Bionic, /etc/resolv.conf is not configured correctly,
which leads to no DNS resolution. In the output below, you will see
that netplan config is correctly to the 10.90.90.1 nameserver, but in
resolv.conf that's a local address.
Resolv.conf should really be configured to use the provided DNS
server(s). That said, despite that fact, DNS resolution doesn't work
with the local address.
Bionic
--
ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
enp0s25:
match:
macaddress: b8:ae:ed:7d:17:d2
mtu: 1500
nameservers:
addresses:
- 10.90.90.1
search:
- maaslab
- maas
set-name: enp0s25
bridges:
br0:
addresses:
- 10.90.90.3/24
gateway4: 10.90.90.1
interfaces:
- enp0s25
parameters:
forward-delay: 15
stp: false
ubuntu@node01:~$ cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
search maaslab maas
ubuntu@node01:~$ ping google.com
ping: google.com: Temporary failure in name resolution
[...]
ubuntu@node01:~$ sudo vim /etc/resolv.conf
ubuntu@node01:~$ cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 10.90.90.1
search maaslab maas
ubuntu@node01:~$ ping google.com
PING google.com (172.217.0.174) 56(84) bytes of data.
64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52
time=4.46 ms
64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52
time=4.38 ms
=
Xenial
==
ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback
dns-nameservers 10.90.90.1
dns-search maaslab maas
auto enp0s25
iface enp0s25 inet static
address 10.90.90.162/24
gateway 10.90.90.1
mtu 1500
ubuntu@node05:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.90.90.1
search maaslab maas
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671274] Re: network interface doesn't come up after installation in VM
** Attachment added: "ipaddrdelifup.png" https://bugs.launchpad.net/maas/+bug/1671274/+attachment/4834700/+files/ipaddrdelifup.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671274 Title: network interface doesn't come up after installation in VM Status in cloud-init: New Status in curtin: New Status in MAAS: Invalid Status in systemd package in Ubuntu: New Bug description: I'm installing into a VM. It commissions fine, and deploy works up to the point where it reboots after curtin finishes, but when it comes back up after reboot, the network interface is not brought up. This means it never finishes deployment. Looking at syslog, there is a Failed to start Raise network interfaces error. You can see it in the attached screenshot. This VM worked fine up until a couple of months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1671274/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671274] Re: network interface doesn't come up after installation in VM
** Attachment added: "ifupvvv.png" https://bugs.launchpad.net/maas/+bug/1671274/+attachment/4834681/+files/ifupvvv.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671274 Title: network interface doesn't come up after installation in VM Status in cloud-init: New Status in curtin: New Status in MAAS: Invalid Status in systemd package in Ubuntu: New Bug description: I'm installing into a VM. It commissions fine, and deploy works up to the point where it reboots after curtin finishes, but when it comes back up after reboot, the network interface is not brought up. This means it never finishes deployment. Looking at syslog, there is a Failed to start Raise network interfaces error. You can see it in the attached screenshot. This VM worked fine up until a couple of months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1671274/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671274] Re: network interface doesn't come up after installation in VM
** Attachment added: "grepinfocloudinit.png" https://bugs.launchpad.net/maas/+bug/1671274/+attachment/4834682/+files/grepinfocloudinit.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671274 Title: network interface doesn't come up after installation in VM Status in cloud-init: New Status in curtin: New Status in MAAS: Invalid Status in systemd package in Ubuntu: New Bug description: I'm installing into a VM. It commissions fine, and deploy works up to the point where it reboots after curtin finishes, but when it comes back up after reboot, the network interface is not brought up. This means it never finishes deployment. Looking at syslog, there is a Failed to start Raise network interfaces error. You can see it in the attached screenshot. This VM worked fine up until a couple of months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1671274/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671274] Re: network interface doesn't come up after installation in VM
maas 2.2.0~beta3+bzr5787-0ubuntu1~16.04.1 python3-curtin 0.1.0~bzr460-0ubuntu1~16.04.1 curtin config: http://paste.ubuntu.com/24146369/ There is nothing in /etc/network/interfaces.d/*.cfg ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1671274 Title: network interface doesn't come up after installation in VM Status in cloud-init: New Status in curtin: New Status in MAAS: Invalid Status in systemd package in Ubuntu: New Bug description: I'm installing into a VM. It commissions fine, and deploy works up to the point where it reboots after curtin finishes, but when it comes back up after reboot, the network interface is not brought up. This means it never finishes deployment. Looking at syslog, there is a Failed to start Raise network interfaces error. You can see it in the attached screenshot. This VM worked fine up until a couple of months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1671274/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1410876] Re: Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a directory - Could not destroy snapshot %s - failed to allocate a pty; Insufficent privileges
This bug is hit very rarely - we deploy thousands of containers a day and
see it a few times a week. I don't have a way to reproduce it reliably
other than waiting to hit it in OIL.
On Fri, Aug 21, 2015 at 12:22 PM, Serge Hallyn 1410...@bugs.launchpad.net
wrote:
@jason-hobbs or @lmic,
can you provide a concise recipe for reproducing this in the
Description?
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1410876
Title:
Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a
directory - Could not destroy snapshot %s - failed to allocate a pty;
Insufficent privileges to control juju-trusty-lxc-template
Status in juju-core:
Invalid
Status in lxc:
Fix Released
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Trusty:
Fix Committed
Bug description:
This is for:
++ export OPENSTACK_RELEASE=juno
++ OPENSTACK_RELEASE=juno
++ export COMPUTE=nova-lxc
++ COMPUTE=nova-lxc
++ export UBUNTU_RELEASE=trusty
++ UBUNTU_RELEASE=trusty
Tool version is 1.20.14:
Launching instance
WARNING picked arbitrary tools {1.20.14-precise-amd64
https://streams.canonical.com/juju/tools/releases/juju-1.20.14-precise-amd64.tgz
932640702b5d9f08a312118a4afe330444308f92b7de350de9e547719f084bd9 8130412}
- /MAAS/api/1.0/nodes/node-5f9c14e6-ae98-11e3-b194-00163efc5068/
and agent-version on node says 1.20.13.
Juju-status.yaml:
'5':
agent-state: started
agent-version: 1.20.13
containers:
5/lxc/0:
agent-state-info: 'error executing lxc-clone: lxc_container:
utils.c: mkdir_p:
220 Not a directory - failed to create directory
''/run/lock/lxc//var/lib/lxc/juju-trusty-lxc-template/snaps'';
lxc_container: lxccontainer.c: do_snapshot_destroy: 3272 Could
not destroy
snapshot %s - failed to allocate a pty; Insufficent privileges
to control
juju-trusty-lxc-template'
instance-id: pending
series: trusty
5/lxc/1:
agent-state-info: cannot clone a running container
instance-id: pending
series: trusty
dns-name: apsaras.oil
hardware: arch=amd64 cpu-cores=4 mem=32768M
tags=hw-ok,oil-slave-1,hardware-dell-poweredge-R210
instance-id:
/MAAS/api/1.0/nodes/node-5f9c14e6-ae98-11e3-b194-00163efc5068/
series: trusty
and from log:
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
apiserver.go:150 - [7C] unit-swift-storage-1
{RequestId:42,Type:Uniter,Request:CharmURL,Params:{Entities:[{Tag:service-swift-storage}]}}
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
apiserver.go:157 - [7C] unit-swift-storage-1 383.812us
{RequestId:42,Response:{Results:[{Error:null,Result:local:trusty/swift-storage-90,Ok:false}]}}
Uniter[].CharmURL
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
apiserver.go:150 - [7C] unit-swift-storage-1
{RequestId:43,Type:Uniter,Request:CharmArchiveSha256,Params:{URLs:[{URL:local:trusty/swift-storage-90}]}}
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
apiserver.go:157 - [7C] unit-swift-storage-1 777.029us
{RequestId:43,Response:{Results:[{Error:null,Result:b8aac93898c3cc661c0804613e5cce79a402fbe596400e8e80e8a3a1bb16c577}]}}
Uniter[].CharmArchiveSha256
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
apiserver.go:150 - [61] machine-2
{RequestId:57,Type:Provisioner,Request:SetStatus,Params:{Entities:[{Tag:machine-2-lxc-0,Status:error,Info:error
executing \lxc-clone\: lxc_container: utils.c: mkdir_p: 220 Not a
directory - failed to create directory
'/run/lock/lxc//var/lib/lxc/juju-trusty-lxc-template/snaps'; lxc_container:
lxccontainer.c: do_snapshot_destroy: 3272 Could not destroy snapshot %s -
failed to allocate a pty; Insufficent privileges to control
juju-trusty-lxc-template,Data:null}]}}
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver
apiserver.go:150 - [7C] unit-swift-storage-1
{RequestId:44,Type:Uniter,Request:SetCharmURL,Params:{Entities:[{Tag:unit-swift-storage-1,CharmURL:local:trusty/swift-storage-90}]}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1410876/+subscriptions
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1410876
Title:
Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a
directory - Could not destroy snapshot %s - failed to allocate a pty;
Insufficent privileges to control juju-trusty-lxc-template
Status in juju-core:
Invalid
Status in lxc:
Fix Released
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Trusty:
Fix Committed
Bug description:
This is for:
++ export OPENSTACK_RELEASE=juno
++ OPENSTACK_RELEASE=juno
++ export
[Touch-packages] [Bug 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory
Steve's suggested work around: # dpkg-divert --rename --add /sbin/telinit # cat /sbin/telinit #!/bin/sh exit 0 ^D # apt-get install [...] # dpkg-divert --rename --remove /sbin/telinit -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1464442 Title: installing or upgrading libc6 in Trusty removes all content from /tmp directory Status in linux package in Ubuntu: Invalid Status in upstart package in Ubuntu: Triaged Bug description: We are seeing an issue with installation of dkms package during a curtin installation which ends up with /tmp directory being wiped clean. This is very bad for curtin as it saves critical installation files in /tmp. It turns out that it's the of upgrading libc6, which is triggered as a result of installing dependencies, that removes content of /tmp. For example, installation of gcc results in the same result since it ends up with libc6 being upgraded. The only way that this won't be recreated is if the latest libc6 is already installed. This problem does not exist in precise. It can also be recreated by installing the .deb file for any version in trusty including 2.17. ubuntu@host:~$ ls /tmp tmpHHbRkP ubuntu@sirrush:~$ sudo apt-get install libc6 sudo: unable to resolve host sirrush Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libc-dev-bin libc6-dev Suggested packages: glibc-doc Recommended packages: manpages-dev The following packages will be upgraded: libc-dev-bin libc6 libc6-dev 3 upgraded, 0 newly installed, 0 to remove and 148 not upgraded. Need to get 6,714 kB of archives. After this operation, 6,144 B disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6-dev amd64 2.19-0ubuntu6.6 [1,910 kB] Get:2 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc-dev-bin amd64 2.19-0ubuntu6.6 [68.9 kB] Get:3 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6 amd64 2.19-0ubuntu6.6 [4,735 kB] Fetched 6,714 kB in 0s (18.5 MB/s) Preconfiguring packages ... (Reading database ... 57798 files and directories currently installed.) Preparing to unpack .../libc6-dev_2.19-0ubuntu6.6_amd64.deb ... Unpacking libc6-dev:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ... Preparing to unpack .../libc-dev-bin_2.19-0ubuntu6.6_amd64.deb ... Unpacking libc-dev-bin (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ... Preparing to unpack .../libc6_2.19-0ubuntu6.6_amd64.deb ... Unpacking libc6:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ... Processing triggers for man-db (2.6.7.1-1) ... Setting up libc6:amd64 (2.19-0ubuntu6.6) ... Setting up libc-dev-bin (2.19-0ubuntu6.6) ... Setting up libc6-dev:amd64 (2.19-0ubuntu6.6) ... Processing triggers for libc-bin (2.19-0ubuntu6.3) ... ubuntu@host:~$ ls /tmp ubuntu@host:~$ This is very recreatable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349412] [NEW] Sound indicator missing
Public bug reported: The sound indicator icon is missing from the bar on the top of my screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Jul 28 14:09:52 2014 InstallationDate: Installed on 2014-06-29 (28 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1349412 Title: Sound indicator missing Status in “unity” package in Ubuntu: New Bug description: The sound indicator icon is missing from the bar on the top of my screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Jul 28 14:09:52 2014 InstallationDate: Installed on 2014-06-29 (28 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349412] Re: Sound indicator missing
blah - the show volume in menu bar checkbox was unchecked. ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1349412 Title: Sound indicator missing Status in “unity” package in Ubuntu: Invalid Bug description: The sound indicator icon is missing from the bar on the top of my screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Jul 28 14:09:52 2014 InstallationDate: Installed on 2014-06-29 (28 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
