| 2011-05-15 04:30:14 |
Eric Metzler |
bug |
|
|
added bug |
| 2011-05-16 17:59:30 |
Chuck Short |
backuppc (Ubuntu): importance |
Undecided |
Low |
|
| 2011-05-16 17:59:30 |
Chuck Short |
backuppc (Ubuntu): status |
New |
Incomplete |
|
| 2011-06-15 13:21:24 |
amichair |
bug |
|
|
added subscriber amichair |
| 2011-08-05 13:52:22 |
Jonathan Ernst |
backuppc (Ubuntu): status |
Incomplete |
New |
|
| 2011-08-07 15:13:47 |
Launchpad Janitor |
backuppc (Ubuntu): status |
New |
Confirmed |
|
| 2011-08-07 15:14:45 |
KyleAnderson |
bug |
|
|
added subscriber KyleAnderson |
| 2011-08-09 05:13:46 |
Tessa |
bug |
|
|
added subscriber Graeme |
| 2011-12-08 00:21:02 |
Thilo-Alexander Ginkel |
bug |
|
|
added subscriber Thilo-Alexander Ginkel |
| 2012-05-03 23:04:51 |
Danny Sauer |
bug |
|
|
added subscriber Danny Sauer |
| 2012-11-06 18:22:34 |
Simon Déziel |
bug |
|
|
added subscriber Simon Déziel |
| 2013-11-26 22:39:14 |
Marcelo Fernandez |
bug |
|
|
added subscriber Marcelo Fernandez |
| 2018-11-22 16:46:02 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Server |
| 2018-11-22 16:46:08 |
Robie Basak |
backuppc (Ubuntu): status |
Confirmed |
Triaged |
|
| 2018-11-22 16:46:15 |
Robie Basak |
tags |
|
bitesize |
|
| 2021-11-19 21:58:41 |
Sergio Durigan Junior |
nominated for series |
|
Ubuntu Bionic |
|
| 2021-11-19 21:58:41 |
Sergio Durigan Junior |
bug task added |
|
backuppc (Ubuntu Bionic) |
|
| 2021-11-19 21:58:41 |
Sergio Durigan Junior |
nominated for series |
|
Ubuntu Focal |
|
| 2021-11-19 21:58:41 |
Sergio Durigan Junior |
bug task added |
|
backuppc (Ubuntu Focal) |
|
| 2021-11-19 21:58:49 |
Sergio Durigan Junior |
backuppc (Ubuntu Bionic): status |
New |
Triaged |
|
| 2021-11-19 21:58:53 |
Sergio Durigan Junior |
backuppc (Ubuntu Focal): status |
New |
Triaged |
|
| 2021-11-19 21:58:55 |
Sergio Durigan Junior |
backuppc (Ubuntu Bionic): importance |
Undecided |
Low |
|
| 2021-11-19 21:58:57 |
Sergio Durigan Junior |
backuppc (Ubuntu Focal): importance |
Undecided |
Low |
|
| 2021-11-19 21:58:59 |
Sergio Durigan Junior |
backuppc (Ubuntu): status |
Triaged |
Fix Released |
|
| 2022-07-27 10:09:31 |
Michał Małoszewski |
backuppc (Ubuntu Bionic): assignee |
|
Michał Małoszewski (michal-maloszewski99) |
|
| 2022-07-27 10:09:33 |
Michał Małoszewski |
backuppc (Ubuntu Focal): assignee |
|
Michał Małoszewski (michal-maloszewski99) |
|
| 2022-08-05 13:01:55 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~michal-maloszewski99/ubuntu/+source/backuppc/+git/backuppc/+merge/427945 |
|
| 2022-08-05 13:13:27 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~michal-maloszewski99/ubuntu/+source/backuppc/+git/backuppc/+merge/427955 |
|
| 2022-08-09 10:21:15 |
Michał Małoszewski |
description |
Binary package hint: backuppc
After upgrading from 3.1.0 to 3.2.0 as part of the Ubuntu server upgrade from maverick to natty, none of my hosts were backing up, and all (including localhost) were reporting "no ping response". I followed all instructions prior to upgrading, and backuppc was at 3.1.0-9ubuntu2 and working. I discovered the addition of the Ping6Path config variable, which is set to "undef" by default. My config.pl file had the line
$Conf{Ping6Path} = undef;
after both an upgrade to 3.2.0-3ubuntu4 and a clean install after purging the package. This, combined with the added code to Lib.pm caused the $pingPath in $pingCmd to be empty, thus causing the "no ping response" errors.
Changing the Ping6Path line in config.pl to
$Conf{Ping6Path} = '/bin/ping6';
solved the problem. This value should be populated by default for a fresh install if /bin/ping6 is found, just as /bin/ping is populated in $Conf{PingPath}.
# lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
# apt-cache policy backuppc
backuppc:
Installed: 3.2.0-3ubuntu4
Candidate: 3.2.0-3ubuntu4
Version table:
*** 3.2.0-3ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
100 /var/lib/dpkg/status |
[Impact]
The backuppc package struggled with ping response on all hosts after upgrade, because the package on both Bionic and Focal doesn’t contain a valid setting for ping6.
This situation before the patch was applied was really unfortunate for users whose backup hosts are using IPv6.
Backport upstream fix to Bionic/Focal
Link to the commit:
https://salsa.debian.org/debian/backuppc/-/commit/b034914233c05982b524414f548ca3454292f457
[Test Plan]
** Reproduction **
Make a container(s) for testing:
First option: (creating focal vm)
$ lxc launch images:ubuntu/focal focal-test
$ lxc shell focal-test
Second option: (creating bionic vm)
$ lxc launch images:ubuntu/bionic bionic-test
$ lxc shell bionic-test
Simply install the backuppc package using ‘apt install’ and check the variables in the config.pl file.
** Verification **
Follow the reproduction steps above to ensure that the variable is properly set.
[Where problems could occur]
First of all, any code change might change the behavior of the package in a specific situation and cause other errors. The regression possibilities here are really low.
It is unlikely but possible that users could hardcore valid setting for ping6. In that case if the same user wants to install backuppc, there is a high risk that a warning message will appear and there is a necessity to unify the setting by removing it and installing again.
Next thing which might cause regression are new dependencies of the package which might not align with changes which were made and it might be a problem.
---------------original bug report----------------------
Binary package hint: backuppc
After upgrading from 3.1.0 to 3.2.0 as part of the Ubuntu server upgrade from maverick to natty, none of my hosts were backing up, and all (including localhost) were reporting "no ping response". I followed all instructions prior to upgrading, and backuppc was at 3.1.0-9ubuntu2 and working. I discovered the addition of the Ping6Path config variable, which is set to "undef" by default. My config.pl file had the line
$Conf{Ping6Path} = undef;
after both an upgrade to 3.2.0-3ubuntu4 and a clean install after purging the package. This, combined with the added code to Lib.pm caused the $pingPath in $pingCmd to be empty, thus causing the "no ping response" errors.
Changing the Ping6Path line in config.pl to
$Conf{Ping6Path} = '/bin/ping6';
solved the problem. This value should be populated by default for a fresh install if /bin/ping6 is found, just as /bin/ping is populated in $Conf{PingPath}.
# lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
# apt-cache policy backuppc
backuppc:
Installed: 3.2.0-3ubuntu4
Candidate: 3.2.0-3ubuntu4
Version table:
*** 3.2.0-3ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
100 /var/lib/dpkg/status |
|
| 2022-08-11 14:53:24 |
Sergio Durigan Junior |
description |
[Impact]
The backuppc package struggled with ping response on all hosts after upgrade, because the package on both Bionic and Focal doesn’t contain a valid setting for ping6.
This situation before the patch was applied was really unfortunate for users whose backup hosts are using IPv6.
Backport upstream fix to Bionic/Focal
Link to the commit:
https://salsa.debian.org/debian/backuppc/-/commit/b034914233c05982b524414f548ca3454292f457
[Test Plan]
** Reproduction **
Make a container(s) for testing:
First option: (creating focal vm)
$ lxc launch images:ubuntu/focal focal-test
$ lxc shell focal-test
Second option: (creating bionic vm)
$ lxc launch images:ubuntu/bionic bionic-test
$ lxc shell bionic-test
Simply install the backuppc package using ‘apt install’ and check the variables in the config.pl file.
** Verification **
Follow the reproduction steps above to ensure that the variable is properly set.
[Where problems could occur]
First of all, any code change might change the behavior of the package in a specific situation and cause other errors. The regression possibilities here are really low.
It is unlikely but possible that users could hardcore valid setting for ping6. In that case if the same user wants to install backuppc, there is a high risk that a warning message will appear and there is a necessity to unify the setting by removing it and installing again.
Next thing which might cause regression are new dependencies of the package which might not align with changes which were made and it might be a problem.
---------------original bug report----------------------
Binary package hint: backuppc
After upgrading from 3.1.0 to 3.2.0 as part of the Ubuntu server upgrade from maverick to natty, none of my hosts were backing up, and all (including localhost) were reporting "no ping response". I followed all instructions prior to upgrading, and backuppc was at 3.1.0-9ubuntu2 and working. I discovered the addition of the Ping6Path config variable, which is set to "undef" by default. My config.pl file had the line
$Conf{Ping6Path} = undef;
after both an upgrade to 3.2.0-3ubuntu4 and a clean install after purging the package. This, combined with the added code to Lib.pm caused the $pingPath in $pingCmd to be empty, thus causing the "no ping response" errors.
Changing the Ping6Path line in config.pl to
$Conf{Ping6Path} = '/bin/ping6';
solved the problem. This value should be populated by default for a fresh install if /bin/ping6 is found, just as /bin/ping is populated in $Conf{PingPath}.
# lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
# apt-cache policy backuppc
backuppc:
Installed: 3.2.0-3ubuntu4
Candidate: 3.2.0-3ubuntu4
Version table:
*** 3.2.0-3ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
100 /var/lib/dpkg/status |
[Impact]
The backuppc package struggled with ping response on all hosts after upgrade, because the package on both Bionic and Focal doesn’t contain a valid setting for ping6.
This situation before the patch was applied was really unfortunate for users whose backup hosts are using IPv6.
Backport upstream fix to Bionic/Focal
Link to the commit:
https://salsa.debian.org/debian/backuppc/-/commit/b034914233c05982b524414f548ca3454292f457
[Test Plan]
** Reproduction **
Make a container(s) for testing:
First option: (creating focal vm)
$ lxc launch images:ubuntu/focal focal-test
$ lxc shell focal-test
Second option: (creating bionic vm)
$ lxc launch images:ubuntu/bionic bionic-test
$ lxc shell bionic-test
Simply install the backuppc package using ‘apt install’ and check the variables in the config.pl file.
** Verification **
Follow the reproduction steps above to ensure that the variable is properly set.
[Where problems could occur]
First of all, any code change might change the behavior of the package in a specific situation and cause other errors. The regression possibilities here are really low.
It is unlikely but possible that users could hardcore valid setting for ping6. In that case if the same user wants to install backuppc, there is a high risk that a warning message will appear and there is a necessity to unify the setting by removing it and installing again.
Another possible (albeit unlikely) source of regressions is the fact that we will be rebuilding backuppc against newer versions of its build dependencies, especially on Bionic.
---------------original bug report----------------------
Binary package hint: backuppc
After upgrading from 3.1.0 to 3.2.0 as part of the Ubuntu server upgrade from maverick to natty, none of my hosts were backing up, and all (including localhost) were reporting "no ping response". I followed all instructions prior to upgrading, and backuppc was at 3.1.0-9ubuntu2 and working. I discovered the addition of the Ping6Path config variable, which is set to "undef" by default. My config.pl file had the line
$Conf{Ping6Path} = undef;
after both an upgrade to 3.2.0-3ubuntu4 and a clean install after purging the package. This, combined with the added code to Lib.pm caused the $pingPath in $pingCmd to be empty, thus causing the "no ping response" errors.
Changing the Ping6Path line in config.pl to
$Conf{Ping6Path} = '/bin/ping6';
solved the problem. This value should be populated by default for a fresh install if /bin/ping6 is found, just as /bin/ping is populated in $Conf{PingPath}.
# lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
# apt-cache policy backuppc
backuppc:
Installed: 3.2.0-3ubuntu4
Candidate: 3.2.0-3ubuntu4
Version table:
*** 3.2.0-3ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
100 /var/lib/dpkg/status |
|
| 2022-08-11 15:00:32 |
Michał Małoszewski |
description |
[Impact]
The backuppc package struggled with ping response on all hosts after upgrade, because the package on both Bionic and Focal doesn’t contain a valid setting for ping6.
This situation before the patch was applied was really unfortunate for users whose backup hosts are using IPv6.
Backport upstream fix to Bionic/Focal
Link to the commit:
https://salsa.debian.org/debian/backuppc/-/commit/b034914233c05982b524414f548ca3454292f457
[Test Plan]
** Reproduction **
Make a container(s) for testing:
First option: (creating focal vm)
$ lxc launch images:ubuntu/focal focal-test
$ lxc shell focal-test
Second option: (creating bionic vm)
$ lxc launch images:ubuntu/bionic bionic-test
$ lxc shell bionic-test
Simply install the backuppc package using ‘apt install’ and check the variables in the config.pl file.
** Verification **
Follow the reproduction steps above to ensure that the variable is properly set.
[Where problems could occur]
First of all, any code change might change the behavior of the package in a specific situation and cause other errors. The regression possibilities here are really low.
It is unlikely but possible that users could hardcore valid setting for ping6. In that case if the same user wants to install backuppc, there is a high risk that a warning message will appear and there is a necessity to unify the setting by removing it and installing again.
Another possible (albeit unlikely) source of regressions is the fact that we will be rebuilding backuppc against newer versions of its build dependencies, especially on Bionic.
---------------original bug report----------------------
Binary package hint: backuppc
After upgrading from 3.1.0 to 3.2.0 as part of the Ubuntu server upgrade from maverick to natty, none of my hosts were backing up, and all (including localhost) were reporting "no ping response". I followed all instructions prior to upgrading, and backuppc was at 3.1.0-9ubuntu2 and working. I discovered the addition of the Ping6Path config variable, which is set to "undef" by default. My config.pl file had the line
$Conf{Ping6Path} = undef;
after both an upgrade to 3.2.0-3ubuntu4 and a clean install after purging the package. This, combined with the added code to Lib.pm caused the $pingPath in $pingCmd to be empty, thus causing the "no ping response" errors.
Changing the Ping6Path line in config.pl to
$Conf{Ping6Path} = '/bin/ping6';
solved the problem. This value should be populated by default for a fresh install if /bin/ping6 is found, just as /bin/ping is populated in $Conf{PingPath}.
# lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
# apt-cache policy backuppc
backuppc:
Installed: 3.2.0-3ubuntu4
Candidate: 3.2.0-3ubuntu4
Version table:
*** 3.2.0-3ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
100 /var/lib/dpkg/status |
[Impact]
The backuppc package struggled with ping response on all hosts after upgrade, because the package on both Bionic and Focal doesn’t contain a valid setting for ping6.
This situation before the patch was applied was really unfortunate for users whose backup hosts are using IPv6.
[Test Plan]
** Reproduction **
Make a container(s) for testing:
First option: (creating focal vm)
$ lxc launch images:ubuntu/focal focal-test
$ lxc shell focal-test
Second option: (creating bionic vm)
$ lxc launch images:ubuntu/bionic bionic-test
$ lxc shell bionic-test
Simply install the backuppc package using ‘apt install’ and check the variables in the config.pl file.
** Verification **
Follow the reproduction steps above to ensure that the variable is properly set.
[Where problems could occur]
First of all, any code change might change the behavior of the package in a specific situation and cause other errors. The regression possibilities here are really low.
It is unlikely but possible that users could hardcode valid settings for ping6. In that case if the same user wants to install backuppc, there is a high risk that a warning message will appear and there is a necessity to unify the setting by removing it and installing again.
Next thing which might cause regression are new dependencies of the package which might not align with changes which were made and it might be a problem.
---------------original bug report----------------------
Binary package hint: backuppc
After upgrading from 3.1.0 to 3.2.0 as part of the Ubuntu server upgrade from maverick to natty, none of my hosts were backing up, and all (including localhost) were reporting "no ping response". I followed all instructions prior to upgrading, and backuppc was at 3.1.0-9ubuntu2 and working. I discovered the addition of the Ping6Path config variable, which is set to "undef" by default. My config.pl file had the line
$Conf{Ping6Path} = undef;
after both an upgrade to 3.2.0-3ubuntu4 and a clean install after purging the package. This, combined with the added code to Lib.pm caused the $pingPath in $pingCmd to be empty, thus causing the "no ping response" errors.
Changing the Ping6Path line in config.pl to
$Conf{Ping6Path} = '/bin/ping6';
solved the problem. This value should be populated by default for a fresh install if /bin/ping6 is found, just as /bin/ping is populated in $Conf{PingPath}.
# lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
# apt-cache policy backuppc
backuppc:
Installed: 3.2.0-3ubuntu4
Candidate: 3.2.0-3ubuntu4
Version table:
*** 3.2.0-3ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
100 /var/lib/dpkg/status |
|
| 2022-08-11 15:51:43 |
Michał Małoszewski |
description |
[Impact]
The backuppc package struggled with ping response on all hosts after upgrade, because the package on both Bionic and Focal doesn’t contain a valid setting for ping6.
This situation before the patch was applied was really unfortunate for users whose backup hosts are using IPv6.
[Test Plan]
** Reproduction **
Make a container(s) for testing:
First option: (creating focal vm)
$ lxc launch images:ubuntu/focal focal-test
$ lxc shell focal-test
Second option: (creating bionic vm)
$ lxc launch images:ubuntu/bionic bionic-test
$ lxc shell bionic-test
Simply install the backuppc package using ‘apt install’ and check the variables in the config.pl file.
** Verification **
Follow the reproduction steps above to ensure that the variable is properly set.
[Where problems could occur]
First of all, any code change might change the behavior of the package in a specific situation and cause other errors. The regression possibilities here are really low.
It is unlikely but possible that users could hardcode valid settings for ping6. In that case if the same user wants to install backuppc, there is a high risk that a warning message will appear and there is a necessity to unify the setting by removing it and installing again.
Next thing which might cause regression are new dependencies of the package which might not align with changes which were made and it might be a problem.
---------------original bug report----------------------
Binary package hint: backuppc
After upgrading from 3.1.0 to 3.2.0 as part of the Ubuntu server upgrade from maverick to natty, none of my hosts were backing up, and all (including localhost) were reporting "no ping response". I followed all instructions prior to upgrading, and backuppc was at 3.1.0-9ubuntu2 and working. I discovered the addition of the Ping6Path config variable, which is set to "undef" by default. My config.pl file had the line
$Conf{Ping6Path} = undef;
after both an upgrade to 3.2.0-3ubuntu4 and a clean install after purging the package. This, combined with the added code to Lib.pm caused the $pingPath in $pingCmd to be empty, thus causing the "no ping response" errors.
Changing the Ping6Path line in config.pl to
$Conf{Ping6Path} = '/bin/ping6';
solved the problem. This value should be populated by default for a fresh install if /bin/ping6 is found, just as /bin/ping is populated in $Conf{PingPath}.
# lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
# apt-cache policy backuppc
backuppc:
Installed: 3.2.0-3ubuntu4
Candidate: 3.2.0-3ubuntu4
Version table:
*** 3.2.0-3ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
100 /var/lib/dpkg/status |
[Impact]
The backuppc package struggled with ping response on all hosts after upgrade, because the package on both Bionic and Focal doesn’t contain a valid setting for ping6.
This situation before the patch was applied was really unfortunate for users whose backup hosts are using IPv6.
[Test Plan]
** Reproduction **
Make a container(s) for testing:
First option: (creating focal vm)
$ lxc launch images:ubuntu/focal focal-test
$ lxc shell focal-test
Second option: (creating bionic vm)
$ lxc launch images:ubuntu/bionic bionic-test
$ lxc shell bionic-test
Simply install the backuppc package using ‘apt install’ and check the variables in the config.pl file.
** Verification **
Follow the reproduction steps above to ensure that the variable is properly set.
[Where problems could occur]
First of all, any code change might change the behavior of the package in a specific situation and cause other errors. The regression possibilities here are really low.
It is unlikely but possible that users could hardcode valid setting for ping6. In that case if the same user wants to install backuppc, there is a high risk that a warning message will appear and there is a necessity to unify the setting by removing it and installing again.
Another possible (albeit unlikely) source of regressions is the fact that we will be rebuilding backuppc against newer versions of its build dependencies, especially on Bionic.
---------------original bug report----------------------
Binary package hint: backuppc
After upgrading from 3.1.0 to 3.2.0 as part of the Ubuntu server upgrade from maverick to natty, none of my hosts were backing up, and all (including localhost) were reporting "no ping response". I followed all instructions prior to upgrading, and backuppc was at 3.1.0-9ubuntu2 and working. I discovered the addition of the Ping6Path config variable, which is set to "undef" by default. My config.pl file had the line
$Conf{Ping6Path} = undef;
after both an upgrade to 3.2.0-3ubuntu4 and a clean install after purging the package. This, combined with the added code to Lib.pm caused the $pingPath in $pingCmd to be empty, thus causing the "no ping response" errors.
Changing the Ping6Path line in config.pl to
$Conf{Ping6Path} = '/bin/ping6';
solved the problem. This value should be populated by default for a fresh install if /bin/ping6 is found, just as /bin/ping is populated in $Conf{PingPath}.
# lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
# apt-cache policy backuppc
backuppc:
Installed: 3.2.0-3ubuntu4
Candidate: 3.2.0-3ubuntu4
Version table:
*** 3.2.0-3ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
100 /var/lib/dpkg/status |
|
| 2022-08-11 18:59:21 |
Michał Małoszewski |
description |
[Impact]
The backuppc package struggled with ping response on all hosts after upgrade, because the package on both Bionic and Focal doesn’t contain a valid setting for ping6.
This situation before the patch was applied was really unfortunate for users whose backup hosts are using IPv6.
[Test Plan]
** Reproduction **
Make a container(s) for testing:
First option: (creating focal vm)
$ lxc launch images:ubuntu/focal focal-test
$ lxc shell focal-test
Second option: (creating bionic vm)
$ lxc launch images:ubuntu/bionic bionic-test
$ lxc shell bionic-test
Simply install the backuppc package using ‘apt install’ and check the variables in the config.pl file.
** Verification **
Follow the reproduction steps above to ensure that the variable is properly set.
[Where problems could occur]
First of all, any code change might change the behavior of the package in a specific situation and cause other errors. The regression possibilities here are really low.
It is unlikely but possible that users could hardcode valid setting for ping6. In that case if the same user wants to install backuppc, there is a high risk that a warning message will appear and there is a necessity to unify the setting by removing it and installing again.
Another possible (albeit unlikely) source of regressions is the fact that we will be rebuilding backuppc against newer versions of its build dependencies, especially on Bionic.
---------------original bug report----------------------
Binary package hint: backuppc
After upgrading from 3.1.0 to 3.2.0 as part of the Ubuntu server upgrade from maverick to natty, none of my hosts were backing up, and all (including localhost) were reporting "no ping response". I followed all instructions prior to upgrading, and backuppc was at 3.1.0-9ubuntu2 and working. I discovered the addition of the Ping6Path config variable, which is set to "undef" by default. My config.pl file had the line
$Conf{Ping6Path} = undef;
after both an upgrade to 3.2.0-3ubuntu4 and a clean install after purging the package. This, combined with the added code to Lib.pm caused the $pingPath in $pingCmd to be empty, thus causing the "no ping response" errors.
Changing the Ping6Path line in config.pl to
$Conf{Ping6Path} = '/bin/ping6';
solved the problem. This value should be populated by default for a fresh install if /bin/ping6 is found, just as /bin/ping is populated in $Conf{PingPath}.
# lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
# apt-cache policy backuppc
backuppc:
Installed: 3.2.0-3ubuntu4
Candidate: 3.2.0-3ubuntu4
Version table:
*** 3.2.0-3ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
100 /var/lib/dpkg/status |
[Impact]
The backuppc package struggled with ping response on all hosts after upgrade, because the package on both Bionic and Focal doesn’t contain a valid setting for ping6.
This situation before the patch was applied was really unfortunate for users whose backup hosts are using IPv6.
[Test Plan]
** Reproduction **
Make a container(s) for testing:
First option: (creating focal vm)
$ lxc launch images:ubuntu/focal focal-test
$ lxc shell focal-test
Second option: (creating bionic vm)
$ lxc launch images:ubuntu/bionic bionic-test
$ lxc shell bionic-test
Simply install the backuppc package using ‘apt install’ and check the variables in the config.pl file.
Follow the reproduction steps above to ensure that the variable is properly set.
[Where problems could occur]
First of all, any code change might change the behavior of the package in a specific situation and cause other errors. The regression possibilities here are really low.
It is unlikely but possible that users could hardcode valid setting for ping6. In that case if the same user wants to install backuppc, there is a high risk that a warning message will appear and there is a necessity to unify the setting by removing it and installing again.
Another possible (albeit unlikely) source of regressions is the fact that we will be rebuilding backuppc against newer versions of its build dependencies, especially on Bionic.
---------------original bug report----------------------
Binary package hint: backuppc
After upgrading from 3.1.0 to 3.2.0 as part of the Ubuntu server upgrade from maverick to natty, none of my hosts were backing up, and all (including localhost) were reporting "no ping response". I followed all instructions prior to upgrading, and backuppc was at 3.1.0-9ubuntu2 and working. I discovered the addition of the Ping6Path config variable, which is set to "undef" by default. My config.pl file had the line
$Conf{Ping6Path} = undef;
after both an upgrade to 3.2.0-3ubuntu4 and a clean install after purging the package. This, combined with the added code to Lib.pm caused the $pingPath in $pingCmd to be empty, thus causing the "no ping response" errors.
Changing the Ping6Path line in config.pl to
$Conf{Ping6Path} = '/bin/ping6';
solved the problem. This value should be populated by default for a fresh install if /bin/ping6 is found, just as /bin/ping is populated in $Conf{PingPath}.
# lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
# apt-cache policy backuppc
backuppc:
Installed: 3.2.0-3ubuntu4
Candidate: 3.2.0-3ubuntu4
Version table:
*** 3.2.0-3ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
100 /var/lib/dpkg/status |
|
| 2022-08-17 18:01:40 |
Michał Małoszewski |
backuppc (Ubuntu Bionic): status |
Triaged |
In Progress |
|
| 2022-08-17 18:01:42 |
Michał Małoszewski |
backuppc (Ubuntu Focal): status |
Triaged |
In Progress |
|
| 2022-10-12 11:49:30 |
Robie Basak |
backuppc (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2022-10-12 11:49:31 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-10-12 11:49:32 |
Robie Basak |
bug |
|
|
added subscriber SRU Verification |
| 2022-10-12 11:49:36 |
Robie Basak |
tags |
bitesize |
bitesize verification-needed verification-needed-focal |
|
| 2022-10-12 11:50:03 |
Robie Basak |
backuppc (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2022-10-12 11:50:09 |
Robie Basak |
tags |
bitesize verification-needed verification-needed-focal |
bitesize verification-needed verification-needed-bionic verification-needed-focal |
|
| 2022-10-12 13:23:56 |
Thilo-Alexander Ginkel |
removed subscriber Thilo-Alexander Ginkel |
|
|
|
| 2023-01-11 20:29:23 |
Brian Murray |
tags |
bitesize verification-needed verification-needed-bionic verification-needed-focal |
bitesize removal-candidate verification-needed verification-needed-bionic verification-needed-focal |
|
| 2023-04-21 14:56:40 |
Robie Basak |
backuppc (Ubuntu Focal): status |
Fix Committed |
Triaged |
|
| 2023-04-21 14:56:53 |
Robie Basak |
tags |
bitesize removal-candidate verification-needed verification-needed-bionic verification-needed-focal |
bitesize removal-candidate verification-needed verification-needed-bionic |
|
| 2023-06-01 07:38:06 |
Łukasz Zemczak |
tags |
bitesize removal-candidate verification-needed verification-needed-bionic |
bitesize removal-candidate verification-needed |
|
| 2023-06-01 07:38:08 |
Łukasz Zemczak |
backuppc (Ubuntu Bionic): status |
Fix Committed |
Won't Fix |
|
| 2023-06-01 07:38:10 |
Łukasz Zemczak |
tags |
bitesize removal-candidate verification-needed |
bitesize removal-candidate |
|
| 2023-10-10 09:32:31 |
Christian Ehrhardt |
backuppc (Ubuntu Focal): assignee |
Michał Małoszewski (michal-maloszewski99) |
|
|
| 2023-10-10 09:32:33 |
Christian Ehrhardt |
backuppc (Ubuntu Bionic): assignee |
Michał Małoszewski (michal-maloszewski99) |
|
|
| 2024-04-08 13:51:40 |
Athos Ribeiro |
tags |
bitesize removal-candidate |
bitesize removal-candidate server-triage-discuss |
|
| 2024-04-10 15:05:54 |
Bryce Harrington |
tags |
bitesize removal-candidate server-triage-discuss |
bitesize removal-candidate |
|
