[Bug 1924766] Re: update-notifier does not handle ESM Apps in the apt-check script

[Lucas Albuquerque Medeiros de Moura]

I have tested this package for released xenial, bionic, focal and
hirsute with the following script:

--
#!/bin/sh
set -x

series=hirsute
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 -- add-apt-repository ppa:lamoura/update-notifier-test-ppa 
-y
#lxc exec $name -- apt update
#lxc exec $name -- apt install update-notifier-common -y
#lxc exec $name -- apt update
#lxc exec $name -- apt install python3-distro-info
#lxc file push data/apt_check.py $name/usr/lib/update-notifier/apt-check
lxc exec $name -- sh -c "cat  /dev/null"
}

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_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"
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"

set +x
-

I can confirm that on all release, the package now in proposed is
working as expected

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

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

Title:
  update-notifier does not handle ESM Apps in the apt-check script

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

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

[Bug 1922089] Re: [ovn] enable_snat cannot be disabled once enabled

[Lucas Alvares Gomes]

Hi,

OK, I was able to reproduce the problem locally in devstack as stated in
comment #3. The patch I proposed does fix it for me, so I am somewhat
confident that it will also fix for you, but wanted to be sure.

If you can take a look at the patch itself, the code is quite small.

Thanks again for reporting

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

Title:
  [ovn] enable_snat cannot be disabled once enabled

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

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

[Bug 1922089] Re: [ovn] enable_snat cannot be disabled once enabled

[Lucas Alvares Gomes]

Hi,

Thanks for reporting it, I was looking into the problem and saw that we
are actually checking if the snat is enabled in order to call
update_nat_rules() in the update_router() method. I've fixed the problem
at https://review.opendev.org/c/openstack/neutron/+/788485

I tested it locally (http://paste.openstack.org/show/804827/) but it
would be good if you also could test and review the patch.

Thank you

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

Title:
  [ovn] enable_snat cannot be disabled once enabled

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

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

[Bug 1922089] Re: [ovn] enable_snat cannot be disabled once enabled

[Lucas Alvares Gomes]

** Changed in: neutron
 Assignee: (unassigned) => Lucas Alvares Gomes (lucasagomes)

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

Title:
  [ovn] enable_snat cannot be disabled once enabled

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

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

[Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

[Lucas Santana Carlota]

Works perfectly in Fedora 34! Thank you so much!

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

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

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

[Bug 1926346] [NEW] Desktop Action missing translation into Brazilian Portuguese

[Lucas Wilm]

Public bug reported:

Using Xubuntu 20.04 and I have a Firefox (version 88) launcher on the
xfce4-panel. When right-clicking, a context menu with Desktop Actions
like "Open a New Private Window" is opened and it's missing translation
into Brazilian Portuguese for that string.

I reported the bug in bugzilla
(https://bugzilla.mozilla.org/show_bug.cgi?id=1705800) and I was told to
report it in my distribution bug tracker.

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

** Attachment added: "Captura de tela_2021-04-16_15-11-34.png"
   
https://bugs.launchpad.net/bugs/1926346/+attachment/5492893/+files/Captura%20de%20tela_2021-04-16_15-11-34.png

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

Title:
  Desktop Action missing translation into Brazilian Portuguese

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

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

[Bug 1926208] Re: standard security upgrade counts should not include ESM packages

[Lucas Albuquerque Medeiros de Moura]

** Description changed:

  [Impact]
  When users are looking at MOTD messages, they might find the text confusing, 
since we don't explicitly say that the security updates count are taking into 
consideration both standard security pockets and ESM pockets.
  
  [Test Case]
  1. Launch the a xenial container
- 2. Run apt update and install the updated version of update-notifier-common
- 3. Add the ubuntu-advantage-tools ppa:
+ 2. Add the ubuntu-advantage-tools ppa:
     https://code.launchpad.net/~ua-client/+archive/ubuntu/daily
- 4. Install ubuntu-advantage-tools
- 5. Install the latest version of uaclient from the stable ppa:
+ 3. Install ubuntu-advantage-tools
+ 4. Install the latest version of uaclient from the stable ppa:
     https://launchpad.net/~ua-client/+archive/ubuntu/stable/
- 6. Comment out all mentions of xenial-security/xenial-updates in 
/etc/apt/source.list
- 7. Run apt update
- 8. Install libkrad0:
+ 5. Comment out all mentions of xenial-security/xenial-updates in 
/etc/apt/source.list
+ 6. Run apt update
+ 7. Install libkrad0:
     apt install libkrad0=1.13.2+dfsg-5
- 9. Run /usr/lib/update-notifier/apt-check --human-readable
- 10. See a message like this:
+ 8. Run /usr/lib/update-notifier/apt-check --human-readable
+ 9. See a message like this:
  
  UA Infra: Extended Security Maintenance (ESM) is not enabled.
  
  UA Infra: Extended Security Maintenance (ESM) is enabled.
  
  3 packages can be updated.
  1 of these updates is fixed through UA Infra: ESM.
  1 of these updates is a security update.
  To see these additional updates run: apt list --upgradable
  
  To verify that the error is fixed:
  
- 1.Perform all the stages above until step 8
+ 1.Perform all the stages above until step 7
  2. Bring back xenial-security on source.list (we need because of the 
python3-distro-info dependency of update-notifier-common)
  3 Install the new update-notifier from this ppa:
    https://launchpad.net/~lamoura/+archive/ubuntu/update-notifier-test-ppa
  4. Remove xenial-security from source.list again
  5. Run /usr/lib/update-notifier/apt-check --human-readable and see a message 
like this:
  
  UA Infra: Extended Security Maintenance (ESM) is enabled.
  
  4 updates can be installed immediately.
  1 of these updates are UA Infra: ESM security updates.
  To see these additional updates run: apt list --upgradable
  
  That is now correct.
  
  [Where problems could occur]
  
  The changes in this package should only be seen when MOTD is getting a
  new message. If that script fails for some reason, it seems that MOTD
  will only not present the message, which is doesn't seem to be a system
  critical issue. Additionally, we would potentially have tracebacks in
  the update-notifier logs. Finally, if the logic is also incorrect, we
  would be displaying incorrect standard security messages to the user.
  
  [Discussion]
  Currently, we treat the upgrades coming from standard security pocket and ESM 
service with the same packaging count. This could be confusing, since we don't 
point that out in the current message that we have:
  
  5 updates can be installed immediately.
  5 of these updates are provide through UA Infrastructure ESM
  5 of these updates are security updates
  
  We believe this will be better if the message stated:
  5 updates can be installed immediately.
  5 of these updates are provide through UA Infrastructure ESM
  
  And if we had a situation like that:
  
  10 updates can be installed immediately.
  5 of these updates are provide through UA Infrastructure ESM
  8 of these updates are security updates
  
  We would change it to:
  
  10 updates can be installed immediately.
  5 of these updates are provide through UA Infrastructure ESM
  3 of these updates are standard security updates

** Description changed:

  [Impact]
  When users are looking at MOTD messages, they might find the text confusing, 
since we don't explicitly say that the security updates count are taking into 
consideration both standard security pockets and ESM pockets.
  
  [Test Case]
  1. Launch the a xenial container
  2. Add the ubuntu-advantage-tools ppa:
     https://code.launchpad.net/~ua-client/+archive/ubuntu/daily
  3. Install ubuntu-advantage-tools
- 4. Install the latest version of uaclient from the stable ppa:
-    https://launchpad.net/~ua-client/+archive/ubuntu/stable/
+ 4. Attach to ua subscription
  5. Comment out all mentions of xenial-security/xenial-updates in 
/etc/apt/source.list
  6. Run apt update
  7. Install libkrad0:
     apt install libkrad0=1.13.2+dfsg-5
  8. Run /usr/lib/update-notifier/apt-check --human-readable
  9. See a message like this:
  
- UA Infra: Extended Security Maintenance (ESM) is not enabled.
+ UA Infra: Extended Security Maintenance (ESM) is not enable4. Install the 
latest version of uaclient from the stable ppa:
+https://launchpad.net/~ua-client/+archive/ubuntu/stable/d.
  
  UA Infra: Extended Security Maintenance (ESM) is enabled.
  
  3 packages 

[Bug 1926208] Re: standard security upgrade counts should not include ESM packages

[Lucas Albuquerque Medeiros de Moura]

** Description changed:

  [Impact]
  When users are looking at MOTD messages, they might find the text confusing, 
since we don't explicitly say that the security updates count are taking into 
consideration both standard security pockets and ESM pockets.
  
  [Test Case]
  1. Launch the a xenial container
  2. Run apt update and install the updated version of update-notifier-common
  3. Add the ubuntu-advantage-tools ppa:
     https://code.launchpad.net/~ua-client/+archive/ubuntu/daily
  4. Install ubuntu-advantage-tools
  5. Install the latest version of uaclient from the stable ppa:
     https://launchpad.net/~ua-client/+archive/ubuntu/stable/
  6. Comment out all mentions of xenial-security/xenial-updates in 
/etc/apt/source.list
  7. Run apt update
  8. Install libkrad0:
     apt install libkrad0=1.13.2+dfsg-5
  9. Run /usr/lib/update-notifier/apt-check --human-readable
  10. See a message like this:
  
  UA Infra: Extended Security Maintenance (ESM) is not enabled.
  
  UA Infra: Extended Security Maintenance (ESM) is enabled.
  
  3 packages can be updated.
  1 of these updates is fixed through UA Infra: ESM.
  1 of these updates is a security update.
  To see these additional updates run: apt list --upgradable
  
  To verify that the error is fixed:
  
  1.Perform all the stages above until step 8
- 2 Install the new update-notifier from this ppa:
+ 2. Bring back xenial-security on source.list (we need because of the 
python3-distro-info dependency of update-notifier-common)
+ 3 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. See a message like this:
+ 4. Remove xenial-security from source.list again
+ 5. Run /usr/lib/update-notifier/apt-check --human-readable and see a message 
like this:
+ 
  UA Infra: Extended Security Maintenance (ESM) is enabled.
  
  4 updates can be installed immediately.
  1 of these updates are UA Infra: ESM security updates.
  To see these additional updates run: apt list --upgradable
  
  That is now correct.
  
  [Where problems could occur]
  
  The changes in this package should only be seen when MOTD is getting a
  new message. If that script fails for some reason, it seems that MOTD
  will only not present the message, which is doesn't seem to be a system
  critical issue. Additionally, we would potentially have tracebacks in
  the update-notifier logs. Finally, if the logic is also incorrect, we
  would be displaying incorrect standard security messages to the user.
  
  [Discussion]
  Currently, we treat the upgrades coming from standard security pocket and ESM 
service with the same packaging count. This could be confusing, since we don't 
point that out in the current message that we have:
  
  5 updates can be installed immediately.
  5 of these updates are provide through UA Infrastructure ESM
  5 of these updates are security updates
  
  We believe this will be better if the message stated:
  5 updates can be installed immediately.
  5 of these updates are provide through UA Infrastructure ESM
  
  And if we had a situation like that:
  
  10 updates can be installed immediately.
  5 of these updates are provide through UA Infrastructure ESM
  8 of these updates are security updates
  
  We would change it to:
  
  10 updates can be installed immediately.
  5 of these updates are provide through UA Infrastructure ESM
  3 of these updates are standard security updates

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

Title:
  standard security upgrade counts should not include ESM packages

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

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

[Bug 1926208] [NEW] standard security upgrade counts should not include ESM packages

[Lucas Albuquerque Medeiros de Moura]

Public bug reported:

[Impact]
When users are looking at MOTD messages, they might find the text confusing, 
since we don't explicitly say that the security updates count are taking into 
consideration both standard security pockets and ESM pockets.

[Test Case]
1. Launch the a xenial container
2. Run apt update and install the updated version of update-notifier-common
3. Add the ubuntu-advantage-tools ppa:
   https://code.launchpad.net/~ua-client/+archive/ubuntu/daily
4. Install ubuntu-advantage-tools
5. Install the latest version of uaclient from the stable ppa:
   https://launchpad.net/~ua-client/+archive/ubuntu/stable/
6. Comment out all mentions of xenial-security/xenial-updates in 
/etc/apt/source.list
7. Run apt update
8. Install libkrad0:
   apt install libkrad0=1.13.2+dfsg-5
9. Run /usr/lib/update-notifier/apt-check --human-readable
10. See a message like this:

UA Infra: Extended Security Maintenance (ESM) is not enabled.

UA Infra: Extended Security Maintenance (ESM) is enabled.

3 packages can be updated.
1 of these updates is fixed through UA Infra: ESM.
1 of these updates is a security update.
To see these additional updates run: apt list --upgradable

To verify that the error is fixed:

1.Perform all the stages above until step 8
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. See a message like this:
UA Infra: Extended Security Maintenance (ESM) is enabled.

4 updates can be installed immediately.
1 of these updates are UA Infra: ESM security updates.
To see these additional updates run: apt list --upgradable

That is now correct.

[Where problems could occur]

The changes in this package should only be seen when MOTD is getting a
new message. If that script fails for some reason, it seems that MOTD
will only not present the message, which is doesn't seem to be a system
critical issue. Additionally, we would potentially have tracebacks in
the update-notifier logs. Finally, if the logic is also incorrect, we
would be displaying incorrect standard security messages to the user.

[Discussion]
Currently, we treat the upgrades coming from standard security pocket and ESM 
service with the same packaging count. This could be confusing, since we don't 
point that out in the current message that we have:

5 updates can be installed immediately.
5 of these updates are provide through UA Infrastructure ESM
5 of these updates are security updates

We believe this will be better if the message stated:
5 updates can be installed immediately.
5 of these updates are provide through UA Infrastructure ESM

And if we had a situation like that:

10 updates can be installed immediately.
5 of these updates are provide through UA Infrastructure ESM
8 of these updates are security updates

We would change it to:

10 updates can be installed immediately.
5 of these updates are provide through UA Infrastructure ESM
3 of these updates are standard security updates

** Affects: update-notifier (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  [Impact]
  When users are looking at MOTD messages, they might find the text confusing, 
since we don't explicitly say that the security updates count are taking into 
consideration both standard security pockets and ESM pockets.
  
  [Test Case]
- 1. Launch the following old version of a xenial container:
-lxc launch 
ubuntu:f4c4c60a6b752a381288ae72a1689a9da00f8e03b732c8d1b8a8fcd1a8890800 dev-x
- 
+ 1. Launch the a xenial container
  2. Run apt update and install the updated version of update-notifier-common
  3. Add the ubuntu-advantage-tools ppa:
-https://code.launchpad.net/~ua-client/+archive/ubuntu/daily
+    https://code.launchpad.net/~ua-client/+archive/ubuntu/daily
  4. Install ubuntu-advantage-tools
  5. Install the latest version of uaclient from the stable ppa:
-https://launchpad.net/~ua-client/+archive/ubuntu/stable/
+    https://launchpad.net/~ua-client/+archive/ubuntu/stable/
  6. Comment out all mentions of xenial-security/xenial-updates in 
/etc/apt/source.list
  7. Run apt update
  8. Install libkrad0:
-apt install libkrad0=1.13.2+dfsg-5
+    apt install libkrad0=1.13.2+dfsg-5
  9. Run /usr/lib/update-notifier/apt-check --human-readable
  10. See a message like this:
  
  UA Infra: Extended Security Maintenance (ESM) is not enabled.
  
  UA Infra: Extended Security Maintenance (ESM) is enabled.
  
  3 packages can be updated.
  1 of these updates is fixed through UA Infra: ESM.
  1 of these updates is a security update.
  To see these additional updates run: apt list --upgradable
  
- 
  To verify that the error is fixed:
  
  1.Perform all the stages above until step 8
  2 Install the new update-notifier from this ppa:
-   https://launchpad.net/~lamoura/+archive/ubuntu/update-notifier-test-ppa
+   https://launchpad.net/~lamoura/+archive/ubuntu/update-notifier-test-ppa
  3. 

[Bug 1896696] Re: Backport fence_ec2 support to Focal and Bionic

[Lucas Kanashiro]

I am marking this bug as Won't Fix because the recommended way to fence
nodes on AWS is using the fence_aws agent present in the fence-agents
packages (already available in Bionic and Focal).

** Changed in: cluster-glue (Ubuntu Bionic)
   Status: Confirmed => Won't Fix

** Changed in: cluster-glue (Ubuntu Focal)
   Status: Confirmed => Won't Fix

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

Title:
  Backport fence_ec2 support to Focal and Bionic

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

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

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

[Lucas Kanashiro]

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

I found the following in the log:

2021-04-24T15:06:45.359221Z 0 [ERROR] [MY-010262] [Server] Can't start server: 
Bind on TCP/IP port: Address already in use
2021-04-24T15:06:45.359439Z 0 [ERROR] [MY-010257] [Server] Do you already have 
another mysqld server running on port: 3306 ?
2021-04-24T15:06:45.359880Z 0 [ERROR] [MY-010119] [Server] Aborting

A process was already running and using the default mysql port, that's
why the installation failed. Could you check if you were already running
a mysql instance before you installed it?

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/1926019

Title:
  package mysql-server-8.0 8.0.23-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/1926019/+subscriptions

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

[Bug 1323758] Re: Mouse stops working when connected usb-storage-device

[Lucas Kanashiro]

@Kendrick could you please tell us which version of Ubuntu and qemu you
are using?

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

Title:
  Mouse stops working when connected usb-storage-device

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

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

[Bug 1883315] Re: Showing esm update as installable when esm is disabled

[Lucas Albuquerque Medeiros de Moura]

** Changed in: update-notifier (Ubuntu Xenial)
 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/1883315

Title:
  Showing esm update as installable when esm is disabled

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

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

[Bug 1924766] Re: update-notifier does not handle ESM Apps in the apt-check script

[Lucas Albuquerque Medeiros de Moura]

** Changed in: update-notifier (Ubuntu Xenial)
 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/1924766

Title:
  update-notifier does not handle ESM Apps in the apt-check script

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

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

[Bug 1883315] Re: Showing esm update as installable when esm is disabled

[Lucas Albuquerque Medeiros de Moura]

[Impact]
when users are getting the message update-notifier message through apt-check 
they may find inconsistent behavior regarding ESM products. This is misleading 
since we will say to the users that they don't have ESM Infra, but they do have 
ESM infra packages that can be installed. This is poor marketing of our products

[Test case]

To reproduce the issue, you can:

1. Launch the following old version of a xenial container:
   lxc launch 
ubuntu:f4c4c60a6b752a381288ae72a1689a9da00f8e03b732c8d1b8a8fcd1a8890800 dev-x

2. Run apt update and install the updated version of update-notifier-common
3. Add the ubuntu-advantage-tools ppa:
   https://code.launchpad.net/~ua-client/+archive/ubuntu/daily
4. Install ubuntu-advantage-tools
5. Install the latest version of uaclient from the stable ppa:
   https://launchpad.net/~ua-client/+archive/ubuntu/stable/
6. Comment out all mentions of xenial-security in /etc/apt/source.list
7. Run apt update
8. Run /usr/lib/update-notifier/apt-check --human-readable
9. See a message like this:
   
UA Infra: Extended Security Maintenance (ESM) is not enabled.

256 packages can be updated.
5 of these updates are fixed through UA Infra: ESM.
5 of these updates are security updates.
To see these additional updates run: apt list --upgradable

Enable UA Infra: ESM to receive 5 additional security updates.
See https://ubuntu.com/security/esm or run: sudo ua status


To verify that the error is fixed:

1.Perform all the stages above until step 8
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. See a message like this:

256 updates can be installed immediately.
5 of these updates are security updates.
To see these additional updates run: apt list --upgradable

5. We are now only showing ESM infra specific message if the distro is
ESM. To enforce that behavior, make the `is_esm_distro` function in
`/usr/lub/update-notifier/apt-check` return True, then you will see this
message:

UA Infra: Extended Security Maintenance (ESM) is not enabled.

256 updates can be installed immediately.
5 of these updates are security updates.
To see these additional updates run: apt list --upgradable

5 additional security updates can be applied with UA Infra: ESM
Learn more about enabling UA Infra: ESM service at https://ubuntu.com/esm

That is now correct.

[Where problems could occur]

The changes in this package should only be seen when MOTD is getting a
new message. If that script fails for some reason, it seems that MOTD
will only not present the message, which is doesn't seem to be a system
critical issue. Additionally, we would potentially have tracebacks in
the update-notifier logs. Finally, if the logic is also incorrect, we
would be displying incorrect ESM messages to the user. But since we are
doing this now, as this bug shows, I don't think this is critical as
well.

[Discussion]

With ESM Apps going to production soon, we have decided to update the
messages delivered by update-notifier apt-check to address the package
count of ESM Apps and the possibility of installing more upgrades if the
user has ESM Apps disabled.

We are also updating other parts of the messaging as well. First, we only 
display ESM Infra status
on ESM distros. However, we will keep showing the ESM Infra package count on 
all of them.

For ESM Apps, we are only performing the alerts (For example, that you
might have x packages updates if ESM Apps is installed) if the user is
on a LTS distro.

Since we going to perform that change, we decided to also address this
bit in the SRU, since it could harm the message we are delivering

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

Title:
  Showing esm update as installable when esm is disabled

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

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

[Bug 1891202] Re: Multipathd hangs with long iscsi target names in Ubuntu 18.04

[Lucas Kanashiro]

@fernando-ferraz I updated the bug description to try to make it more
general.

For the verification work needed by the SRU process you need to trigger
the bug, update the package to the version in -proposed, and then
demonstrate that the bug was fixed. If you can do this using your
SolidFire device that would be enough, just make sure you can trigger
the issue with this new hardware. TIA for your work!

** Description changed:

  [Impact]
  
-  * Users of a NetApp E-Series RDAC due to very long names increasing 
-the VDP page and and cause multipathd to hang
+  * Users of some storage devices (for instance NetApp E-Series RDAC) due
+to very long names increasing the VDP page and and cause multipathd to
+hang
  
-  * Introduced as side effect of other changes in 7.4 and fixed later this
-is backporting the HW exploitation to read an enhanced VDP in this case
-which in such cases works fine again.
+  * Introduced as side effect of other changes in 7.4 and fixed later this
+    is backporting the HW exploitation to read an enhanced VDP in this case
+    which in such cases works fine again.
  
  [Test Case]
  
-  * #1 Case: Test on a NetApp E-Series RDAC, the reporter has such HW and 
-is able to do so.
+  * #1 Case: Test on affected hardware. The NetApp E-Series RDAC is an
+example, the reporter has such HW and is able to do so.
  
-  * #2 regression tests: since this touches multipath discovery any such 
-cases would be interesting tests. From installers using multipath on 
-mainframes to multipath-iscsi disks on an raspi. The Range is huge and 
-unclear how much exactly should be done. I can myself do said mainframe 
-checks and utilize the pkgtests to run through iscsid.
-In addition we should keep this one a bit longer in -proposed IMHO.
+  * #2 regression tests: since this touches multipath discovery any such
+    cases would be interesting tests. From installers using multipath on
+    mainframes to multipath-iscsi disks on an raspi. The Range is huge and
+    unclear how much exactly should be done. I can myself do said mainframe
+    checks and utilize the pkgtests to run through iscsid.
+    In addition we should keep this one a bit longer in -proposed IMHO.
  
  [Regression Potential]
  
-  * All cases asking for vpd 0x83 should be unchanged and only those asking
-for an 0xc9 should get the new improved behavior. But I'm not a 100% 
-sure on potential side effects yet. Changes and thereby regressions
-would be limited to the device discovery of multipathd, so that is what 
-one needs to take an extra eye on e.g. pre/post list of multipath 
-devices (and attributes as those are populated via vpd).
+  * All cases asking for vpd 0x83 should be unchanged and only those asking
+    for an 0xc9 should get the new improved behavior. But I'm not a 100%
+    sure on potential side effects yet. Changes and thereby regressions
+    would be limited to the device discovery of multipathd, so that is what
+    one needs to take an extra eye on e.g. pre/post list of multipath
+    devices (and attributes as those are populated via vpd).
  
  [Other Info]
-  
-  * n/a
+ 
+  * n/a
  
  ---
  
  I've notice recently that multipathd started hanging when trying to
  handle long iscsi target names. In my case these targets are generated
  by the OpenStack cinder driver for SolidFire.
  
  My guess is that the problem is occurring due to a bug introduced in
  multipath-tools 0.7.4, by commit "limbultipath: prefer RDAC checker with
  detect_checker*"*[1].
  
  This change adds a routine to check RDAC compatibility during the
  detect_checker procedure, which runs into an infinite loop in the piece
  of code that tries to gather SCSI VPD pages larger than 254 bytes (this
  is my case due to long iSCSI Target names).
  
  This issue was later addressed by several commits in 0.7.5 and 0.7.6:
  "libmultipath: sgio_get_vpd: add page argument" [2], "libmultipath: Fix
  sgio_get_vpd()" [3], "libmultipath: fix return code of sgio_get_vpd()"
  [4], "libmultipath: get_vpd_sgio: support VPD 0xc9" [5].
  
  I've found a temporary work around for this by using select_checker =
  “no” in Ubuntu 18. This appears to avoid the problem by skipping RDAC
  compatibility check code.
  
  Also, I've also tested 0.8.3 in a RH environment and found no issues
  running default select_checker = “yes” (Ubuntu 20 also delivers 0.8.3).
  ‌
  
  So, in short:
  
  - Looks like Ubuntu multipath-tools is broken,
  - There is a fix in newer versions that aren’t in the ubuntu 18 repo yet.
  - The OpenStack Cinder driver for Solidfire just happen to hit this bug 
because of the long names
  - Setting select_checker = “no” is an possible work-around until Ubuntu 
publishes 0.7.6
  
  Bellow "multipath -r -v3" output from my env:
  
  :/$ cat /etc/multipath.conf
  
  devices {
  device {
  vendor "SolidFir" product "SSD SAN" detect_checker "no"
  }
  }
  
  :/$ sudo multipath -r -v3 Jul 

[Bug 1924766] Re: update-notifier does not handle ESM Apps in the apt-check script

[Lucas Albuquerque Medeiros de Moura]

For this SRU bug I have created the following test script:

---
#!/bin/sh
set -x

series=hirsute
name=$series-dev

function update-notifier-ua-not-installed () {
# Expects this output
# x packages can be updated.
# x of these updates are security updates.
echo "---"
echo "$series: ua not installed"
lxc exec $name -- /usr/lib/update-notifier/apt-check --human-readable
echo "---"
}

function update-notifier-ua-not-attached-esm () {
# x updates can be installed immediately.
# x of these updates are security updates.
#   
# Enable UA Apps: ESM to receive x additional security updates.
# See https://ubuntu.com/security/esm or run: sudo ua status
echo "---"
echo "$series esm: ua not attached"
lxc exec $name -- /usr/lib/update-notifier/apt-check --human-readable
echo "---"
}

function update-notifier-ua-not-attached () {
# Expects this output
# UA Infra: Extended Security Maintenance (ESM) is not enabled.
#   
# x updates can be installed immediately.
# x of these updates are security updates.
echo "---"
echo "$series non-esm: ua not attached"
lxc exec $name -- /usr/lib/update-notifier/apt-check --human-readable
echo "---"
}

function update-notifier-ua-attached-esm () {
# Expects this output
# x updates can be installed immediately.
# x of these updates are fixed through UA Apps: ESM.
# x of these updates are security updates.
# To see these additional updates run: apt list --upgradable
echo "---"
echo "$series esm: ua attached"
lxc exec $name -- /usr/lib/update-notifier/apt-check --human-readable
echo "---"
}

function update-notifier-ua-attached () {
# Expects this output
# x updates can be installed immediately.
# x of these updates are fixed through UA Apps: ESM.
# x of these updates are security updates.
# To see these additional updates run: apt list --upgradable
echo "---"
echo "$series non-esm: ua attached"
lxc exec $name -- /usr/lib/update-notifier/apt-check --human-readable
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 -- add-apt-repository ppa:lamoura/update-notifier-test-ppa -y
lxc exec $name -- apt update
lxc exec $name -- apt install update-notifier-common -y
}

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-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
}

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

setup-update-notifier
update-notifier-ua-not-installed
install-ua
turn-distro-into-esm-mode
update-notifier-ua-not-attached-esm
ua-attach
update-notifier-ua-attached-esm
turn-distro-into-non-esm-mode
ua-detach
update-notifier-ua-not-attached
ua-attach
update-notifier-ua-attached

set +x


I have used it to verify the behavior of the updated package on xenial and 
hirsute. The packages used to perform such testing are found on this ppa:
https://launchpad.net/~lamoura/+archive/ubuntu/update-notifier-test-ppa

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

Title:
  update-notifier does not handle ESM Apps in the apt-check script

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

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

[Bug 1924766] [NEW] update-notifier does not handle ESM Apps in the apt-check script

[Lucas Albuquerque Medeiros de Moura]

Public bug reported:

[Impact]
When ESM Apps goes into production we want to be able to advertise it to our 
users through MOTD.
Currently, update-notifier apt-check does not take into consideration the 
exclusive packages of ESM Apps, which is a problem.

[Test case]

To reproduce the issue, you can:

1. Launch a xenial vm
2. Install the latest version of uaclient from the stable ppa:
   https://launchpad.net/~ua-client/+archive/ubuntu/stable/
3. Change the following line on `/etc/ubuntu-advantage/uaclient.conf` from
   
   contract_url: 'https://contracts.canonical.com'

   To:

   contract_url: 'https://contracts.staging.canonical.com'

4. Attach a staging token to uaclient thorough:

ua attach YOUR_STAGING_TOKEN

5. Run /usr/lib/update-notifier/apt-check --human-readable
6. Verify that no mention to ESM Apps is made and that update-notifier puts all 
of the ESM packages in the same bucket


To verify that the error is fixed:

1.Perform all the stages above until step 4
2 Install the new update-notifier from this ppa:
  https://launchpad.net/~lamoura/+archive/ubuntu/update-notifier-test-ppa
3. Verify now that ESM Apps is reflected in the message

[Where problems could occur]

The changes in this package should only be seen when MOTD is getting a
new message. If that script fails for some reason, it seems that MOTD
will only not present the message, which is doesn't seem to be a system
critical issue.

[Discussion]

With ESM Apps going to production soon, we have decided to update the
messages delivered by update-notifier apt-check to address the package
count of ESM Apps and the possibility of installing more upgrades if the
user has ESM Apps disabled.

We are also updating other parts of the messaging as well. First, we only 
display ESM Infra status
on ESM distros. However, we will keep showing the ESM Infra package count on 
all of them.

For ESM Apps, we are only performing the alerts (For example, that you
might have x packages updates if ESM Apps is installed) if the user is
on a LTS distro.

Finally, we are also addressing this bug here:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1883315

Where we were incorrectly counting ESM packages even if the user did not
have access to those services.

== Changelog ==

  + data/apt-check
- Make distinction of ESM Apps and ESM Infra when doing package count
- Only count ESM packages if the user has access to the service (LP 
#1883315)
- Only display ESM Infra alerts if the distro is ESM

** Affects: update-notifier (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: update-notifier (Ubuntu Xenial)
   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/1924766

Title:
  update-notifier does not handle ESM Apps in the apt-check script

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

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

[Bug 1923108] Re: FTBFS against docker 20.10

[Lucas Kanashiro]

The package built fine on LP which means all the upstream tests passed
during build time.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  FTBFS against docker 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-fsouza-go-dockerclient/+bug/1923108/+subscriptions

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

[Bug 1922509] Re: ssh doesn't work after stoping all open-vpn services

[Lucas Kanashiro]

@mats if you still think this is a bug you can provide detailed
steps on how to reproduce it in a new system. Please, do not provide
steps using scripts found in non-official tutorials on the internet,
they are not supported by us. In case we reproduce it locally this
becomes actionable, until there it will keep as Incomplete. And no need
to file another bug, once you provide the steps to reproduce it you can
change the status of the bug back to New.

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

Title:
  ssh doesn't work after stoping all open-vpn services

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

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

[Bug 1792980] Re: cannot install libudev-dev

[Lucas Kanashiro]

I launched a brand new Focal container and tried to install libudev-dev,
it worked as expected:

root@libudev-test:~# apt install -y libudev-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
The following NEW packages will be installed:
  libudev-dev
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 19.7 kB of archives.
After this operation, 246 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libudev-dev 
amd64 245.4-4ubuntu3.6 [19.7 kB]
Fetched 19.7 kB in 1s (26.2 kB/s)  
Selecting previously unselected package libudev-dev:amd64.
(Reading database ... 31598 files and directories currently installed.)
Preparing to unpack .../libudev-dev_245.4-4ubuntu3.6_amd64.deb ...
Unpacking libudev-dev:amd64 (245.4-4ubuntu3.6) ...
Setting up libudev-dev:amd64 (245.4-4ubuntu3.6) ...
Processing triggers for man-db (2.9.1-1) ...
root@libudev-test:~# cat /etc/os-release 
NAME="Ubuntu"
VERSION="20.04.2 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.2 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal


Not sure which kind of issue you are facing but the package is install-able as 
you can see above.

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

Title:
  cannot install libudev-dev

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

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

[Bug 1806421] Re: perl_bulk_gets patch breaks some scripts

[Lucas Kanashiro]

** Changed in: net-snmp (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  perl_bulk_gets patch breaks some scripts

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

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

[Bug 1919322] Re: Backport the container stack in Hirsute

[Lucas Kanashiro]

More detailed analysis of the reverse build dependencies:

Groovy
==

$ reverse-depends -r groovy -b docker.io
Reverse-Testsuite-Triggers
* python-docker
* ubuntu-fan
* ubuntu-make

Status of the reverse build dependencies listed above in Groovy:

- python-docker
  + It builds fine with the new container stack.
- ubuntu-fan
  + It builds fine with the new container stack.
- ubuntu-make
  + It FTBFS without the container stack update. LP #1923244 was filed to track 
this. Not considered a regression.

$ reverse-depends -r groovy -b golang-github-docker-docker-dev
Reverse-Build-Depends
* golang-github-containers-buildah
* golang-github-containers-common
* golang-github-containers-image
* golang-github-fsouza-go-dockerclient
* golang-github-openshift-imagebuilder
* golang-github-samalba-dockerclient
* golang-github-tonistiigi-fsutil
* libpod
* nomad
* prometheus
* skopeo

Status of the reverse build dependencies listed above in Groovy:

- golang-github-containers-buildah
  + It FTBFS because of the new runc. Fixed in LP #1921011.
- golang-github-containers-common
  + It builds fine with the new container stack.
- golang-github-containers-image
  + It builds fine with the new container stack.
- golang-github-fsouza-go-dockerclient
  + It builds fine with the new container stack.
- golang-github-openshift-imagebuilder
  + It builds fine with the new container stack.
- golang-github-samalba-dockerclient
  + It builds fine with the new container stack.
- golang-github-tonistiigi-fsutil
  + It builds fine with the new container stack.
- libpod
  + It FTBFS because of the new runc. Fixed in LP #1921011.
- nomad
  + It FTBFS without the container stack update. LP #1923237 was filed to track 
this. Not considered a regression.
- prometheus
  + It builds fine with the new container stack.
- skopeo
  + It builds fine with the new container stack.

Focal
==

$ reverse-depends -r focal -b docker.io
Reverse-Testsuite-Triggers
* python-docker
* ubuntu-fan
* ubuntu-make

Status of the reverse build dependencies listed above in Focal:

- python-docker
  + It builds fine with the new container stack.
- ubuntu-fan
  + It builds fine with the new container stack.
- ubuntu-make
  + It FTBFS without the container stack update. LP #1923244 was filed to track 
this. Not considered a regression.

$ reverse-depends -r focal -b golang-github-docker-docker-dev
Reverse-Build-Depends
* cadvisor
* gitlab-ci-multi-runner
* golang-github-containers-image
* golang-github-fsouza-go-dockerclient
* golang-github-openshift-imagebuilder
* golang-github-samalba-dockerclient
* nomad

Status of the reverse build dependencies listed above in Focal:

- cadvisor
  + It FTBFS without the container stack update. LP #1923238 was filed to track 
this. Not considered a regression.
- gitlab-ci-multi-runner
- golang-github-containers-image
  + It builds fine with the new container stack.
- golang-github-fsouza-go-dockerclient
  + It builds fine with the new container stack.
- golang-github-openshift-imagebuilder
  + It builds fine with the new container stack.
- golang-github-samalba-dockerclient
  + It builds fine with the new container stack.
- nomad
  + It FTBFS without the container stack update. LP #1923237 was filed to track 
this. Not considered a regression.

Bionic
==

$ reverse-depends -r bionic -b docker.io
Reverse-Testsuite-Triggers
* python-docker
* ubuntu-fan

Status of the reverse build dependencies listed above in Bionic:

- python-docker
  + It builds fine with the new container stack.
- ubuntu-fan
  + It builds fine with the new container stack.

$ reverse-depends -r bionic -b golang-github-docker-docker-dev
Reverse-Build-Depends
* cadvisor
* golang-github-docker-libnetwork
* golang-github-fsouza-go-dockerclient
* golang-github-samalba-dockerclient
* nomad
* notary
* systemd-docker


Status of the reverse build dependencies listed above in Bionic:

- cadvisor
  + It FTBFS without the container stack update. LP #1923238 was filed to track 
this. Not considered a regression.
- golang-github-docker-libnetwork
  + It FTBFS without the container stack update. LP #1923239 was filed to track 
this. Not considered a regression.
- golang-github-fsouza-go-dockerclient
  + It FTBFS because of the new docker.io. Fixed in LP #1923239.
- golang-github-samalba-dockerclient
  + It builds fine with the new container stack.
- nomad
  + It FTBFS without the container stack update. LP #1923237 was filed to track 
this. Not considered a regression.
- notary
  + It FTBFS without the container stack update. LP #1923242 was filed to track 
this. Not considered a regression.
- systemd-docker
  + It FTBFS without the container stack update. LP #1923243 was filed to track 
this. Not considered a regression.

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

Title:
  Backport the container stack in Hirsute

To manage notifications about this bug go to:

[Bug 1923244] [NEW] FTBFS in multiple Ubuntu series

[Lucas Kanashiro]

Public bug reported:

Groovy
==

ubuntu-make/18.09+disco1 currently FTBFS in Groovy. The following tests
are failing during build time:

==
ERROR: we deliver one successful download under ssl with known cert
--
Traceback (most recent call last):
  File "/<>/tests/small/test_download_center.py", line 541, in 
test_download
result.fd.read())
AttributeError: 'NoneType' object has no attribute 'read'
 >> begin captured logging << 
2021-04-09 19:50:26,869 [tests.tools.local_server] INFO: Stopping serving on 
9876
2021-04-09 19:50:27,361 [tests.tools.local_server] INFO: Serving locally from 
/<>/tests/data/server-content on https://poseidon:9876
2021-04-09 19:50:27,362 [umake.network.download_center] INFO: Start downloading 
DownloadItem(url='https://localhost:9876/simplefile', checksum=None, 
headers=None, ignore_encoding=False, cookies=None) to a temp file
2021-04-09 19:50:27,384 [urllib3.connectionpool] DEBUG: Starting new HTTPS 
connection (1): localhost:9876
2021-04-09 19:50:27,467 [umake.network.download_center] ERROR: 
https://localhost:9876/simplefile couldn't finish download: ('Connection 
aborted.', ConnectionResetError(104, 'Connection reset by peer'))
2021-04-09 19:50:27,478 [umake.network.download_center] INFO: All pending 
downloads for [DownloadItem(url='https://localhost:9876/simplefile', 
checksum=None, headers=None, ignore_encoding=False, cookies=None)] done
- >> end captured logging << -

==
FAIL: we deliver one successful download under ssl with known cert
--
Traceback (most recent call last):
  File "/<>/tests/small/test_download_center.py", line 519, in 
tearDown
super().tearDown()
  File "/<>/tests/tools/__init__.py", line 64, in tearDown
self.assertEqual(self.error_warn_logs.getvalue(), "")
AssertionError: "https://localhost:9876/simplefile couldn[96 chars]))\n" != ''
- https://localhost:9876/simplefile couldn't finish download: ('Connection 
aborted.', ConnectionResetError(104, 'Connection reset by peer'))

 >> begin captured logging << 
2021-04-09 19:50:26,869 [tests.tools.local_server] INFO: Stopping serving on 
9876
2021-04-09 19:50:27,361 [tests.tools.local_server] INFO: Serving locally from 
/<>/tests/data/server-content on https://poseidon:9876
2021-04-09 19:50:27,362 [umake.network.download_center] INFO: Start downloading 
DownloadItem(url='https://localhost:9876/simplefile', checksum=None, 
headers=None, ignore_encoding=False, cookies=None) to a temp file
2021-04-09 19:50:27,384 [urllib3.connectionpool] DEBUG: Starting new HTTPS 
connection (1): localhost:9876
2021-04-09 19:50:27,467 [umake.network.download_center] ERROR: 
https://localhost:9876/simplefile couldn't finish download: ('Connection 
aborted.', ConnectionResetError(104, 'Connection reset by peer'))
2021-04-09 19:50:27,478 [umake.network.download_center] INFO: All pending 
downloads for [DownloadItem(url='https://localhost:9876/simplefile', 
checksum=None, headers=None, ignore_encoding=False, cookies=None)] done
- >> end captured logging << -

==
FAIL: we deliver one successful download after being redirected
--
Traceback (most recent call last):
  File "/<>/tests/small/test_download_center.py", line 559, in 
test_redirect_download
self.assertEqual(result.final_url, 
TestDownloadCenter.build_server_address(self, filename, localhost=True))
AssertionError: None != 'https://localhost:9876/simplefile'
 >> begin captured logging << 
2021-04-09 19:50:27,479 [umake.network.download_center] INFO: Start downloading 
DownloadItem(url='https://localhost:9876/simplefile-redirect', checksum=None, 
headers=None, ignore_encoding=False, cookies=None) to a temp file
2021-04-09 19:50:27,501 [urllib3.connectionpool] DEBUG: Starting new HTTPS 
connection (1): localhost:9876
2021-04-09 19:50:27,568 [umake.network.download_center] ERROR: 
https://localhost:9876/simplefile-redirect couldn't finish download: 
HTTPSConnectionPool(host='localhost', port=9876): Max retries exceeded with 
url: /simplefile-redirect (Caused by SSLError(SSLEOFError(8, 'EOF occurred in 
violation of protocol (_ssl.c:1124)')))
2021-04-09 19:50:27,584 [umake.network.download_center] INFO: All pending 
downloads for [DownloadItem(url='https://localhost:9876/simplefile-redirect', 
checksum=None, headers=None, ignore_encoding=False, cookies=None)] done
- >> end captured logging << -

[Bug 1923243] [NEW] FTBFS in Bionic

[Lucas Kanashiro]

Public bug reported:

systemd-docker/0.2.1+dfsg-2 currently FTBFS in Bionic. A build
dependency seems to be missing:

src/github.com/ibuildthecloud/systemd-docker/main.go:19:2: cannot find package 
"github.com/docker/docker/pkg/mflag" in any of:
/usr/lib/go-1.10/src/github.com/docker/docker/pkg/mflag (from $GOROOT)

/<>/obj-x86_64-linux-gnu/src/github.com/docker/docker/pkg/mflag 
(from $GOPATH)

** Affects: systemd-docker (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: systemd-docker (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Also affects: systemd-docker (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: systemd-docker (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/1923243

Title:
  FTBFS in Bionic

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

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

[Bug 1923242] [NEW] FTBFS in Bionic

[Lucas Kanashiro]

Public bug reported:

notary/0.1~ds1-1 currently FTBFS in Bionic. A build dependency seems to
be missing:

src/github.com/docker/notary/cmd/notary-server/main.go:25:2: cannot find 
package "github.com/Sirupsen/logrus/hooks/bugsnag" in any of:
/usr/lib/go-1.10/src/github.com/Sirupsen/logrus/hooks/bugsnag (from 
$GOROOT)

/<>/obj-x86_64-linux-gnu/src/github.com/Sirupsen/logrus/hooks/bugsnag
 (from $GOPATH)

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

** Affects: notary (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Also affects: notary (Ubuntu Bionic)
   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/1923242

Title:
  FTBFS in Bionic

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

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

[Bug 1923237] Re: FTBFS in multiple Ubuntu series

[Lucas Kanashiro]

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

** Description changed:

  Groovy
  =
  
  nomad/0.10.5+dfsg1-1ubuntu2 currently FTBFS in Groovy. The following
  test has been failing:
  
  === CONT  TestServer_Reload_Vault
  testing.go:129: timed out while shutting down server
  --- FAIL: TestServer_Reload_Vault (60.08s)
  FAIL
  FAILgithub.com/hashicorp/nomad/nomad66.842s
  
  Focal
  =
  
  nomad/0.8.7+dfsg1-1ubuntu1 currently FTBFS in Focal. The following
  failures are reported during the build:
  
  src/github.com/hashicorp/nomad/client/structs/structs.go
  codecgen error: error running 'go run codecgen-main-102.generated.go': exit 
status 2, console: # github.com/hashicorp/nomad/client/stats
  ../stats/host.go:249:70: times.Stolen undefined (type 
"github.com/shirou/gopsutil/cpu".TimesStat has no field or method Stolen)
  # github.com/hashicorp/nomad/nomad/structs
  ../../nomad/structs/structs.go:6889:28: cannot use promoted field 
BasicHandle.DecodeOptions.RawToString in struct literal of type 
"github.com/ugorji/go/codec".MsgpackHandle
  
  src/github.com/hashicorp/nomad/client/structs/structs.go:3: running 
"codecgen": exit status 1
  ...
  src/github.com/hashicorp/nomad/nomad/structs/structs_codegen.go
  codecgen error: error running 'go run codecgen-main-100.generated.go': exit 
status 2, console: # github.com/hashicorp/nomad/nomad/structs
  ./structs.go:6889:28: cannot use promoted field 
BasicHandle.DecodeOptions.RawToString in struct literal of type 
"github.com/ugorji/go/codec".MsgpackHandle
  
  src/github.com/hashicorp/nomad/nomad/structs/structs_codegen.go:3:
  running "../../../../../../../nomad/structs/generate.sh": exit status 1
+ 
+ Bionic
+ ==
+ 
+ nomad/0.4.0+dfsg-1 currently FTBFS in Bionic. The following failures are
+ reported during the build:
+ 
+ github.com/hashicorp/nomad/client/driver/executor
+ # github.com/hashicorp/nomad/client/driver/executor
+ 
src/github.com/hashicorp/nomad/client/driver/executor/executor_linux.go:103:37: 
cannot use true (type bool) as type *bool in assignment
+ 
src/github.com/hashicorp/nomad/client/driver/executor/executor_linux.go:117:31: 
cannot use int64(resources.CPU) (type int64) as type uint64 in assignment

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

Title:
  FTBFS in multiple Ubuntu series

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

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

[Bug 1923238] [NEW] FTBFS in multiple Ubuntu series

[Lucas Kanashiro]

Public bug reported:

Focal
=

cadvisor/0.27.1+dfsg2-4 currently FTBFS in Focal. A build dependency
seems to be missing:

src/github.com/google/cadvisor/container/common/inotify_watcher.go:20:2: cannot 
find package "golang.org/x/exp/inotify" in any of:

/<>/_build/src/github.com/google/cadvisor/vendor/golang.org/x/exp/inotify
 (vendor tree)
/usr/lib/go-1.13/src/golang.org/x/exp/inotify (from $GOROOT)
/<>/_build/src/golang.org/x/exp/inotify (from $GOPATH)

Bionic
==

cadvisor/0.27.1+dfsg-1 currently FTBFS in Bionic. The following error is
reported during build time:

github.com/google/cadvisor/fs
# github.com/google/cadvisor/fs
src/github.com/google/cadvisor/fs/fs.go:109:32: not enough arguments in call to 
mount.GetMounts
have ()
want (mount.FilterFunc)

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

** Affects: cadvisor (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: cadvisor (Ubuntu Focal)
 Importance: Undecided
 Status: New

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

** Summary changed:

- FTBFS in Focal
+ FTBFS in multiple Ubuntu series

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

** Description changed:

+ Focal
+ =
+ 
  cadvisor/0.27.1+dfsg2-4 currently FTBFS in Focal. A build dependency
  seems to be missing:
  
  src/github.com/google/cadvisor/container/common/inotify_watcher.go:20:2: 
cannot find package "golang.org/x/exp/inotify" in any of:
- 
/<>/_build/src/github.com/google/cadvisor/vendor/golang.org/x/exp/inotify
 (vendor tree)
- /usr/lib/go-1.13/src/golang.org/x/exp/inotify (from $GOROOT)
- /<>/_build/src/golang.org/x/exp/inotify (from $GOPATH)
+ 
/<>/_build/src/github.com/google/cadvisor/vendor/golang.org/x/exp/inotify
 (vendor tree)
+ /usr/lib/go-1.13/src/golang.org/x/exp/inotify (from $GOROOT)
+ /<>/_build/src/golang.org/x/exp/inotify (from $GOPATH)
+ 
+ Bionic
+ ==
+ 
+ cadvisor/0.27.1+dfsg-1 currently FTBFS in Bionic. The following error is
+ reported during build time:
+ 
+ github.com/google/cadvisor/fs
+ # github.com/google/cadvisor/fs
+ src/github.com/google/cadvisor/fs/fs.go:109:32: not enough arguments in call 
to mount.GetMounts
+   have ()
+   want (mount.FilterFunc)

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

Title:
  FTBFS in multiple Ubuntu series

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

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

[Bug 1923239] [NEW] FTBFS in Bionic

[Lucas Kanashiro]

Public bug reported:

golang-github-docker-libnetwork/0.8.0-dev.2+git20170202.599.45b4086-3
currently FTBFS in Bionic. The following error is reported during build
time:

github.com/docker/libnetwork
# github.com/docker/libnetwork
src/github.com/docker/libnetwork/controller.go:1096:69: undefined: 
plugingetter.LOOKUP
src/github.com/docker/libnetwork/controller.go:1115:53: undefined: 
plugingetter.LOOKUP
src/github.com/docker/libnetwork/sandbox_externalkey_unix.go:47:12: undefined: 
configs.HookState

** Affects: golang-github-docker-libnetwork (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: golang-github-docker-libnetwork (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Also affects: golang-github-docker-libnetwork (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: golang-github-docker-libnetwork (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/1923239

Title:
  FTBFS in Bionic

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

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

[Bug 1923237] Re: FTBFS in multiple Ubuntu series

[Lucas Kanashiro]

** Summary changed:

- FTBFS
+ FTBFS in multiple Ubuntu series

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

** Description changed:

+ Groovy
+ =
+ 
  nomad/0.10.5+dfsg1-1ubuntu2 currently FTBFS in Groovy. The following
  test has been failing:
  
  === CONT  TestServer_Reload_Vault
- testing.go:129: timed out while shutting down server
+ testing.go:129: timed out while shutting down server
  --- FAIL: TestServer_Reload_Vault (60.08s)
  FAIL
  FAILgithub.com/hashicorp/nomad/nomad66.842s
+ 
+ Focal
+ =
+ 
+ nomad/0.8.7+dfsg1-1ubuntu1 currently FTBFS in Focal. The following
+ failures are reported during the build:
+ 
+ src/github.com/hashicorp/nomad/client/structs/structs.go
+ codecgen error: error running 'go run codecgen-main-102.generated.go': exit 
status 2, console: # github.com/hashicorp/nomad/client/stats
+ ../stats/host.go:249:70: times.Stolen undefined (type 
"github.com/shirou/gopsutil/cpu".TimesStat has no field or method Stolen)
+ # github.com/hashicorp/nomad/nomad/structs
+ ../../nomad/structs/structs.go:6889:28: cannot use promoted field 
BasicHandle.DecodeOptions.RawToString in struct literal of type 
"github.com/ugorji/go/codec".MsgpackHandle
+ 
+ src/github.com/hashicorp/nomad/client/structs/structs.go:3: running 
"codecgen": exit status 1
+ ...
+ src/github.com/hashicorp/nomad/nomad/structs/structs_codegen.go
+ codecgen error: error running 'go run codecgen-main-100.generated.go': exit 
status 2, console: # github.com/hashicorp/nomad/nomad/structs
+ ./structs.go:6889:28: cannot use promoted field 
BasicHandle.DecodeOptions.RawToString in struct literal of type 
"github.com/ugorji/go/codec".MsgpackHandle
+ 
+ src/github.com/hashicorp/nomad/nomad/structs/structs_codegen.go:3:
+ running "../../../../../../../nomad/structs/generate.sh": 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/1923237

Title:
  FTBFS in multiple Ubuntu series

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

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

[Bug 1923237] [NEW] FTBFS

[Lucas Kanashiro]

Public bug reported:

nomad/0.10.5+dfsg1-1ubuntu2 currently FTBFS in Groovy. The following
test has been failing:

=== CONT  TestServer_Reload_Vault
testing.go:129: timed out while shutting down server
--- FAIL: TestServer_Reload_Vault (60.08s)
FAIL
FAILgithub.com/hashicorp/nomad/nomad66.842s

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

** Affects: nomad (Ubuntu Groovy)
 Importance: Undecided
 Status: New

** Also affects: nomad (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/1923237

Title:
  FTBFS

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

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

[Bug 1921011] Re: Fix build against new runc version

[Lucas Kanashiro]

The test plan indicates that the build time tests and DEP-8 tests should
pass.

- Both packages built fine on LP.
- libpod DEP-8 test is passing but the golang-github-containers-buildah DEP-8 
test is failing for a while so I'd ask to ignore it.

golang-github-containers-buildah autopkgtest history:

http://autopkgtest.ubuntu.com/packages/golang-github-containers-buildah

autopkgtest summary output for libpod:

autopkgtest [09:47:06]:  summary
dh-golang-autopkgtest PASS


** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy

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

Title:
  Fix build against new runc version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1921011/+subscriptions

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

[Bug 1919322] Re: Backport the container stack in Hirsute

[Lucas Kanashiro]

I have checked the reverse build dependencies and I noticed the
following FTBFS due to the new docker.io version:

- golang-github-fsouza-go-dockerclient (bionic)

Other reverse build dependencies are failing to build but it is not
because of the container stack update, they were failing already (I
confirmed that building the packages without -proposed enabled).

For golang-github-fsouza-go-dockerclient I already have a fix here
(waiting for the SRU team):

https://bugs.launchpad.net/ubuntu/+source/golang-github-fsouza-go-
dockerclient/+bug/1923108

FWIW I uploaded some of those reverse dependencies to this PPA:

https://launchpad.net/~lucaskanashiro/+archive/ubuntu/buildah-and-
libpod/

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

Title:
  Backport the container stack in Hirsute

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

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

[Bug 1923108] Re: FTBFS against docker 20.10

[Lucas Kanashiro]

Package uploaded.

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

Title:
  FTBFS against docker 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-fsouza-go-dockerclient/+bug/1923108/+subscriptions

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

[Bug 1923108] Re: FTBFS against docker 20.10

[Lucas Kanashiro]

Thanks for the review Sergio!

I indeed forgot the add references to the LP bug, it is done now.
Regarding the DEP-8 tests you are right, there is no definition for
them. I'll update the bug description to add the upstream tests executed
during build time instead of DEP-8 tests, I think we do not have many
options.

** Attachment added: "debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/golang-github-fsouza-go-dockerclient/+bug/1923108/+attachment/5485730/+files/debdiff

** Description changed:

  [Impact]
  
  The version in Bionic FTBFS against docker 20.10 currently in bionic-
  proposed. This would be considered a regression.
  
  [Test Plan]
  
- DEP-8 tests passing.
+ Make sure the upstream test suite is passing during build time.
  
  [Where problems could occur]
  
  There could be any breakage related to the move from Go 1.10 to 1.13.
  Moreover, the network part of the library needs to be patched to support
  the new Go version, so any issue in this area could be related to this
  update.

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

Title:
  FTBFS against docker 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-fsouza-go-dockerclient/+bug/1923108/+subscriptions

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

[Bug 1923108] Re: FTBFS against docker 20.10

[Lucas Kanashiro]

** Description changed:

  [Impact]
  
  The version in Bionic FTBFS against docker 20.10 currently in bionic-
- proposed. This would be consider a regression.
+ proposed. This would be considered a regression.
  
  [Test Plan]
  
  DEP-8 tests passing.
  
  [Where problems could occur]
  
  There could be any breakage related to the move from Go 1.10 to 1.13.
  Moreover, the network part of the library needs to be patched to support
  the new Go version, so any issue in this area could be related to this
  update.

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

Title:
  FTBFS against docker 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-fsouza-go-dockerclient/+bug/1923108/+subscriptions

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

[Bug 1923108] Re: FTBFS against docker 20.10

[Lucas Kanashiro]

The attached patch fixes the FTBFS in bionic (with bionic-proposed
enabled). I uploaded this packages to this PPA to confirm that:

https://launchpad.net/~lucaskanashiro/+archive/ubuntu/buildah-and-libpod

** Attachment added: "debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/golang-github-fsouza-go-dockerclient/+bug/1923108/+attachment/5485715/+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/1923108

Title:
  FTBFS against docker 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-fsouza-go-dockerclient/+bug/1923108/+subscriptions

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

[Bug 1923108] [NEW] FTBFS against docker 20.10

[Lucas Kanashiro]

Public bug reported:

[Impact]

The version in Bionic FTBFS against docker 20.10 currently in bionic-
proposed. This would be considered a regression.

[Test Plan]

DEP-8 tests passing.

[Where problems could occur]

There could be any breakage related to the move from Go 1.10 to 1.13.
Moreover, the network part of the library needs to be patched to support
the new Go version, so any issue in this area could be related to this
update.

** Affects: golang-github-fsouza-go-dockerclient (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: golang-github-fsouza-go-dockerclient (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Also affects: golang-github-fsouza-go-dockerclient (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

Title:
  FTBFS against docker 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-fsouza-go-dockerclient/+bug/1923108/+subscriptions

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

[Bug 1916485] Re: test -x fails inside shell scripts in containers

[Lucas Kanashiro]

Sorry, I forgot to update the tags. Nothing is missing in the runc
verification, we can release it.

** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy

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

Title:
  test -x fails inside shell scripts in containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions

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

[Bug 1889070] Re: [SRU] Add LPAR fence agent to Pacemaker (fence-agents)

[Lucas Kanashiro]

Hi "bw...@de.ibm.com", could you perform the same tests you did
previously but now using the fence-agents package from focal-proposed
instead of my PPA? You can check the "Test plan" section in the bug
description but it is basically what you already did. This is part of
the SRU process and we need that to move forward. TIA!

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

Title:
  [SRU] Add LPAR fence agent to Pacemaker (fence-agents)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889070/+subscriptions

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

[Bug 1921011] Re: Fix build against new runc version

[Lucas Kanashiro]

Packages uploaded.

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

Title:
  Fix build against new runc version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1921011/+subscriptions

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

[Bug 1921011] Re: Fix build against new runc version

[Lucas Kanashiro]

Both packages built fine in this PPA:

https://launchpad.net/~lucaskanashiro/+archive/ubuntu/buildah-and-
libpod/+packages

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

Title:
  Fix build against new runc version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1921011/+subscriptions

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

[Bug 1921011] Re: Fix build against new runc version

[Lucas Kanashiro]

The libpod package FTBFS because of the new version of the docker.io
package in groovy-proposed. The attached debdiff fixes this issue.

** Patch added: "libpod.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/1921011/+attachment/5485291/+files/libpod.debdiff

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

Title:
  Fix build against new runc version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1921011/+subscriptions

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

[Bug 1921011] Re: Fix build against new runc version

[Lucas Kanashiro]

The golang-github-containers-buildah package FTBFS because of the new
version of the docker.io package in groovy-proposed. The attached
debdiff fixes this issue.

** Patch added: "golang-github-containers-buildah.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/1921011/+attachment/5485266/+files/golang-github-containers-buildah.debdiff

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

Title:
  Fix build against new runc version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1921011/+subscriptions

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

[Bug 1912691] Re: [SRU] Support runc/1.0.0~rc93-0ubuntu1

[Lucas Kanashiro]

The test plan says the upstream test suite should be executed to catch
any regression. This was done during the package build process and it
succeeded. Therefore, I am considering the validation as done for this
SRU.

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal verification-needed-groovy
** Tags added: verification-done verification-done-bionic 
verification-done-focal verification-done-groovy

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

Title:
  [SRU] Support runc/1.0.0~rc93-0ubuntu1

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

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

[Bug 1890491] Re: A pacemaker node fails monitor (probe) and stop /start operations on a resource because it returns "rc=189

[Lucas Kanashiro]

Sorry for taking too long to get to this bug. I have some comments about
the proposed debdiff:

1- The version needs to be updated to 1.1.18-0ubuntu1.4. The .3 version
was already released to bionic-updates.

2- The patches need some DEP-3 headers. I see you are just backporting
the upstream patches but it would be good to also add some headers after
the original commit message, such as Origin, Bug-Ubuntu, Reviewed-By.

3- The patches 0001-Fix-libpe_status-don-t-order-implied-stops-
relative-.patch and 0002-Fix-scheduler-remote-state-is-failed-if-node-
is-shut.patch are in the debdiff but they are not mentioned in
debian/patches/series nor debian/changelog. Should they be removed? Or
added to d/p/series and d/changelog?

The proposed debdiff as-is built fine for me locally. We need to address
the comments above to be able to upload this package. In parallel, we
can update the bug description to add the SRU template (impact, test
plan, where problems could occur), are you willing to do that @Jorge?

Thanks for the work you have done so far!

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

Title:
  A pacemaker node fails monitor (probe) and stop /start operations on a
  resource because it returns "rc=189

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

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

[Bug 1889070] Re: [20.10 FEAT] Add LPAR fence agent to Pacemaker (fence-agents)

[Lucas Kanashiro]

** Description changed:

+ [Impact]
+ 
+ fence-agents does not support fencing IBMz LPAR. This is a key feature
+ to support Corosync/Pacemaker clusters in IBM Cloud. We can consider
+ this as hardware enablement.
+ 
+ [Test Plan]
+ 
+ Install the fence-agents package (in Bionic do not forget to install the
+ suggested dependencies) in the nodes of the Corosync/Pacemaker cluster
+ and try to call the fence_ibmz agent to change the status of one of the
+ machines. For instance:
+ 
+ # fence_ibmz --ip= --username= --password= 
--plug=M46/m46lp64 -o status
+ Status: ON
+ # fence_ibmz --ip= --username= --password= 
--plug=M46/m46lp64 -o off
+ Success: Powered OFF
+ # fence_ibmz --ip= --username= --password= 
--plug=M46/m46lp64 -o status
+ Status: OFF
+ # fence_ibmz --ip= --username= --password= 
--plug=M46/m46lp64 -o on
+ Success: Powered ON
+ # fence_ibmz --ip= --username= --password= 
--plug=M46/m46lp64 -o status
+ Status: ON
+ 
+ 
+ [Where problems could occur]
+ 
+ This is a backport of a new agent, therefore, the patch does not touch
+ the existent code base. The only piece that could suffer from a problem
+ would be the IBMz LPAR fence agent itself.
+ 
+ [Original message]
+ 
  Currently following versions are available.
  
- Package fence-agents
- focal (20.04LTS) (admin): Fence Agents for Red Hat Cluster [universe]
- 4.5.2-1: amd64 arm64 armhf ppc64el s390x
- groovy (admin): Fence Agents for Red Hat Cluster [universe]
- 4.5.2-1: amd64 arm64 armhf ppc64el s390x
+ Package fence-agents
+ focal (20.04LTS) (admin): Fence Agents for Red Hat Cluster [universe]
+ 4.5.2-1: amd64 arm64 armhf ppc64el s390x
+ groovy (admin): Fence Agents for Red Hat Cluster [universe]
+ 4.5.2-1: amd64 arm64 armhf ppc64el s390x
  
  A pull request has been accepted upstream:
  
  https://github.com/ClusterLabs/fence-agents/pull/349 but not yet
  released in a public release.
  
- Please add this to 20.10 and also for 20.04. 
+ Please add this to 20.10 and also for 20.04.
  Many thanks in advance

** Summary changed:

- [20.10 FEAT] Add LPAR fence agent to Pacemaker (fence-agents)
+ [SRU] Add LPAR fence agent to Pacemaker (fence-agents)

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

Title:
  [SRU] Add LPAR fence agent to Pacemaker (fence-agents)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889070/+subscriptions

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

[Bug 1889070] Re: [20.10 FEAT] Add LPAR fence agent to Pacemaker (fence-agents)

[Lucas Kanashiro]

Thanks for testing the packages "bw...@de.ibm.com", appreciated! We will
need to double-check them when the SRU team accepts them into the
proposed pocket. For now, we have enough testing :)

Regarding the python-requests package: it is already a suggested
dependency in Bionic. In Focal you did not have this issue because it
was promoted to a hard runtime dependency. That was done by the Debian
maintainer due to this bug:

https://bugs.debian.org/899381

A way to avoid this issue is to pass --install-suggests to your apt
install command. For me it makes sense to be a suggested dependency
since just 2 fence agents (IBMz LPAR and VMWare soup agents) out of
around 50 (Bionic package) depend on python-requests, which makes me
believe that most users installing the fence-agents binary package do
not need this python module installed.

If you think we should promote python-requests in Bionic to a runtime
dependency let's open a new bug and start a discussion there. For now,
I'll leave it as is, a suggested runtime dependency.


** Bug watch added: Debian Bug tracker #899381
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899381

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

Title:
  [20.10 FEAT] Add LPAR fence agent to Pacemaker (fence-agents)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889070/+subscriptions

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

[Bug 1916485] Re: test -x fails inside shell scripts in containers

[Lucas Kanashiro]

To verify runc I am launching a docker container and calling "test -x"
like was done for systemd.

Groovy
==

ubuntu@docker-groovy:~$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="20.10 (Groovy Gorilla)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.10"
VERSION_ID="20.10"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=groovy
UBUNTU_CODENAME=groovy
ubuntu@docker-groovy:~$ dpkg -l | grep runc
ii  runc  1.0.0~rc93-0ubuntu1~20.10.1 
amd64Open Container Project - runtime
ubuntu@docker-groovy:~$ docker run -it ubuntu:focal /bin/bash
Unable to find image 'ubuntu:focal' locally
focal: Pulling from library/ubuntu
a70d879fa598: Pull complete 
c4394a92d1f8: Pull complete 
10e6159c56c0: Pull complete 
Digest: sha256:3c9c713e0979e9bd6061ed52ac1e9e1f246c9495aa063619d9d695fb8039aa1f
Status: Downloaded newer image for ubuntu:focal
root@7fa381c4877b:/# which ls  
/usr/bin/ls
root@7fa381c4877b:/# ls -l /usr/bin/ls
-rwxr-xr-x 1 root root 142144 Sep  5  2019 /usr/bin/ls
root@7fa381c4877b:/# test -x /usr/bin/ls || echo "fail"
root@7fa381c4877b:/#

Focal
=

ubuntu@docker-focal:~$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="20.04.2 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.2 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
ubuntu@docker-focal:~$ dpkg -l | grep runc
ii  runc   1.0.0~rc93-0ubuntu1~20.04.1   amd64  
  Open Container Project - runtime
ubuntu@docker-focal:~$ sudo docker run -it ubuntu:focal /bin/bash
Unable to find image 'ubuntu:focal' locally
focal: Pulling from library/ubuntu
a70d879fa598: Pull complete 
c4394a92d1f8: Pull complete 
10e6159c56c0: Pull complete 
Digest: sha256:3c9c713e0979e9bd6061ed52ac1e9e1f246c9495aa063619d9d695fb8039aa1f
Status: Downloaded newer image for ubuntu:focal
root@bf6b6e1534e5:/# which ls
/usr/bin/ls
root@bf6b6e1534e5:/# test -x /usr/bin/ls || echo "fail"
root@bf6b6e1534e5:/# 


Bionic
==

ubuntu@docker-bionic:~$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="18.04.5 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.5 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
ubuntu@docker-bionic:~$ dpkg -l | grep runc
ii  runc 1.0.0~rc93-0ubuntu1~18.04.1
 amd64Open Container Project - runtime
ubuntu@docker-bionic:~$ sudo docker run -it ubuntu:focal /bin/bash
Unable to find image 'ubuntu:focal' locally
focal: Pulling from library/ubuntu
a70d879fa598: Pull complete 
c4394a92d1f8: Pull complete 
10e6159c56c0: Pull complete 
Digest: sha256:3c9c713e0979e9bd6061ed52ac1e9e1f246c9495aa063619d9d695fb8039aa1f
Status: Downloaded newer image for ubuntu:focal
root@1979a3f523dc:/# which ls
/usr/bin/ls
root@1979a3f523dc:/# test -x /usr/bin/ls || echo "fail"
root@1979a3f523dc:/#

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

Title:
  test -x fails inside shell scripts in containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1916485/+subscriptions

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

[Bug 1919322] Re: Backport the container stack in Hirsute

[Lucas Kanashiro]

Verification - Bionic

With all the components accepted in bionic-proposed I was able to run
the tests needed with them which is basically autopkgtest. All of the
DEP-8 tests are successfully passing (I am installing the 3 packages
from bionic-proposed in the testbed):

[runc]

autopkgtest [15:33:16]:  summary
basic-smoke  PASS
command1 PASS

[containerd]

autopkgtest [15:43:52]:  summary
basic-smoke  PASS

[docker.io]

autopkgtest [16:03:30]:  summary
basic-smoke  PASS
docker-in-lxdPASS

Due to an upgrade issue that was found during this backport process I
also performed the following manual test in a Bionic VM:

1- Install runc, containerd and docker.io currently available in Bionic
2- Launch a container running in background
3- Upgrade the packages to the version in bionic-proposed
   + There is a debconf question in the docker.io package configuration where 
is asked if we want to restart the service. I marked 'No'.
4- Check if the container is still running in background.

The scenario above worked as expected.


** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  Backport the container stack in Hirsute

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

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

[Bug 1919322] Re: Backport the container stack in Hirsute

[Lucas Kanashiro]

Verification - Focal

With all the components accepted in focal-proposed I was able to run the
tests needed with them which is basically autopkgtest. All of the DEP-8
tests are successfully passing (I am installing the 3 packages from
focal-proposed in the testbed):

[runc]

autopkgtest [12:19:54]:  summary
basic-smoke  PASS
command1 PASS

[containerd]

autopkgtest [12:33:49]:  summary
basic-smoke  PASS

[docker.io]

autopkgtest [12:57:18]:  summary
basic-smoke  PASS
docker-in-lxdPASS


Due to an upgrade issue that was found during this backport process I also 
performed the following manual test in a Focal VM:

1- Install runc, containerd and docker.io currently available in Focal
2- Launch a container running in background
3- Upgrade the packages to the version in focal-proposed
   + There is a debconf question in the docker.io package configuration where 
is asked if we want to restart the service. I marked 'No'.
4- Check if the container is still running in background.

The scenario above worked as expected.

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  Backport the container stack in Hirsute

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

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

[Bug 1874954] Re: [SRU] settings manager window will not shrink horizontally after expanding

[Lucas Wilm]

** Tags removed: focal

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

Title:
  [SRU] settings manager window will not shrink horizontally after
  expanding

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

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

[Bug 1874954] Re: [SRU] settings manager window will not shrink horizontally after expanding

[Lucas Wilm]

I confirm that the fix worked well on my Xubuntu 20.04 installation and
I can resize the settings manager window as expected.

** Tags removed: apport-collected verification-done-groovy verification-
needed verification-needed-groovy

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

Title:
  [SRU] settings manager window will not shrink horizontally after
  expanding

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

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

[Bug 1822632] Re: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range

[Lucas Kanashiro]

I just noticed you asked about this on #ubuntu-release IRC channel and
you got the following answer:

cjwatson> Rebuilds would be SRUs like any other 
cjwatson> It's just that the proposed diff would just be the changelog

With that in mind, I believe you can proceed with the upload of the
proposed patches. Thanks!

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

Title:
  gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at
  0x0b69c5feaf58 for symbol `' out of range

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

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

[Bug 1822632] Re: gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at 0x00000b69c5feaf58 for symbol `' out of range

[Lucas Kanashiro]

Thanks for the patches Sergio, the changelog entry looks good. However,
I am not sure what is the SRU team policy about no-changes rebuild. Can
we try to confirm with the SRU team before uploading the proposed
patches? Maybe there is no manual upload involved.

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

Title:
  gosu: error while loading shared libraries: R_PPC64_ADDR16_HA reloc at
  0x0b69c5feaf58 for symbol `' out of range

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

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

[Bug 1919322] Re: Backport the container stack in Hirsute

[Lucas Kanashiro]

Verification - Groovy

Now that all the components were accepted in groovy-proposed I was able
to run the tests needed with them which is basically autopkgtest. All of
the DEP-8 tests are successfully passing (I am installing the 3 packages
from groovy-proposed in the testbed):

[runc]

autopkgtest [17:35:23]:  summary
basic-smoke  PASS
command1 PASS

[containerd]

autopkgtest [17:33:49]:  summary
basic-smoke  PASS

[docker.io]

autopkgtest [17:30:29]:  summary
basic-smoke  PASS
docker-in-lxdPASS

Regarding the runc regressions in Groovy:

- opengcs: There is another SRU going on to fix it (LP: #1912691)

- golang-github-docker-go-connections: It FTBFS in Groovy at the moment
because of an issue with one certificate used in the tests. This bug was
reported upstream here:

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

but since this is totally unrelated to runc I'd ask to ignore it. There
is no breakage, just the certificate expired which is leading to 2 tests
failure.

- libpod: There are 2 SRUs to fix this issue, libpod itself and golang-
github-containers-buildah (LP: #1921011)

** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy

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

Title:
  Backport the container stack in Hirsute

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

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

[Bug 1921011] Re: Fix build against new runc version

[Lucas Kanashiro]

Thanks for helping with the investigation and the review Sergio! The
packages were already uploaded.

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

Title:
  Fix build against new runc version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1921011/+subscriptions

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

[Bug 1921011] Re: Fix build against new runc version

[Lucas Kanashiro]

** Attachment added: "libpod_debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1921011/+attachment/5480328/+files/libpod_debdiff

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

Title:
  Fix build against new runc version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1921011/+subscriptions

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

[Bug 1921011] Re: Fix build against new runc version

[Lucas Kanashiro]

** Attachment added: "golang-github-containers-buildah_debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1921011/+attachment/5480327/+files/golang-github-containers-buildah_debdiff

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

Title:
  Fix build against new runc version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1921011/+subscriptions

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

[Bug 1919322] Re: Backport the container stack in Hirsute

[Lucas Kanashiro]

libpod and golang-github-containers-buildah also need a SRU targeting
Groovy to work fine with the new runc version. The status can be tracked
here:

https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-
buildah/+bug/1921011

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

Title:
  Backport the container stack in Hirsute

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

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

[Bug 1921011] [NEW] Fix build against new runc version

[Lucas Kanashiro]

Public bug reported:

[Impact]

runc/1.0.0~rc93-0ubuntu1 in Hirsute is going to be backported to Groovy 
(already in groovy-
proposed) but libpod and golang-github-containers-buildah FTBFS with it 
(autopkgtest fails as well). Those packages are blocking runc's migration.

Both packages, libpod and golang-github-containers-buildah, have patches
to fix the build against a newer runc version but they are disabled
(commented out) because we have an older runc in the Groovy release
pocket. The fix is basically to uncomment those patches in
debian/patches/series of both packages.

[Test Plan]

Make sure libpod and golang-github-containers-buildah build fine and
DEP-8 tests are also passing.

[Where problems could occur]

The patches which will be enabled are well tested by Debian (they are
not commented out there because they already have a newer runc), but if
a problem could occur it would be where the patches are applied which is
the implementation of how devices and permissions are managed in a linux
system. Check the patches for more info.

** Affects: golang-github-containers-buildah (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: libpod (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: golang-github-containers-buildah (Ubuntu Groovy)
 Importance: Undecided
 Status: In Progress

** Affects: libpod (Ubuntu Groovy)
 Importance: Undecided
 Status: In Progress

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

** Also affects: golang-github-containers-buildah (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: golang-github-containers-buildah (Ubuntu)
   Status: New => Fix Released

** Changed in: libpod (Ubuntu)
   Status: New => Fix Released

** Changed in: golang-github-containers-buildah (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: libpod (Ubuntu Groovy)
   Status: New => In Progress

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

Title:
  Fix build against new runc version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-buildah/+bug/1921011/+subscriptions

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

[Bug 1919322] Re: Backport the container stack in Hirsute

[Lucas Kanashiro]

** Description changed:

  [Impact]
  
  In order to follow our policy on keeping the container stack (docker.io,
  containerd, and runc) up-to-date in our supported releases, let's
  backport the stack in Hirsute to Groovy, Focal, and Bionic.
  
  docker.io version 20.10.2 was introduced in mid January in Hirsute and
  no issue was reported so far against it, which demonstrates its
  stability. Also, runc version 1.0-rc93 has an important fix regarding a
  glibc and seccomp issue (LP: #1916485). And finally, containerd version
  1.4.4 has a fix for CVE-2021-21334.
  
  [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.
+ 
+ [Other Info]
+ 
+ The SRU team brought up to my attention that a couple of changes were
+ made to the containerd service file which worth a mention here. The
+ following lines were added by upstream:
+ 
+ +RestartSec=5
+ +OOMScoreAdjust=-999
+ 
+ The docker.io service file also has some changes made by upstream:
+ 
+ [Unit]
+ -BindsTo=containerd.service
+ +Wants=containerd.service
+ 
+ [Service]
+ +OOMScoreAdjust=-500
+ 
+ The changes in the Unit section is fine because this is the current
+ behavior of our debian packages (we are patching it to apply this
+ change). The second change in the Service section was the default
+ already but then upstream moved from code to the service unit file. Look
+ at the changes dropped from docker.io current in Groovy
+ (components/engine/cmd/dockerd/config_unix.go):
+ 
+ -   flags.IntVar(, "oom-score-adjust", -500,
+ "Set the oom_score_adj for the daemon")
+ 
+ Due to that I believe the changes made are safe to be backported.

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

Title:
  Backport the container stack in Hirsute

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

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

[Bug 1920615] Re: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net

[Lucas Kanashiro]

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

None of the mentioned packages create a link to the certificates
directory (/etc/ssl/certs), so I believe you made some kind of manual
intervention. And IMO this "symlink sensitivity" is an upstream design
decision and not a bug, if you believe this is a bug please go ahead and
file an upstream bug.

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: clamav (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/1920615

Title:
  getcvd: Can't download daily.cvd from
  https://database.clamav.net/daily.cvd despite correct connection to
  https://database.clamav.net

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

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

[Bug 1919322] Re: Backport the container stack in Hirsute

[Lucas Kanashiro]

Filed a bug against upstream golang-github-docker-go-connections:

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

** 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/1919322

Title:
  Backport the container stack in Hirsute

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

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

[Bug 1912691] Re: [SRU] Support runc/1.0.0~rc93-0ubuntu1

[Lucas Kanashiro]

Thanks for the review Sergio! I am going to fix my email address in the
groovy package and upload all of them. Also fix/improve the bug
description.

** Description changed:

  [Impact]
  
  Due to our current policy we keep updating the container stack in all
  supported releases with new upstream versions. runc is part of this
  stack, and currently versions of opengcs in Bionic, Focal and Groovy do
  not support runc / 1.0.0 ~ rc93-0ubuntu1.
  
  opengcs tries to make use of system.GetClockTicks which would require a
  dependency on cgo. runc upstream decided to stop using it here:
  
  
https://github.com/opencontainers/runc/commit/402d645c5c642a4965439a156181cff3fc2f3817
  
  In Hirsute, a similar approach was implemented in opengcs to allow runc
  migration. Now, in order to unblock the runc SRUs we need to backport
  the Hirsute patch.
  
  [Test Plan]
  
- The upstream test suite seems to be enough to caught any potential issue
+ The upstream test suite seems to be enough to catch any potential issue
  in this case.
  
  [Where problems could occur]
  
- We are replacing a system call which would require cgo with a constant.
- According to this comment this is safe enough:
+ We are replacing a system call which would require cgo with a known
+ constant to avoid this dependency. This approach was adopted by runc
+ upstream maintainers, and according to this comment this is safe enough:
  
  https://github.com/containerd/cgroups/pull/12#issuecomment-311322400
  
  But the scenario where someone compile its own kernel and change the
  value of this constant will be inconsistent. However, this is not a big
  deal IMO, someone changing its own kernel needs to handle the
  consequences.
  
  [Original Message]
  
  opencgs test is failing and blocking runc/1.0.0~rc92-0ubuntu1 from
  migrating to hirsute:
  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  hirsute/hirsute/amd64/o/opengcs/20210118_162901_84e57@/log.gz
  
  This is the important bits:
  
  # vendor/github.com/docker/containerd/sys
  src/vendor/github.com/docker/containerd/sys/proc.go:17:34: undefined: 
system.GetClockTicks
  
  The new runc version does not provide GetClockTicks anymore:
  
  
https://github.com/opencontainers/runc/commit/402d645c5c642a4965439a156181cff3fc2f3817
  
  We should do the same in opengcs.

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

Title:
  [SRU] Support runc/1.0.0~rc93-0ubuntu1

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

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

[Bug 1915547] Re: Users are prompted by ucf on upgrade from Trusty to Xenial

[Lucas Albuquerque Medeiros de Moura]

Hi Robie, I just realized that I forgot to change the tag when I posted
my test process :(

This is the reason why this package is not on the -updates pocket yet,
right ?

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

Title:
  Users are prompted by ucf on upgrade from Trusty to Xenial

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

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

[Bug 1919322] Re: Backport the container stack in Hirsute

[Lucas Kanashiro]

The SRU team brought up to my attention that a couple of changes were
made to the containerd service file which worth a mention here. The
following lines were added by upstream:

+RestartSec=5
+OOMScoreAdjust=-999

They were considered fine by the SRU team.

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

Title:
  Backport the container stack in Hirsute

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

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

[Bug 1912691] Re: [SRU] Support runc/1.0.0~rc93-0ubuntu1

[Lucas Kanashiro]

** Attachment added: "debdiff-bionic"
   
https://bugs.launchpad.net/ubuntu/+source/opengcs/+bug/1912691/+attachment/5479208/+files/debdiff-bionic

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

Title:
  [SRU] Support runc/1.0.0~rc93-0ubuntu1

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

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

[Bug 1912691] Re: [SRU] Support runc/1.0.0~rc93-0ubuntu1

[Lucas Kanashiro]

** Attachment added: "debdiff-focal"
   
https://bugs.launchpad.net/ubuntu/+source/opengcs/+bug/1912691/+attachment/5479207/+files/debdiff-focal

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

Title:
  [SRU] Support runc/1.0.0~rc93-0ubuntu1

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

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

[Bug 1912691] Re: [SRU] Support runc/1.0.0~rc93-0ubuntu1

[Lucas Kanashiro]

** Attachment added: "debdiff-groovy"
   
https://bugs.launchpad.net/ubuntu/+source/opengcs/+bug/1912691/+attachment/5479206/+files/debdiff-groovy

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

Title:
  [SRU] Support runc/1.0.0~rc93-0ubuntu1

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

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

[Bug 1912691] Re: [SRU] Support runc/1.0.0~rc93-0ubuntu1

[Lucas Kanashiro]

I prepared packages for Bionic, Focal and Groovy here in this PPA:

https://launchpad.net/~lucaskanashiro/+archive/ubuntu/opengcs

autopkgtest is passing in all of them.

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

Title:
  [SRU] Support runc/1.0.0~rc93-0ubuntu1

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

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

[Bug 1915547] Re: Users are prompted by ucf on upgrade from Trusty to Xenial

[Lucas Albuquerque Medeiros de Moura]

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  Users are prompted by ucf on upgrade from Trusty to Xenial

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

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

[Bug 1912691] Re: [SRU] Support runc/1.0.0~rc93-0ubuntu1

[Lucas Kanashiro]

** Description changed:

+ [Impact]
+ 
+ Due to our current policy we keep updating the container stack in all
+ supported releases with new upstream versions. runc is part of this
+ stack, and currently versions of opengcs in Bionic, Focal and Groovy do
+ not support runc / 1.0.0 ~ rc93-0ubuntu1.
+ 
+ opengcs tries to make use of system.GetClockTicks which would require a
+ dependency on cgo. runc upstream decided to stop using it here:
+ 
+ 
https://github.com/opencontainers/runc/commit/402d645c5c642a4965439a156181cff3fc2f3817
+ 
+ In Hirsute, a similar approach was implemented in opengcs to allow runc
+ migration. Now, in order to unblock the runc SRUs we need to backport
+ the Hirsute patch.
+ 
+ [Test Plan]
+ 
+ The upstream test suite seems to be enough to caught any potential issue
+ in this case.
+ 
+ [Where problems could occur]
+ 
+ We are replacing a system call which would require cgo with a constant.
+ According to this comment this is safe enough:
+ 
+ https://github.com/containerd/cgroups/pull/12#issuecomment-311322400
+ 
+ But the scenario where someone compile its own kernel and change the
+ value of this constant will be inconsistent. However, this is not a big
+ deal IMO, someone changing its own kernel needs to handle the
+ consequences.
+ 
+ [Original Message]
+ 
  opencgs test is failing and blocking runc/1.0.0~rc92-0ubuntu1 from
  migrating to hirsute:
  
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  hirsute/hirsute/amd64/o/opengcs/20210118_162901_84e57@/log.gz
  
  This is the important bits:
  
  # vendor/github.com/docker/containerd/sys
  src/vendor/github.com/docker/containerd/sys/proc.go:17:34: undefined: 
system.GetClockTicks
  
  The new runc version does not provide GetClockTicks anymore:
  
  
https://github.com/opencontainers/runc/commit/402d645c5c642a4965439a156181cff3fc2f3817
  
  We should do the same in opengcs.

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

Title:
  [SRU] Support runc/1.0.0~rc93-0ubuntu1

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

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

[Bug 1912691] Re: autopkgtest failure blocking runc migration

[Lucas Kanashiro]

During the runc/1.0.0~rc93-0ubuntu1 backport to Bionic, Focal and Groovy
(LP #1919322), this very same issue showed up. Due to that I am marking
all those releases as affected as well. Fortunately, opengcs has the
same upstream version in all those releases, so the patch applied to
Hirsute should apply cleanly in all of them. I'll use this bug to drive
the SRU process.

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

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

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

** Summary changed:

- autopkgtest failure blocking runc migration
+ [SRU] Support runc/1.0.0~rc93-0ubuntu1

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

Title:
  [SRU] Support runc/1.0.0~rc93-0ubuntu1

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

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

[Bug 1919322] Re: Backport the container stack in Hirsute

[Lucas Kanashiro]

golang-github-docker-go-connections FTBFS at the moment in Focal and
Groovy because of an issue with one certificate used in the tests.
Likely this certificate needs to be regenerated.

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

Title:
  Backport the container stack in Hirsute

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

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

[Bug 1919322] Re: Backport the container stack in Hirsute

[Lucas Kanashiro]

With the new runc version opengcs needs to be patched in Bionic, Focal
and Groovy in the same way it was done in Hirsute, more info on LP
#1912691 .

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

Title:
  Backport the container stack in Hirsute

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

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

[Bug 1861262] Re: Add message/rfc822 to thunderbird.desktop

[Lucas Sandery]

@seb128 I'm not sure it's upstream.
 has been around
forever and was marked as duplicate of the still open
 where it appears
Mozilla doesn't want to do anything about it. The earliest ancestor of
that file I can find in the source is from 2010
.

** Bug watch added: Mozilla Bugzilla #371734
   https://bugzilla.mozilla.org/show_bug.cgi?id=371734

** Bug watch added: Mozilla Bugzilla #296568
   https://bugzilla.mozilla.org/show_bug.cgi?id=296568

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

Title:
  Add message/rfc822 to thunderbird.desktop

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

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

[Bug 1919322] Re: Backport the container stack in Hirsute

[Lucas Kanashiro]

** Changed in: runc (Ubuntu Groovy)
   Status: New => In Progress

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

** Changed in: runc (Ubuntu Focal)
   Status: New => In Progress

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

** Changed in: runc (Ubuntu Bionic)
   Status: New => In Progress

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

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

** Changed in: docker.io (Ubuntu)
   Status: New => Invalid

** Changed in: containerd (Ubuntu)
   Status: New => Invalid

** Changed in: docker.io (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: docker.io (Ubuntu Groovy)
 Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)

** Changed in: docker.io (Ubuntu Focal)
   Status: New => In Progress

** Changed in: docker.io (Ubuntu Focal)
 Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)

** Changed in: docker.io (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: docker.io (Ubuntu Bionic)
 Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)

** Changed in: containerd (Ubuntu Groovy)
   Status: New => In Progress

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

** Changed in: containerd (Ubuntu Focal)
   Status: New => In Progress

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

** Changed in: containerd (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: containerd (Ubuntu Bionic)
 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/1919322

Title:
  Backport the container stack in Hirsute

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

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

[Bug 1919322] [NEW] Backport the container stack in Hirsute

[Lucas Kanashiro]

Public bug reported:

[Impact]

In order to follow our policy on keeping the container stack (docker.io,
containerd, and runc) up-to-date in our supported releases, let's
backport the stack in Hirsute to Groovy, Focal, and Bionic.

docker.io version 20.10.2 was introduced in mid January in Hirsute and
no issue was reported so far against it, which demonstrates its
stability. Also, runc version 1.0-rc93 has an important fix regarding a
glibc and seccomp issue (LP: #1916485). And finally, containerd version
1.4.4 has a fix for CVE-2021-21334.

[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.

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

** Affects: docker.io (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: containerd (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: docker.io (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: runc (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: containerd (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: docker.io (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: runc (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: containerd (Ubuntu Groovy)
 Importance: Undecided
 Status: New

** Affects: docker.io (Ubuntu Groovy)
 Importance: Undecided
 Status: New

** Affects: runc (Ubuntu Groovy)
 Importance: Undecided
 Status: New

** Also affects: containerd (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: docker.io (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

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

** Also affects: docker.io (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

** Also affects: docker.io (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: containerd (Ubuntu Bionic)
   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/1919322

Title:
  Backport the container stack in Hirsute

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

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

[Bug 1919249] Re: package libsmbclient:amd64 2:4.11.6+dfsg-0ubuntu1.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Lucas Kanashiro]

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

The logs are not very helpful in this case, the only thing I saw was:

dpkg: error processing package libsmbclient:amd64 (--configure):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting configuration

Did you try to remove the package and install it again? I tried to
upgrade it from 2:4.11.6+dfsg-0ubuntu1.4 to 2:4.11.6+dfsg-0ubuntu1.6 in
a Focal as you did, but I was not able to reproduce the failure, it
worked just fine. There are some CVE fixes which does not seem to
introduce a real regression.

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: samba (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/1919249

Title:
  package libsmbclient:amd64 2:4.11.6+dfsg-0ubuntu1.6 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

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

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

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

[Lucas Kanashiro]

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

After reading the logs I believe you tried to abort the package
installation in the middle of the process, I can't spot anything besides
that. You also need to be careful when upgrading to MySQL 8, please take
some time to read the upstream documentation about upgrades:

https://dev.mysql.com/doc/refman/8.0/en/upgrading.html

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/1919119

Title:
  package mysql-server-8.0 8.0.23-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/1919119/+subscriptions

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

[Bug 1919182] [NEW] [FFe] Import version 1.0-rc93

[Lucas Kanashiro]

Public bug reported:

This new upstream release contains an important fix to address LP
#1916485. runc now has special handling for seccomp profiles to avoid
making new syscalls unusable for glibc. Backporting this single fix
would be painful because upstream also updated some of the vendorized
deps in the same git commit:

https://github.com/opencontainers/runc/commit/7a8d7162f9d72f20d83eaa36aeb5426deecd58f2

To stay on the safe side and also bring in some improvements made by
upstream, we decided the best way to fix this issue is importing this
new release. Below you can fine the upstream release notes:

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

And here the diff between version 1.0-rc92 which we already have in
Hirsute and this new version:

https://github.com/opencontainers/runc/compare/v1.0.0-rc92...v1.0.0-rc93

I already have this package (almost) ready in this PPA:

https://launchpad.net/~lucaskanashiro/+archive/ubuntu/docker-20.10/+packages

And I can confirm it is working well along with containerd and docker.io
in Hirsute. All the DEP-8 tests are passing and also my manual smoke
tests, for instance basic features like pulling images from remote
registries and running them locally, binding containers to some host
port, and building your own image locally.

** Affects: runc (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/1919182

Title:
  [FFe] Import version 1.0-rc93

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

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

[Bug 1917718] Re: Can't auto login after upgrading to 2.3.1-3ubuntu4 on 20.10

[Lucas Kanashiro]

Thanks for taking the time to file this bug.

While checking the logs I noticed this:

Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: Loaded settings 
from: /usr/lib/realmd/realmd-defaults.conf /usr/lib/realmd/realmd-distro.conf
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: holding daemon: 
startup
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: starting service
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: connected to bus
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: GLib-GIO: 
_g_io_module_get_default: Found default implementation local (GLocalVfs) for 
‘gio-vfs’
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: released daemon: 
startup
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: claimed name on 
bus: org.freedesktop.realmd
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: client using 
service: :1.115
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: holding daemon: 
:1.115
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]:  * Resolving: 
_ldap._tcp.taipei
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]:  * Resolving: 
_ldap._tcp.taipei
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: Resolving taipei 
failed: No DNS record of the requested type for “_kerberos._udp.taipei”
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: No DNS record of 
the requested type for “_ldap._tcp.taipei”
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]:  * Resolving: 
taipei
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]:  * Resolving: 
taipei
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: Error resolving 
“taipei”: Temporary failure in name resolution
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]:  * No results: 
taipei
Mar  4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]:  * No results: 
taipei

Which makes me believe this is a DNS issue. Could share your sssd conf
to help us understand your setup? And possibly reproduce the bug
locally. FWIW I am subscribing Sergio who has been working on sssd
recently.

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

Title:
  Can't auto login after upgrading to 2.3.1-3ubuntu4 on 20.10

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

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

[Bug 1851232] Re: Laptop does not suspend when using open-iscsi

[Lucas Kanashiro]

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

I just tried to connect to an iscsi target from my Ubuntu Focal
workstation and I was not able to suspend and then wake up my system, as
both of you described. Your analyses seems right, the iscsi target might
be delaying the whole process.

I am marking this bug as Triaged and I am going to subscribe ubuntu-
server for further investigation.

** Changed in: open-iscsi (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Laptop does not suspend when using open-iscsi

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

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

[Bug 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly

[Lucas Kanashiro]

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

>From what you described it seems that Network Manager is the one
responsible for adding the unexpected routing rule, so this might not
affect OpenVPN itself. I quickly tried to reproduce your setup but did
not notice the bug there. Could you please share your config files to
see if I missed something?

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

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

** Changed in: openvpn (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/1917887

Title:
  Network Manager OpenVPN nested connections fail to setup routes
  correctly

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

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

[Bug 1915547] Re: Users are prompted by ucf on upgrade from Trusty to Xenial

[Lucas Albuquerque Medeiros de Moura]

Thanks for the review Robie,

I have tested the package on the proposed pocket by using this script:


#!/bin/sh
set -x

series=trusty
name=$series-upgrade

multipass delete $name
multipass purge
multipass launch $series --name $name


multipass exec $name -- sudo sh -c "cat 

[Bug 1917971] Re: package samba-common (not installed) failed to install/upgrade: installed samba-common package post-installation script subprocess returned error exit status 10

[Lucas Kanashiro]

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

The attached logs do not help too much, the only info I could extract
was dpkg returning the exit code 10. It seems that something is in an
inconsistent state in your system but I was not able to spot anything
with the provided information. Could you please try to purge the package
and re-install it?

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: samba (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/1917971

Title:
  package samba-common (not installed) failed to install/upgrade:
  installed samba-common package post-installation script subprocess
  returned error exit status 10

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

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

[Bug 1573192] Re: apparmor prevents using SCSI hostdevs

[Lucas Kanashiro]

Thanks for taking the time to file this bug.

I am not able to reproduce this bug since I do not have an scsi device
to test it. I am subscribing Christian, he might have a better idea on
how to address 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/1573192

Title:
  apparmor prevents using SCSI hostdevs

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

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

[Bug 1915547] Re: Users are prompted by ucf on upgrade from Trusty to Xenial

[Lucas Albuquerque Medeiros de Moura]

Thank you for this review Robie, we have now updated the package to only
ship two md5sum. The latest version of 50unattended-upgrades of Trusty
and Xenial.

I have already updated the MR with those changes and I Bryce is
reviewing that changes before uploading the new package.

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

Title:
  Users are prompted by ucf on upgrade from Trusty to Xenial

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

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

[Bug 1917766] [NEW] [RM] Do not ship ruby-omniauth-remote-user in Hirsute

[Lucas Kanashiro]

Public bug reported:

ruby-omniauth-remote-user is blocking ruby-defaults/1:2.7+2 migration
because it FTBFS. Related Debian bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959557

I am one of the upstream maintainers and I can confirm this project is
quite dead, unmaintained for many years. Moreover, there is no reverse
dependency in Hirsute:

$ reverse-depends -r hirsute ruby-omniauth-remote-user
No reverse dependencies found
$ reverse-depends -b -r hirsute ruby-omniauth-remote-user
No reverse dependencies found

Please, remove the source and binary packages from Hirsute to unblock
ruby-defaults.

** Affects: ruby-omniauth-remote-user (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/1917766

Title:
  [RM] Do not ship ruby-omniauth-remote-user in Hirsute

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-omniauth-remote-user/+bug/1917766/+subscriptions

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

[Bug 1917036] Re: Some of the modules of cloud-init are not working properly (in this case: runcmd)

[Lucas Albuquerque Medeiros de Moura]

Also, please provide the userdata that you are using to configure cloud-
init too. I forgot to mention that on my last comment

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

Title:
  Some of the modules of cloud-init are not working properly (in this
  case: runcmd)

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

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

[Bug 1917036] Re: Some of the modules of cloud-init are not working properly (in this case: runcmd)

[Lucas Albuquerque Medeiros de Moura]

Hi Kalpesh, thank you for reporting this issue. Can you please provide
the cloud-init logs for the instance that is failing ? Those logs would
be cloud-init.log and cloud-init-output.log

After providing that, you can change the status of this bug to new
again.

** Changed in: cloud-init (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/1917036

Title:
  Some of the modules of cloud-init are not working properly (in this
  case: runcmd)

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

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

[Bug 1917336] Re: Mailman does not honour MAILMAN_USER on startup

[Lucas Kanashiro]

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

Checking the mailman package in Ubuntu Focal I see the logrotate file
installed by this package contains some postrotate scripts that might be
setting back the ownership to list:list. Take a look at
/etc/logrotate.d/mailman and try to make the appropriate changes.

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: mailman (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/1917336

Title:
  Mailman does not honour MAILMAN_USER on startup

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

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

[Bug 1917280] Re: package libsss-nss-idmap0 2.2.3-3ubuntu0.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

[Lucas Kanashiro]

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

I set up a Focal LXD container and installed libsss-nss-idmap0 without
problems in it. I see you tried to install version 2.2.3-3ubuntu0.2, and
now in focal-updates we have 2.2.3-3ubuntu0.4, please try to install
this newer version and check if your problem is fixed.

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: sssd (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/1917280

Title:
  package libsss-nss-idmap0 2.2.3-3ubuntu0.2 failed to install/upgrade:
  dpkg-deb --control subprocess returned error exit status 2

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

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

[Bug 1906307] Re: flaky autopkgtest on arm64

[Lucas Kanashiro]

I forwarded this bug to the upstream maintainers:

https://github.com/puma/puma/issues/2562

** Bug watch added: github.com/puma/puma/issues #2562
   https://github.com/puma/puma/issues/2562

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

Title:
  flaky autopkgtest on arm64

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

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

[Bug 1916954] Re: autopkgtest regression on s390x and arm64

[Lucas Kanashiro]

I tested the attached debdiff in Canonistack VMs (s390x and arm64) and I
got no autopkgtest failure.

** Attachment added: "debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/puma/+bug/1916954/+attachment/5467252/+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/1916954

Title:
  autopkgtest regression on s390x and arm64

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

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

[Bug 1916954] [NEW] autopkgtest regression on s390x and arm64

[Lucas Kanashiro]

Public bug reported:

The test is hanging on s390x and arm64 architectures only, blocking its
migration and also rails. Below my findings so far.

On s390x the TestPlugin#test_plugin is hanging, not sure why that is
happening exactly but this test is new (not present in the puma version
in hirsute's release pocket) so I am not considering a regression. I am
in contact with the Debian maintainer but as a workaround for now we
could skip this test. This regression was also detected in Debian but it
did not block its migration there (different policies).

On arm64 I was not able to pinpoint a problematic test, different tests
randomly hang. Since the failing tests try to run some services I tried
to add a "needs-root" restriction to the DEP-8 test definition and it
apparently worked out. I ran autopkgtest 10 times in sequence after
applying this change and none failed (it was consistently failing before
that).

** Affects: puma (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/1916954

Title:
  autopkgtest regression on s390x and arm64

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

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

[Bug 1915547] Re: sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to 1.1ubuntu1.18.04.7~16.04.7 ) Xenial

[Lucas Albuquerque Medeiros de Moura]

I will further increase this SRU bug with information that is lacking on
from the original bug proposal:

[Impact]
During an upgrade from trusty to xenial, users will be prompted to make a 
decision regarding the diff on unattended-upgrades. This is not a good user 
experience, specially because the user can make an uninformed decision of 
keeping the old config file, which will make unattended-upgrades to not work as 
we expect.

[Test case]

To reproduce the isse, you can:

1. Launch a trusty vm
2. Perform a do-release-upgrade and observe that you will be prompted with the 
50unattende-upgrades change

To verify that the error is fixed:

1. Launch a trusty vm 
2. Import this ppa into the system:
   https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
3. Configure do-release-upgrade to allow using third parties during upgrade
4. Run a do-release-upgrade
5. Verify the prompt is no longer there and that we end up with the expected 
50unattended-upgrades
   config file

[Where problems could occur]

The changes is this package should only be surface during an upgrade
operation. Because we are now delivering a new file to the system and
configuring postinst to use it. Because of that, we believe this is the
only scenario that could be affect in case of a regression is discovered
in the package.


---

Finally, if there is any additional information that I need to add to
this SRU, just let me know and I will provide it

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

Title:
   sru unattended-upgrades (  1.1ubuntu1.18.04.7~16.04.6  update to
  1.1ubuntu1.18.04.7~16.04.7 ) Xenial

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

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

[Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

[Lucas Santana Carlota]

So sad, Asus doesn't care about linux users, that's the reality ... Our
only hope is a community developed driver for this feature.

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

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

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

[Bug 1916659] [NEW] The default config in Bionic does not work on Azure

[Lucas Kanashiro]

Public bug reported:

By default the "transport" field is not set in
/etc/corosync/corosync.conf which means "udp" is used. However, it does
not work in Ubuntu Bionic on Azure for some reason, I thought it could
be some issue regarding multicast but I was told it is supported. In
order to make it work I need to set "transport" to "udpu".

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

** Affects: corosync (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Also affects: corosync (Ubuntu Bionic)
   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/1916659

Title:
  The default config in Bionic does not work on Azure

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

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