jlebon

What "Assisted-by" means

You may have ended up here by following a link from one of my PRs marked with an Assisted-by trailer. There is a large variance currently in (1) what patch authors may mean when they say "Assisted-by", and (2) what patch reviewers may interpret when they see "Assisted-by". This document describes what "Assisted-by" means for my commits to reduce guesswork and have a productive collaboration. (Unless I've explicitly stated in the commit or PR body that it should be interpreted differently.)

TL;DR

• I used an AI coding agent to help me write some (or rarely, all) of the patch.
• I take full responsibility for the changes in the patch.
• I self-reviewed every line in the patch and understand its logic.
• I made a best effort to verify its fit within the larger design of the project.

jlebon

```
$ podman run --rm -ti docker://$(oc adm release info --image-for=rhel-coreos quay.io/openshift-release-dev/ocp-release:4.19.8-x86_64) cat /etc/passwd
root:x:0:0:Super User:/root:/bin/bash
containers:x:993:995:User for rootless containers:/nonexistent:/sbin/nologin
```

jlebon

( O)> using the docs in this repo, what is the machine config operator?
I'll start by searching the documentation for "Machine Config Operator" to understand what it is.
─── shell | developer ──────────────────────────
command: rg "Machine Config Operator" -l



Okay, many files. I'll check `modules/understanding-machine-config-operator.adoc` and `modules/machine-config-operator.adoc` first, starting with the former.
─── text_editor | developer ──────────────────────────

jlebon

1. Download RHCOS 4.1 from the RHCOS release browser (qemu qcow2) or the mirror (metal BIOS or UEFI image).
2. Write a spec v2 Ignition config that sets the password for core to e.g. changeme:

{
  "ignition": {
    "config": {},
    "security": {
      "tls": {}
    },
    "timeouts": {},

jlebon

NAME="Red Hat Enterprise Linux CoreOS"
VERSION="9.4.202409221629-0 (Plow)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="9.4"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Red Hat Enterprise Linux CoreOS 9.4.202409221629-0 (Plow)"
ANSI_COLOR="0;31"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:redhat:enterprise_linux:9::baseos"

jlebon

Start the container using at least these switches:

      (host) podman run -ti \
               --privileged \
               --pid=host \
               -v /:/host \
               --name gdb \
               --detach-keys=ctrl-t \
                 registry.fedoraproject.org/fedora:32 /bin/bash

jlebon

{
    "ref": "fedora/x86_64/coreos/testing",
    "ostree-n-metadata-total": 8363,
    "ostree-n-metadata-written": 2800,
    "ostree-n-content-total": 4836,
    "ostree-n-content-written": 241,
    "ostree-n-cache-hits": 15054,
    "ostree-content-bytes-written": 120538393,
    "ostree-commit": "f482e2f1870124abf1f0094b7fcc66f86db8394a4096e1e66984b80178e84b34",
    "ostree-content-checksum": "ca63ec06f384ec21076be1f0f14c6c80fdaaf7edd1d862733942cd46c2541a88",

jlebon

{
  "ignition": {
    "version": "2.2.0"
  },
  "storage": {
    "files": [
      {
        "filesystem": "root",
        "path": "/etc/udev/rules.d/39-redhat.rules",
        "mode": 420,

jlebon

{
    "ignition": {
        "config": {},
        "security": {
            "tls": {}
        },
        "timeouts": {},
        "version": "3.0.0"
    },
    "passwd": {

jlebon

Switch to a dev branch and enable initrd regeneration:

ostree commit -b dev --fsync=no --tree=ref=$booted_commit
rpm-ostree rebase :dev
rpm-ostree initramfs --enable
reboot

Updating files: