[2.3, tgt] When not using tgt, MAAS shouldn't be managing tgt

[Andres Rodriguez]

MAAS, by default, no longer uses tgt. However, MAAS is sitll managing it. That means:

- service tracking
- re-writing tgt config

Unless tgt is re-enabled again, then MAAS should not be managing it at all nor attempt to do as above.

[Lee Trager (ltrager)]

This is partially solved by LP:1735025. The error from TGT is ignored and the images continue to get processed but the following is in the log:

Rack import warning - Unable to update TGT config: Command `/snap/maas/x1/usr/sbin/tgt-admin --conf /var/snap/maas/x1/var/lib/maas/boot-resources/current/maas.tgt --update ALL` returned non-zero exit status 107: tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected tgtadm: failed to send request hdr to tgt daemon, Transport endpoint is not connected

MAAS checks that TGT is up and running, rewrites the TGT config file, then tells TGT to reread its config file. For whatever reason tgt-admin cannot connect to the tgt daemon to request it to reread the config. As this works with the Debian package I suspect this is due to the Snap.

This means TGT is not working in the Snap currently. LP:1735025 logs this error instead of falling over so everything works for HTTP booting. What will fail is if the user sets the global variable http_boot=False as the image won't be loaded in tgt.

[Lee Trager (ltrager)]

MAAS does not report any problems with TGT with LP:1735025 applied.

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team