Re: Friday bug triage
On Fri, Jan 7, 2022 at 5:10 PM Bryce Harrington wrote: > > On Fri, Jan 07, 2022 at 08:34:57PM +0530, Utkarsh Gupta wrote: > > Hello, > > > > On Fri, Jan 7, 2022 at 7:56 PM Utkarsh Gupta > > wrote: > > > LP: #1954854 - (Incomplete) [bind9] - bind > > > 9.16.1-ubuntu on ubuntu 20.04 randomly > > > exits with [...] > > > > > > The bug reporter got back with some logs > > > and files collected via apport. Since the > > > bug is not easily reproducible, I am not quite > > > sure what's the best way forward. That said, > > > me/Paride are looking into it. > > > > Here's an update: we couldn't find anything worthwhile from the > > upstream tracker or changelog or anything and neither of us have > > enough experience with crash files. > > Here's a paint-by-numbers way to get stacktraces from .crash files: > > 0. Enable debug symbols. Various ways to do this, one way is to append > ddebs to your apt sources: > > $ echo "deb http://ddebs.ubuntu.com focal main restricted universe > multiverse" | sudo tee -a /etc/apt/sources.list > $ echo "deb http://ddebs.ubuntu.com focal-updates main restricted > universe multiverse" | sudo tee -a /etc/apt/sources.list > > $ sudo apt install ubuntu-dbgsym-keyring > $ sudo apt update > > 1. Install package with debug symbols > > $ sudo apt install bind9 bind9*-dbgsym Note this (using ddebs repo) only works if the crash resulted with the latest version of all associated packages; in a normal support situation where at least some package versions (that are relevant to what caused the crash, e.g. application package and dep libs) are not the latest, the ddebs repo unfortunately isn't useful since it only provides the dbgsyms for the latest package versions. It's frequently more helpful to simply use pull-lp-ddebs to get the specific dbgsyms for the package versions that generated the crash file. Of course, hopefully eventually someone (*ahem* sergiodj) will get an Ubuntu debuginfod server set up, which would allow direct access to the appropriate dbgsyms, but that's not available yet. > > Often there are also secondary libs or deps with more syms we'll > need. This examines the binary for other possible dbgsym's: > > $ sudo apt install debian-goodies > $ sudo apt install $(find-dbgsym-packages /usr/sbin/named 2>/dev/null) > > The following NEW packages will be installed: > libcap2-dbgsym libcom-err2-dbgsym libgcc-s1-dbgsym libicu67-dbgsym > libjson-c5-dbgsym libkeyutils1-dbgsym > libkrb5-dbg liblmdb0-dbgsym liblzma5-dbgsym libmaxminddb0-dbgsym > libxml2-dbgsym zlib1g-dbgsym > > > 2. Download the .crash file to a tmp directory > > $ mkdir /tmp/bind9-crash > $ cd /tmp/bind9-crash > $ wget > https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1954854/+attachment/5551855/+files/_usr_sbin_named.114.crash > > 3. Register the package with the crash file > > $ cat <(echo "Package: bind9") _usr_sbin_named.114.crash > > bind9_named.114.crash > > Apport-retrace complains if the package isn't specified, but apport > hooks don't insert it, so you have to do it manually. ¯\_(ツ)_/¯ > > 4. Doublecheck that your installed version matches the reporter's > version exactly: > > $ apt-cache policy bind9 | grep '^ Installed' > Installed: 1:9.16.1-0ubuntu2.9 > > Unfortunately the .crash file doesn't include the version number, > but the LP bug report will show it: > > Package: bind9 1:9.16.1-0ubuntu2.9 > > 5. Retrace symbols > > $ sudo apt-get install apport-retrace > $ apport-retrace bind9_named.114.crash > > The above command inserted an empty 'separator: ' line into the crash > file, which apport-unpack will choke on, so delete that line: > > $ sed -i '/^separator: *$/d' ./bind9_named.114.crash > > > 6. Unpack crash > > $ apport-unpack bind9_named.114.crash crash-114 > > The 'crash-114/' subdirectory will now include a ThreadStacktrace file > that hopefully(!) should have a usable backtrace. This one looks > great but the full stacktrace is rather TMI. > > $ wc -l crash-114/ThreadStacktrace > 415 crash-114/ThreadStacktrace > > > 7. (Advanced) GDB > > $ apt-get source bind9 > $ cd bind9-9.16.1/ > > $ apport-retrace --gdb /tmp/bind9-crash/bind9_named.114.crash > > This will give you an interactive gdb session on the reporter's > coredump. For example, with this particular crash, we can get a > simple backtrace: > > (gdb) bt > #0 isc__nm_tcp_send (handle=0x7eff7522dbb0, region=0x7eff7d39a9b8, > cb=0x7eff887675a0 , > cbarg=0x7eff7d39a9a8) at tcp.c:852 > #1 0x7eff88a2e707 in client_sendpkg (client=client@entry=0x7eff754c31b0, > buffer=, > buffer=) at client.c:331 > #2 0x7eff88a2ffe9 in ns_client_send (client=client@entry=0x7eff754c31b0) > at client.c:592 > #3 0x7eff88a3e9b0 in query_send (client=0x7eff754c31b0) at query.c:552 > #4 0x7eff88a469a7 in ns_query_done (qctx=qctx@en
Re: Wednesday Triage Report (2021-07-14)
On Wed, Jul 14, 2021 at 11:48 AM Sergio Durigan Junior wrote: > > ustriage found 9 bugs. Nothing worthwhile to report; everything is > being properly handled by the team. Could you expand on this a bit? It's not exactly clear what it means. For example from the links on the server team wiki page (https://wiki.ubuntu.com/ServerTeam) I see the 'Top 20 Bugs' (which are all the ones tagged 'server-next' right?) which includes bugs where there's been no update in over a year (e.g. LP:#1860997, LP:#1872145) and others where the bug appears to be already fixed (e.g. LP:#1916485). The full list of bugs subscribed by ~ubuntu-server is larger than seems useful, currently 815, so is that list being used for active work? If so, can you go into some detail on what work is done to bugs in that list? > > -- > Sergio > GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Tuesday bug triage report
On Tue, Jun 22, 2021 at 8:34 AM Lucas Kanashiro wrote: > > Bugs last updated on 2021-06-21 (Monday) > Date range identified as: "Tuesday triage" > Found 12 bugs > > There are active people working on almost all bugs, just one comment below: > > https://pad.lv/1933161 - (New)[ubuntu-advantage-tools] - Errors > on enabling livepatch > -> I believe this bug is missing information to actually be reproducible, but > I decided to not touch it since I am not aware of what's happening in the > ua-tools land. I'll leave this to someone from the table-flip squad. what's the "table-flip squad"? > > --- > Bugs tagged 'server-next' and not touched in 60 days > Found 0 bugs > > --- > Bugs in backlog and not touched in 180 days > Found 0 bugs > > Lucas Kanashiro. > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Bug Triage Monday 22nd Feb 2021
On Tue, Feb 23, 2021 at 7:12 AM Lucas Kanashiro wrote: > > Hi, > > On Tue, Feb 23, 2021 at 4:41 AM Christian Ehrhardt > wrote: >> >> >> https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1915828 >> An issue with pacemaker / libqb not releasing the cluster. >> Lucas is already subscribed I also added the team subscription now. >> @Lucas should this be server-next tagged and assigned to you? > > > I think so, this bug needs some further investigation. However, I am not sure > what is the exact meaning of the "sts" tag, is someone from the STS team > working on it? Or are they just tracking changes on the bug report? Yes, this is owned by dgadomski and slashd > > Lucas Kanashiro. > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: ubuntu-helpers: New script "enable-proposed"
On Wed, Jul 22, 2020 at 3:39 PM Bryce Harrington wrote: > > On Wed, Jul 22, 2020 at 08:57:05AM -0500, Simon Quigley wrote: > > Hello, > > > > On 7/22/20 8:22 AM, Dan Streetman wrote: > > > Since it's related to this topic, the add-apt-repository in this ppa > > > has support for adding/enabling deb-src and arbitrary pockets as well > > > as private ppas and more: > > > https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/add-apt-repository > > If that makes it easy to enable -proposed, that would indeed be very > helpful. yeah just like $ sudo add-apt-repository -p proposed > > Googling "how to enable -proposed from CLI" returns too many results > that have people either hand edit sources.list or simply append > hand-written deb strings. If those docs can give a simple-to-run > invocation of add-apt-repository it would help eliminate user error and > confusion. > > > > I need to find some time to push the changes into the upstream repo. > > > https://code.launchpad.net/~ubuntu-support-team/software-properties/+git/software-properties/+ref/devel > > > > Merged, here you go: > > https://launchpad.net/ubuntu/+source/software-properties/0.99.0 > > > > (We're still a little bit away from Feature Freeze and we just released > > an LTS. Now is the time to test major updates to software.) > > > > On 7/21/20 8:37 PM, Bryce Harrington wrote:> I've also added an > > 'enable-proposed' script, similar to enable-debsrc, > > > which adds DIST-proposed entries (deb and deb-src) for components > > > currently enabled. IOW, if you don't have > > > universe/restricted/multiverse components enabled for anything, it won't > > > add them for -proposed, but if you do, it will. > > > > > > The script also strives to use the same archive URI you are using for > > > the main component, so if you're using a mirror it will also pull > > > -proposed from that mirror too. > > > > > > https://git.launchpad.net/~ubuntu-server/ubuntu-helpers/tree/bryce/enable-proposed > > > > Thanks for your work here! How much of this is now in Groovy with the > > above changes, and what can be merged into software-properties? > > Not sure, but I did notice a couple things I wished were in the API. > > First, a way to easily fuzzy search for a given entry, such as the one > for the main component. I ended up just iterating through all the > components and examining their props, but it feels a bit brittle. A > sp.sourceslist.search() or similar would have given a cleaner solution. I added a list option, e.g.: $ add-apt-repository -L deb http://archive.ubuntu.com/ubuntu focal universe restricted multiverse main deb http://archive.ubuntu.com/ubuntu focal-updates universe restricted multiverse main deb http://archive.ubuntu.com/ubuntu focal-backports universe restricted multiverse main deb http://security.ubuntu.com/ubuntu focal-security universe restricted multiverse main deb http://ppa.launchpad.net/ubuntu-support-team/add-apt-repository/ubuntu focal main it filters out deb-src lines by default but you can include them with: $ add-apt-repository -Ls deb http://archive.ubuntu.com/ubuntu focal multiverse main universe restricted deb-src http://archive.ubuntu.com/ubuntu focal multiverse main universe restricted deb http://archive.ubuntu.com/ubuntu focal-updates multiverse main universe restricted deb-src http://archive.ubuntu.com/ubuntu focal-updates multiverse main universe restricted deb http://archive.ubuntu.com/ubuntu focal-backports multiverse main universe restricted deb-src http://archive.ubuntu.com/ubuntu focal-backports multiverse main universe restricted deb-src http://archive.canonical.com/ubuntu focal partner deb http://security.ubuntu.com/ubuntu focal-security multiverse main universe restricted deb-src http://security.ubuntu.com/ubuntu focal-security multiverse main universe restricted deb http://ppa.launchpad.net/ubuntu-support-team/add-apt-repository/ubuntu focal main deb-src http://ppa.launchpad.net/ubuntu-support-team/add-apt-repository/ubuntu focal main > > Second, I'm not sure whether it's expected that users should access the > internals of entries (e.g. entry.dist, entry.file). If so, the docs > don't document them and would make them more convenient to use. If not, > then getter/setter routines or similar might be appropriate. > > > Thanks Dan and Bryce, this definitely makes things a lot easier. > > Hey and thanks for maintaining SoftwareProperties. Going into this task > I was anticipating needing to parse sources.list myself, so in examining > add-apt-repository's code was pleased to discover SoftwareProperties and &
Re: ubuntu-helpers: New script "enable-proposed"
Since it's related to this topic, the add-apt-repository in this ppa has support for adding/enabling deb-src and arbitrary pockets as well as private ppas and more: https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/add-apt-repository I need to find some time to push the changes into the upstream repo. https://code.launchpad.net/~ubuntu-support-team/software-properties/+git/software-properties/+ref/devel On Wed, Jul 22, 2020 at 8:38 AM Bryce Harrington wrote: > > I've also added an 'enable-proposed' script, similar to enable-debsrc, > which adds DIST-proposed entries (deb and deb-src) for components > currently enabled. IOW, if you don't have > universe/restricted/multiverse components enabled for anything, it won't > add them for -proposed, but if you do, it will. > > The script also strives to use the same archive URI you are using for > the main component, so if you're using a mirror it will also pull > -proposed from that mirror too. > > https://git.launchpad.net/~ubuntu-server/ubuntu-helpers/tree/bryce/enable-proposed > > Bryce > > On Tue, Jul 21, 2020 at 04:20:58PM -0700, Bryce Harrington wrote: > > I've added a simple little script to enable deb-src lines in > > sources.list to ubuntu-helpers: > > > > > > https://git.launchpad.net/~ubuntu-server/ubuntu-helpers/tree/bryce/enable-debsrc > > > > This script modifies your /etc/apt/sources.list and > > /etc/apt/sources.list.d/* files, and for each enabled deb line, it > > uncomments the corresponding deb-src line. > > > > In case anyone else finds it useful, there it is. > > > > Bryce > > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Monday Triage (2020-06-15) - Did by accident @paride, sorry
On Mon, Jun 15, 2020 at 3:08 AM Rafael David Tinoco wrote: > > Bugs last updated between 2020-06-12 (Friday) and 2020-06-14 (Sunday) > inclusive > Date range identified as: "Monday triage" > Found 20 bugs > > https://pad.lv/1817955 - (Confirmed) [krb5] - Getting > new DN is out of the realm subtree error on adding principal > > > subscribed ebarretto (author of the security fix that caused the regression) > > subscribed ubuntu-server > > triaged for trusty, fix released for groovy > > https://pad.lv/1882527 - (Confirmed) [mysql-8.0] - mysql > timeoutsec results in killing mysql process > > > triaged for all supported releases > > tagged as server-next and high prio for groovy > > it shall be an easy fix/sru: disable TimeoutSec from systemd service unit > > (upstreamed already) > > https://pad.lv/1882791 - (Confirmed) [mysql-8.0] - package > mysql-server-8.0 8.0.20-0ubuntu0.20.04.1 failed to install/upgrade: > installed mysql-server-8.0 package post-installation script subprocess > returned error exit status 1 > > > incomplete (upgrade) > > could not stop previous instance issue (very frequent) > > https://pad.lv/1883090 - (Confirmed) [apache2]- package > apache2 2.4.41-4ubuntu3 failed to install/upgrade: el subproceso > instalado paquete apache2 script post-installation devolvió el código > de salida de error 1 > > > similar upgrade issues have been seen with apache2 and its mods > > asked @bryce if he hadn't worked on this (iirc) recently > > it seems that deferred pkg configuration (after deps) does not work > > https://pad.lv/1883307 - (New) [mysql-8.0] - package > mysql-server-8.0 (not installed) failed to install/upgrade: el > subproceso nuevo paquete mysql-server-8.0 script pre-installation > devolvió el código de salida de error 1 > > > incomplete, weird error about /etc/mysql/FROZEN > > asked more information > > https://pad.lv/1883320 - (New) [sosreport] - [kvm] > change check_enabled to /dev/kvm > > > sosreport and @slashd is on it, nothing on our side > > https://pad.lv/1883398 - (New) [qemu] - USB > serial device passtrough causes qemu to segfault and kill the VM > > > asked for detailed reproducer or core file > > subscribed ubuntu-virt and @cpaelzer > > stated as incomplete until then > > https://pad.lv/1883413 - (New) [bind9] - bind9 > /var/cache/bind rights not set properly > > > not a bug, end user wanted to document his finding more than anything > > flagged as opinion and subscribed ubuntu-server > > --- > Bugs tagged 'server-next' and not touched in 60 days > Found 2 bugs > > https://pad.lv/1785383 - (Triaged)[dnsmasq]- missing > EDNS0 record confuses systemd-resolved > also: - (New)[systemd]- missing > EDNS0 record confuses systemd-resolved > > > @ddstreet seems to have caught this to himself, cc'ing him yes, this is an unfortunate loong running bug that is due to a patch to systemd that we carry, that isn't upstream. It will require me (or someone) being able to go to a Starbucks to test with their wifi, so I (or someone) can create a proper patch to workaround their broken wifi captive portal, that we can then get merged upstream and drop the problematic patch we carry. That's been made difficult by COVID-19, of course, but I do still want to try to get to this sometime this summer. > > --- > Bugs in backlog and not touched in 180 days > Found 0 bugs -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Triage report for 2020-05-04 (Tuesday triage)
On Tue, May 5, 2020 at 6:28 PM Lucas Kanashiro wrote: > > == Migration == > > The regressions below seem real issues, they were already re-triggered and > they failed: > > * php-parser/4.2.2-2 regression in armhf is blocking php7.4/7.4.3-4ubuntu2 > * chrony/3.5-6ubuntu6 regression in armhf is blocking libcap/1.9.1-4 > > I did not have too much time to investigate the issues above. And most of the > other packages listed in our page are waiting for builds or are candidates to > migrate. > > == Triage == > Bugs last updated on 2020-05-04 (Monday) > Date range identified as: "Tuesday triage" > Found 12 bugs > > Many bugs have been worked on by the team. > Some notes below: > > LP: #1869848 - (Confirmed) [libvirt]- libvirtd > virNetSocketReadWire:1811 : End of file while reading data: Input/output error > * Subscribed ubuntu-server. It has affected some users but I was not able to > confirm the bug be > cause they are using a version not in the main archive, maybe in some cloud > related PPA? I think Christian or Rafael should take a look at it. > > LP: #1876537 - (Incomplete) [dovecot]- dovecot eating mail > indexes /var/dovecot-index/user > * The reporter mentioned it was an issue on their side, not a bug, so I > marked it as Invalid. > > LP: #1876781 - (New)[vlan] - ifupdown scripts have no > execute rights! > * Marked as Triaged and subscribed ubuntu-server. The scenario described in > the bug report is true, and we should check this out. wow, it's been like that since disco...I'm not really sure how I screwed that up, but I definitely did...I'll do an upload for that. Oops. > > --- > Bugs tagged 'server-next' and not touched in 60 days > Found 2 bugs > LP: #1723350 - (Confirmed) [sssd] - sssd offline on boot, > stays offline forever > * Andreas, I think you want to revisit this bug when you have some time. > > LP: #1865501 - (Triaged)[libpcap]- libpcap-dev and > derivatives missing libpcap.pc > * Bryce, you provided a patch for this bug for Disco, are you planning to > keep working on this? > > --- > Bugs in backlog and not touched in 180 days > Found 0 bugs > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: git-ubuntu commands to drop for 1.0?
On Thu, Apr 9, 2020 at 5:29 PM Bryce Harrington wrote: > > git-ubuntu has proof-of-concepted a number of subcommands during its > initial development. As we're nearing the 1.0 release, we'd like to > narrow our supported featureset to the ones in heaviest use by users. > > Ones that are more challenging to support or that are less heavily used, > will be removed from the codebase, allowing us to focus on strengthening > the remaining set. > > The UNIX philosophy is "Do one thing, and do it well", and for > git-ubuntu the principle theme is the management of the repository > itself, as opposed to the wider packaging workflow for which there are > other tools available. > > Here's our first take at what we think might stay vs. go: > > * git ubuntu clone [Keep] this is the only command I've ever used, actually. I think that's probably largely due to: $ git ubuntu --help No manual entry for git-ubuntu I know there are issues around being able to provide man pages from a snap, but man pages really are helpful... Also, I also know that 'git-ubuntu --help' (or 'git ubuntu -h') does produce some help output, but that output also refers to man pages that don't (seem to) exist, e.g.: "For more information on the commands see: $ git ubuntu --help $ man git-ubuntu- More information about git ubuntu itself is available at: $ man git-ubuntu " In any case, removing any of the subcommands below wouldn't impact me personally. Thanks! > * git ubuntu export-orig[Keep] > * git ubuntu import [Keep] > * git ubuntu merge [Keep] > * git ubuntu queue [Keep] > * git ubuntu remote [Keep] > * git ubuntu submit [Keep] > * git ubuntu tag[Keep] > > * git ubuntu import-local [Remove] > - We suspect this is mostly unused? > > * git ubuntu import-ppa [Remove] > - We suspect this is mostly unused? > > * git ubunt lint[Remove] > - We suspect this is mostly unused? > - Has been useful in the past, might be candidate to return later > > * git ubuntu build [Remove] > - It's a good idea, definitely a candidate to return one day, but > the code for this is cumbersome, has no test cases, and constrains > our internal refactoring. There are numerous bugs reported about > it, and there are numerous alternate build approaches users can > use. > > * git ubuntu review [Remove] > - Another good idea, but was highly experimental and needs more > implementation work to be actually useful. > > > What do you think? If you have strong reasons to keep any of the > above, please explain the justifications for consideration. > > Otherwise, in the next week or two I plan to start proposing MPs to drop > the subcommands, with the goal of finishing their removal by the 1.0 > release. > > Post-1.0, new CLI subcommands will be introduced (and wanted old ones > re-introduced), using some standard engineering processes. E.g. a spec > outlining the feature, a prototype done in a branch, and corresponding > test cases. > > Bryce > > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Proposed-migration and Triage report for Tuesday, March 31, 2020
On Tue, Mar 31, 2020 at 10:44 AM Lucas Kanashiro wrote: > > == Migration == > No packages in migration more than a day > > == Triage == > Bugs last updated on 2020-03-30 (Monday) > Date range identified as: "Tuesday triage" > Found 35 bugs > > Most of the bugs have been worked on by the team. > Notes on remainder: > > LP: #1866385 - *+(New) [kronosnet] - [FFe][focal] kronosnet > need fixes from just released upstream version > * Rafael requested a FFe, so now it is up to the release team > > LP: #1869649 - *+(New) [gpsd] - provide a skeleton for > /etc/device-hook > * Triaged it as a wishlist bug for the next cycle > > LP: #1641238 - *(New) [apache2]- as a reverse proxy, a 100 > continue response is sent prematurely when a request contains expects: > 100-continue > * A new issue was brought up by another user in the linked upstream bug, I > asked them to file a new Ubuntu bug if the issue is pertinent. > > LP: #1673255 - (New)[drbd-utils] - drbd udev rule with > multiple symlinks fails > * I did nothing. It is not clear to me what to do here, the > sts-sponsor-volunteer tag was added. Please let me know if I need to do > something. you can ignore it. > > --- > Bugs tagged 'server-next' and not touched in 60 days > Found 0 bugs > > --- > Bugs in backlog and not touched in 180 days > Found 0 bugs > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Merge Opportunities Report - 2019-12-09
On Mon, Dec 9, 2019 at 8:08 AM Bryce Harrington wrote: > > New Version in Debian Unstable > -- > high clamav0.102.1+dfsg-1 > 0.101.4+dfsg-1ubuntu1 > high nut 2.7.4-10 2.7.4-9ubuntu1 > high vlan 2.0.52.0.4ubuntu1 vlan is only needed by ifupdown; since that's being removed from focal (right?), vlan should probably be removed too > low autofs5.1.6-1 5.1.5-1ubuntu1 > low ebtables 2.0.10.4+snapshot20181205-3 > 2.0.10.4+snapshot20181205-1ubuntu1 > low exim4 4.93~RC7-1 4.93~RC2-1ubuntu1 > low freeipmi 1.6.4-3 1.6.3-1.1ubuntu2 > low ipxe 1.0.0+git-20190125.36a4c85-1 > 1.0.0+git-20190109.133f4c4-0ubuntu2 > low libvirt 5.6.0-3 5.4.0-0ubuntu5 > low lxc 1:3.1.0+really3.0.4-23.0.4-0ubuntu2 > low net-snmp 5.8+dfsg-2 > 5.7.3+dfsg-5ubuntu6 > low nss 2:3.47.1-1 2:3.47-1ubuntu2 > low php7.37.3.12-1 7.3.11-0ubuntu1 > low qemu 1:4.1-3 > 1:4.0+dfsg-0ubuntu10 > low resource-agents 1:4.4.0-21:4.4.0-1ubuntu1 > low runc 1.0.0~rc9+dfsg1-1 > 1.0.0~rc8+git20190923.3e425f80-0ubuntu1 > low spice-protocol0.14.0-1 0.14.0-0ubuntu1 > low xen 4.11.1+92-g6c33308a8d-2 4.9.2-0ubuntu2 > > > New Version in Experimental > -- > low dpdk 19.11-1 18.11.5-1 > low freeradius3.0.20+dfsg-2 3.0.20+dfsg-1 > low haproxy 2.1.0-2 2.0.10-1ubuntu1 > low ipmctl02.00.00.3658+ds-1 > 02.00.00.3474+really01.00.00.3481-1 > low ruby-defaults 1:2.5.7~0 1:2.5.2 > > > New Upstream not in Debian > -- > high logwatch 7.5.2/logwatch-7.5.2 7.5.0-2ubuntu1 > high multipath-tools 0.8.2 0.7.9-3ubuntu6 > high openipmi 2.0.272.0.27-0ubuntu1 > high pacemaker 2.0.2 2.0.1-5ubuntu1 > (Low priority upstream releases skipped) > > high == Packages seeded for Ubuntu-Server > low == Non-seeded packages Server team is subscribed to > > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Triage/Migration report of the day
On Sat, Sep 28, 2019 at 1:58 PM Christian Ehrhardt wrote: > > On Fri, Sep 27, 2019 at 1:32 PM Dan Streetman > wrote: > > > > On Fri, Sep 27, 2019 at 1:58 AM Christian Ehrhardt > > wrote: > > > > > > Triage > > > - 16 bugs to triage, interesting ones: > > > - Mostly activity from us => no-action items > > > - 1841936 is interesting as a planned no-change-rebuild against > > > openssl1.1.1 not only > > > picked up the expected TLSv1.3 but also increased DH key sizes. > > > - No new bugs added to our work queues (all that need action are > > > already on our queues) > > > > > > Proposed migration > > > - libvirt test is still broken by new systemd 243 > > >=> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1844879 > > > > hasn't systemd been reverted back to 242 in Eoan? > > Yes, but we have to fix it in systemd and/or libvirtd for the 20.04 scope. > So the bug still exists, it just doesn't matter for Eoan and current > proposed migration anymore. that was my only confusion, that it was listed as a work item for current (Eoan) proposed migration. > > > > - No new issues since yesterday (again - thanks beta freeze) > > > > > > -- > > > Christian Ehrhardt > > > Software Engineer, Ubuntu Server > > > Canonical Ltd > > > > > > -- > > > ubuntu-server mailing list > > > ubuntu-server@lists.ubuntu.com > > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > > > More info: https://wiki.ubuntu.com/ServerTeam > > > > -- > Christian Ehrhardt > Software Engineer, Ubuntu Server > Canonical Ltd -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Ubuntu Server Guide - VCS docs
On Fri, Sep 27, 2019 at 5:47 PM Joshua Powers wrote: > > Hi Dan, > > On 9/27/19 2:41 PM, Dan Streetman wrote: > > So, the "commercial" and "community" support links go to the same page > > - UA support. Is that intentional? > > Can you to the page you are referring to? sorry, I was referring to the first "support" page; it has both: "For more information see the Ubuntu Advantage1 page." which links to http://www.ubuntu.com/management "See the Ubuntu Support page for more information." which links to http://www.ubuntu.com/support the ubuntu.com/management just redirects to ubuntu.com/support, and the /support page is just the UA landing page. Maybe it meant to link to https://ubuntu.com/support/community-support -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Ubuntu Server Guide - VCS docs
So, the "commercial" and "community" support links go to the same page - UA support. Is that intentional? On Fri, Sep 27, 2019 at 4:35 PM Bryce Harrington wrote: > > On Thu, Sep 26, 2019 at 02:15:15PM -0700, Doug Smythies wrote: > > On 2019.09.25 10:28 Bryce Harrington wrote: > > > > > - Removed the git basic usage directions > > > > Sorry to be late to the party. > > I disagree with the deletion of the git page. > > > > On 2019:09:12 12:51 Bryce wrote: > > > > > Given the prevalence of git these days, ... > > > and I think it is safe to assume most readers > > > will know at least the minimal amount > > > of git documented here. > > > > Disagree. > > We want the serverguide to be useful to new and old server types. > > It was my bible when I started. > > > Thanks for the feedback on the vcs changes, and appreciate the > opportunity to further justify the changes. > > Years ago git was one of many vcs's, and many of us were new to it. > These days it really is common knowledge, at least among technical > folk. I think it's safe to assume people already know it. > > Second, in terms of scope, the guide is more about services that run on > ubuntu, and less about training for sysadmin skills. > > Third, given our low manpower I think the guide will be healthiest if > we're selective in what we commit to maintain. Just as pruning a tree > helps it focus its energy for growth, pruning the guide will help ensure > we're delivering unique value to our readers. > > > Also I never remember how to do those two git config lines, > > and find them useful. > > Since these are global, you set them only once per user account. > They're stored in your ~/.gitconfig, so you could just copy them along > with your editor settings, .bash*, etc. when setting up a new account. > > The guide really doesn't address account management (maybe it should), > but if it did I could see moving the git config settings there. > > Bryce > > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Triage/Migration report of the day
On Fri, Sep 27, 2019 at 1:58 AM Christian Ehrhardt wrote: > > Triage > - 16 bugs to triage, interesting ones: > - Mostly activity from us => no-action items > - 1841936 is interesting as a planned no-change-rebuild against > openssl1.1.1 not only > picked up the expected TLSv1.3 but also increased DH key sizes. > - No new bugs added to our work queues (all that need action are > already on our queues) > > Proposed migration > - libvirt test is still broken by new systemd 243 >=> https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1844879 hasn't systemd been reverted back to 242 in Eoan? > - No new issues since yesterday (again - thanks beta freeze) > > -- > Christian Ehrhardt > Software Engineer, Ubuntu Server > Canonical Ltd > > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: UA for Apps process docs
On Fri, Sep 20, 2019 at 5:28 AM Bryce Harrington wrote: > > Hi Josh, > > Lucas and I have a draft completed for your review of a doc defining the > processes for handling UA for Apps projects, from effort estimation, to > package development, to review and upload for the security team. Hi Bryce, Josh, I like the doc, but I'm concerned that it doesn't mention Sustaining Engineering anywhere in the doc, nor are we involved in reviewing or approving new UA for Apps packages during or after the process. Can you please include us in the process since we're the team supporting these packages? > > There are a couple of ?'s sprinkled in for latter steps we're not clear > on. As we progress to the finish line on Kafka we should update with > proper links/teamnames/etc. > > https://docs.google.com/document/d/1SAC1qgrxLiD7qdYfip7qVFb7QZk5M7Ik0o7qVvJJV-o > > Bryce > > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Where is network configuration "hidden" on Ubuntu 16.04?
On Fri, Oct 5, 2018 at 3:31 PM Leroy Tennison wrote: > > I have two identical hardware devices, call them "2" (running Ubuntu 16.04.5 > x86_64) and "5" (running Ubuntu 16.04.3 i686). On "2" a couple of NICs > failed so I replaced the chassis by doing a hard drive swap between "2" and > "5". I updated /etc/udev/rules.d/70-persistent-net.rules on the swapped hard > drive and everything worked on "2" with the swapped chassis (this was the > subject of my last post to this list). > > The chassis of "2" (the original "2") has enough good NICs to use for testing > a planned keepalived enhancement but has the unit "5" hard drive. I updated > /etc/network/* (recursive) to have the configuration from "2" but, upon boot, > the device keeps getting it's old IP address for eth3 and eth9 (the unit "5" > IP addresses). It gets the correct IP address for eth0, no IP address for > eth5, eth6 or eth8 (all of which are configured as static in the interfaces.d > file). eth9 is the more unusual IP address so I did a recursive grep of /etc > for it's first two octets and found nothing. In fact /etc/rc.local has the > default contents and neither /etc/network/interfaces or the file in > /etc/network/interfaces.d even configures eth9. It's unclear what configuration exactly you're using for each interface, but if you're using dhcp then the dhcp server is likely giving the same IP address to the nic mac address, so it would follow the hardware (not your configuration). If you're not using dhcp, then I suggest you post exactly your config and what you want your nics to be configured as, and people can help you adjust your files. > > Where else can I look for the remnnts of the "5" configuration which are > being applied at boot and preventing parts of the file-based configuration > from working? I even decompressed a copy of initrd.img... and found nothing. > > > Leroy Tennison > Network Information/Cyber Security Specialist > E: le...@datavoiceint.com > 2220 Bush Dr > McKinney, Texas > 75070 > www.datavoiceint.com > TThis message has been sent on behalf > of a company that is part of the Harris Operating Group of > Constellation Software Inc. These companies are listed > here > . > If you prefer not to be contacted by Harris > Operating Group > please notify us > . > This message is intended exclusively for the > individual or entity to which it is addressed. This communication > may contain information that is proprietary, privileged or > confidential or otherwise legally exempt from disclosure. If you are > not the named addressee, you are not authorized to read, print, > retain, copy or disseminate this message or any part of it. If you > have received this message in error, please notify the sender > immediately by e-mail and delete all copies of the > message. > > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Where is network configuration "hidden" on Ubuntu 16.04?
On Sun, Oct 7, 2018 at 9:16 PM Mark Constable wrote: > > On 08/10/18 10:57, Little Girl wrote: > >> Where else can I look for the remnnts of the "5" configuration which > >> are being applied at boot and preventing parts of the file-based > >> configuration from working? I even decompressed a copy of > >> initrd.img... and found nothing. > > [...] > > If nothing else, hopefully this message will draw attention to your > > original message and maybe someone with a more appropriate solution > > will join in. > > I find this alias useful to search or query various config settings... > > alias q='find -type f -print0 | xargs -0 grep ' > > then "cd /etc" (most often) and ie; "q 12.34.56.78" the IP being set you can do that a lot easier with just: $ grep -r 12.34.56.78 /etc > from the previous 5 machine on the 2 machine. Change the IP for any > unique info related to the other machine and you may locate the > remnants of old config files. /var/lib/ is another place to look. > > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Testing for lp #1701023
Hi all, I've fixed a regression in how ifupdown handles vlans in lp 1701023, and would like to ask for anyone with ifupdown configurations using vlans to give it a test. The patched ifupdown and vlan pkgs are in -proposed for t/x/a/b, so if you upgrade to them and notice any issues with your network configuration, at boot, or ifup, or interface hotplug, please let me know and/or add a comment to the bug. I'll leave them in -proposed for a bit longer than usual to try to get more testing in. https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1701023 Thanks! -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: Timeout for Ubuntu Server ISO bootsplash
On Thu, Nov 23, 2017 at 10:01 AM, Mathieu Trudel-Lapierre wrote: > On Thu, Nov 23, 2017 at 4:55 AM, Christian Ehrhardt > wrote: >> On Thu, Nov 23, 2017 at 1:02 AM, Mathieu Trudel-Lapierre >> wrote: >>> Hi, >>> >>> I'm revising some of the bootloader logic for the ISO images. Ubuntu Server >>> currently seems to be one of the things that just wait indefinitely at the >>> bootloader (grub or isolinux, depending on what/where you are booting). >>> >>> Is anyone against putting a 5 second timeout in the bootloader, such that >>> the system carries on to starting the installer automatically? >> >> Hi Mathieu, >> not against the change, but I want to check on a Detail. >> Is it correct that today it does: >> A1. boot into bootloader >> A2. wait forever on users choice >> >> And you suggest: >> B1. boot into bootloader >> B2. wait 5 sec for users to choose anything special >> B3. go into the installer (and wait there on the user) >> >> If a user can influcence/choose anything in A2 that they can not do >> anymore in B3 (e.g. special kernel boot options I'd think). >> Then we should make the timeout on server a bit more than 5 seconds IMHO. >> > > There is, but it's a matter of setting custom kernel options > (disabling ACPI, for instance) or adding command-line parameters such > as for preseeding (which obviously needs to happen before the > installer starts). > >> The reason I point this out is the (unfortunately usual) combination >> of slow remote consoles plus 5-10 minute server initialization times. >> I'm afraid of the admin sitting on a remote server control on a crappy >> connection for 10 minutes and hitting "oh crap B2 just passed faster >> than I could see it". > > It's always a possibility, but putting the timeout too high is also > just waiting for no reason. We should also expect users who preseed or > install many systems to do so via the network or other means; and the > idea behind this is to have one common timeout value everywhere rather > than having many different images behave differently. > >> Not sure what the right value would be, but 30 seconds seem safer to >> me and it would still eventually reach B3. > > Does it really need to be 30 seconds though? If you're looking for > things to be more or less automatic, and if you preseed via the initrd > (which you may do, and we do for automatic testing AFAIK), then you're > sitting there waiting for 30 seconds when you could have waited for > much less. if it's automatic via preseeding, why would anyone be sitting there waiting for it? > > Remember, any keypress will cancel the timeout, you don't need to have > done everything within that window. > > On trans-oceanic links, 5 seconds is maybe cutting it a bit short, but > I wouldn't make it past 15. IMHO the problem isn't only high RTT (but that certainly makes it much worse), many times the serial console refresh is very slow (especially using the IPMI api to the server BMC - which sometimes disconnects during a reboot but doesn't let you know), so by the time you see the grub menu starting to draw, it's too late. 15 seconds probably is enough time if you're staring at the screen ready to press a key immediately, but if your server takes a few minutes (or worse) to (re)boot, it gets hard to stare at the screen waiting to press a key fast enough. Personally, for a server installer, I think 15 seconds is the minimum, not maximum. > > -- > > Mathieu Trudel-Lapierre > Freenode: cyphermox, Jabber: mathieu...@gmail.com > 4096R/65B58DA1 818A D123 0992 275B 23C2 CF89 C67B B4D6 65B5 8DA1 > > -- > ubuntu-server mailing list > ubuntu-server@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-server > More info: https://wiki.ubuntu.com/ServerTeam -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
