Fix failing unittests by including BuildRequires: passwd

The unittests started failing because of upstream commit
7c07af2 where cloud-init can now support using `usermod` to
lock an account if `passwd` isn't installed. Since `passwd`
wasn't installed in our mock buildroot it was choosing to
use `usermod` and the unittests were failing.

See: https://github.com/canonical/cloud-init/commit/7c07af2
This commit is contained in:
Dusty Mabe 2020-02-23 10:14:04 -05:00
parent 0c8287c279
commit cbaaeee097
No known key found for this signature in database
GPG Key ID: 3302DBD73952E671

View File

@ -28,6 +28,7 @@ BuildRequires: systemd
# For tests
BuildRequires: iproute
BuildRequires: passwd
BuildRequires: python3-configobj
# https://bugzilla.redhat.com/show_bug.cgi?id=1695953
BuildRequires: python3-distro
@ -160,6 +161,13 @@ nosetests-%{python3_version} tests/unittests/
%changelog
* Sun Feb 23 2020 Dusty Mabe <dusty@dustymabe.com> - 19.4-2
- Fix sed substitutions for unittest2 and assertItemsEqual
- Fix failing unittests by including `BuildRequires: passwd`
- The unittests started failing because of upstream commit
7c07af2 where cloud-init can now support using `usermod` to
lock an account if `passwd` isn't installed. Since `passwd`
wasn't installed in our mock buildroot it was choosing to
use `usermod` and the unittests were failing. See:
https://github.com/canonical/cloud-init/commit/7c07af2
* Fri Feb 14 2020 Eduardo Otubo <otubo@redhat.com> - 19.4-1
- Updated to 19.4