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.

Sign up for GitHub

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

Jump to bottom

Follow-ups to osmet #224

Closed
2 of 4 tasks
jlebon opened this issue Apr 24, 2020 · 4 comments
Closed
2 of 4 tasks

Follow-ups to osmet #224

jlebon opened this issue Apr 24, 2020 · 4 comments

Comments

@jlebon
Copy link
Member

jlebon commented Apr 24, 2020 •
edited by bgilbert
Loading

Tracker issue to jot down follow-up patches for osmet before we forget about them.
@dustymabe
Copy link
Member

  • opportunistically use osmet even when --stream is provided if the artifact matches the osmet version.

my interpretation of this: "if $stream version on remote servers matches the embedded content version then opportunistically use the embedded content rather than pulling file from remote". Is that correct?

@jlebon
Copy link
Member Author

jlebon commented Apr 30, 2020

my interpretation of this: "if $stream version on remote servers matches the embedded content version then opportunistically use the embedded content rather than pulling file from remote". Is that correct?

Yup, exactly!

@jlebon jlebon mentioned this issue May 5, 2020
Closed
@cgwalters
Copy link
Member

support for RHCOS' cipher_null LUKS container.

I'm taking this.

This was referenced Oct 29, 2022
Open
Open
@bgilbert
Copy link
Contributor

Moved the remaining items to #1034 and #1035.

@bgilbert bgilbert closed this as not planned Won't fix, can't repro, duplicate, stale Oct 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@cgwalters @bgilbert @dustymabe @jlebon