Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ostree on live PXE systems #1921

Open
bgilbert opened this issue Sep 15, 2019 · 3 comments · May be fixed by #1995
Open

ostree on live PXE systems #1921

bgilbert opened this issue Sep 15, 2019 · 3 comments · May be fixed by #1995

Comments

@bgilbert
Copy link
Contributor

When Fedora CoreOS is booted as a live PXE system, ostree would ideally function in read-only mode, where it refuses to deploy updates (since that isn't a meaningful operation on a live system) but still provides read-only status info.

rpm-ostreed currently refuses to start on such systems because ostree is unhappy:

Error setting up sysroot: Unexpected state: /run/ostree-booted found and in / sysroot but not in a booted deployment

Live PXE systems don't need anything in /boot, since the kernel and initramfs are provided externally. Fedora CoreOS could generate a fake BLS entry if needed, though note that /proc/cmdline doesn't contain an ostree argument so we'd need to deal with that also (#1920).

What's the best way to proceed here?

@cgwalters
Copy link
Member

We could "standardize" /run/ostree-live here?

@cgwalters
Copy link
Member

#1995 is a WIP PR for this.

cgwalters added a commit to cgwalters/ostree that referenced this issue Mar 19, 2020
Support read-only queries, but deny any attempts to make
changes with a clear error.

Now...in the future, we probably do want to support making
"transient" overlays.  See:
coreos/fedora-coreos-tracker#354 (comment)

Closes: ostreedev#1921
cgwalters added a commit to cgwalters/ostree that referenced this issue Mar 21, 2020
Support read-only queries, but deny any attempts to make
changes with a clear error.

Now...in the future, we probably do want to support making
"transient" overlays.  See:
coreos/fedora-coreos-tracker#354 (comment)

Closes: ostreedev#1921
cgwalters added a commit to cgwalters/ostree that referenced this issue Mar 21, 2020
Support read-only queries, but deny any attempts to make
changes with a clear error.

Now...in the future, we probably do want to support making
"transient" overlays.  See:
coreos/fedora-coreos-tracker#354 (comment)

Closes: ostreedev#1921
cgwalters added a commit to cgwalters/ostree that referenced this issue Mar 23, 2020
Support read-only queries, but deny any attempts to make
changes with a clear error.

Now...in the future, we probably do want to support making
"transient" overlays.  See:
coreos/fedora-coreos-tracker#354 (comment)

Closes: ostreedev#1921
cgwalters added a commit to cgwalters/ostree that referenced this issue Mar 24, 2020
Support read-only queries, but deny any attempts to make
changes with a clear error.

Now...in the future, we probably do want to support making
"transient" overlays.  See:
coreos/fedora-coreos-tracker#354 (comment)

Closes: ostreedev#1921
@jlebon
Copy link
Member

jlebon commented May 26, 2020

This oddly works now in a locally built FCOS live ISO and PXE artifacts:

[root@localhost ~]# rpm-ostree status
State: idle
Deployments:
● ostree://fedora:fedora/x86_64/coreos/testing-devel
                   Version: 31.20200526.dev.0 (2020-05-26T19:18:19Z)
                    Commit: f1bbe310d7ec3ac03e1dba2c819f43daf3c7f6c88c000b20892d7d4a25881f2e
              GPGSignature: (unsigned)
[root@localhost ~]# cat /proc/cmdline
BOOT_IMAGE=fedora-coreos-31.20200526.dev.0-live-kernel-x86_64 ip=dhcp rd.neednet=1 initrd=fedora-coreos-31.20200526.dev.0-live-initramfs.x86_64.img console=tty0 console=ttyS0 ignition.config.url=http://192.168.122.1:8000/config-fcos.ign ignition.firstboot ignition.platform.id=metal BOOTIF=01-52-54-00-44-96-c9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants