treewide: remove dependencies on mapper.target

The mapper is dbus activated now, so these explicit dependency
declarations are unnecessary and redundant.

Change-Id: I9898fa6c9918a6ab4fe166acf5d335f

treewide: remove dependencies on mapper.target

The mapper is dbus activated now, so these explicit dependency
declarations are unnecessary and redundant.

Change-Id: I9898fa6c9918a6ab4fe166acf5d335f89c1540fd
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>

show more ...

service-deps: remove logging as dependency

With the introduction of the following best practice:
https://github.com/openbmc/docs/commit/43421bdd06dece37b2acc4c656d7839bfedcc681

It was determined th

service-deps: remove logging as dependency

With the introduction of the following best practice:
https://github.com/openbmc/docs/commit/43421bdd06dece37b2acc4c656d7839bfedcc681

It was determined that phosphor-logging should be a d-bus activated
service. That is, this service will be activated when called so there is
no reason to specifically list it as a dependency in service files.

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

show more ...

Ensure POR reset is logged

In situations where the last reboot cause is not changed to POR,
specifically after unexpected AC losses, bmc-state-manager fails to
update the property. Therefore after a

Ensure POR reset is logged

In situations where the last reboot cause is not changed to POR,
specifically after unexpected AC losses, bmc-state-manager fails to
update the property. Therefore after a power cycle the last reboot
cause property is set to unknown. Thankfully, chassis-state-manager
generates a file indicating an AC loss occurred and that can be used
to identify that the last reboot cause was a power-on-cycle. It was
necessary to add an "After xyz.openbmc_project.State.Chassis"
dependency to bmc-state-managers service file to ensure the AC loss
was generated prior to bmc-state-manager executing.

Tested:

- Ensured that when the system was power cycled that the last reboot
cause was set to "POR" when the chassis lost power file was present.

- Verified that when the file was not present the last reboot
cause was set accordingly (typically unknown)

Change-Id: Ifa6d5d6f89c221477ee2f2fa1ed15adade359e45
Signed-off-by: NodeMan97 <corey.hardesty@icloud.com>

show more ...

ensure proper phosphor-logging dependencies

As more errors are added to state-manager services, need to ensure they
are run after phosphor-logging is up and running. I saw an error path
recently on

ensure proper phosphor-logging dependencies

As more errors are added to state-manager services, need to ensure they
are run after phosphor-logging is up and running. I saw an error path
recently on a BMC reset with the host up scenario where
bmc-state-manager tried to log an error but phosphor-logging was not
running yet, resulting in an unhandled exception.

Tested:
- Verify all state services start after logging (bmc is earliest):
Mar 09 18:40:33 p10bmc systemd[1]: Starting Phosphor Log Manager...
Mar 09 18:40:34 p10bmc systemd[1]: Started Phosphor Log Manager.
Mar 09 18:40:34 p10bmc systemd[1]: Starting Phosphor BMC State Manager...
Mar 09 18:40:35 p10bmc systemd[1]: Started Phosphor BMC State Manager.

- Verify PEL data after all services running:
"User Data 0": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "0x2000",
"BMCState": "Ready",
"BootState": "Unspecified",
"ChassisState": "Off",
"FW Version ID": "fw1020.00-44.2-9-g1186c2a5f8",
"HostState": "Off",
"System IM": "50001001"
},

- Verify PEL data when BMC state service is stopped, and logging service
is restarted (to mimic error prior to state service running)
"User Data 0": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "0x2000",
"BMCState": "",
"BootState": "Unspecified",
"ChassisState": "Off",
"FW Version ID": "fw1020.00-44.2-9-g1186c2a5f8",
"HostState": "Off",
"System IM": "50001001"
},

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

show more ...

move state manager service files into its repo

OpenBMC is moving towards individual repos hosting and maintaining their
own service files. This allows the corresponding maintainer more c

move state manager service files into its repo

OpenBMC is moving towards individual repos hosting and maintaining their
own service files. This allows the corresponding maintainer more control
over their service file and removes the meta-* layer maintainer from
needing to be involved.

Once this is merged, its bump will need to be combined with a change in
the meta-phosphor layer that removes the service files.

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

show more ...