reject Transition request while firmware being flashed

When users request to flash BMC/Host... firmware, the BMC should reject
turning on the host or rebooting BMC requests to protect the system.
As

reject Transition request while firmware being flashed

When users request to flash BMC/Host... firmware, the BMC should reject
turning on the host or rebooting BMC requests to protect the system.
As defined in the PDIs [1], the ActivationBlocksTransition interface is
used to prevent power-on during flashing. The phosphor-state-manager
shall look for this interface to make decision should transition request
is executed or not. When BMC rejects the transition request, an error is
thrown as defined in PDIs [2].

[1] https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Software/ActivationBlocksTransition.interface.yaml
[2] https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/75231

Tested:
Enable check-fwupdate-before-do-transition option
1. Request to flash Host's firmware via Redfish or WebUi
2. Request to turn off the Host.
$ipmitool power off
3. BMC turns off the power.
4. Request to turn on the Host.
$ipmitool power on
5. BMC rejects above request. No power action is executed.
6. Request to reboot BMC.
$ipmitool mc reset cold
7. BMC did not reboot.
8. Request turn on the Host after flashing done.
9. BMC turns on the Power.
10. Request to reboot BMC.
11. BMC reboots.

Disable check-fwupdate-before-do-transition option
1. Request to flash Host's firmware via Redfish or WebUi
2. Request to turn off the Host.
$ipmitool power off
3. BMC turns off the power.
4. Request to turn on the Host.
$ipmitool power on
5. BMC does not reject this request, but no power action is handled
6. When flashing done, BMC turns on the power.

Change-Id: If3998e58d24cfb72d13b01eb5b8c8cc5a39b3c95
Signed-off-by: Thang Tran <thuutran@amperecomputing.com>

show more ...

clang-tidy: Enable readability-simplify-boolean-expr check

This checks for boolean expressions involving boolean constants
and simplifies them to use the appropriate boolean expression
directly.

Ch

clang-tidy: Enable readability-simplify-boolean-expr check

This checks for boolean expressions involving boolean constants
and simplifies them to use the appropriate boolean expression
directly.

Change-Id: I4ad7ec4ddfa4cfe9a0cf0d569d3d81c478c1776a
Signed-off-by: Pavithra Barithaya <pavithrabarithaya07@gmail.com>

show more ...

prefer std::format over fmt

Now that std::format is implemented we aren't using complex enough fmt
to warrant using it over the std version. Switch to std and remove the
dependency.

Signed-off-by:

prefer std::format over fmt

Now that std::format is implemented we aren't using complex enough fmt
to warrant using it over the std version. Switch to std and remove the
dependency.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ib03cdb6a9db4d25de345bdb49b28157880c19bc1

show more ...

reduce dbus string constants

There are a large number of dbus constants scattered throughout the
code that could/should be obtained from phosphor-dbus-interface values.
Perform minor refactoring to

reduce dbus string constants

There are a large number of dbus constants scattered throughout the
code that could/should be obtained from phosphor-dbus-interface values.
Perform minor refactoring to greatly reduce the number of string
constants.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ie8700bc90611d21eee7160f4686bc978fe0a0eb4

show more ...

sdbus++: use non-deprecated namespaces

The sdbusplus repository has deprecated some namespaces and they are
currently only enabled with the SDBUSPP_REMOVE_DEPRECATED_NAMESPACE
guard. Switch to the

sdbus++: use non-deprecated namespaces

The sdbusplus repository has deprecated some namespaces and they are
currently only enabled with the SDBUSPP_REMOVE_DEPRECATED_NAMESPACE
guard. Switch to the new namespace names.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I9f67e74a02616d8ea2241c18758308f2b669672d

show more ...

bmc-ready: don't allow power operations if not ready

Tested:
- Put BMC in NotReady state and verified error was returned when
requesting a chassis or host power on
- Verified that a power off was

bmc-ready: don't allow power operations if not ready

Tested:
- Put BMC in NotReady state and verified error was returned when
requesting a chassis or host power on
- Verified that a power off was still possible in this state

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8f17c681469c01c701e80cdb57ed623e04c8b921

show more ...

move systemd subscribe to util function

This code is replicated in multiple source files in this repo, put it in
the util repo so everyone can call it in one place.

Tested:
- Verified systemd signa

move systemd subscribe to util function

This code is replicated in multiple source files in this repo, put it in
the util repo so everyone can call it in one place.

Tested:
- Verified systemd signals seen and system boots

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I8bf0343c79012cc91dea033038894a011fd37ef5

show more ...

Support chassis power cycle

A new system is being designed which will utilize phosphor-state-manager
and it requires the chassis system power cycle feature.

Test plan:
Change property "RequestedPow

Support chassis power cycle

A new system is being designed which will utilize phosphor-state-manager
and it requires the chassis system power cycle feature.

Test plan:
Change property "RequestedPowerTransition" to trigger
chassis power cycle target.

Change-Id: I30b0efd7c0fc72a9fb378f48e47c4c1af2b22ad6
Signed-off-by: Bonnie Lo <Bonnie_Lo@wiwynn.com>

show more ...

call new obmc-chassis-blackout@.target on blackout

The following commit introduced a new systemd target to be called when
OpenBMC firmware detects a power blackout has occurred (system
unexpectedly

call new obmc-chassis-blackout@.target on blackout

The following commit introduced a new systemd target to be called when
OpenBMC firmware detects a power blackout has occurred (system
unexpectedly lost all power to system):
https://gerrit.openbmc.org/c/openbmc/docs/+/54204

This target is now in place and the appropriate services have been
installed into it. Switch the state-manager code over to call this new
target.

Tested:
- Verified in simulation that the target was called when the system
experienced a blackout.

From a powered off state.
root@p10bmc: systemctl stop xyz.openbmc_project.State.Chassis.service

Manipulated file to indicate that the power was on before service ended
root@p10bmc: vi /var/lib/chassStateChangeTime

root@p10bmc: systemctl start xyz.openbmc_project.State.Chassis.service
Jun 22 17:05:37 p10bmc phosphor-chassis-state-manager[1155]:
The system suffered a power blackout.

root@p10bmc: systemctl status obmc-chassis-blackout@0.target
Active: active since Wed 2022-06-22 17:05:37 UTC; 8s ago

root@p10bmc: systemctl status phosphor-reset-state-sensors@0.service
Jun 22 17:05:37 p10bmc systemd[1]: Finished Reset host sensors.

root@p10bmc: systemctl status obmc-led-group-stop@power_on.service
Active: active (exited) since Wed 2022-06-22 17:05:37 UTC; 8s ago

Signed-off-by: Corey Hardesty <corey.hardesty@icloud.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: If95f8da52ec024e699204f4b26784c7457da5abf

show more ...

Only run power restore on AC losses

Added a meson build option that allows the customer to enable automatic
power restore policy only for AC losses where the chassis power was
on prior to a BMC rese

Only run power restore on AC losses

Added a meson build option that allows the customer to enable automatic
power restore policy only for AC losses where the chassis power was
on prior to a BMC reset(and off when it comes back online).

The default is set to 'false' which provides the standard behavior of
APR which is to always run APR on an BMC reboot.
If the option 'only-run-apr-on-power-loss' is 'true' then APR is only
run in the case of the chassis losing power. AC power losses trigger the
creation of a file called 'chassis@0-lost-power' that identifies an
AC power loss has occurred. This generated file can be found in the
directory '/run/openbmc/'.

Tested:
- Verified that when built with option 'only-run-apr-on-power-loss'
set to false(default) that APR was ran.
- Verified that when built with option 'only-run-apr-on-power-loss'
set to true that apr was not ran when a power loss did not occur.
- Verified that when built with option 'only-run-apr-on-power-loss'
set to true that apr was only ran when a power loss occured.

Jun 08 01:55:13 p10bmc phosphor-chassis-state-manager[3009]:
The system suffered a power blackout.

root@p10bmc:/lib/systemd/system# ls /run/openbmc/
chassis@0-lost-power

Signed-off-by: Corey Hardesty <corey.hardesty@icloud.com>
Change-Id: Iac37761416d699e3a469936e00868a8d9b6dfdb1

show more ...

sdbusplus: use shorter type aliases

The sdbusplus headers provide shortened aliases for many types.
Switch to using them to provide better code clarity and shorter
lines. Possible replacements are

sdbusplus: use shorter type aliases

The sdbusplus headers provide shortened aliases for many types.
Switch to using them to provide better code clarity and shorter
lines. Possible replacements are for:
* bus_t
* exception_t
* manager_t
* match_t
* message_t
* object_t
* slot_t

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I41103c892db258a85640aa1442acd9a295c8a847

show more ...

update to latest openbmc clang format standards

Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
Change-Id: Ibb0e97e8850bbd3c1eff82f4630328e2b5d15220

call auto power restart when chassis power recovers

When the power status transitions from bad to good, call the Auto
Power-on Restart (APR) functionality to see if the system should be
automaticall

call auto power restart when chassis power recovers

When the power status transitions from bad to good, call the Auto
Power-on Restart (APR) functionality to see if the system should be
automatically powered back on.

In most cases, a power issue to the system will result in the BMC
losing power as well. The APR functionality already runs as a part of
the BMC boot. However there are a few situations where the chassis power
may need to be turned off but the BMC will continue to operate on
standby power. This commit addresses that scenario, where once the
chassis power can be turned back on, the BMC runs the APR logic.

This allows systems to get up and running automatically after brownout
and UPS battery low issues.

Note that a change to phosphor-state-manager-systemd-links.inc is
required here to make the APR service a WantedBy vs. RequiredBy
relationship. Restarting a service that is required by multi-user.target
restarts all the other oneshot service in multi-user.target which is not
wanted here. This change will be included with the bump of this
function.

Tested:
- Verified system called APR when CurrentPowerStatus went from
UninterruptiblePowerSupply to Good
- Verified system did not power on when APR was not set to AlwaysOn
- Verified system did power on when APR was set to AlwaysOn

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: If9a5e1a91eb8da6e39e021900ad07848eebbdd02

show more ...

ensure power status is always correct

There's a slight bug here in that anytime determineStatusOfPower() is
called, the PowerStatus was set to Good for a period of time. This can
cause confusion on

ensure power status is always correct

There's a slight bug here in that anytime determineStatusOfPower() is
called, the PowerStatus was set to Good for a period of time. This can
cause confusion on clients monitoring the property. Instead of
defaulting it to good, set it after the true status is known.

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: If48eb5bd1c2bd94d51d12aff54a186aba295b179

show more ...

phosphor-state-manager: Support multi-host for persist files

phosphor-host-state-manager and phosphor-chassis-state-manager store
informations in files then restore that on service starting.
Since s

phosphor-state-manager: Support multi-host for persist files

phosphor-host-state-manager and phosphor-chassis-state-manager store
informations in files then restore that on service starting.
Since state-managers already change to multi-host now, information
should store into different files from each service instance.

forbackward capability, if there are legacy persist file exist,
rename it to the new file format of instance ;0',i.e, rename files:
'requestedHostTransition' to 'host0-PersistData',
'POHCounter' to 'chassis-POHCounter',
'chassisStateChangeTime' to 'chassis0-StateChangeTime'

Changes:
a.phosphor-host-state-manager:
'/var/lib/phosphor-state-manager/requestedHostTransition'
this file not only store requestedHostTransition now,
rename to PersistData and add host-N prefix for each service.
For example, bus xyz.openbmc_project.State.Host1 store data to
'/var/lib/phosphor-state-manager/host1-PersistData'
xyz.openbmc_project.State.Host2 store date to
'/var/lib/phosphor-state-manager/host2-PersistData'

b.phosphor-chassis-state-manager:

There are two files to store informations
'/var/lib/phosphor-state-manager/POHCounter',
'/var/lib/phosphor-state-manager/chassisStateChangeTime'
change to:
'/var/lib/phosphor-state-manager/chassis1-POHCounter',
'/var/lib/phosphor-state-manager/chassis2-POHCounter'
...
'/var/lib/phosphor-state-manager/chassis1-StateChangeTime'
'/var/lib/phosphor-state-manager/chassis2-StateChangeTime'
... for each service.

Tested on Bletchley HW,

set xyz.openbmc_project.State.Host1 RequestedHostTransition to On
'busctl set-property xyz.openbmc_project.State.Host1 /xyz/openbmc_project/state/host1
xyz.openbmc_project.State.Host RequestedHostTransition s "xyz.openbmc_project.State.Host.Transition.On"'

This request will store in file:
'cat /var/lib/phosphor-state-manager/host1-PersistData'
{
"value0": {
"cereal_class_version": 1,
"value0": "xyz.openbmc_project.State.Host.Transition.On",
"value1": "xyz.openbmc_project.State.Boot.Progress.ProgressStages.Unspecified",
"value2": "xyz.openbmc_project.State.OperatingSystem.Status.OSStatus.Inactive"
}

restart xyz.openbmc_project.State.Host1~Host6 or reboot BMC, 'RequestedHostTransition' for host1 still "On"
'busctl get-property xyz.openbmc_project.State.Host1 /xyz/openbmc_project/state/host1
xyz.openbmc_project.State.Host RequestedHostTransition'
s "xyz.openbmc_project.State.Host.Transition.On"
'RequestedHostTransition' of the rest 5 Hosts are default value "xyz.openbmc_project.State.Host.Transition.Off"

Also, set POHCounter of xyz.openbmc_project.State.Chassis2
'busctl set-property xyz.openbmc_project.State.Chassis2 /xyz/openbmc_project/state/chassis2
xyz.openbmc_project.State.PowerOnHours POHCounter u 5'
it will restore after service restart or BMC reboot,
'busctl get-property xyz.openbmc_project.State.Chassis2 /xyz/openbmc_project/state/chassis2
xyz.openbmc_project.State.PowerOnHours POHCounter'
u 5

Change-Id: I739c62707bb805e7c25f399a2fea06beee5543a0
Signed-off-by: Allen.Wang <Allen_Wang@quantatw.com>

show more ...

chassis: Monitor the PowerSystemInputs for power status

In addition to the uPower interface, monitor the PowerSystemInputs
interface to detect a Brownout condition. Reference:
https://gerrit.openbmc

chassis: Monitor the PowerSystemInputs for power status

In addition to the uPower interface, monitor the PowerSystemInputs
interface to detect a Brownout condition. Reference:
https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/48015

Tested: In simulation, trigger a power supply brownout and clear it,
verify that phosphor-chassis-check-power-status detects the condition:

Mar 29 19:02:21 p10bmc phosphor-chassis-state-manager[1101]: Power
System Inputs status changed to
xyz.openbmc_project.State.Decorator.PowerSystemInputs.Status.Fault
Mar 29 19:02:21 p10bmc phosphor-chassis-state-manager[1101]: Power
System Inputs status is in Fault state

root@p10bmc:~# /usr/bin/phosphor-chassis-check-power-status --chassis 0
<3> Chassis power status is not good:
xyz.openbmc_project.State.Chassis.PowerStatus.BrownOut
Mar 29 19:08:20 p10bmc phosphor-chassis-check-power-status[1133]:
Chassis power status is not good:
xyz.openbmc_project.State.Chassis.PowerStatus.BrownOut
Mar 29 19:08:20 p10bmc phosphor-log-manager[319]: Created PEL 0x50000004
(BMC ID 4) with SRC BDA13402
Mar 29 19:08:20 p10bmc phosphor-ledmanager[447]: SAI: FRU path:
/xyz/openbmc_project/inventory/system

Mar 29 19:02:21 p10bmc phosphor-chassis-state-manager[1101]: Power
System Inputs status changed to
xyz.openbmc_project.State.Decorator.PowerSystemInputs.Status.Good
Mar 29 19:02:21 p10bmc phosphor-chassis-state-manager[1101]:
determineStatusOfPSUPower(): Good

root@p10bmc:~# /usr/bin/phosphor-chassis-check-power-status --chassis 0
<6> Chassis power status good, start power on

Change-Id: I6adbb6474155e50219b6a48dd9b2cf872934f4a6
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>

show more ...

power-on-hours: ensure not incremented when system off

Poh counter is incrementing once the timer expires and chassis is power
on. setEnabled will not stops the timer if chassis is poweroff, and the

power-on-hours: ensure not incremented when system off

Poh counter is incrementing once the timer expires and chassis is power
on. setEnabled will not stops the timer if chassis is poweroff, and the
counter get increments within remaining expring time. Hence, resetting
the remainingexpiring time for poweron state, so counter get increment
after 1 hour intervel.

tested:
root@dgx:~# ipmitool chassis power off
Chassis Power Control: Down/Off

jounal logs:
------------
4267:Jan 01 00:05:52 dgx phosphor-chassis-state-manager[369]: Received
signal that power OFF is complete
4268:Jan 01 00:05:52 dgx phosphor-chassis-state-manager[369]: Change to
Chassis Power State: xyz.openbmc_project.State.Chassis.PowerState.Off
4269:Jan 01 00:05:52 dgx phosphor-host-state-manager[448]: Received sig-
nal that host is off
4270:Jan 01 00:05:52 dgx phosphor-host-state-manager[448]: Change to Host
State: xyz.openbmc_project.State.Host.HostState.Off
root@dgx:~#
root@dgx:~# ipmitool chassis power status
Chassis Power is off
root@dgx:~#
root@dgx:~# ipmitool raw 0x0 0x0f
3c 16 00 00 00
root@dgx:~#

journal logs:
------------

7471:Jan 01 01:38:29 dgx phosphor-chassis-state-manager[369]: Received
signal that power ON is complete
7472:Jan 01 01:38:29 dgx phosphor-chassis-state-manager[369]: Change to
Chassis Power State: xyz.openbmc_project.State.Chassis.PowerState.On
7473:Jan 01 01:38:29 dgx phosphor-host-state-manager[448]: Received sig-
nal that host is running
7474:Jan 01 01:38:29 dgx phosphor-host-state-manager[448]: Change to Host
State: xyz.openbmc_project.State.Host.HostState.Running

root@dgx:~# ipmitool raw 0x0 0x0f
3c 16 00 00 00
root@dgx:~# date
Thu Jan 1 01:39:25 UTC 1970

root@dgx:~# ipmitool chassis power status
Chassis Power is on
root@dgx:~# ipmitool raw 0x0 0x0f
3c 16 00 00 00
root@dgx:~# date
Thu Jan 1 02:25:58 UTC 1970
root@dgx:~# date
Thu Jan 1 02:38:29 UTC 1970
root@dgx:~# ipmitool raw 0x0 0x0f
3c 16 00 00 00
root@dgx:~# ipmitool raw 0x0 0x0f
3c 17 00 00 00

Signed-off-by: shamim ali <shamima@ami.com>
Change-Id: I8ca2c6b32813ed9559ef2edcc26c7216b0fc33b2

show more ...

chassis-state-manager: Correct poweroff state Unit

Previous commit changes the poweroff state unit to
"obmc-chassis-hard-poweroff@N.target" in accident,

currentPowerState should be set to Off if
"o

chassis-state-manager: Correct poweroff state Unit

Previous commit changes the poweroff state unit to
"obmc-chassis-hard-poweroff@N.target" in accident,

currentPowerState should be set to Off if
"obmc-chassis-poweroff@N.target" be activated

correct it back to "obmc-chassis-poweroff@{}.target"

Tested on Bletchley Platform:

root@bletchley:# systemctl start obmc-chassis-poweroff@1.target
root@bletchley:# journalctl -u xyz.openbmc_project.State.Chassis@1.service
Mar 23 08:31:02 bletchley phosphor-chassis-state-manager[15189]: Received signal that power OFF is complete
Mar 23 08:31:02 bletchley phosphor-chassis-state-manager[15189]: Change to Chassis Power State: xyz.openbmc_project.State.Chassis.PowerState.Off

Change-Id: I6464f92184147a7e1e72e408053848342eece801
Signed-off-by: Allen.Wang <Allen_Wang@quantatw.com>

show more ...

chassis-state-manager: Add multi-chassis support

Add multi-chassis management support, each chassis bus separates by
giving a unique chassis id.

Current code only support single chassis, and alway

chassis-state-manager: Add multi-chassis support

Add multi-chassis management support, each chassis bus separates by
giving a unique chassis id.

Current code only support single chassis, and alway assume bus name is
"xyz.openbmc_project.State.Chassis".

This patch allow user to launch chassis-state-manager with a chassis id,
and chassis id is added into service bus name for identification.

Because there are many places hardcode with bus name
"xyz.openbmc_project.State.Chassis", if chassis id is 0,
chassis-state-manager will request both
"xyz.openbmc_project.State.Chassis" and
"xyz.openbmc_project.State.Chassis0" bus name to meet backwards
compatibility.

Tested on Bletchley:
root@bletchley:~# busctl tree xyz.openbmc_project.State.Chassis
`-/xyz
`-/xyz/openbmc_project
`-/xyz/openbmc_project/state
`-/xyz/openbmc_project/state/chassis0
root@bletchley:~# busctl tree xyz.openbmc_project.State.Chassis0
`-/xyz
`-/xyz/openbmc_project
`-/xyz/openbmc_project/state
`-/xyz/openbmc_project/state/chassis0
root@bletchley:~# busctl tree xyz.openbmc_project.State.Chassis1
`-/xyz
`-/xyz/openbmc_project
`-/xyz/openbmc_project/state
`-/xyz/openbmc_project/state/chassis1
......

patch dependencies:
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-state-manager/+/51465

Signed-off-by: Potin Lai <potin.lai@quantatw.com>
Change-Id: I2ce3e9ab2c95a2688143f4e3775da164a5c33c19

show more ...

Set Critical severity for Blackout errors

Previously the PEL code for Blackout had severity default to critical.
This change allows fine-tuned control over severity to only set the
critical level fo

Set Critical severity for Blackout errors

Previously the PEL code for Blackout had severity default to critical.
This change allows fine-tuned control over severity to only set the
critical level for this Blackout event.

Signed-off-by: Mike Capps <mikepcapps@gmail.com>
Change-Id: I6f0b3604141b50c316c5bd04f69bf1c4d6fe6feb

show more ...

Correct pinhole reset logic for chassis state

The BMC state manager had the logic corrected to check for 0 to indicate
pinhole reset, 1 is NOT pinhole reset. The Chassis state manager also
needed a

Correct pinhole reset logic for chassis state

The BMC state manager had the logic corrected to check for 0 to indicate
pinhole reset, 1 is NOT pinhole reset. The Chassis state manager also
needed a change. Correcting this now.

Trace if pinholse reset was the cause in the else leg.

See: 2e352a21b64c6dcfe3bea980ff459d99f355828f

Tested:
Rainier 2S4U
Power on.
Remove input power to all four power supplies.
Apply power to all four power supplies.
Wait for BMC Ready.
Verify Blackout (110000AC) error logged.

Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
Change-Id: I3d8f7669627a78232dd0d5202447f488ef71a510

show more ...

host-sensors: Reset when system off but last state was on

When power was on before a BMC reboot and system is now off, the host
sensors need to be reset to show the correct system state of `off` now

host-sensors: Reset when system off but last state was on

When power was on before a BMC reboot and system is now off, the host
sensors need to be reset to show the correct system state of `off` now.
This is done by starting the `phosphor-reset-sensor-states@0.service`
unit, which handles setting the appropriate dbus properties.

Tested:
Power on system and then remove/add AC
Check BootProgress, etc.. properties set by reset service

Change-Id: I4928a231495a1295425dc828606b40de03253bab
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>

show more ...

ups: watch for property changes

Monitor for any changes to the properties the chassis manger is
interested in with the UPower interface.

Tested:
- Changed the properties via busctl after the chassi

ups: watch for property changes

Monitor for any changes to the properties the chassis manger is
interested in with the UPower interface.

Tested:
- Changed the properties via busctl after the chassis manager was
running and verified the chassis power status was updated correctly

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I13f23d33581c2339506f9c4739ce36bf07aef46e

show more ...

ups: check state on startup and update power status

Look for a UPS (uninterruptible power supply) D-Bus object on chassis
startup. If found, read its State and BatteryLevel properties to check
the c

ups: check state on startup and update power status

Look for a UPS (uninterruptible power supply) D-Bus object on chassis
startup. If found, read its State and BatteryLevel properties to check
the condition of the power to the chassis. Update the CurrentPowerStatus
property hosted by the chassis state manager based on this information.

Tested:
- Utilized ibm-ups feature to start in debug mode so all properties
could be manually set. Validated good path and bad paths for all
properties and ensured CurrentPowerStatus was set as expected for each
test.

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I064a9e7fecbed8f859828359a761877e0fa95251

show more ...

pinhole: do not log power loss error on pinhole

If the user did a pinhole reset to reboot the BMC and that happens to
cause a chassis power off, do not log an error as this was user
initiated. A sep

pinhole: do not log power loss error on pinhole

If the user did a pinhole reset to reboot the BMC and that happens to
cause a chassis power off, do not log an error as this was user
initiated. A separate error is logged to inform the user a pinhole
reset was done to the system.

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ib9059eeaa4325e7742ce024eed2f33923c6dea2a

show more ...