fcpushservice Is Re-enabled and Started During FileCloud Server Upgrade
Original Question or Issue:
The fcpushservice service was previously disabled by the customer but was unexpectedly re-enabled and started after a FileCloud Server upgrade/OS patching and server reboot. The service subsequently consumed disk space in the customer environment.
Environment:
- Product - FileCloud Server
- Version - 23.261
- Platform - Linux
Steps to Reproduce:
- Disable the
fcpushserviceservice before performing a FileCloud Server upgrade. - Perform the FileCloud Server upgrade using the applicable RHEL or Ubuntu upgrade process.
- Complete the upgrade and reboot the server if required.
- Check the status of the
fcpushserviceservice. - Observe that the service has been re-enabled and started despite being disabled before the upgrade.
Error or Log Message:
No specific error message is generated. The issue is observed as unexpected service activation after the upgrade.
Defect or Enhancement Number:
FCL-13323
Cause:
The RHEL and Ubuntu FileCloud Server upgrade scripts currently re-enable and start the fcpushservice service during the upgrade process, regardless of the service state configured by the customer before the upgrade.
As a result, a service that was intentionally disabled before the upgrade may become enabled and start automatically after the upgrade.
Resolution or Workaround:
If fcpushservice is disabled before performing an upgrade, manually disable the service again after the upgrade has completed.
Verify the service status after the upgrade and ensure that it remains disabled if the customer does not require it.
Notes: