Project

General

Profile

Segnalazione #259

fussclient -a -n

Added by Michael Guggenberg over 8 years ago. Updated over 8 years ago.

Status:
Risolto
Priority:
Normale
Assignee:
Michael Guggenberg
Start date:
05/16/2017
Due date:
% Done:

0%

Estimated time:

Description

fuss-client -h
-n, --no-nfs Don't use NFS homes, but local homes instead

E possibile che fuss-client non tiene in considerazione di ignorare il mount da nfs della home?

TASK [homes : Remount /home] *******************************************
fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["systemctl", "start", "home.mount"], "delta": "0:00:00.035382", "end": "2017-05-16 11:09:11.595565", "failed": true, "rc": 1, "start": "2017-05-16 11:09:11.560183", "stderr": "Job for home.mount failed. See 'systemctl status home.mount' and 'journalctl -xn' for details.", "stdout": "", "stdout_lines": [], "warnings": []}


Files

fuss-client_-a_-n_-g_test1.log (13.4 KB) fuss-client_-a_-n_-g_test1.log Michael Guggenberg, 05/16/2017 11:20 AM

History

#1

Updated by Michael Guggenberg over 8 years ago

  • Assignee set to TRUELITE
#2

Updated by Elena Grandi over 8 years ago

  • Assignee changed from TRUELITE to Elena Grandi
#3

Updated by Elena Grandi over 8 years ago

  • Status changed from Nuovo to Commenti
  • Assignee changed from Elena Grandi to Michael Guggenberg

Ho trovato che in due task c'erano delle condizioni buggate che in alcuni casi venivano eseguite comunque.

Sto aggiornando il pacchetto, sarĂ  disponibile a breve la versione 8.0.6 di fuss-client che le fixa.

#4

Updated by Michael Guggenberg over 8 years ago

  • Status changed from Commenti to Risolto

Also available in: Atom PDF