ipa-client-automount fails

Bug #1645201 reported by KC on 2016-11-28
30
This bug affects 7 people
Affects Status Importance Assigned to Milestone
freeipa (Ubuntu)
Undecided
Unassigned

Bug Description

Host was successfully enrolled with the FreeIPA server using the 'ipa-client-install' command.

$ sudo ipa-client-automount
Searching for IPA server...
IPA server: DNS discovery
Location: default
Continue to configure the system with these values? [no]: y
Configured /etc/default/nfs-common
Configured /etc/idmapd.conf
rpcidmapd failed to restart: Command '/bin/systemctl restart nfs-idmap.service' returned non-zero exit status 5
rpcgssd failed to restart: Command '/bin/systemctl restart nfs-secure.service' returned non-zero exit status 5
Restarting sssd, waiting for it to become available.
Started autofs

Distribution: Ubuntu 16.04
Architecture: amd64
Version: 4.3.1-0ubuntu1

CVE References

KC (bluelineswinger) on 2016-11-28
description: updated
Timo Aaltonen (tjaalton) wrote :

yeah, service mapping was wrong on ipaplatform/debian/services.py

Changed in freeipa (Ubuntu):
status: New → In Progress
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package freeipa - 4.3.2-5

---------------
freeipa (4.3.2-5) unstable; urgency=medium

  * fix-cve-2016-5404.diff: Fix permission check bypass (Closes: #835131)
    - CVE-2016-5404
  * ipa-kdb-support-dal-version-5-and-6.diff: Support mit-krb5 1.15.
    (Closes: #844114)

 -- Timo Aaltonen <email address hidden> Sat, 03 Dec 2016 01:02:40 +0200

Changed in freeipa (Ubuntu):
status: In Progress → Fix Released
KC (bluelineswinger) wrote :

Any chance this update will make its way into Xenial and Yakkety?

Gaëtan Trellu (goldyfruit) wrote :

Same question as @KC, any update about a landing in Xenial ?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers