Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AA6AE17995 for ; Tue, 2 Jan 2024 22:57:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="SQdknyPP" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1704236225; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=kPXVAGZXba2DXFGvooB642sVvt98D19bIqrB9G5hrJU=; b=SQdknyPPZIsUFswVMJqsiws/S3FUBtRLzLD3qHeY9Kh5nmWS4B4f9pfU//CIot5D9lAxym k8YUMk8jfEqNSjRnRhoIBUU60U2aXm3Uc1cMNFVRGiHAMsTMQ1OFQiJgaIm4Fil0jK6sLL TY6qK5xfNcAnWkieQSRN/qZVh9c9Wo0= Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-57-6WolWiVVNhurDLu9X4GNew-1; Tue, 02 Jan 2024 17:57:04 -0500 X-MC-Unique: 6WolWiVVNhurDLu9X4GNew-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 13DEA1C0BA4A for ; Tue, 2 Jan 2024 22:57:04 +0000 (UTC) Received: from aion.redhat.com (unknown [10.22.32.219]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 04AD01121306 for ; Tue, 2 Jan 2024 22:57:04 +0000 (UTC) Received: from aion.redhat.com (localhost [IPv6:::1]) by aion.redhat.com (Postfix) with ESMTP id 7CCA41142D4 for ; Tue, 2 Jan 2024 17:57:03 -0500 (EST) From: Scott Mayhew To: kdevops@lists.linux.dev Subject: [PATCH] ktls: the tlshd service doesn't support reloading Date: Tue, 2 Jan 2024 17:57:03 -0500 Message-ID: <20240102225703.35416-1-smayhew@redhat.com> Precedence: bulk X-Mailing-List: kdevops@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.3 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true Use "state: restarted" instead. Fixes this error: fatal: [kdevops-nfs-default]: FAILED! => {"changed": false, "msg": "Unable to reload service tlshd.service: Failed to reload tlshd.service: Job type reload is not applicable for unit tlshd.service.\n"} Signed-off-by: Scott Mayhew --- playbooks/roles/ktls/tasks/main.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/playbooks/roles/ktls/tasks/main.yml b/playbooks/roles/ktls/tasks/main.yml index 41a980c9..85254cdf 100644 --- a/playbooks/roles/ktls/tasks/main.yml +++ b/playbooks/roles/ktls/tasks/main.yml @@ -107,4 +107,4 @@ ansible.builtin.systemd_service: name: tlshd.service enabled: true - state: reloaded + state: restarted -- 2.41.0