from:"Lucas"

I confirmed the golang-github-docker-go-connections regression in
Hirsute and I filed another SRU bug to fix it:

https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-
connections/+bug/1930891

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219

Title:
  context deadline exceeded: unknown in containerd with latest runc
  version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1927219/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930891] Re: FTBFS in Hirsute is blocking runc migration

After further discussion within the team we decided that using
ubuntu0.21.04.1 is the best option here. There is the unlikely but
possible case where -3 is removed from impish-proposed and Impish gets
released with -2.

** Attachment added: "debdiff3"
   
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+attachment/5502484/+files/debdiff3

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930891

Title:
  FTBFS in Hirsute is blocking runc migration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930891] Re: FTBFS in Hirsute is blocking runc migration

Thanks for taking another look on this Utkarsh!

We append ubuntu0.XX.YY.1 to the version string when we have the same
version in 2 releases but in this case this version was released only in
Hirsute, Impish was not released yet :)

I'll be uploading the last debdiff I attached.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930891

Title:
  FTBFS in Hirsute is blocking runc migration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930891] Re: FTBFS in Hirsute is blocking runc migration

There you go, the attached debdiff has some DEP-3 headers in the added
patch.

** Attachment added: "debdiff2"
   
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+attachment/5502460/+files/debdiff2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930891

Title:
  FTBFS in Hirsute is blocking runc migration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930891] Re: FTBFS in Hirsute is blocking runc migration

I tried to just import the patch added by the Debian maintainer with no
changes but I think it is better to add some DEP-3 headers as you
mentioned. Checking the upstream bug tracker I noticed I filed this very
same bug some months ago :) but no replies so far:

https://github.com/docker/go-connections/issues/83

** Also affects: golang-github-docker-go-connections (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: golang-github-docker-go-connections (Ubuntu)
   Status: New => Fix Released

** Changed in: golang-github-docker-go-connections (Ubuntu Hirsute)
   Status: New => In Progress

** Bug watch added: github.com/docker/go-connections/issues #83
   https://github.com/docker/go-connections/issues/83

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930891

Title:
  FTBFS in Hirsute is blocking runc migration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930891] Re: FTBFS in Hirsute is blocking runc migration

The attached debdiff adds the patch to skip the tests as mentioned in
the description and fixes the FTBFS.

** Attachment added: "debdiff"

https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+attachment/5502458/+files/debdiff

** Description changed:

+ [Impact]
+
+ This FTBFS is avoiding runc users to get an important update (LP
+ #1927219). Moreover, the fix adopted by the Debian maintainer is minimal
+ and very simple.
+
+ [Test Plan]
+
+ Check if the package is building fine in Hirsute.
+
+ [Where problems could occur]
+
+ TBH I can't foresee any problem at all, no feature code is touched and
+ just a couple of tests are skippped. In case something bad happens will
+ be when running TLS related tests.
+
+ [Original message]
+
golang-github-docker-go-connections is FTBFS in Hirsute because a couple
of tests rely on an expired certificate. This failure is blocking the
runc migration.

The Debian maintainer fixed it in the next revision but it did not make
into Hirsute. The simple fix is to backport this patch as-is to Hirsute
to also skip those tests there.

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930891

Title:
FTBFS in Hirsute is blocking runc migration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930891] [NEW] FTBFS in Hirsute is blocking runc migration

Public bug reported:

golang-github-docker-go-connections is FTBFS in Hirsute because a couple
of tests rely on an expired certificate. This failure is blocking the
runc migration.

The Debian maintainer fixed it in the next revision but it did not make
into Hirsute. The simple fix is to backport this patch as-is to Hirsute
to also skip those tests there.

** Affects: golang-github-docker-go-connections (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930891

Title:
  FTBFS in Hirsute is blocking runc migration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929597] Re: [SRU] ubuntu-advantage-tools (27.0.2 -> 27.1) Xenial, Bionic, Focal, Groovy, Hirsute

2021-06-02 Thread Lucas Albuquerque Medeiros de Moura

** Description changed:

  [Impact]
- This release includes bug-fixes and we would like to
- make sure all of our supported customers have access to these
- improvements. The notable ones are:
+ This release provides fixes to numerous issues encountered and reported by 
users against the recent uatools 27.0.2 release. In general, there were 
situations or phrasing of things that causes user confusion, such as if trying 
to enable livepatch with an old snapd installed (LP: #1927329) and noise in 
logs from (non-critical) segfault messages (LP: #1929123). In addition, this 
includes some refinements to how we communicate product availability based on 
what the user already has installed.
+ 
+ See the changelog entry below for a full list of fixes and other
+ changes.
  
     * avoid segfault when comparing null Apt file origin to esm (LP: #1929123)
     * make cis service non-beta
     * livepatch: alert when snapd does not have wait cmd (LP: #1927329)
     * Do not show beta services in autocomplete (GH: #1594)
     * Block enabling fips if fips-updates once enabled (GH: #1600)
     * pro: obtain AWS IMDSv2 API token before trying to grab pkcs7 doc (GH: 
#1608)
     * Several tweaks to output and messages
+ 
+ Finally, these are the links for the notable github issues we are
+ solving in this release:
+ 
+ https://github.com/canonical/ubuntu-advantage-client/issues/1600
+ https://github.com/canonical/ubuntu-advantage-client/issues/1594
+ https://github.com/canonical/ubuntu-advantage-client/issues/1608
+ 
  
  See the changelog entry below for a full list of changes and bugs.
  
  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/UbuntuAdvantageToolsUpdates
  
  The ubuntu-advantage-tools team will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug.
  ubuntu-advantage-tools team members will not mark ‘verification-done’
  until this has happened.
  
  * Automated Test Results
  Attached in a comment below.
  
  * Manual Test Results
  
  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.
  
  This release mostly touches various messages output by ua-tools. If
  anyone is relying on particular output of ua-tools (which they
  shouldn't), then these changes will affect them.
  
  We overrode some lintian errors in this release. It is possible that if
  we overrode them too liberally, it could prevent us from getting
  legitimate lintian errors in the future.
  
  [Discussion]
  This is a follow up release to 27 that addresses the issues discovered and 
reported after that release. It does not introduce any major features. The 
closest thing to a "new feature" is removing beta status from the "cis" 
service, but that is not so much adding a new feature as it is making an 
existing feature more visible.
  
  [Changelog]
  ubuntu-advantage-tools (27.1) impish; urgency=medium
  
    * d/control:
  - specify debianutils min version
    * d/changelog:
  - fix lintian typos amend and redact incorrect 27.0 entry (GH: #1624)
    * lintian:
  - override ubuntu-advantage-pro wanted-by-target cloud-init
  - override xenial specific errors
  - rename package-specific overrides for pro vs tools
    * New upstream release 27.1:
  - apt-hook:
    + avoid segfault when comparing null Apt file origin to esm
  (LP: #1929123)
    + avoid wrapping static message formats at 80 chars
    + update go build flags based on lintian warnings (GH: #1626)
    + only add newlines for MOTD if message file length is non-zero
  - attach: do not print contract name if empty
  - autocomplete: Do not show beta services in autocomplete (GH: #1594)
  - cis:
    + make service non-beta
    + post enable message pointing to docs
    + update cis help url
  - docs: update releases.md per SRU review feedback on branch structuring
  - enable: correct messaging for beta service (GH: #1588)
  - errors: print a more helpful message when ssl fails (GH: #1618)
  - fips:
    + Block enabling fips if fips-updates once enabled (GH: #1600)
    + Update output of fips commands (GH: #1631)
  - livepatch: alert when snapd does not have wait cmd (LP: #1927329)
  - logging: remove tracebacks for UserFacingErrors (GH: #1586)
  - messaging:
    + Infra and Apps messaging is mutually exclusive (GH: #1573)
    + point to u.com/16-04 instead of u.com/advantage on ESM (GH: #1584)
    + separate _remove_msg_template. emit no warranty on infra disabled
  - pro: obtain AWS IMDSv2 API token before trying to grab pkcs7 doc
    (GH: #1608)
  - status: do not show info if not on contract (GH: #1592)
  - tests:
    + drop trusty specific tests
    + fix mock for handle_message_operations
    + fix motd message for bionic (GH: #1615)
    +

[Bug 1926819] Re: Empty MOTD on up-to-date systems (includes fix)

2021-06-01 Thread Lucas Albuquerque Medeiros de Moura

Also, regarding the autopkgtest failures we are seeing, they seem related to 
this update-manager bug:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1929865

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926819

Title:
  Empty MOTD on up-to-date systems (includes fix)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1926819/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926819] Re: Empty MOTD on up-to-date systems (includes fix)

2021-06-01 Thread Lucas Albuquerque Medeiros de Moura

I can confirm that the xenial, bionic, focal and hirsute packages are
working as expected.

To perform the verification I have used the following script:

--
#!/bin/sh
set -x

series=xenial
name=$series-dev


function generate_motd_message() {
message=$1
echo "---"
echo $message
lxc exec $name -- /usr/lib/update-notifier/update-motd-updates-available 
--force
lxc exec $name -- update-motd
echo "---"
}

function turn_distro_into_esm_mode() {
# guarantee that xenial distro is on ESM mode
lxc exec $name -- sed -i 's/is_esm_supported and 
is_not_currently_supported/True #comment/' /usr/lib/update-notifier/apt-check
}

function turn_distro_into_non_esm_mode() {
# guarantee that xenial distro is on ESM mode
lxc exec $name -- sed -i 's/True #comment/False/' 
/usr/lib/update-notifier/apt-check
}

function setup_update_notifier() {
lxc exec $name -- sh -c "cat  /dev/null"
}

function install_ua_from_branch() {
lxc exec $name --cwd /var/tmp/uac -- apt-get update
lxc exec $name --cwd /var/tmp/uac -- apt-get install make
lxc exec $name -- git clone 
https://github.com/canonical/ubuntu-advantage-client.git /var/tmp/uac
lxc exec $name --cwd /var/tmp/uac -- sh -c "make deps > /dev/null"
lxc exec $name --cwd /var/tmp/uac -- sh -c "DEB_BUILD_OPTIONS=nocheck 
dpkg-buildpackage -us -uc > /dev/null"
lxc exec $name -- apt-get remove ubuntu-advantage-tools --assume-yes
lxc exec $name --cwd /var/tmp/uac -- dpkg -i 
/var/tmp/ubuntu-advantage-tools_27.0_amd64.deb
lxc exec $name -- ua version
}

function install_ua() {
lxc exec $name -- add-apt-repository ppa:ua-client/daily -y
lxc exec $name -- sudo apt-get update
lxc exec $name -- sudo apt-get install ubuntu-advantage-tools -y
lxc exec $name -- ua version
lxc exec $name -- sudo apt-get update
}

function ua_disable_esm_apps() {
lxc exec $name -- sudo ua disable esm-apps
}

function install_all_upgrades() {
lxc exec $name -- sudo sh -c "apt update > /dev/null"
lxc exec $name -- sudo sh -c "apt upgrade -y > /dev/null"
}

function ua_attach() {
lxc exec $name -- sed -i 's/contracts.can/contracts.staging.can/' 
/etc/ubuntu-advantage/uaclient.conf
lxc exec $name -- ua attach $UACLIENT_BEHAVE_CONTRACT_TOKEN_STAGING
}

function ua_detach() {
lxc exec $name -- ua detach --assume-yes
}

function generate_ua_motd_messages() {
lxc exec $name -- python3 /usr/lib/ubuntu-advantage/ua_update_messaging.py
}

function install_update_motd() {
lxc exec $name -- apt install update-motd -yq 
}

function turn_esm_apps_into_non_beta() {
lxc exec $name -- sh -c "echo 'features:\n  allow_beta: true' >> 
/etc/ubuntu-advantage/uaclient.conf"
}

function update_contract_effectiveto() {
operation=$1
num_days=$2
replace_date=$(date -d "$date $operation$num_days days" 
+"%Y-%m-%dT00:00:00Z")
echo $replace_date

lxc exec $name -- sed -i "s/\"effectiveTo\": \"[^\"]*\"/\"effectiveTo\": 
\"$replace_date\"/g" /var/lib/ubuntu-advantage/private/machine-token.json
}


lxc delete --force $name
lxc launch ubuntu-daily:$series $name
sleep 10

setup_update_notifier
install_update_motd
generate_motd_message "$series: ua not installed"
install_ua
turn_esm_apps_into_non_beta
generate_ua_motd_messages
turn_distro_into_esm_mode
generate_motd_message "$series esm: ua not attached"
ua_attach
generate_ua_motd_messages
generate_motd_message "$series esm: ua attached"
ua_disable_esm_apps
generate_ua_motd_messages
generate_motd_message "$series esm: ua attached, apps disabled"
turn_distro_into_non_esm_mode
ua_detach
generate_ua_motd_messages
generate_motd_message "$series non-esm: ua not attached"
ua_attach
generate_ua_motd_messages
generate_motd_message "$series non-esm: ua attached"
update_contract_effectiveto - 30
generate_ua_motd_messages
generate_motd_message "$series esm: ua attached - contract expired"
update_contract_effectiveto - 5 
generate_ua_motd_messages
generate_motd_message "$series esm: ua attached - contract grace period"
update_contract_effectiveto + 5 
generate_ua_motd_messages
generate_motd_message "$series esm: ua attached - contract expire soon"
install_all_upgrades
generate_ua_motd_messages
generate_motd_message "$series esm: ua attached - all upgrades installed"

set +x
-

I verified the messages and they are consistent with the modifications
delivered by the proposed package

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal verification-needed-hirsute verification-needed-xenial
** Tags added:

[Bug 1926990] Re: update-notifier should not alert users about esm-apps in a ESM machine

2021-05-31 Thread Lucas Albuquerque Medeiros de Moura

** Changed in: update-notifier (Ubuntu Xenial)
 Assignee: (unassigned) => Lucas Albuquerque Medeiros de Moura (lamoura)

** Changed in: update-notifier (Ubuntu Bionic)
 Assignee: (unassigned) => Lucas Albuquerque Medeiros de Moura (lamoura)

** Changed in: update-notifier (Ubuntu Focal)
 Assignee: (unassigned) => Lucas Albuquerque Medeiros de Moura (lamoura)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926990

Title:
  update-notifier should not alert users about esm-apps in a ESM machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1926990/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927219] Re: context deadline exceeded: unknown in containerd with latest runc version

2021-05-31 Thread Lucas Kanashiro

Thanks for the testing Colin!

FYI I already uploaded the fix to Impish (development release) and as
soon it lands in the release pocket I can start the SRUs. At the moment
it is blocked by one regression:

https://people.canonical.com/~ubuntu-archive/proposed-
migration/impish/update_excuses.html#runc

I'll be working on that today to sort it out.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219

Title:
  context deadline exceeded: unknown in containerd with latest runc
  version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1927219/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929859] Re: wine and wine-development FTBFS with OpenLDAP 2.5

2021-05-28 Thread Lucas Kanashiro

Thanks for the patches Sergio. The changes LGTM, the patch was provided
by upstream (more like a workaround for the stable release) and they
said it'd be safe.

A small thing I'd fix in the changelog of both packages is to align the
text better. Instead of:

  * Fix FTBFS with OpenLDAP 2.5. (LP: #1929859)
- d/p/fixes/fix-ftbfs-openldap-2.5.patch: New patch to rename
wldap32's 'ldap_connect' to something else so that it doesn't conflict
with OpenLDAP's function with the same name.

I'd use:

  * Fix FTBFS with OpenLDAP 2.5. (LP: #1929859)
- d/p/fixes/fix-ftbfs-openldap-2.5.patch: New patch to rename
  wldap32's 'ldap_connect' to something else so that it doesn't conflict
  with OpenLDAP's function with the same name.

And the added patch is missing the Description header (in both packages)
which I think it is important.

Apart from that, +1 from me for both packages.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929859

Title:
  wine and wine-development FTBFS with OpenLDAP 2.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1929859/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929613] Re: Unblock version 0.1.1-2 from impish-proposed

2021-05-27 Thread Lucas Kanashiro

The maintainer will be uploading a fixed version (0.1.2-1) to Debian. We
will need to sync it when it gets available.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929613

Title:
  Unblock version 0.1.1-2 from impish-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bdebstrap/+bug/1929613/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927004] Re: [MIR] fence-agents

2021-05-27 Thread Lucas Kanashiro

The description of this bug was updated after the renaming of the binary
packages happened. Now we have src:fence-agents providing the following
binary packages in Impish:

- fence-agents (transitional package)
- fence-agents-common
- fence-agents-base
- fence-agents-extra

If I got everything right we are waiting for the +1 from the security
team. Is that correct?

** Description changed:

  [Availability]
  
  fence-agents is present in the Ubuntu archive since Precise, it builds
  fine and tests pass in all supported architectures. It was promoted in
  Precise:
  
  https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/897492
  
  In Trusty it was demoted, not sure about the reason.
  
  [Rationale]
  
  The fence-agents package provides a set of scripts used to fence
  (STONITH) nodes in a Corosync/Pacemaker cluster. It has been heavily
  used in HA solutions and the Ubuntu Server team is starting to support
  some of those scripts in the fence-agents-supported binary package. The
- supported agents have been tested daily via Jenkins jobs. The idea is to
- have fence-agents-common and fence-agents-supported binary packages in
- main.
+ curated agents have been tested daily via Jenkins jobs. The idea is to
+ have fence-agents-common and fence-agents-base binary packages in main.
  
  [Security]
  
  A couple of CVEs were reported against fence-agents:
  
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10153
  - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0104
  
  They are already fixed in the archive, CVE-2014-0104 in version 4.0.17-1
  and CVE-2019-10153 in version 4.3.3-2.
  
  [Quality assurance]
  
  The package is quite simple, no configuration file is needed and it
  works out-of-the-box. There is no outstanding bug reported upstream, nor
  in Debian and Ubuntu. The Debian maintainer is very active and willing
  to collaborate with us.
  
  Upstream does not provide a test suite but all the scripts are tested
  during build time to check if they at least can load everything needed.
  We also have some DEP-8 tests in place (they do not cover most of the
  scripts). But thinking about the quality of the package, all the agents
- shipped in the fence-agents-supported binary package are going to have
+ shipped in the fence-agents-base binary package are going to have
  automated tests running daily in our testing infrastructure.
  
  [UI standards]
  
  N/A
  
  [Dependencies]
  
  The binaries to be promoted to main are: fence-agents-common and fence-
- agents-supported. All their runtime dependencies are in main already
- which are python3-pexpect and python3-pycurl.
+ agents-base. All their runtime dependencies are in main already which
+ are python3-pexpect and python3-pycurl.
  
  [Standards compliance]
  
  There is one error reported by lintian:
  
  E: fence-agents-common: dir-or-file-in-var-run var/run/cluster/
  
  This directory is created by the package because a couple of agents
  expect this directory:
  
  agents/mpath/fence_mpath.py
  184:  options["--store-path"] = "/var/run/cluster"
  
  agents/scsi/fence_scsi.py
  16:STORE_PATH = "/var/run/cluster/fence_scsi"
  
  Those two fence agents are not in the supported list yet but a bug was
  filed upstream to get it fixed:
  
  https://github.com/ClusterLabs/fence-agents/issues/405
  
  [Maintenance]
  
  This package has been maintained by the Ubuntu Server team and this will
  continue to apply as part of the work on the HA (High Availability)
  stack.
  
  [Background information]
  
- In Impish, two new binary packages were created: fence-agents-common and
- fence-agents-supported. The -common package contains the common files
- used by supported and unsupported agents, and the -supported contains
- the agents supported by the Ubuntu Server team.
+ In Impish, three new binary packages were created: fence-agents-common
+ and fence-agents-base and fence-agents-extra. The -common package
+ contains the common files used by supported and unsupported agents, and
+ the -base contains the agents curated by the Ubuntu Server team.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927004

Title:
  [MIR] fence-agents

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1927004/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929744] Re: One moment, checking your subscription first Unexpected APT error. See /var/log/ubuntu-advantage.log

2021-05-26 Thread Lucas Albuquerque Medeiros de Moura

Hi bigsicret, thanks for reporting that. We will definitely take a look
on it.

However, this bug reporting is leaking your private token.
Please, contact customer services to invalidate that token and get a new one

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929744

Title:
  One moment, checking your subscription first Unexpected APT error. See
  /var/log/ubuntu-advantage.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1929744/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929613] Re: Unblock version 0.1.1-2 from impish-proposed

2021-05-26 Thread Lucas Kanashiro

There is still an issue with non-amd64 architectures. I filed a bug
upstream to start a discussion:

https://github.com/bdrung/bdebstrap/issues/2

** Bug watch added: github.com/bdrung/bdebstrap/issues #2
   https://github.com/bdrung/bdebstrap/issues/2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929613

Title:
  Unblock version 0.1.1-2 from impish-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bdebstrap/+bug/1929613/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927996] Re: /usr/lib/update-notifier/apt_check.py:FileNotFoundError:/usr/lib/update-notifier/apt_check.py@16:check_output:run:init:_execute_child

2021-05-26 Thread Lucas Albuquerque Medeiros de Moura

** Description changed:

  update-notifier-common does not depend on lsb-release and both
  apt_check.py and apt-cdrom-check both utilize lsb_release.
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
update-notifier.  This problem was most recently seen with package version 
3.192.40.1, the problem page at 
https://errors.ubuntu.com/problem/b26aeaa1e162c894747c195ce1b13a70c981e3eb 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.
+ 
+ --
+ 
+ [Impact]
+ Because update-notifier does not explicit have the `lsb-release` package as a 
dependency, users may install the package and rely on `apt-cdrom-check` to 
work, but it will fail, since it runs
+ the `lsb_release -sr` command on it.
+ 
+ [Test case]
+ 
+ To reproduce the issue:
+ 
+ 1. Launch a xenial container
+ 2. Install update-notifier on it
+ 3. Run apt-cache depends update-notifier-common
+ 4. Verify that lsb-release does not appear
+ 
+ To verify that the error is fixed:
+ 
+ 1. Install the new update-notifier from this ppa:
+ https://launchpad.net/~lamoura/+archive/ubuntu/update-notifier-test-ppa/
+ 2. Run apt-cache depends update-notifier-common
+ 3. Verify that lsb-release will now appear as a dependency
+ 
+ [Where problems could occur]
+ 
+ We are only adding a missing dependency to the package. I cannot think
+ of a problem that this might cause to the users of this package.
+ 
+ [Discussion]
+ 
+ We can verify that `apt-cdrom-check` does make use of the `lsb_release`
+ command. Since we don't have that dependency on the package control
+ file, errors can appear when users are executing/relying on that script.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927996

Title:
  /usr/lib/update-notifier/apt_check.py:FileNotFoundError:/usr/lib
  /update-
  notifier/apt_check.py@16:check_output:run:__init__:_execute_child

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1927996/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929613] Re: Unblock version 0.1.1-2 from impish-proposed

Thanks for the review Andreas! Package uploaded:

$ dput ubuntu ../bdebstrap_0.1.1-2ubuntu1_source.changes 
Checking signature on .changes
gpg: ../bdebstrap_0.1.1-2ubuntu1_source.changes: Valid signature from 
F823A2729883C97C
Checking signature on .dsc
gpg: ../bdebstrap_0.1.1-2ubuntu1.dsc: Valid signature from F823A2729883C97C
Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading bdebstrap_0.1.1-2ubuntu1.dsc: done.
  Uploading bdebstrap_0.1.1-2ubuntu1.debian.tar.xz: done. 
  Uploading bdebstrap_0.1.1-2ubuntu1_source.changes: done.
Successfully uploaded packages.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929613

Title:
  Unblock version 0.1.1-2 from impish-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bdebstrap/+bug/1929613/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929613] Re: Unblock version 0.1.1-2 from impish-proposed

The attached debdiff fixes the regression.

autopkgtest is happy now:

autopkgtest [17:59:38]:  summary
unittest PASS
examples PASS

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929613

Title:
  Unblock version 0.1.1-2 from impish-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bdebstrap/+bug/1929613/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929613] Re: Unblock version 0.1.1-2 from impish-proposed

** Attachment added: "debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bdebstrap/+bug/1929613/+attachment/5500320/+files/debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929613

Title:
  Unblock version 0.1.1-2 from impish-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bdebstrap/+bug/1929613/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929613] [NEW] Unblock version 0.1.1-2 from impish-proposed

Public bug reported:

bdebstrap/0.1.1-2 is blocked in impish-proposed because of a missing
autopkgtest dependency on debian-archive-keyring.

I submitted a PR to upstream to fix this and it was already merged:

https://github.com/bdrung/bdebstrap/commit/91c4ac2a3b67e835eb628f11680bb9df17bf1e2f

This fix will be introduced in the next upload but because of the freeze
in Debian it might take a while. Let's upload this as a delta for now.

** Affects: bdebstrap (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: update-excuse

** Tags added: update-excuse

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929613

Title:
  Unblock version 0.1.1-2 from impish-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bdebstrap/+bug/1929613/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929443] Re: upgrade mysql 5.7 to 8.0 during release upgrade (18.04.5 to 20.04.2) fails due to unsupported SQL mode

Thanks for taking the time to file this bug.

Your analysis seems right and there is nothing we can do as Ubuntu,
upstream decided to remove that option and we cannot support it without
upstream. What you need to do is to avoid the usage of the
NO_AUTO_CREATE_USER sql_mode option if you want to upgrade to MySQL 8,
from the release notes you linked in the bug description:

"For MySQL 5.7 applications that use SQL modes removed in MySQL 8.0,
statements may fail when replicated from a MySQL 5.7 master to a MySQL
8.0 slave, or may have different effects on master and slave. To avoid
such problems, applications that use modes removed in MySQL 8.0 should
be revised to avoid them."

Since this is a local configuration problem, rather than a bug in
Ubuntu, I am marking this bug as 'Invalid'.

** Changed in: mysql-8.0 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929443

Title:
  upgrade mysql 5.7 to 8.0 during release upgrade (18.04.5 to 20.04.2)
  fails due to unsupported SQL mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1929443/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912390] Re: [Patch] TLS/DTLS: inconsistent allowed_uses behaviour when in debug mode / not in debug mode

Thanks for the heads-up Graham. Our team will be taking a look at it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912390

Title:
  [Patch] TLS/DTLS: inconsistent allowed_uses behaviour when in debug
  mode / not in debug mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1912390/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912389] Re: [Patch] SIGSEGV: crash when certificate contains extension longer than 512 bytes

Thanks for the heads-up Graham. Our team will be taking a look at it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912389

Title:
   [Patch] SIGSEGV: crash when certificate contains extension longer
  than 512 bytes

To manage notifications about this bug go to:
https://bugs.launchpad.net/netsnmp/+bug/1912389/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 461354] Re: finger doesn't support utf8 characters

2021-05-24 Thread Lucas De Angelis

This bug is still here in Ubuntu 20.04. Is there anything I could do to
help to add the patch and fix the bug?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/461354

Title:
  finger doesn't support utf8 characters

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bsd-finger/+bug/461354/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926990] Re: update-notifier should not alert users about esm-apps in a ESM machine

2021-05-21 Thread Lucas Albuquerque Medeiros de Moura

** Description changed:

  [Impact]
  When users are running an ESM distro and looking at the MOTD they may be 
surprised by an alert generated by update-notifier that both esm-infra and 
esm-apps could be enabled in the machine to receive future updates. However, 
esm-apps will not bring much to an ESM distro. This means that users will be 
receiving alerts about esm-apps unnecessarily.
  
  [Test case]
  
  To reproduce the issue:
  
  1. Launch a xenial container
  2. Create the file /etc/ubuntu-advantage/uaclient.conf with the following 
content:
  
  # Ubuntu-Advantage client config file.
  contract_url: 'https://contracts.canonical.com'
  security_url: 'https://ubuntu.com/security'
  data_dir: /var/lib/ubuntu-advantage
  log_level: debug
  log_file: /var/log/ubuntu-advantage.log
  features:
    allow_beta: true
  
  3. Install ubuntu-advantage-client from this PPA:
  https://code.launchpad.net/~ua-client/+archive/ubuntu/daily
  
  PS: Make sure to not allow the installation to override the config file
  you have just created.
  
  4. Update the version of update-notifier to the one in proposed
  5. Run `/usr/lib/update-notifier/apt-check --human-readable`
  6. Verify that both esm-infra and esm-apps alerts appear at the end of the 
message
  
  To verify that the error is fixed:
  
  1. Run the past scenario until step 3
  2. Install the new update-notifier from this ppa:
  https://launchpad.net/~lamoura/+archive/ubuntu/update-notifier-test-ppa/
  3. Run `/usr/lib/update-notifier/apt-check --human-readable`
  4. Verify that only esm-infra is now showing an alert message at the end
  
  [Where problems could occur]
  
- We are only changing the condition for when to output esm-apps alerts.
- If that condition is not right, we may miss displaying the messages to
- users that need them.
+ We are changing some aspects of the package that could generate
+ problems:
+ 
+ 1) We are changing the condition for when to output esm-apps alerts. If that 
condition is not right, we may miss displaying the messages to users that need 
them.
+ 2) We are adding a new dependency to the package, lsb-release. But since the 
package was already relying on that dependency, we are just fixing a packaging 
mistake here.
+ 3) Instead of relying on `lsb_release` for distro-info, we are now getting 
that info directly from `/etc/os-release`. Since is an attempt to not rely on 
subprocess python calls on that script. However, since we are adding more 
python code, logic errors can not happen because of that new chunk of code.
+ 4) Since we are touching translatable message, translation errors can happen 
because of the modifications we are providing here.
+ 5) We are now adding a ESM Apps headers for the case where users now have
+ esm-apps source files in the system. If our logic is incorrect, we could be 
displaying that info on situations that are not needed.
+ 
+ However, we believe that all of the risks mentioned above are manageable
+ and should not block the changes we are bringing to the package.
  
  [Discussion]
  When running /usr/lib/update-notifier/apt-check on a ESM machine, we could 
alert the user about the existence of both esm-infra and esm-apps if the system 
has unauthenticated source files for both services. Therefore, we would display 
a message like this in the system:
  
  --
  Enable UA Apps: ESM to receive additional future security updates.
  See https://ubuntu.com/security/esm or run: sudo ua status
  
  Enable UA Infra: ESM to receive additional future security updates.
  See https://ubuntu.com/security/esm or run: sudo ua status
  --
  
  This is not ideal, since ESM machines will not gain much from esm-apps.
  Also, this messaging may hide the importance of using esm-infra on ESM
  machines, since the users will not know beforehand which service to
  prioritize.
  
+ Furthermore, we are also bringing back the message:
+ 
+ 0 updates can be applied immediately
+ 
+ When the system has no packages to install. This is because users found
+ that omission confusing, since they thought that maybe something went
+ wrong with motd if display no messages when the system is up to date.
+ 
+ Additionally, we are adding an esm-apps header to the `apt-check`
+ message if the system is a LTS one with esm-apps source files on it. The
+ header should behave exactly like the one we have for esm-infra:
+ 
+  UA Apps: Extended Security Maintenance (ESM) is (enabled|disabled).
+ 
+ We doing this to be consistent with the message we have on ESM distros
+ 
+ Finally, we are no longer relying on `lsb_release` on `apt-check` to get
+ distro info, like name and version. We are parsing `/etc/os-release` for
+ that now. The rationale for this change is some errors we have saw
+ regarding the use of `subprocess.check_output`. Since we can parse the
+ os-release file directly, we believe it is safer to do so than to rely
+ on shell out for getting that info.
+ 
  ==

[Bug 1927996] Re: /usr/lib/update-notifier/apt_check.py:FileNotFoundError:/usr/lib/update-notifier/apt_check.py@16:check_output:run:init:_execute_child

2021-05-21 Thread Lucas Albuquerque Medeiros de Moura

[Impact]
Because update-notifier does not explicit have the `lsb-release` package as a 
dependency, users may install the package and rely on `apt-cdrom-check` to 
work, but it will fail, since it runs
the `lsb_release -sr` command on it. 

[Test case]

To reproduce the issue:

1. Launch a xenial container
2. Install update-notifier on it
3. Run apt-cache depends update-notifier-common
4. Verify that lsb-release does not appear

To verify that the error is fixed:

1. Install the new update-notifier from this ppa:
https://launchpad.net/~lamoura/+archive/ubuntu/update-notifier-test-ppa/
2. Run apt-cache depends update-notifier-common
3. Verify that lsb-release will now appear as a dependency


[Where problems could occur]

We are only adding a missing dependency to the package. I cannot think
of a problem that this might cause to the users of this package.

[Discussion]

We can verify that `apt-cdrom-check` does make use of the `lsb_release`
command. Since we don't have that dependency on the package control
file, errors can appear when users are executing/relying on that script.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927996

Title:
  /usr/lib/update-notifier/apt_check.py:FileNotFoundError:/usr/lib
  /update-
  notifier/apt_check.py@16:check_output:run:__init__:_execute_child

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1927996/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927219] Re: context deadline exceeded: unknown in containerd with latest runc version

** Changed in: runc (Ubuntu)
 Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)

** Changed in: runc (Ubuntu Focal)
 Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)

** Changed in: runc (Ubuntu Groovy)
 Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)

** Changed in: runc (Ubuntu Bionic)
 Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)

** Changed in: runc (Ubuntu Hirsute)
 Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219

Title:
  context deadline exceeded: unknown in containerd with latest runc
  version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1927219/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927219] Re: context deadline exceeded: unknown in containerd with latest runc version

** Description changed:

+ [Impact]
+ 
+ Several regressions were identified by upstream in version 1.0.0-rc93
+ and were fixed in version 1.0.0-rc94:
+ 
+ https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc94
+ 
+ "This release fixes several regressions found in v1.0.0-rc93. We
+ recommend users update as soon as possible."
+ 
+ And in version 1.0.0-rc95 we also have the fix for CVE-2021-30465.
+ 
+ [Test Plan]
+ 
+ Per https://wiki.ubuntu.com/DockerUpdates, our test case is the
+ autopkgtests
+ 
+ [Where problems could occur]
+ 
+ As usual, we deliver most benefit to our users by delivering an upstream
+ experience. A risk of regressions is part of that.
+ 
+ [Original Message]
+ 
  When upgrading runc to the latest version from focal-updates, Kubernetes, 
using containerd, fails to start new containers after a certain amount of 
container have been reached a certain amount (more than 100 ~ 150 containers).
  With the previous version of runc, I was able to run more than 340 containers 
on a single server without any issue.
  
  I got those logs in containerd (journalctl -u containerd)
  ```
  May 05 00:48:17 node6 containerd[1368656]: 
time="2021-05-05T00:48:17.260349619Z" level=warning msg="could not use 
snapshotter devmapper in metadata plugin" error="devmapper not configured"
  May 05 00:48:21 node6 containerd[1368656]: 
time="2021-05-05T00:48:21.807947009Z" level=error msg="get state for 
71005cc34ac16f6976a7aebd72faa734792639b003c5dec67f666449cf6eb8d7" 
error="context deadline exceeded: unknown"
  May 05 00:48:23 node6 containerd[1368656]: 
time="2021-05-05T00:48:23.810434820Z" level=error msg="get state for 
71005cc34ac16f6976a7aebd72faa734792639b003c5dec67f666449cf6eb8d7" 
error="context deadline exceeded: unknown"
  May 05 00:48:25 node6 containerd[1368656]: 
time="2021-05-05T00:48:25.813453574Z" level=error msg="get state for 
c6497bbf82f668f8b8b534204cd2efaa30a97f884da3dd5fca4f51489298f855" 
error="context deadline exceeded: unknown"
  May 05 00:48:27 node6 containerd[1368656]: 
time="2021-05-05T00:48:27.816285268Z" level=error msg="get state for 
c6497bbf82f668f8b8b534204cd2efaa30a97f884da3dd5fca4f51489298f855" 
error="context deadline exceeded: unknown"
  May 05 00:48:29 node6 containerd[1368656]: 
time="2021-05-05T00:48:29.823052797Z" level=error msg="get state for 
f90f054966ab6b78304797d420a1f948c85e5b6e425037417f8966c08cd9a0f1" 
error="context deadline exceeded: unknown"
  May 05 00:48:31 node6 containerd[1368656]: 
time="2021-05-05T00:48:31.826412096Z" level=error msg="get state for 
f90f054966ab6b78304797d420a1f948c85e5b6e425037417f8966c08cd9a0f1" 
error="context deadline exceeded: unknown"
  ```
  
  This version of runc triggered the problem:
  ```
  runc (1.0.0~rc93-0ubuntu1~20.04.1) focal; urgency=medium
  
-   * Backport version 1.0.0~rc93-0ubuntu1 from Hirsute (LP: #1919322,
- LP: #1916485).
+   * Backport version 1.0.0~rc93-0ubuntu1 from Hirsute (LP: #1919322,
+ LP: #1916485).
  
-  -- Lucas Kanashiro   Tue, 16 Mar 2021 15:34:35 -0300
+  -- Lucas Kanashiro   Tue, 16 Mar 2021 15:34:35 -0300
  ```
  
  ```
  # runc -v
  runc version spec: 1.0.2-dev
  go: go1.13.8
  libseccomp: 2.5.1
  ```
- 
  
  Reverting to the previous version of runc solved the problem, and I was able 
to run more than 340 pods / containers without any error.
  ```
  apt-get install runc=1.0.0~rc10-0ubuntu1
  
  # runc -v
  runc version spec: 1.0.1-dev
  ```
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: runc 1.0.0~rc93-0ubuntu1~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed May  5 12:06:30 2021
  SourcePackage: runc
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219

Title:
  context deadline exceeded: unknown in containerd with latest runc
  version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1927219/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929106] Re: runc -v empty output

** Description changed:

+ [Impact]
+ 
+ Users cannot check the runc version running 'runc --version'. This is
+ not a big deal but it would land along with LP #1927219 which is an
+ important fix.
+ 
+ [Test Plan]
+ 
+ Check if 'runc --version' returns the runc version.
+ 
+ [Where problems could occur]
+ 
+ As usual, we deliver most benefit to our users by delivering an upstream
+ experience. A risk of regressions is part of that.
+ 
+ [Original Message]
+ 
  Apparently runc is built in some non-standard way, so it does not show
  its version:
  
  kir@ubu2004:~$ runc -v
  runc version spec: 1.0.2-dev
  go: go1.13.8
  libseccomp: 2.5.1
  
  In the output above, version string is empty and there is no newline
  added, so we have a version of the spec in the same line. Thus, docker
  has the same problem reporting runc version:
  
  kir@ubu2004:~$ docker version | grep -A2 runc
