meta-facebook: yosemite4: Adjust power state checks after AC cycle

Description:
- Set log-chassis-powercycle.service (Log-service) dependency to start
  after phosphor-discover-system.service (policy-service).
- Added lock check in Log-service to prevent failures during DC ON
  execution latency.
- Configured chassis-powercycle.service (AC-cycle-service) and
  Log-services as mutually exclusive using systemd Conflicts.

Motivation:
1. The failure is observed policy-service may run slower, so DC-on
   process was delayed due to a timing. When the Log-service checked
   the DC power status, it assumed DC was not on yet and logged
   failed AC cycle.
2. Consecutive AC cycle commands, leading to timing conflict between
   the second command execution and Log-service status check failed.

This change ensures that Log-service only executes after the DC ON/OFF
sequence is fully stabilized. Additionally, it enforces mutual
exclusivity between AC cycle command and Log-service to prevent
concurrent execution during AC cycles.

Tested:
- Stress 2,500 blade AC cycle and ensure the power state remains
  normal - pass

Change-Id: If7f9d4ca5c8ecd38ef4bae1a22fc6fd9f9ec045d
Signed-off-by: Zoey YJ Chung <zoey.yj.chung.wiwynn@gmail.com>

0 files changed, 0 insertions, 0 deletions