Error in Deployment
-
Here's the schema for the boot profile, which is also the profile I selected when I uploaded the updated image:
EDIT: Just saw your response. I do have it set to standard, but I'm not forcing default legacy or efi partitions. Should I be?
-
Also, when I go into the profle, it looks like this:
Initially, the schema table is invisible. If I change the Create Partitions Method to something else and back to Standard, the Schema table shows up.
-
Modify schema should be checked. When you uploaded, did you upload over an existing image or create a new one?
-
@theopenem_admin Over an existing, since I have 8 profiles made for it.
-
@jason-cline Actually, if I pick Standard for Create Partition Method, I can't move the Modify the Image Schema toggle. If I set it to custom, or original, I can.
EDIT: Correction, I couldn't after making a few changes, but I exited out and went back in and was able to. Interestingly, my other profiles are set that way. It's like uploading the image to that profile overwrote the modified schema.
-
I'll try that again in a bit and see if that happens. Changing the profile back fixed it, obvoiusly. But I wonder if it changing the profile on an updated upload is an unintended behaviour.
Thanks for the quick responses!
-
Yea, the problem is that the schema changes, but the custom schema is saved based on the original schema, which causes the issue. I haven't figured out a good way to fix this yet.
-
@theopenem_admin Well, as long as we're aware of it, we can certainly be prepared for it. It's not like it's a hard thing to fix manually.
-
I mean, the quickest way, if I'm following correctly, would be to make a profile JUST for image uploads, and then use the ones that are still properly configured for deployment.
-
You should probably always upload to the default profile, but I still think it messes with the deployment for the other profiles, because there is always only 1 schema for the image regardless of the profiles.