-  runc:
-   Version:  spec: 1.0.2-dev
-   GitCommit:  
+  runc:
+   Version:  spec: 1.0.2-dev
+   GitCommit:
  
  For comparison, here is the correct/expected output:
  
  [kir@kir-rhat runc]$ runc -v
  runc version 1.0.0-rc93+dev
  commit: ba257d2de86e7e530eeb28fe697e206630ef45f8
  spec: 1.0.2-dev
  go: go1.15.8
  libseccomp: 2.5.0
  
  Package information:
  
  kir@ubu2004:~$ dpkg -l runc
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--=
  ii  runc   1.0.0~rc93-0ubuntu1~20.04.2 amd64Open Container 
Project - runtime
  kir@ubu2004:~$ runc -v
  runc version spec: 1.0.2-dev
  go: go1.13.8
  libseccomp: 2.5.1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929106

Title:
  runc -v empty output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1929106/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927219] Re: context deadline exceeded: unknown in containerd with latest runc version

** Also affects: runc (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: runc (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: runc (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: runc (Ubuntu Focal)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219

Title:
  context deadline exceeded: unknown in containerd with latest runc
  version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1927219/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929106] Re: runc -v empty output

** Also affects: runc (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: runc (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: runc (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: runc (Ubuntu Groovy)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929106

Title:
  runc -v empty output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1929106/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929106] Re: runc -v empty output

Thanks for taking the time to file this bug.

This is a known issue and I already addressed it in my PPA where I am
preparing the next version to be uploaded to the archive:

https://launchpad.net/~lucaskanashiro/+archive/ubuntu/container-
stack/+packages

Therefore, this will be fixed soon across all supported releases.

** Changed in: runc (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929106

Title:
  runc -v empty output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1929106/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928416] Re: Error when attaching UA ESM key

2021-05-20 Thread Lucas Albuquerque Medeiros de Moura

Thank you for this Rakesh and just to be sure can you install any other
snap in your system ? Or you are only seeing that snap error when trying
to run ua attach ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928416

Title:
  Error when attaching UA ESM key

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1928416/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927219] Re: context deadline exceeded: unknown in containerd with latest runc version

2021-05-20 Thread Lucas Kanashiro

@Colin I updated my PPA with version 1.0-rc95 which also contains the
fix for CVE-2021-30465. Could you test this new version and make sure
your regression is fixed?

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-30465

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219

Title:
  context deadline exceeded: unknown in containerd with latest runc
  version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1927219/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928416] Re: Error when attaching UA ESM key

2021-05-19 Thread Lucas Albuquerque Medeiros de Moura

Hi Rakesh, looking at the logs maybe snapd is not working as expected.
Can you please provide the output of:

systemctl status snapd.service

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928416

Title:
  Error when attaching UA ESM key

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1928416/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928697] Re: package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1

*** This bug is a duplicate of bug 1928635 ***
https://bugs.launchpad.net/bugs/1928635

Thank you for taking the time to file a bug report.

After checking the logs the only thing relevant to your problem was this
part of the apt log:

Setting up mysql-server-8.0 (8.0.25-0ubuntu0.20.04.1) ...
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as pid 28189
Error: Unable to shut down server with process id 28189
dpkg: error processing package mysql-server-8.0 (--configure):
 installed mysql-server-8.0 package post-installation script subprocess 
returned error exit status 1

Which means that a mysqld process was already running when you tried to
upgrade the package. Could you confirm you did not have another mysql
process bind to the default port?

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Changed in: mysql-8.0 (Ubuntu)
   Status: New => Incomplete

** This bug has been marked a duplicate of bug 1928635
   package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to install/upgrade: 
installed mysql-server-8.0 package post-installation script subprocess returned 
error exit status 1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928697

Title:
  package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to
  install/upgrade: installed mysql-server-8.0 package post-installation
  script subprocess returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1928697/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928635] Re: package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1

Thank you for taking the time to file a bug report.

After checking the logs the only thing relevant to your problem was this
part of the apt log:

Setting up mysql-server-8.0 (8.0.25-0ubuntu0.20.04.1) ...
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as pid 8278
Error: Unable to shut down server with process id 8278
[1mdpkg:[0m error processing package mysql-server-8.0 (--configure):
 installed mysql-server-8.0 package post-installation script subprocess 
returned error exit status 1

Which means that a mysqld process was already running when you tried to
upgrade the package. Could you confirm you did not have another mysql
process bind to the default port?

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Changed in: mysql-8.0 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928635

Title:
  package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to
  install/upgrade: installed mysql-server-8.0 package post-installation
  script subprocess returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1928635/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928604] Re: ubuntu-advantage-tools should not be auto-installed on supported Ubuntu releases

Thanks for taking the time to file this bug and trying to make Ubuntu
better.

ubuntu-advantage-tools does not provide only a way to enable ESM, it
also provides a bunch of other services (from the project README):

"The Ubuntu Advantage client provides users with a simple mechanism to
view, enable, and disable offerings from Canonical on their system. The
following entitlements are supported:

Common Criteria EAL2 certification artifacts provisioning
Canonical CIS Benchmark Audit Tool
Ubuntu Extended Security Maintenance
FIPS 140-2 Certified Modules
FIPS 140-2 Non-Certified Module Updates
Livepatch Service
"

Those other services might be useful in non-EOL releases. Due to that,
the package is installed by default in all supported releases.

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928604

Title:
  ubuntu-advantage-tools should not be auto-installed on supported
  Ubuntu releases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1928604/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1817374] Re: mysql-server-5.7 5.7.25 upgrade did not complete properly

Thank you for taking the time to file a bug report.

I created a Bionic container to test the upgrade of mysql version
5.7.21-1ubuntu1 to 5.7.34-0ubuntu0.18.04.1 and it worked as expected:

root@mysql-test:~# apt list --upgradable
Listing... Done
mysql-server-5.7/bionic-updates,bionic-security 5.7.34-0ubuntu0.18.04.1 amd64 
[upgradable from: 5.7.21-1ubuntu1]
mysql-server-core-5.7/bionic-updates,bionic-security 5.7.34-0ubuntu0.18.04.1 
amd64 [upgradable from: 5.7.21-1ubuntu1]
root@mysql-test:~# apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
The following packages will be upgraded:
  mysql-server-5.7 mysql-server-core-5.7
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 10.3 MB of archives.
After this operation, 2650 kB disk space will be freed.
Do you want to continue? [Y/n] 
Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
mysql-server-5.7 amd64 5.7.34-0ubuntu0.18.04.1 [2905 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
mysql-server-core-5.7 amd64 5.7.34-0ubuntu0.18.04.1 [7418 kB]
Fetched 10.3 MB in 3s (3986 kB/s)  
Preconfiguring packages ...
(Reading database ... 29454 files and directories currently installed.)
Preparing to unpack .../mysql-server-5.7_5.7.34-0ubuntu0.18.04.1_amd64.deb ...
Unpacking mysql-server-5.7 (5.7.34-0ubuntu0.18.04.1) over (5.7.21-1ubuntu1) ...
Preparing to unpack .../mysql-server-core-5.7_5.7.34-0ubuntu0.18.04.1_amd64.deb 
...
Unpacking mysql-server-core-5.7 (5.7.34-0ubuntu0.18.04.1) over 
(5.7.21-1ubuntu1) ...
Setting up mysql-server-core-5.7 (5.7.34-0ubuntu0.18.04.1) ...
Setting up mysql-server-5.7 (5.7.34-0ubuntu0.18.04.1) ...
Installing new version of config file /etc/apparmor.d/usr.sbin.mysqld ...
Checking if update is needed.
Checking server version.
Running queries to upgrade MySQL server.
Checking system database.
mysql.columns_priv OK
mysql.db   OK
mysql.engine_cost  OK
mysql.eventOK
mysql.func OK
mysql.general_log  OK
mysql.gtid_executedOK
mysql.help_categoryOK
mysql.help_keyword OK
mysql.help_relationOK
mysql.help_topic   OK
mysql.innodb_index_stats   OK
mysql.innodb_table_stats   OK
mysql.ndb_binlog_index OK
mysql.plugin   OK
mysql.proc OK
mysql.procs_priv   OK
mysql.proxies_priv OK
mysql.server_cost  OK
mysql.servers  OK
mysql.slave_master_infoOK
mysql.slave_relay_log_info OK
mysql.slave_worker_infoOK
mysql.slow_log OK
mysql.tables_priv  OK
mysql.time_zoneOK
mysql.time_zone_leap_secondOK
mysql.time_zone_name   OK
mysql.time_zone_transition OK
mysql.time_zone_transition_typeOK
mysql.user OK
Found outdated sys schema version 1.5.1.
Upgrading the sys schema.
Checking databases.
sys.sys_config OK
Upgrade process completed successfully.
Checking if update is needed.
Processing triggers for systemd (237-3ubuntu10.47) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for ureadahead (0.100.0-21) ...
root@mysql-test:~# systemctl status mysql
● mysql.service - MySQL Community Server
   Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Tue 2021-05-18 18:48:36 UTC; 36s ago
 Main PID: 4387 (mysqld)
Tasks: 27 (limit: 77042)
   CGroup: /system.slice/mysql.service
   └─4387 /usr/sbin/mysqld --daemonize --pid-file=/run/mysqld/mysqld.pid

May 18 18:48:36 mysql-test systemd[1]: Starting MySQL Community Server...
May 18 18:48:36 mysql-test systemd[1]: Started MySQL Community Server.
May 18 18:48:36 mysql-test systemd[1]: mysql.service: Failed to reset 
devices.list: Operation not permitted
root@mysql-test:~# 


Could you provide the mysql logs and the apt logs of the package upgrade? Also 
any "special" change you have made in your config files.

Since there is not enough information in your

[Bug 1928758] Re: All apt commands failed after upgrade to 27.0.2~20.04.1

2021-05-18 Thread Lucas Albuquerque Medeiros de Moura

Hi Ulrik, thanks for reporting this problem.

How are you creating the machines in the serves ? I just want to
understand the process you are using to reproduce the issue here and
find a fix for it.

Also, when can you also say the apt version that was being used when you
upgraded ubuntu-advantage-tools to 27.0.2 ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928758

Title:
  All apt commands failed after upgrade to 27.0.2~20.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1928758/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896223] Re: no-quorum-policy=demote and on-fail=demote features for MSSQL servers

2021-05-17 Thread Lucas Kanashiro

** Description changed:

[Impact]

- This feature allows the use of other mechanisms to deal with failures.
+ This feature allows the use of other mechanisms to deal with failures
instead of fencing nodes (usually reboot a machine), and let for
instance MS SQL server handle some failures by itself. We can consider
this SRU as part of a "hardware enablement" for MS SQL Server.

[Test Plan]

Set up a Corosync/Pacemaker cluster and configure a resource to manage
MS SQL server and use the new policies. Check if the cluster loose the
minimum quorum or if the node where the failure happens are not fenced
but just demoted.

[Where problems could occur]

This SRU will be introducing some new actions when a node fails or if
the minimum quorum of the cluster is not reached, those are new
features. So no regression is expected. But if it occurs it would be
related to the schedule of actions when a failure happens and the quorum
is not reached.

[Original description]

Ubuntu Release Team:

This is a FFe for this feature. Despite the size of patches, the core
changes are not so big. Most of the commits are documentation OR tests
for this new feature. Nevertheless, I preferred to be conservative and I
have fully run all "CTS" (cluster test suite) with this new proposed
package and it seems that everything is fine (no known regressions were
caused, functional tests were good). With that in mind, I ask you to
please approve this FFe. The management burden will be on Ubuntu Server
team.

In bug:

https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1895883

I did the stabilization patches for pacemaker 2.0.4.. and I did not
merge this feature so it could have its own FFe (this bug).

The following patch-set:

* this is the no-quorum-policy feature microsoft needs for mssqlserver
|\
| * c4429d86e - Log: scheduler: downgrade "active on" messages to trace (3
mont
| * 7eec572db - Build: libcrmcommon: bump CRM feature set (3 months ago) https://bugs.launchpad.net/bugs/1896223

Title:
no-quorum-policy=demote and on-fail=demote features for MSSQL servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896223] Re: no-quorum-policy=demote and on-fail=demote features for MSSQL servers

2021-05-17 Thread Lucas Kanashiro

** Description changed:

+ [Impact]
+
+ This feature allows the use of other mechanisms to deal with failures.
+ instead of fencing nodes (usually reboot a machine), and let for
+ instance MS SQL server handle some failures by itself. We can consider
+ this SRU as part of a "hardware enablement" for MS SQL Server.
+
+ [Test Plan]
+
+ Set up a Corosync/Pacemaker cluster and configure a resource to manage
+ MS SQL server and use the new policies. Check if the cluster loose the
+ minimum quorum or if the node where the failure happens are not fenced
+ but just demoted.
+
+ [Where problems could occur]
+
+ This SRU will be introducing some new actions when a node fails or if
+ the minimum quorum of the cluster is not reached, those are new
+ features. So no regression is expected. But if it occurs it would be
+ related to the schedule of actions when a failure happens and the quorum
+ is not reached.
+
+ [Original description]
+
Ubuntu Release Team:

In bug:

https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1895883

I did the stabilization patches for pacemaker 2.0.4.. and I did not
merge this feature so it could have its own FFe (this bug).

The following patch-set:

Title:
no-quorum-policy=demote and on-fail=demote features for MSSQL servers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1896223/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926819] Re: Empty MOTD on up-to-date systems (includes fix)

2021-05-14 Thread Lucas Albuquerque Medeiros de Moura

SRU template verification

[Impact]
On a system without updates to be installed, not showing any message in motd 
feels that something went wrong in the backend. Also, currently we are printing 
unwanted white spaces in that scenario, which is not a good user experience 
here.

[Test case]

To reproduce the issue, you can:

1. Launch a xenial container
2. Remove ubuntu-advantage-tools from the system
   This package will make update-notifier show more messages which are not 
needed in that test
3. Run an apt update
4. Install update-notifier
5. Run apt upgrade
6. Run /usr/lib/update-notifier/apt_check.py --human-readable
7. Verify we deliver an empty message

To verify that the error is fixed:

1. Run the past scenario until step 4
2. Install the new update-notifier from this ppa:
https://launchpad.net/~lamoura/+archive/ubuntu/update-notifier-test-ppa/
3. Run `/usr/lib/update-notifier/apt-check --human-readable`
4. Verify that the command print the following message:

   0 updates can be applied immediately.

[Where problems could occur]

We are bringing back a behavior that was already present in the package,
but removed in the last version of it. We will now be impacting users
that may not be relying in that message anymore. But we believe this
should not be a huge issue if that happens, since users were already
relying on the old behavior.

[Discussion]
Currently, motd will not output a message if the system does not have any 
updates to apply. However, this is not ideal since this may cause the 
impression that there is something wrong with motd or the system. Also, the 
empty message we produce in that scenario is not completely empty, it does 
contain some white spaces on it, which is completely unnecessary.

Because of that, we are bringing back the behavior of printing the
message:

0 updates can be applied immediately.

If no updates need to be applied in the system.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926819

Title:
  Empty MOTD on up-to-date systems (includes fix)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1926819/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926990] Re: update-notifier should not alert users about esm-apps in a ESM machine

2021-05-14 Thread Lucas Albuquerque Medeiros de Moura

** Also affects: update-notifier (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: update-notifier (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: update-notifier (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: update-notifier (Ubuntu)
 Assignee: (unassigned) => Lucas Albuquerque Medeiros de Moura (lamoura)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926990

Title:
  update-notifier should not alert users about esm-apps in a ESM machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1926990/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928416] Re: Error when attaching UA ESM key

2021-05-14 Thread Lucas Albuquerque Medeiros de Moura

Hi Rakesh, thanks for reporting this problem. Can you please attach the content 
of
/var/log/ubuntu-advantage.log file here so we can better understand how can we 
tackle this issue ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928416

Title:
  Error when attaching UA ESM key

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1928416/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927029] Re: ua attach command fails

2021-05-13 Thread Lucas Albuquerque Medeiros de Moura

Hi Alex, I think this error is happening because cloud-init has not
fully run. I think rebooting the machines would be enough to handle that
issue.

But if you don't want to do that, you can restart cloud-init manually by
running:

DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force
cloud-init clean --logs
cloud-init init --local
cloud-init init > /dev/null
cloud-init modules --mode=config
cloud-init modules --mode=final
cloud-init status --wait --long

This will run all of the cloud-init modules. Let me know if that fix it.

Also, regarding the token, you will need to revoke it unfortunately :(

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927029

Title:
  ua attach command fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1927029/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927329] Re: 'snap wait' fails when enabling livepatch

2021-05-13 Thread Lucas Albuquerque Medeiros de Moura

We have landed a PR on main that address this issue:
https://github.com/canonical/ubuntu-advantage-client/pull/1621

We will now better informing the user about this situation and we also
not block enabling livepatch because of it

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: New => Fix Committed

** Changed in: ubuntu-advantage-tools (Ubuntu)
 Assignee: (unassigned) => Lucas Albuquerque Medeiros de Moura (lamoura)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927329

Title:
  'snap wait' fails when enabling livepatch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1927329/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927029] Re: ua attach command fails

2021-05-12 Thread Lucas Albuquerque Medeiros de Moura

Looking at the logs, I am seeing two distinct errors. One is livepatch
issue that we have:

Failed running command '/snap/bin/canonical-livepatch config remote-
server=https://livepatch.canonical.com' [exit(1)]. Message: 2021/05/04
15:18:29 error executing config: Livepatchd error: Couldn't setup system
logger.

And the other one is related to cloud-init:
File "/usr/lib/python3/dist-packages/uaclient/clouds/identity.py", line 56,
in get_cloud_type_from_result_file
dsname = result["v1"]["datasource"].split()[0].lower()
AttributeError: 'NoneType' object has no attribute 'split'

What is interesting in this error is that we are calling the
get_cloud_type_from_result_file function. We should only be calling this
function if we don't have the cloud-id command in the machine. Since we
are running on xenial machines, was not expecing that to happen.

So there is something wrong with cloud-init here. Maybe that is related
to the snap issue we are seeing.

Can you run the following cloud-init command and attach the logs here please
cloud-init collect-logs

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927029

Title:
ua attach command fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1927029/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927219] Re: context deadline exceeded: unknown in containerd with latest runc version

2021-05-12 Thread Lucas Kanashiro

Thanks for raising this issue. The VERSION file is not missing but we
are not using the upstream Makefile to build the source, that's why the
version is not set.

I fixed this issue and uploaded the fix to my PPA (it might take some
minutes to get it published), now if you update the runc package you
will have the correct version when running 'runc --version'.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219

Title:
  context deadline exceeded: unknown in containerd with latest runc
  version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1927219/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927219] Re: context deadline exceeded: unknown in containerd with latest runc version

I updated the runc package to version 1.0-rc94 and it is available in
this PPA for testing:

https://launchpad.net/~lucaskanashiro/+archive/ubuntu/container-stack

Let me know if this indeed fix your issue. If yes, I'll update runc in
the development release (a.k.a. impish) and then start the SRU process
(I'll need you to perform the same tests at this stage).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219

Title:
  context deadline exceeded: unknown in containerd with latest runc
  version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1927219/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1857404] Re: package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: the installed subprocess of the mysql-server-8.0 package, the post-installation script returned exit statu

I just noticed you filed a new bug here:

https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1927982

I replied to the bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857404

Title:
  package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to
  install/upgrade: the installed subprocess of the mysql-server-8.0
  package, the post-installation script returned exit status error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1857404/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927982] Re: package mysql-server-8.0 (not installed) failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 2

Thank you for taking the time to file a bug report.

The error in the log is the following:

Setting up mysql-server-8.0 (8.0.23-0ubuntu0.20.04.1) ...
update-alternatives: error: alternative path /etc/mysql/mysql.cnf doesn't exist
[1mdpkg:[0m error processing package mysql-server-8.0 (--configure):
 installed mysql-server-8.0 package post-installation script subprocess 
returned error exit status 2

Which means /etc/mysql/mysql.cnf is not available at the moment of the
configuration. Didn't you move this file to another directory by
mistake? In default mysql installations this file is present.

FWIW I was able to upgrade to version 8.0.23-0ubuntu0.20.04.1 in a LXD
container without any issue.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Changed in: mysql-8.0 (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927982

Title:
  package mysql-server-8.0 (not installed) failed to install/upgrade:
  installed mysql-server-8.0 package post-installation script subprocess
  returned error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1927982/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928000] Re: open-iscsi fails to upgrade (2.0.874-7.1ubuntu6.2)

Thank you for taking the time to file a bug report and try to make
Ubuntu better.

The configuration process did hang in this part of the postinst script:

# We switched over to modules-load.d logic, so we have to take
# care of this in postinst now.
MODULES_FILE=/lib/modules-load.d/open-iscsi.conf
if [ -f /etc/modules-load.d/open-iscsi.conf ] ; then
MODULES_FILE=/etc/modules-load.d/open-iscsi.conf
fi
grep '^[^#]' $MODULES_FILE | while read module args ; do
[ "$module" ] || continue
modprobe $module $args >/dev/null 2>&1 || true
done

This seems a mechanism to support some old version. However, none of the
MODULES_FILE's paths are installed by the package which are:

- /lib/modules-load.d/open-iscsi.conf
- /etc/modules-load.d/open-iscsi.conf

/etc/modules-load.d directory is used by systemd to configure kernel
modules to load at boot time (/lib/modules-load.d seems obsoleted):

https://www.freedesktop.org/software/systemd/man/modules-load.d.html

I am not sure if we still need to support MODULES_FILE (it was removed
from newer versions), but even if we still need it, the postinst script
shouldn't rely on a file which is not installed by the package and we
can't ensure it will be present in the system. I was able to reproduce
the same log error after upgrading to version 2.0.874-7.1ubuntu6.2 in a
clean LXD container:

root@open-iscsi-test:~# sudo apt install open-iscsi
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'sudo apt autoremove' to remove it.
The following packages will be upgraded:
  open-iscsi
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 283 kB of archives.
After this operation, 1024 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 open-iscsi 
amd64 2.0.874-7.1ubuntu6.2 [283 kB]
Fetched 283 kB in 2s (186 kB/s)  
Preconfiguring packages ...
(Reading database ... 31611 files and directories currently installed.)
Preparing to unpack .../open-iscsi_2.0.874-7.1ubuntu6.2_amd64.deb ...
Unpacking open-iscsi (2.0.874-7.1ubuntu6.2) over (2.0.874-7.1ubuntu6.1) ...
Setting up open-iscsi (2.0.874-7.1ubuntu6.2) ...
grep: /lib/modules-load.d/open-iscsi.conf: No such file or directory
Processing triggers for systemd (245.4-4ubuntu3.6) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for initramfs-tools (0.136ubuntu6.4) ...
root@open-iscsi-test:~#

However, you can see the grep error but it did not hang as you explained
in the bug report, which makes me think that this is not the real
problem you are facing. Maybe there is something in your config which is
making it hang.

To proceed with the investigation I'd ask you to provide some extra
info, like the config files (if possible) and any other log you have
available (not just apt output).

I am marking this bug as Incomplete, when you provide more info that
could help us with the investigation set it back to New and we will take
a look.


** Changed in: open-iscsi (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928000

Title:
  open-iscsi fails to upgrade (2.0.874-7.1ubuntu6.2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1928000/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927980] Re: smartd-runner bug causes loss of email recipients

Thank you for taking the time to report this bug and helping to make Ubuntu
better.

This bug is present in Debian as well and Ubuntu currently does not make any
changes to the Debian package. Therefore, this bug would be best fixed
directly in Debian, and then Ubuntu will pick up the fix automatically. Once
it is fixed in the development release we can consider a SRU:

https://wiki.ubuntu.com/StableReleaseUpdates

Would you mind filing a bug with Debian please?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927980

Title:
  smartd-runner bug causes loss of email recipients

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1927980/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927219] Re: context deadline exceeded: unknown in containerd with latest runc version

Thanks for the investigation! It seems that a bunch of regressions were
found in 1.0.0~rc93 as we can see in the 1.0.0~rc94 release notes:

"This release fixes several regressions found in v1.0.0-rc93. We
recommend users update as soon as possible."

https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc94

I'll be preparing a PPA with this new runc version and ask you to test
it if possible.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927219

Title:
  context deadline exceeded: unknown in containerd with latest runc
  version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/1927219/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1857404] Re: package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: the installed subprocess of the mysql-server-8.0 package, the post-installation script returned exit statu

@Tanmay, you did not provide some useful information. What are you
trying to achieve? What did you do? Did you change any default settings?
Without these kind of info we cannot distinguish this from a local
config issue or a real bug. Moreover, this should be reported as a
separate bug since this does not seem related to the one reported here.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857404

Title:
  package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to
  install/upgrade: the installed subprocess of the mysql-server-8.0
  package, the post-installation script returned exit status error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1857404/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927712] Re: The Pacemaker module "ocf:heartbeat:CTDB" does not work on Bionic