Record the Fedora CoreOS update stream with the VM

[afbjorklund]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind feature

Description

Currently only the resulting image url is stored, not the original stream:

• default (nothing chosen, currently: testing)
• next
• testing
• stable
• custom (user has provided path or url)

https://docs.fedoraproject.org/en-US/fedora-coreos/update-streams/

Steps to reproduce the issue:

1. podman machine init

Describe the results you received:

 "ImagePath": "/home/anders/.local/share/containers/podman/machine/qemu/podman-machine-default_fedora-coreos-35.20211017.1.0-qemu.x86_64.qcow2",

Describe the results you expected:

 "ImageStream": "next",
 "ImagePath": "/home/anders/.local/share/containers/podman/machine/qemu/podman-machine-default_fedora-coreos-35.20211017.1.0-qemu.x86_64.qcow2",

Additional information you deem important (e.g. issue happens only occasionally):

Optionally this could be shown in podman machine list as well.

Output of podman version:

Version:      3.3.1
API Version:  3.3.1
Go Version:   go1.16.6
Built:        Thu Jan  1 01:00:00 1970
OS/Arch:      linux/amd64

Output of podman info --debug:

(paste your output here)

Package info (e.g. output of rpm -q podman or apt list podman):

(paste your output here)

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)

Yes

Additional environment details (AWS, VirtualBox, physical, etc.):

Ubuntu 20.04

[afbjorklund]

The main confusion with podman 3.3.1* is that when you choose "", it actually selects "next" (and not "testing").

• Issue Fix machine image #11701

So there it is not really possible to know the current stream, which means that "" is interpreted just as "default"

* it is the latest available for Ubuntu 20.04

[ashley-cui]

Sure, looks like a good idea!

[afbjorklund]

Advanced users can also change streams on their VM:

https://docs.fedoraproject.org/en-US/fedora-coreos/update-streams/

No idea why Podman doesn't use "stable"

Or why there is no CentOS Stream CoreOS

[rhatdan]

We don't use stable yet, because podman on a MAC is moving too quickly. Hopefully early next year when we have he missing features we will more to stable.

There is no general supported CoreOS for CentOS or RHEL.
RHCOS is for OpenShift and it is based on versions of OpenShift.

Podman does not want to be in the OS Business. So we are relying on other teams to support the OS part. In this case Fedora CoreOS.

[afbjorklund]

Thank you for the clarification, I guess this configuration is fixed (to Fedora CoreOS) and user just chooses the stream.

Not sure if general access to "-devel" streams is needed, or if the custom build url workaround will be enough for that ?