meta-phosphor: systemd: always run systemd-sysusers
systemd-sysusers.service is gated on ConditionNeedsUpdate=/etc, which
only fires while /etc is older than /usr. A reproducible build pins the
mtime of /usr, and /etc/.updated is written on the first boot into the
persistent /etc, so from that boot onwards the condition can never be
satisfied and the unit is skipped for good. Every sysusers.d fragment
on the image is then inert, no matter which package shipped it.
Clear both trigger conditions. They are OR-ed, so leaving
ConditionCredential in place would keep the unit gated on a credential
that is never present. systemd-sysusers is idempotent; on a bletchley15
BMC it takes ~240 ms when it creates accounts and ~123 ms when it has
no work.
This on its own does not fix the case that found it. usbmuxd's udev
rule needs a usbmux account that no recipe creates, and the recipe
change that defines it belongs in meta-openembedded, where it is now
upstream as 5b4d5deac5bb ("usbmuxd: create the usbmux user the udev
rule requires"); it is being brought in here as change 93705. This
change only makes sure that once such a fragment exists, it is acted
on.
Tested: bletchley15. Before, systemd-sysusers.service was skipped on
every boot after the first, with systemctl reporting the condition
unmet. After, it runs on each boot at the times above and accounts
declared in sysusers.d are present once systemd-udevd parses its rules.
The end-to-end usbmuxd result was observed with the meta-openembedded
recipe change also applied, and is not claimed for this commit alone.
Change-Id: I38cbec7a7ebbefb48603cf81320032249655d40a
Signed-off-by: Eric Chiang Quanta <Eric.Chiang@quantatw.com>
OpenBMC is a Linux distribution for management controllers used in devices such as servers, top of rack switches or RAID appliances. It uses Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your platform.
See the Yocto documentation for the latest requirements
sudo apt install git gcc g++ make file wget \ gawk diffstat bzip2 cpio chrpath zstd lz4 bzip2
sudo dnf install git python3 gcc g++ gawk which bzip2 chrpath cpio \ hostname file diffutils diffstat lz4 wget zstd rpcgen patch
git clone https://github.com/openbmc/openbmc cd openbmc
Any build requires an environment set up according to your hardware target. There is a special script in the root of this repository that can be used to configure the environment as needed. The script is called setup and takes the name of your hardware target as an argument.
The script needs to be sourced while in the top directory of the OpenBMC repository clone, and, if run without arguments, will display the list of supported hardware targets, see the following example:
$ . setup <machine> [build_dir] Target machine must be specified. Use one of: ...
A more complete list of supported machines can be found under meta-phosphor/docs.
Once you know the target (e.g. romulus), source the setup script as follows:
. setup romulus
bitbake obmc-phosphor-image
Additional details can be found in the docs repository.
The OpenBMC community maintains a set of tutorials new users can go through to get up to speed on OpenBMC development out here
Commits submitted by members of the OpenBMC GitHub community are compiled and tested via our Jenkins server. Commits are run through two levels of testing. At the repository level the makefile make check directive is run. At the system level, the commit is built into a firmware image and run with an arm-softmmu QEMU model against a barrage of CI tests.
Commits submitted by non-members do not automatically proceed through CI testing. After visual inspection of the commit, a CI run can be manually performed by the reviewer.
Automated testing against the QEMU model along with supported systems are performed. The OpenBMC project uses the Robot Framework for all automation. Our complete test repository can be found here.
Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.
Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.
First, please do a search on the internet. There's a good chance your question has already been asked.
For general questions, please use the openbmc tag on Stack Overflow. Please review the discussion on Stack Overflow licensing before posting any code.
For technical discussions, please see contact info below for Discord and mailing list information. Please don‘t file an issue to ask a question. You’ll get faster results by using the mailing list or Discord.
This is a common question, particularly regarding boards from popular COTS (commercial off-the-shelf) vendors such as Supermicro and ASRock. You can see the list of supported boards by running . setup (with no further arguments) in the root of the OpenBMC source tree. Most of the platforms supported by OpenBMC are specialized servers operated by companies running large datacenters, but some more generic COTS servers are supported to varying degrees.
If your motherboard is not listed in the output of . setup it is not currently supported. Porting OpenBMC to a new platform is a non-trivial undertaking, ideally done with the assistance of schematics and other documentation from the manufacturer (it is not completely infeasible to take on a porting effort without documentation via reverse engineering, but it is considerably more difficult, and probably involves a greater risk of hardware damage).
However, even if your motherboard is among those listed in the output of . setup, there are two significant caveats to bear in mind. First, not all ports are equally mature -- some platforms are better supported than others, and functionality on some “supported” boards may be fairly limited. Second, support for a motherboard is not the same as support for a complete system -- in particular, fan control is critically dependent on not just the motherboard but also the fans connected to it and the chassis that the board and fans are housed in, both of which can vary dramatically between systems using the same board model. So while you may be able to compile and install an OpenBMC build on your system and get some basic functionality, rough edges (such as your cooling fans running continuously at full throttle) are likely.
See also “Supported Machines”.
Dive deeper into OpenBMC by opening the docs repository.
The Technical Oversight Forum (TOF) guides the technical direction of the project. Members are voted on by community members based on the membership and voting guidelines.