NethVoice: failed FreePBX startup can block updates #8315

Steps to reproduce

1. On a disposable NethVoice 1.8.0 installation, trigger a FreePBX initialization failure during an update, for example the obsolete chan_sip TLS failure described in NethVoice: obsolete chan_sip TLS prevents startup #8301.
2. Leave pending CTI reload and reports restart notifications created by FreePBX while the upgrade has stopped watcher.path.
3. Retry the application update to NethVoice 1.8.1.

Expected behavior

A FreePBX startup failure must not leave notification files that prevent a subsequent application update. Pending CTI reload and reports restart requests should be removed after the FreePBX container stops.

Actual behavior

An update failure was reported on two machines:

chown: changing ownership of './state/notify/reload_nethcti-server': Operation not permitted
chown: changing ownership of './state/notify/restart_reports-api': Operation not permitted
extract-image ghcr.io/nethesis/nethvoice:1.8.1 returned non-zero exit status 1.

FreePBX creates these files through ctiReloadHelper.sh. When created as the container's asterisk user (UID 990, GID 991), they have subordinate host IDs rather than the module user's ownership. Normally the watcher removes them. The upgrade stops the watcher before starting FreePBX and restores it only after successful initialization, so a startup failure can leave the requests pending.

NS8's extract-image then runs chown -cR --reference=. ., which also traverses runtime state. The unprivileged module user cannot change ownership of these files, so extraction and the next update fail.

Source inspection establishes this failure path; the exact sequence and file ownership on the two affected machines have not been inspected directly. Existing affected installations can be recovered manually; automatic recovery is outside this fix.

Components

NethVoice 1.8.0; reported failure while updating to 1.8.1. NS8 core image extraction; installed core version was not supplied.

See also

• NethVoice: obsolete chan_sip TLS prevents startup #8301: FreePBX startup failure caused by obsolete chan_sip TLS settings.
• NethVoice: saving outbound routes fails with PIN disabled #8302: reported alongside the incident, but its outbound-route save failure does not establish a startup-loop connection.