-
Notifications
You must be signed in to change notification settings - Fork 15
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
[bug] http 500 on some pulls #61
Comments
This is expected, order of system extensions might matter as they are layered one on top of another, this is not a bug. |
The error might have been more helpful, but it looks like |
Correct, that's just the context, not the bug. |
There is nothing in the docs about something needed to be "registered" as a schematic. How it's writen in the readme, is that registration happens at pull (as they get build to order, as listed in the section about docker pulls), not on get-request. |
If the schematic is not registered, it's invalid: https://github.com/siderolabs/image-factory#post-schematics If the bug reproduces with registered schematics, please feel free to re-open. |
can this at least actually get documented? |
I don't know how it can be more clear? How that ID got acquired in the first place? |
That doesn't say anything about registration, just that it's returned by something. ill pr a change to make this more clear. |
This is the call which registers the schematic, if it's not registered, the ID is meaningless, as it's not clear where it came from. I'm probably missing something, but I don't see how it can be otherwise. You're like asking for schematic |
Talhelper generated it in this case, which is their mistake tbh, see above referenced issue. But the mistake is specifying this in the docker section: So, its not odd to read this and think "ohh if I call a certain id, it gets build automatically". I've already filed a PR to make the above post/get more clear |
I think you should redirect this to |
I get the feeling you're either very busy and not reading carefully...
As you would've seen above the issue was already forwarded to talhelper, even linked this issue.
It's clear what To be clear: I get if from your docs, now that you explain what you meant. It's no shame of writhing docs that can be read in multiple ways, happens to all of us. But you can at least take feedback about it not being clear to, at least, two other developers and not be defensive about it. Because it turns out to not-be as clear as you assumed it to be. See: |
Talos has extensive documentation for you to follow. I hope that helps to understand things. |
As I already wrote: Anyway, That article has some of the same problematic language, that caused confusion to me here:
On-demand allows people to assume the same about the schematic. Yes, it's refering to the boot-assets... But easy to misunderstand
Retrieve != create/register TLDR: |
I perfectly got your point, I'm leaving links to other people who might hit this issue so that the things are more clear. |
When the listed systemExtentions have a different order than the one from the GUI factory, they have a different hash.
However, when this is the case, they also often fail with HTTP error 500:
I've seen this happen multiple times, with multiple different selections of extentions
Note:
Previously filed as: siderolabs/talos#7986
The text was updated successfully, but these errors were encountered: