4.1.1

Fixed​

• Updating a server from 4.0.9 to 4.1.0 ended with hitechcloudcli portals converge did not finish: The Mail portal: portal-mail.tar.gz is not published for release 4.0.9 on the mirror. The convergence runs before the update records the new version, and the portal step read the recorded one, so it asked for the release being replaced. Every command the convergence runs, and every hitechcloudcli child the update starts (update, update --panel, update --repair), is now told the release being installed (HITECHCLOUD_RELEASE_VERSION); the components fetched during the convergence (the portal apps, the prebuilt webmail, the firewall, Meet and the Sentinel binaries) are those of that release. A second hitechcloudcli portals converge had worked only because the version was recorded by then.
• The portal API (hitechcloud-portalapi) did not start on a server without /var/cache/bind (for example AlmaLinux, where BIND keeps its data under /var/named): systemd refused the unit at its mount-namespace step (status=226/NAMESPACE) and restarted it for ever. The - that skips a missing path in ReadWritePaths= applies to each path, not to the whole line, and only the first path of each line had it. Every path the unit may lack now has its own -, /run/hitechcloud comes from RuntimeDirectory=, and a test fails if any unit in the release requires a path other than the directories every server has.
• hitechcloudcli portals status and the did not start error say why a portal unit is down (for example crash-looping, status=226/NAMESPACE, restarted 15 times: Failed to set up mount namespacing: /var/cache/bind: No such file or directory) instead of only stopped.