package tgt 1:1.0.63-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Petar Bojovic]

TGT is failing, reinstall attempt also failed.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tgt 1:1.0.63-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl
ApportVersion: 2.20.1-0ubuntu2
AptOrdering:
 tgt: Install
 tgt: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Apr 30 16:11:52 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2015-09-11 (232 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt 1.2.10ubuntu1
SourcePackage: tgt
Title: package tgt 1:1.0.63-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-04-22 (8 days ago)

[Robie Basak (racb)]

From log:

апр 30 16:14:44 hostname maas.boot_image_download_service[4530]: [ERROR] Failed to download images: Unable to parse the active state from systemd for service 'tgt', active state reported as 'deactivating'.

[Andres Rodriguez (andreserl)]

Looking at the logs, this doesn't seem like a MAAS issue. MAAS monitors tgt daemon and starts it if it needs to be started or it attempts to restart it if it failed.

The following error log shows that MAAS found an error while querying for service status (meaning that something caused it to fail and MAAS doesn't know what).

апр 30 16:06:37 hostname maas.service_monitor[4530]: [ERROR] While monitoring service 'tgt' an error was encountered: Unable to parse the active state from systemd for service 'tgt', active state reported as 'deactivating'.

Then, looking at other logs this seems like the actual tgt service failed:

Setting up tgt (1:1.0.63-1ubuntu1) ...
Job for tgt.service failed because a fatal signal was delivered to the control process. See "systemctl status tgt.service" and "journalctl -xe" for details.
invoke-rc.d: initscript tgt, action "start" failed.

And the following:

апр 30 16:07:19 hostname systemd[1]: tgt.service: State 'stop-sigterm' timed out. Killing.
апр 30 16:07:19 hostname systemd[1]: Failed to start (i)SCSI target daemon.
апр 30 16:07:19 hostname systemd[1]: tgt.service: Failed with result 'signal'.

All in all, MAAS doesn't do anything other than try to start/stop tgt. If tgt is failing to start/install for whatever reason, then this is not MAAS' fault.

Can you please post the output of systemd to see what tgt faisl to start?

[Launchpad Janitor (janitor)]

[Expired for tgt (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for maas (Ubuntu) because there has been no activity for 60 days.]