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

Make it harder to rpm-ostree upgrade when using an update driver #2536

Closed
jlebon opened this issue Feb 3, 2021 · 3 comments · Fixed by #2566
Closed

Make it harder to rpm-ostree upgrade when using an update driver #2536

jlebon opened this issue Feb 3, 2021 · 3 comments · Fixed by #2566
Assignees
Labels
jira for syncing to jira

Comments

@jlebon
Copy link
Member

jlebon commented Feb 3, 2021

Follow-up to #1747.

In FCOS, it's too easy for users to type rpm-ostree upgrade and blow past update barriers (see e.g. coreos/fedora-coreos-tracker#731 (comment)).

One path is to make FCOS use checksum origins like RHCOS, though that then drives knowledge about the OSTree refspec into Zincati.

Another approach which I think would work well with #1747 is to have rpm-ostree upgrade print out a message if an update driver is registered, and require some override switch. (Maybe even down the line have it call out to the update driver which could check for updates immediately?)

@jlebon
Copy link
Member Author

jlebon commented Feb 3, 2021

Something like:

$ rpm-ostree upgrade
This node is updated by $driver_pretty_name; see the documentation
for that software at $driver_systemd_unit_documentation. Use --force
to force upgrading anyway.

@cgwalters
Copy link
Member

100% on board with that!

@travier
Copy link
Member

travier commented Feb 10, 2021

Sounds great!

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

Successfully merging a pull request may close this issue.

4 participants