[Bug 1848902] Re: haproxy in bionic can get stuck
** Changed in: haproxy (Ubuntu) Importance: Undecided => High ** Changed in: haproxy (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1848902 Title: haproxy in bionic can get stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1848902/+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 1772705] Re: IKEv2 VPN connections fail to use DNS servers provided by the server
** Changed in: strongswan (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1772705 Title: IKEv2 VPN connections fail to use DNS servers provided by the server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1772705/+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 1723350] Re: sssd offline on boot, stays offline forever
** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1723350 Title: sssd offline on boot, stays offline forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1723350/+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 1848834] Re: ClusterMon resource creation core-dumps while created with extra_option -E
Good to know. I also couldn't reproduce it just by using those commands, some more setting up is probably needed. If we get reproducible steps, we might be able to identify the commit (or series of commits) that fixed it after 1.1.14. I took a quick look at the ChangeLog file but failed to spot anything obvious. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1848834 Title: ClusterMon resource creation core-dumps while created with extra_option -E To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1848834/+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 1851302] Re: Error in update
For reference: https://wiki.ubuntu.com/DebuggingInstallationIssues#triggers_ci_file_contains_unknown_directive_syntax -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1851302 Title: Error in update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1851302/+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 1851301] Re: error in install and update
*** This bug is a duplicate of bug 1851302 *** https://bugs.launchpad.net/bugs/1851302 ** This bug has been marked a duplicate of bug 1851302 Error in update -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1851301 Title: error in install and update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1851301/+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 1851302] Re: Error in update
Thanks for filing this bug in ubuntu. You seem to have a corrupted trigger file. What's the contents of /var/lib/dpkg/info/samba-libs.triggers? It might have a slightly different name, like have an architecture as part of the name. ** Changed in: samba (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1851302 Title: Error in update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1851302/+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 810736] Re: logrotate script needs to notify all samba processes when logs are rotated
Bug still in our queue. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/810736 Title: logrotate script needs to notify all samba processes when logs are rotated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/810736/+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 1670450] Re: samba4 bind dlz module stops working on rndc reload
This bug is still in our queue. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1670450 Title: samba4 bind dlz module stops working on rndc reload To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1670450/+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 1850212] Re: The following packages have been kept back: libsnmp30. dist-upgrade does not resolve.
Thanks for filing this bug in Ubuntu. Do you mean that in your current disco system, dist-upgrade does not install all available updates? Or is this error something you only get when running do-release-upgrade? Could you please also attach the release upgrader logs from /var/log /dist-upgrade? Also, if dist-upgrade is saying that a certain package won't be updated, could you please paste the output of: sudo apt-get install sudo apt-cache policy I'll mark this bug as incomplete for now. Once you provide the requested information, please switch its status back to "new". ** Changed in: net-snmp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/1850212 Title: The following packages have been kept back: libsnmp30. dist-upgrade does not resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1850212/+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 1850154] Re: package nmap-common 7.80+dfsg1-1build1 failed to install/upgrade: trying to overwrite '/usr/share/nmap/nmap-mac-prefixes', which is also in package nmap 7.70-2
Thanks for filing this bug in Ubuntu. The package you were upgrading from, 7.70-2, was apparently never published in Ubuntu, according to the list here: https://launchpad.net/ubuntu/+source/nmap/+publishinghistory Was that a local build perhaps? ** Changed in: nmap (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to nmap in Ubuntu. https://bugs.launchpad.net/bugs/1850154 Title: package nmap-common 7.80+dfsg1-1build1 failed to install/upgrade: trying to overwrite '/usr/share/nmap/nmap-mac-prefixes', which is also in package nmap 7.70-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nmap/+bug/1850154/+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 1850183] Re: package postfix (not installed) failed to install/upgrade: il sottoprocesso nuovo pacchetto postfix script pre-installation è stato terminato dal segnale (Terminato)
Thanks for filing this bug in Ubuntu. It's not clear why the postfix postinst script failed. I suggest you look in /var/log/mail.log and /var/log/mail.err to see if there is more helpful information there. Since there is not enough information in this bug report to diagnose the problem, I'll mark it as incomplete. ** Changed in: postfix (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1850183 Title: package postfix (not installed) failed to install/upgrade: il sottoprocesso nuovo pacchetto postfix script pre-installation è stato terminato dal segnale (Terminato) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1850183/+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 1834963] Re: apache dependency should be documented in package description
I personally think what we have is good enough. If someone thinks otherwise, please file a merge request in https://salsa.debian.org/php- team/php-defaults ** Changed in: php7.2 (Ubuntu) Status: Triaged => Opinion ** Changed in: php7.3 (Ubuntu) Status: Triaged => Opinion -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to php7.2 in Ubuntu. https://bugs.launchpad.net/bugs/1834963 Title: apache dependency should be documented in package description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1834963/+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 1723350] Re: sssd offline on boot, stays offline forever
I agree. Do you have a way to reproduce this somewhat reliably? ** Changed in: sssd (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1723350 Title: sssd offline on boot, stays offline forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1723350/+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 1845334] Re: Update DEP8 test to python3
Salsa MR: https://salsa.debian.org/postfix-team/postfix- dev/merge_requests/3 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1845334 Title: Update DEP8 test to python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1845334/+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 1845334] Re: Update DEP8 test to python3
I have a pass with python3 for 3.4.7-1 in debian/sid. Let me clean that branch up now and make a MR in salsa. ** Attachment added: "log" https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1845334/+attachment/5302040/+files/log -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1845334 Title: Update DEP8 test to python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1845334/+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 1845334] Re: Update DEP8 test to python3
Looking at this now. ** Changed in: postfix (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1845334 Title: Update DEP8 test to python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1845334/+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 1832757] Re: Update ubuntu-advantage-client
I'm satisfied with the results, also considering test (5) done in the other bug. Just to be sure, I also tried it via dist-upgrade. That is a bit more hacky, as it involves changing s/precise/trusty/ in sources.list snippets, ignoring gpg errors (as precise doesn't have the gpg key for trusty-esm) and so on, but it also worked in the end. Flipping the tags. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832757 Title: Update ubuntu-advantage-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1832757/+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 1832757] Re: Update ubuntu-advantage-client
Test 4: >From a fresh trusty instance, which has uat installed (from updates): a) enable esm (via ubuntu-advantage enable-esm), upgrade to proposed b) upgrade to proposed, enable esm (via ua attach) Result: PASS Details: In the end, both instances have the same proposed package: $ lxc exec esm-sru-4a apt-cache policy ubuntu-advantage-tools ubuntu-advantage-tools: Installed: 19.6~ubuntu14.04.3 Candidate: 19.6~ubuntu14.04.3 Version table: *** 19.6~ubuntu14.04.3 0 500 http://br.archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 10ubuntu0.14.04.4 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages And both have ESM enabled. In the (b) case, it's using the new infra pocket names because ESM was enabled with the new client via ua attach: $ lxc exec esm-sru-4b apt-cache policy |grep esm 500 https://esm.ubuntu.com/ubuntu/ trusty-infra-updates/main amd64 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages origin esm.ubuntu.com Content comparison - etc directory (/dev/null was used because of the broken absolute symlinks; here is the suppressed output: https://paste.ubuntu.com/p/n98rSKBqvP/): $ diff -uNr 4a/etc 4b/etc 2>/dev/null diff -uNr 4a/etc/apt/auth.conf.d/90ubuntu-advantage 4b/etc/apt/auth.conf.d/90ubuntu-advantage --- 4a/etc/apt/auth.conf.d/90ubuntu-advantage 2019-10-31 15:52:19.613041203 -0300 +++ 4b/etc/apt/auth.conf.d/90ubuntu-advantage 2019-10-31 15:57:10.593242280 -0300 @@ -1 +1 @@ -machine esm.ubuntu.com/ login myuser password mypass +machine esm.ubuntu.com/ login bearer password longrandompass # ubuntu-advantage-tools Since (4b) runs ua attach, the credentials are converted to the new bearer format, so the above is expected and correct. diff -uNr 4a/etc/apt/sources.list.d/ubuntu-esm-infra-trusty.list 4b/etc/apt/sources.list.d/ubuntu-esm-infra-trusty.list --- 4a/etc/apt/sources.list.d/ubuntu-esm-infra-trusty.list 2019-10-31 15:52:19.629041498 -0300 +++ 4b/etc/apt/sources.list.d/ubuntu-esm-infra-trusty.list 2019-10-31 15:57:10.605241750 -0300 @@ -1,5 +1,4 @@ -deb https://esm.ubuntu.com/ubuntu trusty-security main -# deb-src https://esm.ubuntu.com/ubuntu trusty-security main - -deb https://esm.ubuntu.com/ubuntu trusty-updates main -# deb-src https://esm.ubuntu.com/ubuntu trusty-updates main +deb https://esm.ubuntu.com/ubuntu trusty-infra-security main +# deb-src https://esm.ubuntu.com/ubuntu trusty-infra-security main +deb https://esm.ubuntu.com/ubuntu trusty-infra-updates main +# deb-src https://esm.ubuntu.com/ubuntu trusty-infra-updates main Since (4b) runs attach, the pockets are renamed to the new infra names, so the above is also expected and correct. - /var: Also broken symlinks, and: $ diff -uNr 4a/var 4b/var|diffstat -l diff: 4a/var/lib/cloud/instance: No such file or directory diff: 4b/var/lib/cloud/instance: No such file or directory cache/apt/pkgcache.bin cache/apt/srcpkgcache.bin cache/man/index.db lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-security_InRelease lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-security_main_binary-amd64_Packages lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-updates_InRelease lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-updates_main_binary-amd64_Packages lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-security_InRelease lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-security_main_binary-amd64_Packages lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-updates_InRelease lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-updates_main_binary-amd64_Packages lib/cloud/data/status.json lib/cloud/instances/esm-sru-4a/boot-finished lib/cloud/instances/esm-sru-4a/user-data.txt.i lib/cloud/instances/esm-sru-4a/vendor-data.txt.i lib/dhcp/dhclient.eth0.leases lib/ubuntu-advantage/private/machine-access-cc-eal.json lib/ubuntu-advantage/private/machine-access-esm-infra.json lib/ubuntu-advantage/private/machine-access-fips-updates.json lib/ubuntu-advantage/private/machine-access-fips.json lib/ubuntu-advantage/private/machine-access-livepatch.json lib/ubuntu-advantage/private/machine-access-support.json lib/ubuntu-advantage/private/machine-token.json lib/ubuntu-advantage/status.json lib/urandom/random-seed log/apt/history.log log/apt/term.log log/cloud-init-output.log log/cloud-init.log log/dmesg log/dmesg.0 log/dmesg.1.gz log/dpkg.log log/kern.log log/syslog log/ubuntu-advantage.log log/upstart/acpid.log log/upstart/apport.log log/upstart/console-setup.log log/upstart/cryptdisks.log log/upstart/hwclock.log log/upstart/kmod.log log/upstart/mountall.log log/upstart/mounted-debugfs.log log/upstart/mounted-dev.log log/upstart/mounted-proc.log log/upstart/procps-static-network-up.log log/upstart/procps-virtual-filesystems.log log/upstart/setvtrgb.log log/upstart/systemd-logind.log log/upstart/ttyS0.log log/wtmp The /var/lib/ubuntu-advantage files are
[Bug 1832757] Re: Update ubuntu-advantage-client
Test 3:
>From a fresh trusty system, no uat installed, no ubuntu-minimal installed
a) install uat from updates, enable esm, upgrade to proposed
b) install uat from proposed, enable esm (via ua attach)
Result: PASS
Details:
At the end, confirmed that both chroots have esm enabled and with a positive
pinning:
# chroot /tank/trusty-3a/ apt-cache policy | grep esm
500 https://esm.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
origin esm.ubuntu.com
500 https://esm.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
origin esm.ubuntu.com
# chroot /tank/trusty-3b/ apt-cache policy | grep esm
500 https://esm.ubuntu.com/ubuntu/ trusty-infra-updates/main amd64 Packages
origin esm.ubuntu.com
500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
origin esm.ubuntu.com
Note how (3b) is using the new infra pocket names, however. That's
because "ua attach" was run in that case, and it wasn't run in (3a).
Both work, though, and it's expected that users will eventually run "ua
attach" after upgrading even if they had esm enabled before. This is
mentioned in the [Other Info] section of the bug description.
Filesystem differences:
# diff -uNr /tank/trusty-3{a,b}/ 2>/dev/null | diffstat -l
etc/apt/auth.conf.d/90ubuntu-advantage
etc/apt/sources.list.d/ubuntu-esm-infra-trusty.list
var/cache/apt/archives/ubuntu-advantage-tools_10ubuntu0.14.04.4_all.deb
var/cache/apt/pkgcache.bin
var/cache/apt/srcpkgcache.bin
var/cache/ldconfig/aux-cache
var/lib/apt/extended_states
var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-security_InRelease
var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-security_main_binary-amd64_Packages
var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-updates_InRelease
var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-updates_main_binary-amd64_Packages
var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-security_InRelease
var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-security_main_binary-amd64_Packages
var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-updates_InRelease
var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-updates_main_binary-amd64_Packages
var/lib/dpkg/available
var/lib/dpkg/available-old
var/lib/dpkg/status-old
var/lib/ubuntu-advantage/machine-id
var/lib/ubuntu-advantage/private/machine-access-cc-eal.json
var/lib/ubuntu-advantage/private/machine-access-esm-infra.json
var/lib/ubuntu-advantage/private/machine-access-fips-updates.json
var/lib/ubuntu-advantage/private/machine-access-fips.json
var/lib/ubuntu-advantage/private/machine-access-livepatch.json
var/lib/ubuntu-advantage/private/machine-access-support.json
var/lib/ubuntu-advantage/private/machine-token.json
var/lib/ubuntu-advantage/status.json
var/log/apt/history.log
var/log/apt/term.log
var/log/dpkg.log
var/log/ubuntu-advantage.log
Of the above, only /etc/apt is of interest, so let's take a closer look:
# diff -uNr /tank/trusty-3{a,b}/etc/apt
diff -uNr /tank/trusty-3a/etc/apt/auth.conf.d/90ubuntu-advantage
/tank/trusty-3b/etc/apt/auth.conf.d/90ubuntu-advantage
--- /tank/trusty-3a/etc/apt/auth.conf.d/90ubuntu-advantage 2019-10-31
15:04:20.083887502 -0300
+++ /tank/trusty-3b/etc/apt/auth.conf.d/90ubuntu-advantage 2019-10-31
15:06:51.943489600 -0300
@@ -1 +1 @@
-machine esm.ubuntu.com/ login myuser password mypass
+machine esm.ubuntu.com/ login bearer password verylongrandompass #
ubuntu-advantage-tools
The above confirms that ua attach was run on (3b), because the old style
credentials were removed and the new style was put in place.
diff -uNr /tank/trusty-3a/etc/apt/sources.list.d/ubuntu-esm-infra-trusty.list
/tank/trusty-3b/etc/apt/sources.list.d/ubuntu-esm-infra-trusty.list
--- /tank/trusty-3a/etc/apt/sources.list.d/ubuntu-esm-infra-trusty.list
2019-10-31 15:04:20.083887502 -0300
+++ /tank/trusty-3b/etc/apt/sources.list.d/ubuntu-esm-infra-trusty.list
2019-10-31 15:06:51.935489610 -0300
@@ -1,5 +1,4 @@
-deb https://esm.ubuntu.com/ubuntu trusty-security main
-# deb-src https://esm.ubuntu.com/ubuntu trusty-security main
-
-deb https://esm.ubuntu.com/ubuntu trusty-updates main
-# deb-src https://esm.ubuntu.com/ubuntu trusty-updates main
+deb https://esm.ubuntu.com/ubuntu trusty-infra-security main
+# deb-src https://esm.ubuntu.com/ubuntu trusty-infra-security main
+deb https://esm.ubuntu.com/ubuntu trusty-infra-updates main
+# deb-src https://esm.ubuntu.com/ubuntu trusty-infra-updates main
This also confirms that ua attach was run on (3b), since we now have the
new infra pocket names.
Like with test (2), absolute symlinks in the chroot get broken when
looked at from the outside, so here is a list of what was suppressed
from the full diff output: https://paste.ubuntu.com/p/7BmfzQjtqt/
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ubuntu-advantage-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1832757
Title:
Update ubuntu-advantage-client
To manage
[Bug 1832757] Re: Update ubuntu-advantage-client
Test 2:
a) fresh install from t-updates, go to t-proposed
b) fresh install from t-proposed directly
Result: PASS
Details:
At the end, we have two chroots: /tank/trusty-2a and /tank/trusty-2b
# chroot /tank/trusty-2a apt-cache policy ubuntu-advantage-tools
ubuntu-advantage-tools:
Installed: 19.6~ubuntu14.04.3
Candidate: 19.6~ubuntu14.04.3
Version table:
*** 19.6~ubuntu14.04.3 0
500 http://br.archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64
Packages
100 /var/lib/dpkg/status
10ubuntu0.14.04.4 0
500 http://br.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
# chroot /tank/trusty-2b apt-cache policy ubuntu-advantage-tools
ubuntu-advantage-tools:
Installed: 19.6~ubuntu14.04.3
Candidate: 19.6~ubuntu14.04.3
Version table:
*** 19.6~ubuntu14.04.3 0
500 http://br.archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64
Packages
100 /var/lib/dpkg/status
10ubuntu0.14.04.4 0
500 http://br.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
Diffing content of both chroots:
# find /tank/trusty-2b/ -xdev | sed -r 's,^/tank/[^/]+,,' | sort >
full-trusty-2b.list
# find /tank/trusty-2a/ -xdev | sed -r 's,^/tank/[^/]+,,' | sort >
full-trusty-2a.list
The diff is:
# diff -u full-trusty-2{a,b}.list
--- full-trusty-2a.list 2019-10-31 14:46:33.307720630 -0300
+++ full-trusty-2b.list 2019-10-31 14:46:26.487592874 -0300
@@ -1567,7 +1567,6 @@
/opt
/proc
/root
-/root/.bash_history
/root/.bashrc
/root/.profile
/run
@@ -13724,7 +13723,6 @@
/var/cache/apt/archives/sysv-rc_2.88dsf-41ubuntu6_all.deb
/var/cache/apt/archives/tar_1.27.1-1_amd64.deb
/var/cache/apt/archives/tzdata_2014b-1_all.deb
-/var/cache/apt/archives/ubuntu-advantage-tools_10ubuntu0.14.04.4_all.deb
/var/cache/apt/archives/ubuntu-advantage-tools_19.6~ubuntu14.04.3_amd64.deb
/var/cache/apt/archives/ubuntu-keyring_2012.05.19_all.deb
/var/cache/apt/archives/ucf_3.0027+nmu1_all.deb
The above shows that trusty-2a went through the trusty-updates u-a-t
package, while trusty-2b didn't.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ubuntu-advantage-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1832757
Title:
Update ubuntu-advantage-client
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1832757/+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 1832757] Re: Update ubuntu-advantage-client
addendum for test 2:
# diff -uNr /tank/trusty-2{a,b}/ 2>/dev/null|diffstat
root/.bash_history |2
var/cache/apt/archives/ubuntu-advantage-tools_10ubuntu0.14.04.4_all.deb |binary
var/cache/apt/pkgcache.bin |binary
var/cache/ldconfig/aux-cache|binary
var/lib/apt/extended_states | 24
var/lib/dpkg/available | 46
var/lib/dpkg/available-old | 601
-
var/lib/dpkg/status-old | 105
-
var/log/apt/history.log | 12
var/log/apt/term.log|7
var/log/dpkg.log| 639
--
11 files changed, 409 insertions(+), 1027 deletions(-)
2>/dev/null was added because of broken absolute symlinks, which are
only fine inside the chroot, but not from the outside. Full list at
https://paste.ubuntu.com/p/sMmzYRrJT9/
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ubuntu-advantage-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1832757
Title:
Update ubuntu-advantage-client
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1832757/+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 1832757] Re: Update ubuntu-advantage-client
Test 1: basic attach w/ proposed Result: PASS Details: $ lxc launch ubuntu-daily:trusty t1 Creating t1 Starting t1 # enable proposed, update, check $ lxc exec t1 apt-get update $ lxc exec t1 apt-cache policy ubuntu-advantage-tools ubuntu-advantage-tools: Installed: 10ubuntu0.14.04.3 Candidate: 19.6~ubuntu14.04.3 Version table: 19.6~ubuntu14.04.3 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 10ubuntu0.14.04.4 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages *** 10ubuntu0.14.04.3 0 # update $ lxc exec t1 apt-get install ubuntu-advantage-tools # attach $ lxc exec t1 ua attach $token Enabling default service esm-infra Updating package lists ESM Infra enabled This machine is now attached to 'panli...@gmail.com' SERVICE ENTITLED STATUSDESCRIPTION cc-ealyes n/a Common Criteria EAL2 Provisioning Packages cis-audit no— Center for Internet Security Audit Tools esm-infra yes enabled UA Infra: Extended Security Maintenance fips yes n/a NIST-certified FIPS modules fips-updates yes n/a Uncertified security updates to FIPS modules livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: panli...@gmail.com Subscription: panli...@gmail.com # confirm esm repo is enabled with positive pinning $ lxc exec t1 apt-cache policy|grep esm 500 https://esm.ubuntu.com/ubuntu/ trusty-infra-updates/main amd64 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages origin esm.ubuntu.com # test download an esm update $ lxc exec t1 -- apt-get install -d sudo Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libfreetype6 os-prober Use 'apt-get autoremove' to remove them. The following packages will be upgraded: sudo 1 upgraded, 0 newly installed, 0 to remove and 59 not upgraded. Need to get 833 kB of archives. After this operation, 1072 kB of additional disk space will be used. Get:1 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main sudo amd64 1.8.9p5-1ubuntu1.5+esm2 [833 kB] Fetched 833 kB in 5s (166 kB/s) Download complete and in download only mode -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832757 Title: Update ubuntu-advantage-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1832757/+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 1832757] Re: Update ubuntu-advantage-client
Repeating tests 1-4 here. Test number 5, which failed in the previous verification, can be seen done in bug https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage- tools/+bug/1850672. It was done with do-release-upgade, which is how I expect users would upgrade from precise, and I took care with the repositories to make sure esm was included in the upgrades, and the right ubuntu-advantage-tools package was used each time (either from trusty-updates, or from -proposed). -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832757 Title: Update ubuntu-advantage-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1832757/+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 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
Trusty verification, in two parts: a) following the [testing] section, i.e., upgrading from precise, to trusty, then to trusty-updates b) almost the same setup, but upgrading from precise to trusty with the u-a-t proposed package, without going through the intermediary current u-a-t from trusty-updates. Since the logs are rather long, I'll do these in separate comments -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+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 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
trusty verification succeeded ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+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 1849851] Re: Drop python3-flake8 build-dep on trusty
The package https://launchpad.net/ubuntu/+source/ubuntu-advantage- tools/19.6~ubuntu14.04.3 built just fine, confirming the fix. trusty verification succeeded. ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1849851 Title: Drop python3-flake8 build-dep on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1849851/+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 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
b) almost the same setup, but upgrading from precise to trusty with the u-a-t proposed package, without going through the intermediary current u-a-t from trusty-updates. $ lxc launch ubuntu-daily:precise p1 $ lxc exec p1 ubuntu-advantage enable-esm $u:$p Running apt-get update... Ubuntu ESM repository enabled. # confirming $ lxc exec p1 apt-cache policy|grep esm 500 https://esm.ubuntu.com/ubuntu/ precise/main i386 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ precise/main amd64 Packages origin esm.ubuntu.com # enable precise-proposed, which do-release-upgrade will change to trusty-proposed $ lxc exec p1 -- bash -c "echo deb http://archive.ubuntu.com/ubuntu precise-proposed main > /etc/apt/sources.list.d/precise-proposed.list" # ssh in and create a pinning config so not all of trusty-proposed is used root@p1:~# cat > /etc/apt/preferences.d/proposed-pinning < Package: * > Pin: release a=trusty-proposed > Pin-Priority: 400 > > Package: ubuntu-advantage-tools > Pin: release a=trusty-proposed > Pin-Priority: 500 > EOF # perform the upgrade root@p1:~# sudo do-release-upgrade ... # after reboot # confirm only u-a-t was taken from trusty-proposed $ lxc exec p1 grep trusty-proposed /var/log/dist-upgrade/screenlog.0 Get:11 http://archive.ubuntu.com trusty-proposed Release.gpg [916 B] Get:19 http://archive.ubuntu.com trusty-proposed Release [64.9 kB] Get:31 http://archive.ubuntu.com trusty-proposed/main amd64 Packages [4,598 B] Get:44 http://archive.ubuntu.com trusty-proposed/main i386 Packages [2,792 B] Get:60 http://archive.ubuntu.com trusty-proposed/main TranslationIndex [202 B] Get:74 http://archive.ubuntu.com trusty-proposed/main Translation-en [2,932 B] Get:87 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main ubuntu-advantage-tools amd64 19.6~ubuntu14.04.3 [47.3 kB] $ # confirm upgrade path: version from precise, direct to trusty-proposed $ lxc exec p1 grep ubuntu-advantage-tools /var/log/dist-upgrade/apt-term.log Preparing to unpack .../ubuntu-advantage-tools_19.6~ubuntu14.04.3_amd64.deb ... Unpacking ubuntu-advantage-tools (19.6~ubuntu14.04.3) over (1) ... Setting up ubuntu-advantage-tools (19.6~ubuntu14.04.3) ... # confirm esm is enabled and shows a positive pinning value $ lxc exec p1 apt-cache policy|grep esm 500 https://esm.ubuntu.com/ubuntu/ trusty-security/main i386 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages origin esm.ubuntu.com # finally, confirm we can ua attach and esm keeps working $ lxc exec p1 ua attach $token Updating 'esm-infra' apt sources list on changed directives. Updating package lists Updating package lists This machine is now attached to 'panli...@gmail.com' SERVICE ENTITLED STATUSDESCRIPTION cc-ealyes n/a Common Criteria EAL2 Provisioning Packages cis-audit no— Center for Internet Security Audit Tools esm-infra yes enabled UA Infra: Extended Security Maintenance fips yes n/a NIST-certified FIPS modules fips-updates yes n/a Uncertified security updates to FIPS modules livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: panli...@gmail.com Subscription: panli...@gmail.com # and esm pinning value is non negative, and using the new infra names $ lxc exec p1 apt-cache policy|grep esm 500 https://esm.ubuntu.com/ubuntu/ trusty-infra-updates/main i386 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ trusty-infra-updates/main amd64 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main i386 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages origin esm.ubuntu.com -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+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 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
a) upgrading from precise, to trusty, then to trusty-updates $ lxc launch ubuntu-daily:precise p1 Creating p1 Starting p1 $ lxc exec p1 ubuntu-advantage enable-esm $u:$p Running apt-get update... Ubuntu ESM repository enabled. # esm enabled, positive pinning: $ lxc exec p1 apt-cache policy|grep esm 500 https://esm.ubuntu.com/ubuntu/ precise/main i386 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ precise/main amd64 Packages origin esm.ubuntu.com # starting do-release-upgrade to trusty ubuntu@p1:~$ sudo do-release-upgrade ... reboot # ua version after do-release-upgrade: root@p1:~# apt-cache policy ubuntu-advantage-tools ubuntu-advantage-tools: Installed: 10ubuntu0.14.04.4 Candidate: 10ubuntu0.14.04.4 Version table: *** 10ubuntu0.14.04.4 0 500 http://br.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages # how u-a-t was upgraded, from do-release-upgrade logs: Unpacking ubuntu-advantage-tools (10ubuntu0.14.04.4) over (1) ... # esm trusty packages were included in the do-release-upgrade: root@p1:~# grep -E 'esm\.ubuntu' /var/log/dist-upgrade/screenlog.0 |tail -n 2 Get:492 https://esm.ubuntu.com/ubuntu/ trusty-security/main linux-headers-virtual amd64 3.13.0.174.185 [1,754 B] Get:493 https://esm.ubuntu.com/ubuntu/ trusty-security/main wpasupplicant amd64 2.1-0ubuntu1.7+esm2 [752 kB] # add trusty-proposed $ lxc exec p1 -- bash -c "echo deb http://archive.ubuntu.com/ubuntu trusty-proposed main > /etc/apt/sources.list.d/trusty-proposed.list $ lxc exec p1 apt-get update ... # install u-a-t from proposed $ lxc exec p1 -- apt-get install -y ubuntu-advantage-tools ... Get:3 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main ubuntu-advantage-tools amd64 19.6~ubuntu14.04.3 [47.3 kB] ... Unpacking ubuntu-advantage-tools (19.6~ubuntu14.04.3) over (10ubuntu0.14.04.4) ... $ lxc exec p1 apt-get update ... # confirm esm is enabled and shows a positive pinning value $ lxc exec p1 apt-cache policy|grep esm 500 https://esm.ubuntu.com/ubuntu/ trusty-security/main i386 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages origin esm.ubuntu.com # as an extra step, let's confirm we can attach now with the new client $ lxc exec p1 ua attach $token Updating 'esm-infra' apt sources list on changed directives. Updating package lists Updating package lists This machine is now attached to 'panli...@gmail.com' SERVICE ENTITLED STATUSDESCRIPTION cc-ealyes n/a Common Criteria EAL2 Provisioning Packages cis-audit no— Center for Internet Security Audit Tools esm-infra yes enabled UA Infra: Extended Security Maintenance fips yes n/a NIST-certified FIPS modules fips-updates yes n/a Uncertified security updates to FIPS modules livepatch yes n/a Canonical Livepatch service Enable services with: ua enable Account: panli...@gmail.com Subscription: panli...@gmail.com # and esm remains enabled as expected, but now using the new infra pocket names: $ lxc exec p1 apt-cache policy|grep esm 500 https://esm.ubuntu.com/ubuntu/ trusty-infra-updates/main i386 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ trusty-infra-updates/main amd64 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main i386 Packages origin esm.ubuntu.com 500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages origin esm.ubuntu.com -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+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 1804542] Re: [SRU] Multiple intermittent socket failures during name resolutions
Please remember that in order for this update to be released, the tags need to be updated, as explained in comment #16. Thanks for testing! -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1804542 Title: [SRU] Multiple intermittent socket failures during name resolutions To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1804542/+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 1850699] Re: Please remove net-tools from bind9 Depends (replaced by iproute2)
** Changed in: bind9 (Ubuntu) Status: New => Triaged ** Changed in: bind9 (Ubuntu) Importance: Undecided => High ** Changed in: bind9 (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1850699 Title: Please remove net-tools from bind9 Depends (replaced by iproute2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1850699/+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 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
** Description changed: [Impact] When enabling ESM on precise, then upgrading that to current trusty, and from there to the proposed new trusty client (see #1832757), ESM gets disabled. This was found when executing test case (5) in the original SRU bug #1832757. The reason is that d/postinst, when dealing with this upgrade path, was conditioning a file rename on the package upgrade coming from version 1, which is the precise one. The fix is to drop that conditional, since the filename we intend to rename is the precise one (it has "precise" in its name) and there is no need to check for the version. [Test Case] lxc launch ubuntu-daily:precise p1 lxc exec p1 ubuntu-advantage enable-esm $USER:$PASS - # confirm esm is enabled and working by downloading a package - lxc exec p1 -- apt-get install -d python-jinja2 - lxc exec p1 apt-get clean + # confirm esm is enabled and shows a positive pinning value + lxc exec p1 apt-cache policy|grep esm # ssh into p1 and call do-release-upgrade (doesn't work via lxc exec) ssh p1 - sudo do-release-upgrade - logout + sudo do-release-upgrade + logout lxc exec p1 -- bash -c "echo deb http://archive.ubuntu.com/ubuntu trusty-proposed main > /etc/apt/sources.list.d/trusty-proposed.list" lxc exec p1 apt-get update lxc exec p1 -- apt-get install -y ubuntu-advantage-tools lxc exec p1 apt-get update + # confirm esm is enabled and shows a positive pinning value lxc exec p1 apt-cache policy|grep esm - # try to download a trusty esm package, it should work - lxc exec p1 -- apt-get install -d python-jinja2 - lxc exec p1 apt-get clean [Regression Potential] Before we were pinning this upgrade path on having come from the exact precise package version, which is "1". Now we are dropping that requirement, and only checking if the precise esm sources.list file exists, then we rename it to the trusty name: ubuntu-esm-precise.list -> ubuntu-esm-infra-trusty.list do-release-upgrade will have renamed "precise" to "trusty" inside ubuntu-esm-precise.list. If someone is doing the upgrade manually via dist-upgrade, for example, then this person is expected to rename the precise repositories to trusty ones in all of /etc/apt/sources.list* [Other Info] As with the $1832757 SRU, this is being published only on trusty. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+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 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
** Description changed: [Impact] When enabling ESM on precise, then upgrading that to current trusty, and from there to the proposed new trusty client (see #1832757), ESM gets disabled. This was found when executing test case (5) in the original SRU bug #1832757. The reason is that d/postinst, when dealing with this upgrade path, was conditioning a file rename on the package upgrade coming from version 1, which is the precise one. The fix is to drop that conditional, since the filename we intend to rename is the precise one (it has "precise" in its name) and there is no need to check for the version. [Test Case] lxc launch ubuntu-daily:precise p1 - lxc exec p1 ubuntu-advantage enable-esm $USER:$PASS + lxc exec p1 ubuntu-advantage enable-esm $USER:$PASS + # confirm esm is enabled and working by downloading a package + lxc exec p1 -- apt-get install -d python-jinja2 + lxc exec p1 apt-get clean lxc exec p1 do-release-upgrade lxc exec p1 -- bash -c "echo deb http://archive.ubuntu.com/ubuntu trusty-proposed main > /etc/apt/sources.list.d/trusty-proposed.list" lxc exec p1 apt-get update lxc exec p1 -- apt-get install -y ubuntu-advantage-tools lxc exec p1 apt-get update lxc exec p1 apt-cache policy|grep esm # try to download a trusty esm package, it should work lxc exec p1 -- apt-get install -d python-jinja2 - + lxc exec p1 apt-get clean [Regression Potential] Before we were pinning this upgrade path on having come from the exact precise package version, which is "1". Now we are dropping that requirement, and only checking if the precise esm sources.list file exists, then we rename it to the trusty name: ubuntu-esm-precise.list -> ubuntu-esm-infra-trusty.list do-release-upgrade will have renamed "precise" to "trusty" inside ubuntu-esm-precise.list. If someone is doing the upgrade manually via dist-upgrade, for example, then this person is expected to rename the precise repositories to trusty ones in all of /etc/apt/sources.list* [Other Info] As with the $1832757 SRU, this is being published only on trusty. ** Description changed: [Impact] When enabling ESM on precise, then upgrading that to current trusty, and from there to the proposed new trusty client (see #1832757), ESM gets disabled. This was found when executing test case (5) in the original SRU bug #1832757. The reason is that d/postinst, when dealing with this upgrade path, was conditioning a file rename on the package upgrade coming from version 1, which is the precise one. The fix is to drop that conditional, since the filename we intend to rename is the precise one (it has "precise" in its name) and there is no need to check for the version. [Test Case] lxc launch ubuntu-daily:precise p1 - lxc exec p1 ubuntu-advantage enable-esm $USER:$PASS + lxc exec p1 ubuntu-advantage enable-esm $USER:$PASS # confirm esm is enabled and working by downloading a package lxc exec p1 -- apt-get install -d python-jinja2 lxc exec p1 apt-get clean - lxc exec p1 do-release-upgrade + # ssh into p1 and call do-release-upgrade (doesn't work via lxc exec) + ssh p1 + sudo do-release-upgrade + logout lxc exec p1 -- bash -c "echo deb http://archive.ubuntu.com/ubuntu trusty-proposed main > /etc/apt/sources.list.d/trusty-proposed.list" lxc exec p1 apt-get update lxc exec p1 -- apt-get install -y ubuntu-advantage-tools lxc exec p1 apt-get update lxc exec p1 apt-cache policy|grep esm # try to download a trusty esm package, it should work lxc exec p1 -- apt-get install -d python-jinja2 lxc exec p1 apt-get clean [Regression Potential] Before we were pinning this upgrade path on having come from the exact precise package version, which is "1". Now we are dropping that requirement, and only checking if the precise esm sources.list file exists, then we rename it to the trusty name: ubuntu-esm-precise.list -> ubuntu-esm-infra-trusty.list do-release-upgrade will have renamed "precise" to "trusty" inside ubuntu-esm-precise.list. If someone is doing the upgrade manually via dist-upgrade, for example, then this person is expected to rename the precise repositories to trusty ones in all of /etc/apt/sources.list* [Other Info] As with the $1832757 SRU, this is being published only on trusty. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+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 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
** Description changed: [Impact] When enabling ESM on precise, then upgrading that to current trusty, and from there to the proposed new trusty client (see #1832757), ESM gets disabled. This was found when executing test case (5) in the original SRU bug #1832757. The reason is that d/postinst, when dealing with this upgrade path, was conditioning a file rename on the package upgrade coming from version 1, which is the precise one. The fix is to drop that conditional, since the filename we intend to rename is the precise one (it has "precise" in its name) and there is no need to check for the version. [Test Case] - * detailed instructions how to reproduce the bug + lxc launch ubuntu-daily:precise p1 + lxc exec p1 ubuntu-advantage enable-esm $USER:$PASS + lxc exec p1 do-release-upgrade + lxc exec p1 -- bash -c "echo deb http://archive.ubuntu.com/ubuntu trusty-proposed main > /etc/apt/sources.list.d/trusty-proposed.list" + lxc exec p1 apt-get update + lxc exec p1 -- apt-get install -y ubuntu-advantage-tools + lxc exec p1 apt-get update + lxc exec p1 apt-cache policy|grep esm + # try to download a trusty esm package, it should work + lxc exec p1 -- apt-get install -d python-jinja2 - * these should allow someone who is not familiar with the affected - package to reproduce the bug and verify that the updated package fixes - the problem. [Regression Potential] + Before we were pinning this upgrade path on having come from the exact precise package version, which is "1". Now we are dropping that requirement, and only checking if the precise esm sources.list file exists, then we rename it to the trusty name: - * discussion of how regressions are most likely to manifest as a result - of this change. + ubuntu-esm-precise.list -> ubuntu-esm-infra-trusty.list - * It is assumed that any SRU candidate patch is well-tested before - upload and has a low overall risk of regression, but it's important - to make the effort to think about what ''could'' happen in the - event of a regression. - - * This both shows the SRU team that the risks have been considered, - and provides guidance to testers in regression-testing the SRU. + do-release-upgrade will have renamed "precise" to "trusty" inside + ubuntu-esm-precise.list. If someone is doing the upgrade manually via + dist-upgrade, for example, then this person is expected to rename the + precise repositories to trusty ones in all of /etc/apt/sources.list* [Other Info] - - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + As with the $1832757 SRU, this is being published only on trusty. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+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 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
** Description changed: + [Impact] + + * An explanation of the effects of the bug on users and + + * justification for backporting the fix to the stable release. + + * In addition, it is helpful, but not required, to include an +explanation of how the upload fixes this bug. + + [Test Case] + + * detailed instructions how to reproduce the bug + + * these should allow someone who is not familiar with the affected +package to reproduce the bug and verify that the updated package fixes +the problem. + + [Regression Potential] + + * discussion of how regressions are most likely to manifest as a result + of this change. + + * It is assumed that any SRU candidate patch is well-tested before +upload and has a low overall risk of regression, but it's important +to make the effort to think about what ''could'' happen in the +event of a regression. + + * This both shows the SRU team that the risks have been considered, +and provides guidance to testers in regression-testing the SRU. + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + When enabling ESM on precise, then upgrading that to current trusty, and from there to the proposed new trusty client (see #1832757), ESM gets disabled. Upstream bug: https://github.com/CanonicalLtd/ubuntu-advantage- client/issues/899 The reason is that d/postinst, when dealing with this upgrade path, was conditioning a file rename on the package upgrade coming from version 1, which is the precise one. The fix is to drop that conditional, since the filename we intend to rename is the precise one (it has "precise" in its name) and there is no need to check for the version. ** Description changed: [Impact] + When enabling ESM on precise, then upgrading that to current trusty, and from there to the proposed new trusty client (see #1832757), ESM gets disabled. - * An explanation of the effects of the bug on users and - - * justification for backporting the fix to the stable release. - - * In addition, it is helpful, but not required, to include an -explanation of how the upload fixes this bug. - - [Test Case] - - * detailed instructions how to reproduce the bug - - * these should allow someone who is not familiar with the affected -package to reproduce the bug and verify that the updated package fixes -the problem. - - [Regression Potential] - - * discussion of how regressions are most likely to manifest as a result - of this change. - - * It is assumed that any SRU candidate patch is well-tested before -upload and has a low overall risk of regression, but it's important -to make the effort to think about what ''could'' happen in the -event of a regression. - - * This both shows the SRU team that the risks have been considered, -and provides guidance to testers in regression-testing the SRU. - - [Other Info] - - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance - - When enabling ESM on precise, then upgrading that to current trusty, and - from there to the proposed new trusty client (see #1832757), ESM gets - disabled. - - Upstream bug: https://github.com/CanonicalLtd/ubuntu-advantage- - client/issues/899 + This was found when executing test case (5) in the original SRU bug + #1832757. The reason is that d/postinst, when dealing with this upgrade path, was conditioning a file rename on the package upgrade coming from version 1, which is the precise one. The fix is to drop that conditional, since the filename we intend to rename is the precise one (it has "precise" in its name) and there is no need to check for the version. + + [Test Case] + + * detailed instructions how to reproduce the bug + + * these should allow someone who is not familiar with the affected + package to reproduce the bug and verify that the updated package fixes + the problem. + + [Regression Potential] + + * discussion of how regressions are most likely to manifest as a result + of this change. + + * It is assumed that any SRU candidate patch is well-tested before + upload and has a low overall risk of regression, but it's important + to make the effort to think about what ''could'' happen in the + event of a regression. + + * This both shows the SRU team that the risks have been considered, + and provides guidance to testers in regression-testing the SRU. + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance -- You received this bug notification because you are a member of Ubuntu Server,
[Bug 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
** Also affects: ubuntu-advantage-tools (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: ubuntu-advantage-tools (Ubuntu Trusty) Importance: Undecided => High ** Changed in: ubuntu-advantage-tools (Ubuntu Trusty) Status: New => In Progress ** Changed in: ubuntu-advantage-tools (Ubuntu Trusty) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: In Progress => Triaged ** Changed in: ubuntu-advantage-tools (Ubuntu) Importance: High => Low ** Changed in: ubuntu-advantage-tools (Ubuntu) Assignee: Andreas Hasenack (ahasenack) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+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 1850672] [NEW] "precise esm -> trusty -> trusty new client" upgrade disables ESM
Public bug reported: When enabling ESM on precise, then upgrading that to current trusty, and from there to the proposed new trusty client (see #1832757), ESM gets disabled. Upstream bug: https://github.com/CanonicalLtd/ubuntu-advantage- client/issues/899 The reason is that d/postinst, when dealing with this upgrade path, was conditioning a file rename on the package upgrade coming from version 1, which is the precise one. The fix is to drop that conditional, since the filename we intend to rename is the precise one (it has "precise" in its name) and there is no need to check for the version. ** Affects: ubuntu-advantage-script Importance: Unknown Status: Unknown ** Affects: ubuntu-advantage-tools (Ubuntu) Importance: High Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: New => In Progress ** Bug watch added: github.com/CanonicalLtd/ubuntu-advantage-client/issues #899 https://github.com/CanonicalLtd/ubuntu-advantage-client/issues/899 ** Also affects: ubuntu-advantage-script via https://github.com/CanonicalLtd/ubuntu-advantage-client/issues/899 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+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 1832757] Re: Update ubuntu-advantage-client
An 19.6~ubuntu14.04.3 upload with the fix will be done shortly. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832757 Title: Update ubuntu-advantage-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1832757/+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 1832757] Re: Update ubuntu-advantage-client
Test (5a) failed. The scenario is an upgrade from precise with esm enabled to trusty, and then to trusty-proposed. What happened is that after installing the trusty proposed package in this sequence, ESM became disabled. Upstream bug: https://github.com/CanonicalLtd/ubuntu-advantage- client/issues/899 ** Bug watch added: github.com/CanonicalLtd/ubuntu-advantage-client/issues #899 https://github.com/CanonicalLtd/ubuntu-advantage-client/issues/899 ** Tags removed: verification-needed-trusty ** Tags added: verification-failed-trusty -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832757 Title: Update ubuntu-advantage-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1832757/+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 1845334] Re: Update DEP8 test to python3
I'll resume distro packaging work starting tomorrow, thanks for the ping. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1845334 Title: Update DEP8 test to python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1845334/+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 1832757] Re: Update ubuntu-advantage-client
trusty verification, test case (4) Both scenarios, (a) and (b), start from trusty with u-a-t already installed from updates Test (a): enable esm -> upgrade to proposed Test (b): upgrade to proposed -> ua attach (which enables esm) The u-a-t package from updates that was used is: 10ubuntu0.14.04.4 The u-a-t package from proposed that was used is: 19.6~ubuntu14.04.2 At the end, this is the diff between the files on both containers. I manually removed uninteresting bits like /etc/hostname, /etc/ssh/*, cloud-init data, etc. This is what remains: 1) output of diff -uNr 4a 4b (minus the manually excluded hunks described above): --- 4a/etc/apt/auth.conf.d/90ubuntu-advantage +++ 4b/etc/apt/auth.conf.d/90ubuntu-advantage @@ -1 +1 @@ -machine esm.ubuntu.com/ login $user password $pass +machine esm.ubuntu.com/ login bearer password $newverylongpass Since (a) didn't run ua attach, but just upgraded to the proposed package, the credentials were not migrated to the new bearer token. ESM keeps working without this step, but "ua status" will say the machine is unattached. This is expected and explained in the last paragraph of the "[Other Info]" section in this SRU bug. --- 4a/etc/apt/sources.list.d/ubuntu-esm-infra-trusty.list +++ 4b/etc/apt/sources.list.d/ubuntu-esm-infra-trusty.list @@ -1,5 +1,4 @@ -deb https://esm.ubuntu.com/ubuntu trusty-security main -# deb-src https://esm.ubuntu.com/ubuntu trusty-security main - -deb https://esm.ubuntu.com/ubuntu trusty-updates main -# deb-src https://esm.ubuntu.com/ubuntu trusty-updates main +deb https://esm.ubuntu.com/ubuntu trusty-infra-security main +# deb-src https://esm.ubuntu.com/ubuntu trusty-infra-security main +deb https://esm.ubuntu.com/ubuntu trusty-infra-updates main +# deb-src https://esm.ubuntu.com/ubuntu trusty-infra-updates main Only an "ua attach" command will rewrite the esm pockets in the sources.list snippet to include the "infra" word. The old names, without "infra", will not be removed from the ESM server for trusty, so having step (a) keep using the old names isn't a problem. 2) diff -u 4a/files.list 4b/files.list Manually removed the following diff noise: - /var/cache/apt/archives - /var/lib/cloud/instances - /var/log/auth.log and /var/log/dmesg.1.gz The following hunks remain: --- 4a/files.list +++ 4b/files.list @@ -29617,10 +29623,10 @@ /var/lib/apt/lists/br.archive.ubuntu.com_ubuntu_dists_trusty-proposed_InRelease /var/lib/apt/lists/br.archive.ubuntu.com_ubuntu_dists_trusty-proposed_main_binary-amd64_Packages /var/lib/apt/lists/br.archive.ubuntu.com_ubuntu_dists_trusty-proposed_main_i18n_Translation-en -/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-security_InRelease -/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-security_main_binary-amd64_Packages -/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-updates_InRelease -/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-updates_main_binary-amd64_Packages +/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-security_InRelease +/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-security_main_binary-amd64_Packages +/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-updates_InRelease +/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-updates_main_binary-amd64_Packages /var/lib/apt/lists/lock /var/lib/apt/lists/partial /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_trusty-security_InRelease (a) is still using the trusty pockets without the "infra" name, and (b), because it ran an "ua attach", that also runs "apt update", therefore the infra pockets are shown in apt's lists/ directory for (b) and not for (a). @@ -31900,6 +31953,15 @@ /var/lib/systemd/deb-systemd-helper-enabled/ssh.socket.dsh-also /var/lib/systemd/deb-systemd-helper-enabled/syslog.service /var/lib/ubuntu-advantage +/var/lib/ubuntu-advantage/private +/var/lib/ubuntu-advantage/private/machine-access-cc-eal.json +/var/lib/ubuntu-advantage/private/machine-access-esm-infra.json +/var/lib/ubuntu-advantage/private/machine-access-fips.json +/var/lib/ubuntu-advantage/private/machine-access-fips-updates.json +/var/lib/ubuntu-advantage/private/machine-access-livepatch.json +/var/lib/ubuntu-advantage/private/machine-access-support.json +/var/lib/ubuntu-advantage/private/machine-token.json +/var/lib/ubuntu-advantage/status.json /var/lib/ubuntu-release-upgrader /var/lib/ubuntu-release-upgrader/release-upgrade-available /var/lib/ucf Since (b) ran "ua attach", that fully migrated that setup to the new client, which is then showing content in its data directory at /var/lib /ubuntu-advantage/. The (a) case did not run attach. I declare test case (4) as having succeeded. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832757 Title: Update ubuntu-advantage-client To manage notifications about this bug go to:
[Bug 1832757] Re: Update ubuntu-advantage-client
trusty verification, test case (3)
Both start from fresh trusty minimal with no u-a-t installed
a) u-a-t updates -> enable esm -> upgrade proposed
b) u-a-t proposed -> attach
The u-a-t package from updates that was used is: 10ubuntu0.14.04.4
The u-a-t package from proposed that was used is: 19.6~ubuntu14.04.2
1) Output of diff -uNr /tank/trusty-3{a,b}/etc/apt. An explanation follows each
hunk:
--- /tank/trusty-3a/etc/apt/auth.conf.d/90ubuntu-advantage
+++ /tank/trusty-3b/etc/apt/auth.conf.d/90ubuntu-advantage
@@ -1 +1 @@
-machine esm.ubuntu.com/ login $user password $pass
+machine esm.ubuntu.com/ login bearer password $reallylongpass
Since (a) didn't run ua attach, but just upgraded to the proposed
package, the credentials were not migrated to the new bearer token. ESM
keeps working without this step, but "ua status" will say the machine is
unattached. This is expected and explained in the last paragraph of the
"[Other Info]" section in this SRU bug.
--- /tank/trusty-3a/etc/apt/sources.list.d/ubuntu-esm-infra-trusty.list
+++ /tank/trusty-3b/etc/apt/sources.list.d/ubuntu-esm-infra-trusty.list
@@ -1,5 +1,4 @@
-deb https://esm.ubuntu.com/ubuntu trusty-security main
-# deb-src https://esm.ubuntu.com/ubuntu trusty-security main
-
-deb https://esm.ubuntu.com/ubuntu trusty-updates main
-# deb-src https://esm.ubuntu.com/ubuntu trusty-updates main
+deb https://esm.ubuntu.com/ubuntu trusty-infra-security main
+# deb-src https://esm.ubuntu.com/ubuntu trusty-infra-security main
+deb https://esm.ubuntu.com/ubuntu trusty-infra-updates main
+# deb-src https://esm.ubuntu.com/ubuntu trusty-infra-updates main
Only an "ua attach" command will rewrite the esm pockets in the
sources.list snippet to include the "infra" word. The old names, without
"infra", will not be removed from the ESM server for trusty, so having
step (a) keep using the old names isn't a problem.
2) File listing diff. An explanation follows each hunk:
--- trusty-3a.list
+++ trusty-3b.list
@@ -13723,7 +13723,6 @@
/var/cache/apt/archives/sysv-rc_2.88dsf-41ubuntu6_all.deb
/var/cache/apt/archives/tar_1.27.1-1_amd64.deb
/var/cache/apt/archives/tzdata_2014b-1_all.deb
-/var/cache/apt/archives/ubuntu-advantage-tools_10ubuntu0.14.04.4_all.deb
/var/cache/apt/archives/ubuntu-advantage-tools_19.6~ubuntu14.04.2_amd64.deb
/var/cache/apt/archives/ubuntu-keyring_2012.05.19_all.deb
/var/cache/apt/archives/ucf_3.0027+nmu1_all.deb
(b) didn't go through trusty-updates, therefore that package isn't
cached.
@@ -13765,10 +13764,10 @@
/var/lib/apt/lists/br.archive.ubuntu.com_ubuntu_dists_trusty-updates_InRelease
/var/lib/apt/lists/br.archive.ubuntu.com_ubuntu_dists_trusty-updates_main_binary-amd64_Packages
/var/lib/apt/lists/br.archive.ubuntu.com_ubuntu_dists_trusty-updates_main_i18n_Translation-en
-/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-security_InRelease
-/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-security_main_binary-amd64_Packages
-/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-updates_InRelease
-/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-updates_main_binary-amd64_Packages
+/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-security_InRelease
+/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-security_main_binary-amd64_Packages
+/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-updates_InRelease
+/var/lib/apt/lists/esm.ubuntu.com_ubuntu_dists_trusty-infra-updates_main_binary-amd64_Packages
/var/lib/apt/lists/lock
/var/lib/apt/lists/partial
/var/lib/apt/mirrors
(a) is still using the trusty pockets without the "infra" name, and (b),
because it ran an "ua attach", that also runs "apt update", therefore
the infra pockets are shown in apt's lists/ directory.
@@ -14881,6 +14880,15 @@
/var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also
/var/lib/systemd/deb-systemd-helper-enabled/syslog.service
/var/lib/ubuntu-advantage
+/var/lib/ubuntu-advantage/machine-id
+/var/lib/ubuntu-advantage/private
+/var/lib/ubuntu-advantage/private/machine-access-cc-eal.json
+/var/lib/ubuntu-advantage/private/machine-access-esm-infra.json
+/var/lib/ubuntu-advantage/private/machine-access-fips.json
+/var/lib/ubuntu-advantage/private/machine-access-fips-updates.json
+/var/lib/ubuntu-advantage/private/machine-access-livepatch.json
+/var/lib/ubuntu-advantage/private/machine-access-support.json
+/var/lib/ubuntu-advantage/private/machine-token.json
/var/lib/ubuntu-advantage/status.json
/var/lib/ucf
/var/lib/ucf/cache
Since (b) ran "ua attach", that fully migrated that setup to the new
client, which is then showing content in its data directory at /var/lib
/ubuntu-advantage/. The (a) case did not run attach.
I declare test case (3) as having succeeded.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ubuntu-advantage-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1832757
Title:
Update ubuntu-advantage-client
To manage
[Bug 1849972] Re: apt list --upgradable shows no additional updates
I saw something similar a while back, and had a conversation with juliank about it: out 09 11:22:08juliank: but apt list --upgradable is showing: out 09 11:22:12apport/trusty-updates,trusty-security,now 2.14.1-0ubuntu3.29 all [installed,upgradable to: 2.14.1-0ubuntu3.29] out 09 11:22:19i.e. upgradable to the same version (...) out 09 11:36:04andreas: this is a display bug in apt list, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753297 out 09 11:36:33Caused by weird behavior in the old pinning implementation, the fix for that is more like a workaround out 09 11:40:20trusty's pinning implementation is not very good out 09 11:41:17 * apt-pkg/cachefile.cc: out 09 11:41:20 - ensure we have a Policy in CacheFile.BuildDepCache() out 09 11:41:25maybe that's all that's needed really out 09 11:49:19andreas: so we could fix that in ESM I guess, it's inserting two lines in cachefile.cc: https://paste.ubuntu.com/p/5FsRtcySx8/ out 09 11:50:23the problem was that pkgDepCache was called with Policy == NULL because Policy was never initialized out 09 11:50:36other releases are not affected out 09 11:52:03this caused a mismatch, because depcache never saw the policy and calculated that apport is upgradable to esm out 09 11:52:17but then we print the candidate version based on policy, and it's the same one :D out 09 12:00:21 * fginther has quit (Ping timeout: 121 seconds) out 09 12:06:18 * fginther (fgint...@50-82-191-167.client.mchsi.com) has joined out 09 12:07:26andreas: Created https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1847496 but I'm not sure about the procedure here ** Bug watch added: Debian Bug tracker #753297 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753297 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1849972 Title: apt list --upgradable shows no additional updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1849972/+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 1849972] Re: apt list --upgradable shows no additional updates
Have you used apt 1.0.1ubuntu2.24 ? It should have the fix for the bug that was filed during the conversation above, which I'm assuming is the same as this one. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1849972 Title: apt list --upgradable shows no additional updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1849972/+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 1849851] [NEW] Drop python3-flake8 build-dep on trusty
Public bug reported: In trusty, python3-flake8 is in universe, and back then (trusty times) it wasn't allowed to have such a build dependency even if the final result didn't depend on the universe package. In this case, it's used to run a flake8 check at package build time, so it indeed doesn't grow a dependency on the universe package, but it's still not allowed for trusty. ** Affects: ubuntu-advantage-tools (Ubuntu) Importance: Critical Assignee: Andreas Hasenack (ahasenack) Status: Fix Released ** Affects: ubuntu-advantage-tools (Ubuntu Trusty) Importance: Critical Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Also affects: ubuntu-advantage-tools (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: ubuntu-advantage-tools (Ubuntu Trusty) Status: New => In Progress ** Changed in: ubuntu-advantage-tools (Ubuntu Trusty) Importance: Undecided => Critical ** Changed in: ubuntu-advantage-tools (Ubuntu Trusty) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1849851 Title: Drop python3-flake8 build-dep on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1849851/+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 1798786] Re: can't retrieve gmail emails. fetchmail: OU=No SNI provided; please fix your client./CN=invalid2.invalid
Thanks for reporting that here: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1847716 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1798786 Title: can't retrieve gmail emails. fetchmail: OU=No SNI provided; please fix your client./CN=invalid2.invalid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1798786/+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 1832757] Re: Update ubuntu-advantage-client
** Description changed: [Impact] This is a major rewrite of ubuntu-advantage-client. This version introduces an updated command line interface (UA Client) to simplify some interaction with Ubuntu Advantage support offerings, and interacts with a new service backend built specifically for this new streamlined experience. - Disco and Eoan already have this new version (but slightly older), but - trusty, xenial, bionic and cosmic do not. This update is for trusty only - at the moment, because the other LTSs and later releases have other - services available under the UA umbrella which haven't yet been fully - converted to the new backend. + Disco, Eoan, and Focal already have this rewrite (but an older version + of it), but trusty, xenial, bionic and cosmic do not. This update is for + trusty only at the moment, because the other LTSs and later releases + have other services available under the UA umbrella which haven't yet + been fully converted to the new backend. [Test Case] There are free services available for Trusty and anyone with an ubuntu one account can try them out with the new client. - You can sign up interactively by just typing: - - sudo ua attach - - That will prompt you for your ubuntu one login credentials, and 2FA if - needed, and enable ESM and Livepatch (the latter if running an HWE - kernel). - - Alternatively, you can go to https://auth.contracts.canonical.com/, - obtain a token, and attach your machine with: + In order to attach a machine to UA, first obtain a token at + https://auth.contracts.canonical.com/. With that token, attach the + machine with this command: sudo ua attach + + If that's successful, you will have ESM-infra enabled at the end. Additional test cases to confirm that the package correctly handles upgrades for all relevant cases: 2. a. Start with a fresh Ubuntu instance which does not have u-a-t installed (i.e. ubuntu-minimal is not installed). Install u-a-t from -updates. Do not enable ua. Upgrade to u-a-t from -proposed. b. In an identical instance, install u-a-t from -proposed. c. Confirm that the on-disk results of a) and b) are identical. 3. a. Start with a fresh Ubuntu instance which does not have u-a-t installed (i.e. ubuntu-minimal is not installed). Install u-a-t from -updates. Enable esm with 'ubuntu-advantage enable-esm'. Upgrade to u-a-t from -proposed. b. In an identical instance, install u-a-t from -proposed. Enable esm with 'ubuntu-advantage attach'. c. Confirm that the on-disk results of a) and b) are identical. 4. a. Start with a fresh Ubuntu instance which does have u-a-t installed. Enable esm with 'ubuntu-advantage enable-esm'. Upgrade to u-a-t from -proposed. b. In an identical instance, upgrade to u-a-t from -proposed. Enable esm with 'ubuntu-advantage attach'. c. Confirm that the on-disk results of a) and b) are identical. 5. a. Start with a fresh Ubuntu *precise* instance which does have u-a-t installed and esm enabled. Dist-upgrade to trusty, then upgrade to u-a-t from -proposed. b. In an identical instance, dist-upgrade to trusty with -proposed enabled. c. Confirm that the on-disk results of a) and b) are identical. [Regression Potential] This is a major rewrite from bash to python3 and there are changes in behavior. - new services will be listed, but not avaialble for trusty, only for later LTSs - even when ESM is not enabled, an apt hook will advertise the availability of updates in that repository. This hook has failed in the past while this package was in disco, and that failed the apt transaction. This has of course been fixed since then (see #1824523 and #1824523). [Other Info] This is the FFe bug that got this rewrite into Disco at that time: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1814157 Development of this client is happening on github: https://github.com/CanonicalLtd/ubuntu-advantage-client The GPG keys can be verified by checking the signed release files over https. Respectively: CC (not available on trusty atm): https://esm.ubuntu.com/cc/ubuntu/dists/xenial/InRelease FIPS (not available on trusty atm): https://esm.ubuntu.com/fips/ubuntu/dists/xenial/InRelease FIPS-updates (not available on trusty atm): https://esm.ubuntu.com/fips-updates/ubuntu/dists/xenial-updates/InRelease ESM: https://esm.ubuntu.com/ubuntu/dists/trusty-updates/InRelease and https://esm.ubuntu.com/ubuntu/dists/trusty-security/InRelease cis-audit is not ready and we don't have a gpg key for it yet, so we are shpping a placeholder file in the package called ubuntu- securitybenchmarks-keyring.gpg and that is a zero-sized file. Since cis- audit is not available for trusty, and gpg keyrings are only copied over to /etc/apt/trusted.gpg.d/ at enable time, this isn't an issue. And even if it was copied over to that directory, an empty file there doesn't cause issues. The
[Bug 1832757] Re: Update ubuntu-advantage-client
** Changed in: ubuntu-advantage-tools (Ubuntu Trusty) Status: In Progress => Triaged ** Changed in: ubuntu-advantage-tools (Ubuntu Trusty) Assignee: Andreas Hasenack (ahasenack) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832757 Title: Update ubuntu-advantage-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1832757/+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 1848237] [NEW] amd64-only test running on i386
Public bug reported:
Some tests in d/t/control are not meant to be run on non-amd64 architectures.
The test script tries to detect this and skip them:
arch = platform.machine()
if sys.argv[1].startswith('isa_') and arch == 'x86_64':
print("Skipping {} test for {} architecture".format(sys.argv[1], arch))
else:
...
In eoan, at some point during the development cycle, the VM running i386 tests
is actually on an amd64 kernel:
"""
...
-name adt-eoan-i386-python-pyeclib-20191014-091043 --image
adt/ubuntu-eoan-i386-server
...
Get:5 http://ftpmaster.internal/ubuntu eoan-proposed/universe Sources [127 kB]
Get:6 http://ftpmaster.internal/ubuntu eoan-proposed/main amd64 Packages [18.0
kB]
Get:7 http://ftpmaster.internal/ubuntu eoan-proposed/main i386 Packages [12.9
kB]
...
linux-generic:amd64 is already the newest version (5.3.0.18.21).
...
utopkgtest [09:11:51]: testbed running kernel: Linux 5.3.0-18-generic
#19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019
autopkgtest [09:11:51]: testbed dpkg architecture: i386
"""
In such an environment, platform.machine() will return "x86_64", and the test
will be run, but fail:
autopkgtest [09:22:26]: test command7: python debian/tests/encode-decode.py
isa_l_rs_vand
autopkgtest [09:22:26]: test command7: [---
Traceback (most recent call last):
File "debian/tests/encode-decode.py", line 15, in
ec = ECDriver(k=3, m=3, hd=3, ec_type=sys.argv[1])
File "/usr/lib/python2.7/dist-packages/pyeclib/ec_iface.py", line 212, in
__init__
validate=int(self.validate)
File "/usr/lib/python2.7/dist-packages/pyeclib/utils.py", line 73, in
create_instance
instance = object_class(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pyeclib/core.py", line 61, in __init__
validate)
pyeclib.ec_iface.ECBackendInstanceNotAvailable: pyeclib_c_init ERROR: Backend
instance not found. Please inspect syslog for liberasurecode error report.
init: autopkgtest [09:22:26]: test command7: ---]
It's probably best to use "dpkg --architecture" for this check.
** Affects: python-pyeclib (Ubuntu)
Importance: Undecided
Status: New
** Affects: six (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
** Also affects: six (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to six in Ubuntu.
https://bugs.launchpad.net/bugs/1848237
Title:
amd64-only test running on i386
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pyeclib/+bug/1848237/+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 1846506] Re: autopkgtest fail in Eoan
The python-azure test failed in bileto in the same way, so it can be used to further troubleshoot this issue. My first attempt would be to unset the http_proxy variable, or set it to localhost so connections fail, and see what happens. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-cryptography in Ubuntu. https://bugs.launchpad.net/bugs/1846506 Title: autopkgtest fail in Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-azure/+bug/1846506/+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 1846506] Re: autopkgtest fail in Eoan
Given the tests pass locally in a container (autopkgtest ... -- lxd ubuntu-daily;eoan), I'm trying a bileto run (https://bileto.ubuntu.com/#/ticket/3818) to see if that reproduces the test failure. If yes, then I can use that platform for troubleshooting. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-cryptography in Ubuntu. https://bugs.launchpad.net/bugs/1846506 Title: autopkgtest fail in Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-azure/+bug/1846506/+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 1846237] Re: Kernel Panic while virsh dump of Guest with 300G RAM is triggered.
comment #4 suggested that the panic only happened because kernel.softlockup_panic was set to 1, was that verified? -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1846237 Title: Kernel Panic while virsh dump of Guest with 300G RAM is triggered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1846237/+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 1647285] Re: SSL trust not system-wide
This isn't "just" a bug, it's a roadmap item in my view, as many products are affected. It needs a spec, like in the fedora case. I agree that it would be awesome to have this. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1647285 Title: SSL trust not system-wide To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+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 1845652] Re: rsync sends everything, not just changes
When using vfat and running rsync twice, this is the diff in the stats output: --- log1.vfat 2019-10-08 11:43:04.381667860 -0300 +++ log2.vfat 2019-10-08 11:43:17.609728451 -0300 @@ -1,5 +1,5 @@ Number of files: 78 (reg: 77, dir: 1) -Number of created files: 77 (reg: 77) +Number of created files: 0 Number of deleted files: 0 Number of regular files transferred: 77 Total file size: 3,990,531 bytes @@ -12,6 +12,6 @@ Total bytes sent: 3,996,271 Total bytes received: 8,830 -sent 3,996,271 bytes received 8,830 bytes 534,013.47 bytes/sec +sent 3,996,271 bytes received 8,830 bytes 2,670,067.33 bytes/sec total size is 3,990,531 speedup is 1.00 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1196) [sender=3.1.2] As expected, the files are transferred again, because rsync couldn't set the permissions or ownership. These concepts don't exist in vfat. When using ext4, the same rsync command, the diff between the two runs shows a different story: --- log1.ext4 2019-10-08 11:49:01.687411326 -0300 +++ log2.ext4 2019-10-08 11:49:11.795461543 -0300 @@ -1,16 +1,16 @@ Number of files: 78 (reg: 77, dir: 1) -Number of created files: 77 (reg: 77) -Number of deleted files: 1 (dir: 1) -Number of regular files transferred: 77 +Number of created files: 0 +Number of deleted files: 0 +Number of regular files transferred: 0 Total file size: 3,990,531 bytes -Total transferred file size: 3,990,531 bytes -Literal data: 3,990,531 bytes +Total transferred file size: 0 bytes +Literal data: 0 bytes Matched data: 0 bytes File list size: 0 File list generation time: 0.001 seconds File list transfer time: 0.000 seconds -Total bytes sent: 3,996,271 -Total bytes received: 1,504 +Total bytes sent: 1,598 +Total bytes received: 19 -sent 3,996,271 bytes received 1,504 bytes 7,995,550.00 bytes/sec -total size is 3,990,531 speedup is 1.00 +sent 1,598 bytes received 19 bytes 3,234.00 bytes/sec +total size is 3,990,531 speedup is 2,467.86 The rsync command I used was: rsync -v -a -r -W -p -o -g -t --delete --stats /testdata/ /media/andreas/dataext4/ /testdata was populated with a copy of all files in /usr/bin that start with "b*". I don't think the --exclusion parameters you used play a factor here. Can you please verify the target filesystem in your test case, and if rsync reported errors? And there are other scenarios, like outlined in comment #2. I guess, to summarize, we need a testcase. I showed you two cases with pendrives (vfat, and ext4), where what you describe does NOT happen. ** Changed in: rsync (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1845652 Title: rsync sends everything, not just changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1845652/+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 1845765] Re: asterisk-modules package built without amr_codec.so
** Changed in: asterisk (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1845765 Title: asterisk-modules package built without amr_codec.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1845765/+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 1846506] Re: autopkgtest fail in Eoan
Adding a task for python-cryptography so this bug shows up in the excuses page, even though it's not a bug in python-cryptography itself. ** Also affects: python-cryptography (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to python-cryptography in Ubuntu. https://bugs.launchpad.net/bugs/1846506 Title: autopkgtest fail in Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-azure/+bug/1846506/+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 1845765] Re: asterisk-modules package built without amr_codec.so
In bionic, that codec was added by a debian patch: debian/patches/amr.patch Description: Add AMR and AMR-WB codec modules supporting transcoding That patch is present in disco and eoan, but neither have the codec_arm.so file shipped, nor is codec_amr.c mentioned in their respective build logs. There is this difference in the build's configure output: bionic (with codec): checking for Encoder_Interface_init in -lopencore-amrnb... yes checking opencore-amrnb/interf_enc.h usability... yes checking opencore-amrnb/interf_enc.h presence... yes checking for opencore-amrnb/interf_enc.h... yes checking for D_IF_init in -lopencore-amrwb... yes checking opencore-amrwb/dec_if.h usability... yes checking opencore-amrwb/dec_if.h presence... yes checking for opencore-amrwb/dec_if.h... yes checking for E_IF_init in -lvo-amrwbenc... yes checking vo-amrwbenc/enc_if.h usability... yes checking vo-amrwbenc/enc_if.h presence... yes checking for vo-amrwbenc/enc_if.h... yes Disco (without): checking for Encoder_Interface_init in -lopencore-amrnb... yes checking opencore-amrnb/interf_enc.h usability... yes checking opencore-amrnb/interf_enc.h presence... yes checking for opencore-amrnb/interf_enc.h... yes checking for D_IF_init in -lopencore-amrwb... yes checking opencore-amrwb/dec_if.h usability... yes checking opencore-amrwb/dec_if.h presence... yes checking for opencore-amrwb/dec_if.h... yes checking for E_IF_init in -lvo-amrwbenc... no The file codec_amr.so is also not present in the debian buster package: https://packages.debian.org/buster/amd64/asterisk-modules/filelist -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1845765 Title: asterisk-modules package built without amr_codec.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1845765/+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 1845652] Re: rsync sends everything, not just changes
What's the filesystem on the target? If the target is vfat, for example, setting ownership and permissions won't work, and -W tells rsync to transfer the whole file. ** Changed in: rsync (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1845652 Title: rsync sends everything, not just changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1845652/+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 1843729] Re: byobu ftbfs in eoan
@cosmos-door, thanks for that merge request against upstream. We are just a few days away from Final Freeze, though. Would you perhaps be able to make a merge proposal against the packaging, with a quilt patch? That would be the ubuntu/devel branch, if you clone the repository according to the instructions in https://code.launchpad.net/ubuntu/+source/byobu -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1843729 Title: byobu ftbfs in eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1843729/+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 1847105] [NEW] very slow disk creation, snapshotting
Public bug reported: This is a regression in eoan for me. I use virt-manager to create vms, and I noticed that creating one now takes more than a minute. Looking at the process listing while the backing disk is being created, I see this qemu-img command line: 15658 ?Ssl0:00 /usr/sbin/libvirtd 23726 ?Sl 0:04 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=falloc,compat=1.1,lazy_refcounts /var/lib/libvirt/images/live-server.qcow2 41943040K If I run qemu-img with that preallocation parameter set, even on bionic, then it also takes a very long time. On eoan, for comparison: andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 lazy_refcounts=off refcount_bits=16 real0m0,016s user0m0,010s sys 0m0,006s andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 image: no-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 17K no-prealloc-image.qcow2 andreas@nsn7:~$ and now with preallocation=falloc: andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc with-prealloc-image.qcow2 40G Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 preallocation=falloc lazy_refcounts=off refcount_bits=16 real1m43,196s user0m3,564s sys 1m26,720s andreas@nsn7:~$ qemu-img info with-prealloc-image.qcow2 image: with-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 2.7M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs with-prealloc-image.qcow2 2,8Mwith-prealloc-image.qcow2 andreas@nsn7:~$ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libvirt-daemon 5.4.0-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Oct 7 11:36:03 2019 InstallationDate: Installed on 2019-10-07 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.nwfilter.allow-arp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-arp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp-server.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp-server.xml'] modified.conffile..etc.libvirt.nwfilter.allow-dhcp.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-dhcp.xml'] modified.conffile..etc.libvirt.nwfilter.allow-incoming-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.allow-ipv4.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/allow-ipv4.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic-gateway.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic-gateway.xml'] modified.conffile..etc.libvirt.nwfilter.clean-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/clean-traffic.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-ip-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-mac-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-arp-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-arp-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-ip-multicast.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-ip-multicast.xml'] modified.conffile..etc.libvirt.nwfilter.no-ip-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-ip-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-mac-broadcast.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-mac-broadcast.xml'] modified.conffile..etc.libvirt.nwfilter.no-mac-spoofing.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-mac-spoofing.xml'] modified.conffile..etc.libvirt.nwfilter.no-other-l2-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-other-l2-traffic.xml'] modified.conffile..etc.libvirt.nwfilter.no-other-rarp-traffic.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/nwfilter/no-other-rarp-traffic.xml'] modifie
[Bug 1828496] Re: service haproxy reload sometimes fails to pick up new TLS certificates
** Changed in: haproxy (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1828496 Title: service haproxy reload sometimes fails to pick up new TLS certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1828496/+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 1826158] Re: Failed to install guestOS ubuntu-19.04-live-server-amd64.iso(GA) in ESXi with new installer subiquity 19.04.5 when create VM with NVME disk
So, on the GA iso, one cannot get to the step where the installer is updated. Do you get at least to the language selection prompt, i.e., does the installer at least stop somewhere asking you a question? You say: "4. We get a continuous flash at early install stage." I ask because if you are able to switch to another console, you can update the installer manually with a command like: sudo snap refresh subiquity But if you can't get that far with the GA iso, then I think just an iso respin would fix this. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1826158 Title: Failed to install guestOS ubuntu-19.04-live-server-amd64.iso(GA) in ESXi with new installer subiquity 19.04.5 when create VM with NVME disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/probert/+bug/1826158/+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 1638210] Re: saidar segmentation fault
This may be tricky to reproduce reliably on a test machine, unless you own a system where it is already happening. In the upstream bug at https://github.com/libstatgrab/libstatgrab/issues/102, there is a hint that https://github.com/libstatgrab/libstatgrab/commit/84fd8c38ee4feb0117ed22ab56f6b46661411ec6 might fix the problem. For SRU purposes, we need a verification step. Would people affected by this be able to test a package from a ppa with that patch to see if it fixes the problem? ** Bug watch added: github.com/libstatgrab/libstatgrab/issues #102 https://github.com/libstatgrab/libstatgrab/issues/102 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1638210 Title: saidar segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libstatgrab/+bug/1638210/+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 1842701] Re: Apache2 Balancer Manager mod_proxy_balancer not working after Update
** Bug watch added: Debian Bug tracker #941202 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941202 ** Also affects: apache2 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941202 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1842701 Title: Apache2 Balancer Manager mod_proxy_balancer not working after Update To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1842701/+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 1845335] [NEW] Update DEP8 tests to python3
Public bug reported: d/t/test-squid.py should be updated to python3 ** Affects: squid (Ubuntu) Importance: Low Status: Triaged ** Tags: dep8 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/1845335 Title: Update DEP8 tests to python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1845335/+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 1845335] Re: Update DEP8 tests to python3
According to git log, https://git.launchpad.net/qa-regression- testing/tree/scripts/test-squid.py already got some changes to work with py3. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1845335 Title: Update DEP8 tests to python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1845335/+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 1845334] [NEW] Update DEP8 test to python3
Public bug reported: The postfix dep8 tests[1][2] should be updated to python3. Some work about this was already done in the qa-regression-testing[3][4] repository, which is where this test came from originally, so it should hopefully just be a matter of cherry-picking the needed fixes. We could also take the opportunity to update the script with new tests that have been added. Since postfix is a sync from debian, once we know the updated tests work with py3 on both debian and ubuntu, the changes should be proposed to Debian via salsa at https://salsa.debian.org/postfix-team/postfix-dev 1. https://git.launchpad.net/ubuntu/+source/postfix/tree/debian/tests/testlib.py 2. https://git.launchpad.net/ubuntu/+source/postfix/tree/debian/tests/test-postfix.py 3. https://git.launchpad.net/qa-regression-testing/tree/scripts/testlib.py 4. https://git.launchpad.net/qa-regression-testing/tree/scripts/test-postfix.py ** Affects: postfix (Ubuntu) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: Triaged -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1845334 Title: Update DEP8 test to python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1845334/+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 1843804] Re: DEP8 segfault on arm64
By blocking the ruby2.5 migration this also affects ruby2.5 (for tracking) ** Also affects: ruby2.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ruby2.5 in Ubuntu. https://bugs.launchpad.net/bugs/1843804 Title: DEP8 segfault on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1843804/+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 1810827] Re: /usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon
I mean the crash is not frequent enough. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1810827 Title: /usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1810827/+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 1810827] Re: /usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon
There is a fix available, but is not frequent enough and there is a simple workaround: restart instead of reload. Also only that specific "force group" config change is affected. ** Tags removed: server-next ** Also affects: samba (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: samba (Ubuntu) Status: Triaged => Fix Released ** Changed in: samba (Ubuntu Bionic) Status: New => Triaged ** Changed in: samba (Ubuntu Bionic) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1810827 Title: /usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1810827/+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 1516451] Re: check_disk plugin broken after upgrade to 15.10
** Changed in: nagios-plugins (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Tags removed: server-next -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1516451 Title: check_disk plugin broken after upgrade to 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1516451/+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 1804542] Re: [SRU] Multiple intermittent socket failures during name resolutions
Bryce, I think this can perhaps be proposed and uploaded, given the previous comments. For the actual [test] section of the sru, perhaps point at the comments above. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1804542 Title: [SRU] Multiple intermittent socket failures during name resolutions To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1804542/+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 1843806] Re: Please build with DNSTAP
It's part of our delta. If you clone bind9, you'll see the commit disabling it: commit 27364096b130d52beef7aaacfa5c824e3968a66d Author: Andreas Hasenack Date: Fri Jul 27 14:16:35 2018 -0300 - Don't build dnstap as it depends on universe packages: + d/control: drop build-depends on libfstrm-dev, libprotobuf-c-dev and protobuf-c-compiler (universe packages) + d/dnsutils.install: don't install dnstap + d/libdns1104.symbols: don't include dnstap symbols + d/rules: don't build dnstap nor install dnstap.proto You can just revert that to enable it iirc. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1843806 Title: Please build with DNSTAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1843806/+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 1843806] Re: Please build with DNSTAP
hm, I'm sorry, I may be mixing things up. The lmdb commit is another one: commit 4f9a9b60845feb1202020ec71bd6a9e7298e6e19 Author: Andreas Hasenack Date: Wed Jun 20 17:28:42 2018 -0300 - Build without lmdb support as that package is in Universe I don't remember now if lmdb was related to dnstap or not, I'm a bit confused. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1843806 Title: Please build with DNSTAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1843806/+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 1843806] Re: Please build with DNSTAP
Maybe you figured this out by now, but to use dnstap we need to MIR lmdb. And I just saw that the lmdb mir was accepted and it's in main in eoan: https://bugs.launchpad.net/ubuntu/+source/lmdb/+bug/1833745 So were we not in feature freeze, we could enable this... -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1843806 Title: Please build with DNSTAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1843806/+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 1843474] [NEW] /usr/bin/fetchmailconf not completely removed
Public bug reported: Saw this debian bug which also affects ubuntu: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939522 I did a release upgrade from disco to eoan, and even though it didn't fail the upgrade, the problem is there: Preparing to unpack .../142-fetchmail_6.4.0~rc4-1ubuntu1_amd64.deb ... Unpacking fetchmail (6.4.0~rc4-1ubuntu1) over (6.3.26-3ubuntu1) ... dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/bin/fetchmailconf', which is also in package fetchmailconf 6.3.26-3ubuntu1 dpkg: warning: overriding problem because --force enabled: dpkg: warning: trying to overwrite '/usr/share/man/man1/fetchmailconf.1.gz', which is also in package fetchmailconf 6.3.26-3ubuntu1 And fetchmailconf, the one still shipped but now in the fetchmail package, is busted: # fetchmailconf /usr/bin/fetchmailconf: 2: exec: :: not found # cat /usr/bin/fetchmailconf #! /bin/sh exec : /fetchmailconf.py "$@" This is fixed in fetchmail/6.4.0~rc4-2 unfortunately the long description of the fetchmail package still mentions fetchmailconf: """ ... The fetchmailconf package includes an interactive GUI configurator suitable for end-users. """ ** Affects: fetchmail (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to fetchmail in Ubuntu. https://bugs.launchpad.net/bugs/1843474 Title: /usr/bin/fetchmailconf not completely removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1843474/+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 1810827] Re: /usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon
Still in our queue. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1810827 Title: /usr/sbin/smbd:6:dump_core:smb_panic_s3:smb_panic:change_to_user_internal:smbd_smb2_request_check_tcon To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1810827/+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 1843032] Re: Storage graph error
*** This bug is a duplicate of bug 1843036 *** https://bugs.launchpad.net/bugs/1843036 I think this is a duplicate of bug #1843036, which is tracking a regression in net-snmp introduced by the previous update. Could you please follow that bug instead? There are packages available for testing already. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/1843032 Title: Storage graph error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1843032/+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 1843325] Re: FTBFS with glibc 2.30: sysctl.h is deprecated
In progress branch: https://code.launchpad.net/~ahasenack/ubuntu/+source/squid/+git/squid/+ref /eoan-squid-ftbfs-glibc-230 With accompanying ppa: https://launchpad.net/~ahasenack/+archive/ubuntu/squid-ftbfs-glibc-230 I'm waiting a bit to hear from upstream before uploading that to ubuntu. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/1843325 Title: FTBFS with glibc 2.30: sysctl.h is deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1843325/+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 1843032] Re: Storage graph error
5.7.3+dfsg-1ubuntu4.3 has this changelog entry: net-snmp (5.7.3+dfsg-1ubuntu4.3) xenial; urgency=medium * Skip autofs entries when calling statfs to prevent autofs being mounted on snmpd startup (LP: #1835818): - d/p/autofs-skip-autofs-entries.patch - d/p/autofs-fix-a-recently-introduced-bug.patch So this is skipping autofs mount points. Is that your case perhaps? -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/1843032 Title: Storage graph error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1843032/+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 1483751] Re: Issues traversing a sftp server when files or folders contain the character "]"
I filed https://bugzilla.mindrot.org/show_bug.cgi?id=3069 upstream ** Bug watch added: OpenSSH Portable Bugzilla #3069 https://bugzilla.mindrot.org/show_bug.cgi?id=3069 ** Also affects: openssh via https://bugzilla.mindrot.org/show_bug.cgi?id=3069 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1483751 Title: Issues traversing a sftp server when files or folders contain the character "]" To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1483751/+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 1843325] Re: FTBFS with glibc 2.30: sysctl.h is deprecated
** Changed in: squid (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: squid (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/1843325 Title: FTBFS with glibc 2.30: sysctl.h is deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1843325/+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 1843325] [NEW] FTBFS with glibc 2.30: sysctl.h is deprecated
Public bug reported: >From the announcement at >https://savannah.gnu.org/forum/forum.php?forum_id=9515: """ The Linux-specific header and the sysctl function have been deprecated and will be removed from a future version of glibc. Application should directly access /proc instead. For obtaining random bits, the getentropy function can be used. """ This results in a build failure: In file included from Eui48.cc:49: /usr/include/x86_64-linux-gnu/sys/sysctl.h:21:2: error: #warning "The header is deprecated and will be removed." [-Werror=cpp] 21 | #warning "The header is deprecated and will be removed." | ^~~ ** Affects: squid Importance: Unknown Status: Unknown ** Affects: squid (Ubuntu) Importance: High Status: New ** Tags: ftbfs ** Summary changed: - FTBFS glibc 2.30: sysctl.h is deprecated + FTBFS with glibc 2.30: sysctl.h is deprecated ** Bug watch added: Squid Bugzilla #4985 http://bugs.squid-cache.org/show_bug.cgi?id=4985 ** Also affects: squid via http://bugs.squid-cache.org/show_bug.cgi?id=4985 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/1843325 Title: FTBFS with glibc 2.30: sysctl.h is deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1843325/+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 1843031] Re: version `SAMBA_4.10.7' not found (libraries) in Samba 4.10.8
For what is worth, your log shows the /usr/local path for the samba binaries. This indicates that this is not an ubuntu package, but likely an installation from source or some other method. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1843031 Title: version `SAMBA_4.10.7' not found (libraries) in Samba 4.10.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1843031/+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 1842923] [NEW] FTBFS with glibc 2.30
Public bug reported: gcc -fPIC -I. -I../../include -DDEBIAN -DHAS_PCRE -DHAS_LDAP -DUSE_LDAP_SASL -DHAS_SQLITE -DMYORIGIN_FROM_FILE -DHAS_CDB -DHAS_LMDB -DHAS_MYSQL -I/usr/include/mysql -DHAS_PGSQL -I/usr/include/postgresql -DHAS_SQLITE -I/usr/include -DHAS_SSL -I/usr/include/openssl -DUSE_SASL_AUTH -I/usr/include/sasl -DUSE_CYRUS_SASL -DUSE_TLS -DHAS_DEV_URANDOM -DDEF_DAEMON_DIR=\"/usr/lib/postfix/sbin\" -DDEF_HTML_DIR=\"/usr/share/doc/postfix/html\" -DDEF_MANPAGE_DIR=\"/usr/share/man\" -DDEF_README_DIR=\"/usr/share/doc/postfix\" -DUSE_DYNAMIC_LIBS -DUSE_DYNAMIC_MAPS -Wmissing-prototypes -Wformat -Wno-comment -fPIC -g -O2 -I. -I../../include -DLINUX4 -c dns_str_resflags.c dns_str_resflags.c:55:13: warning: RES_AAONLY is deprecated 55 | "RES_AAONLY", RES_AAONLY, | ^ dns_str_resflags.c:57:13: warning: RES_PRIMARY is deprecated 57 | "RES_PRIMARY", RES_PRIMARY, | ^~~ dns_str_resflags.c:63:22: error: ‘RES_INSECURE1’ undeclared here (not in a function); did you mean ‘RES_RECURSE’? 63 | "RES_INSECURE1", RES_INSECURE1, | ^ | RES_RECURSE dns_str_resflags.c:64:22: error: ‘RES_INSECURE2’ undeclared here (not in a function); did you mean ‘RES_RECURSE’? 64 | "RES_INSECURE2", RES_INSECURE2, | ^ | RES_RECURSE dns_str_resflags.c:66:22: error: ‘RES_USE_INET6’ undeclared here (not in a function) 66 | "RES_USE_INET6", RES_USE_INET6, | ^ dns_str_resflags.c:71:13: warning: RES_NOCHECKNAME is deprecated 71 | "RES_NOCHECKNAME", RES_NOCHECKNAME, | ^~~ dns_str_resflags.c:76:13: warning: RES_KEEPTSIG is deprecated 76 | "RES_KEEPTSIG", RES_KEEPTSIG, | ^ dns_str_resflags.c:79:13: warning: RES_BLAST is deprecated 79 | "RES_BLAST", RES_BLAST, | ^~~ make: *** [Makefile:85: dns_str_resflags.o] Error 1 Also reported here: http://postfix.1071664.n5.nabble.com/build-failure-with-glibc-2-30-td102511.html With fix being in 3.5: """ etc. Fixed in Postfix 3.5. You cn delete the offending lines. """ I believe I located it in a hunk in this commit: https://github.com/vdukhovni/postfix/commit/3274c3cea9d739f86e84b65664aabb692e37e83f#diff-777bfb681a1cd539ddc8e1e606959ffa ** Affects: postfix (Ubuntu) Importance: High Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Tags: ftbfs -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1842923 Title: FTBFS with glibc 2.30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1842923/+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 1787834] Re: package winbind 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 failed to install/upgrade: installed winbind package post-installation script subprocess returned error exit status 1
Hello, I appreciate that you are having similar problems with winbind, but let's please use a new bug for that. This one here had a clear error in the configuration file. Steven, I would appreciate a new bug with details of your case, in particular, the config file and the ordering of events that are leading to a postinst failure. I've seen failures in automated deploys where winbind is started before being correctly joined to a domain, or something of the sort. We should definitely find a way to streamline that, if this is the case you are describing. The bits you mentioned are added by debhelper automatically to any package shipping systemd and/or sysv scripts. This is what is in the samba source package regarding winbind.postinst, for example: """ #! /bin/sh set -e getent group winbindd_priv >/dev/null 2>&1 || addgroup --system --force-badname --quiet winbindd_priv winbindd_privileged_socket_directory='/var/lib/samba/winbindd_privileged' mkdir -pv "$winbindd_privileged_socket_directory" chgrp -c winbindd_priv "$winbindd_privileged_socket_directory" chmod -c 0750 "$winbindd_privileged_socket_directory" #DEBHELPER# """ Here, #DEBHELPER# is the special text that is replaced by debhelper with other shell snippets as needed, and is what you probably saw. Regarding systemd and sysv, I agree that it is confusing to ship both. I have actually seen packages that also ship an upstart snippet along those two. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1787834 Title: package winbind 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 failed to install/upgrade: installed winbind package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1787834/+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 1834963] Re: apache dependency should be documented in package description
Bryce, is this something we could do for eoan's new php 7.3? -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1834963 Title: apache dependency should be documented in package description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1834963/+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 1842316] Re: DEP8 failures on xenial
** Changed in: ruby2.3 (Ubuntu) Status: New => Triaged ** Changed in: ruby2.3 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ruby2.3 in Ubuntu. https://bugs.launchpad.net/bugs/1842316 Title: DEP8 failures on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby2.3/+bug/1842316/+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 1834671] Re: TLSv1.3 client certificate authentication with renegotiation unsupported in browsers
This can be enabled in firefox 68+ by going to "about:config" and setting security.tls.enable_post_handshake_auth to true. It's disabled by default (from upstream), not sure why. ** Changed in: apache2 (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1834671 Title: TLSv1.3 client certificate authentication with renegotiation unsupported in browsers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1834671/+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 1723350] Re: sssd offline on boot, stays offline forever
A PR which might address this was posted to the sssd mailing list: https://github.com/SSSD/sssd/pull/864 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1723350 Title: sssd offline on boot, stays offline forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1723350/+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 1842316] [NEW] DEP8 failures on xenial
Public bug reported: While doing the SRU verification for bug #1834072, two DEP8 failures came up that we believe can be fixed: a) test/io/console/test_io_console.rb Apply patch from ruby2.5: https://github.com/ruby/ruby/commit/ac40fc997b6b27c4f61084d9f6fae83ea251d614 b) test/ruby/test_time_tz.rb Test fails with current tzdata in xenial. It check that these two should be equal, but they are not: ["1911-12-31 23:59:59 -0036", -2192, "-0036", "-00:36", "-00:36:32"], ["1912-01-01 00:36:31 +", 0, "+", "+00:00", "+00:00:00"], Downgrading tzdata in xenial to the release version (sudo apt install tzdata=2016d-0ubuntu0.16.04) makes the test pass: $ ruby2.3 test/runner.rb test/ruby/test_time_tz.rb Run options: # Running tests: Finished tests in 0.056691s, 1940.3463 tests/s, 18186.3371 assertions/s. 110 tests, 1031 assertions, 0 failures, 0 errors, 0 skips ruby -v: ruby 2.3.1p112 (2016-04-26) [s390x-linux-gnu] I believe the fix for (b) can be extracted from commit https://github.com/ruby/ruby/commit/4041a4ff759a5a757f032053cba40a4d1e69ee0e (untested) ** Affects: ruby2.3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ruby2.3 in Ubuntu. https://bugs.launchpad.net/bugs/1842316 Title: DEP8 failures on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby2.3/+bug/1842316/+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 1842076] [NEW] Eoan migration failing due to new lxml 4.4.1
Public bug reported: test_defined_xhtml() is failing with the newer lxml 4.4.1. Upstream has a fix at https://github.com/facelessuser/soupsieve/pull/152. That fix is included in the 1.9.3 release of soupsieve, but that includes changes that I believe would break the feature freeze of ubuntu at this time. ** Affects: soupsieve (Ubuntu) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to soupsieve in Ubuntu. https://bugs.launchpad.net/bugs/1842076 Title: Eoan migration failing due to new lxml 4.4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/soupsieve/+bug/1842076/+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 1841364] Re: AppArmor breaks the default Unbound installation in a live session
** Tags added: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to unbound in Ubuntu. https://bugs.launchpad.net/bugs/1841364 Title: AppArmor breaks the default Unbound installation in a live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1841364/+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 1841281] Re: ClamAV needs updated to reflect security fixes
Thanks, looks like clamav has bzip2 vendored in, in libclamav/nsis/bzlib.c (or at least bits of bzip2), and was missed in the CVE 2019-12900 bzip2 fix (https://people.canonical.com/~ubuntu- security/cve/2019/CVE-2019-12900.html) I flagged the bug as public security, and contacted the security team. ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1841281 Title: ClamAV needs updated to reflect security fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1841281/+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 1841281] Re: ClamAV needs updated to reflect security fixes
eoan has 0.101.4+dfsg-1ubuntu1 and has the fix. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to clamav in Ubuntu. https://bugs.launchpad.net/bugs/1841281 Title: ClamAV needs updated to reflect security fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1841281/+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 1840152] Re: Upgrade Nmap package from 7.70 to 7.80
This is now in eoan. ** Changed in: nmap (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to nmap in Ubuntu. https://bugs.launchpad.net/bugs/1840152 Title: Upgrade Nmap package from 7.70 to 7.80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nmap/+bug/1840152/+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 1840958] Re: defragfs.ocfs2 hangs (or takes too long) on arm64, ppc64el
** Summary changed: - defragfs.ocfs2 hangs (or takes too long) on arm64 + defragfs.ocfs2 hangs (or takes too long) on arm64, ppc64el -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/1840958 Title: defragfs.ocfs2 hangs (or takes too long) on arm64, ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ocfs2-tools/+bug/1840958/+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 1840958] Re: defragfs.ocfs2 hangs (or takes too long) on arm64
** Bug watch added: github.com/markfasheh/ocfs2-tools/issues #42 https://github.com/markfasheh/ocfs2-tools/issues/42 ** Also affects: ocfs2-tools via https://github.com/markfasheh/ocfs2-tools/issues/42 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/1840958 Title: defragfs.ocfs2 hangs (or takes too long) on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ocfs2-tools/+bug/1840958/+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 1840958] [NEW] defragfs.ocfs2 hangs (or takes too long) on arm64
Public bug reported: The new defragfs.ocfs2 test added in the 1.8.6-1 version of the package hangs (or takes too long) in our dep8 infrastructure. I reproduced this on an arm64 VM. The command stays silent, and consuming 99% of CPU. There is no I/O being done (checked with iostat and iotop). strace -f shows it stopping at this write: 2129 write(1, "defragfs.ocfs2 1.8.6\n", 21) = 21 Which is just a version print. Also tested with kernel 5.2.0-13-generic from eoan-proposed. debian's ci only runs this test on amd64 it seems. On an amd64 VM in the same cloud this tests completes in less than 1s. ** Affects: ocfs2-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/1840958 Title: defragfs.ocfs2 hangs (or takes too long) on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/1840958/+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 1840905] Re: krb5-user seems not installing on Bionic
Thanks for getting back to us! I'll mark the ticket as invalid, since it looks like it was just a local configuration error. If you later determine you reached this state due to a bug, please feel free to comment here. ** Changed in: krb5 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1840905 Title: krb5-user seems not installing on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1840905/+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
