Bigger partiton table for SVM & ambigous redirect bugfix#2832
Conversation
|
@DennisKonrad why did you close this one? |
|
I am trying to squash another commit into this pull request because: Im tryning to wrap my head about git rebase and all the things to get this right. I will reopen this if everything is looking like I want it to be. |
|
Ok, I see how changes work now. I wasnt able to check if the 80MB for /boot are working right now. |
|
@DennisKonrad don't bother with master. we will merge it forward once merged in 4.11 |
|
yeah, my current build infrastructure is using the master of my fork for automatically building the So to not change my build infrastructure I wanted to pull the commit into my master to test if 80MB is working. I managed this now and the build is running at the moment. I dont now if your CI infrastructure is checking at all if the SVM build is working so I would like to make sure this works before this change gets commited |
|
80 MB is working. LGTM now |
yadvr
left a comment
yadvr
left a comment
There was a problem hiding this comment.
I'm okay with the redirection fix, for the size related changes I'm building a systemvmtemplate with existing size of 1.8G to see if we can reproduce the build error.
|
LGTM |
Habilitação de suporte a SNI para as _system_ VMs Closes apache#2832 See merge request scclouds/scclouds!1227
4 participants
Description
build.sh systemvmtemplate failed while pulling updates. Reason was ‘No Space Left on Device’ Error on the root partition.
So I went on and increased the partition size and it built succesfully.
Testing revealed, that the boot partition has to be bigger than 60MB to allow installing updates.
Also I had bash ambiguous redirect error in shar_cloud_scripts.sh wich I fixed by placing quotes
Types of changes
How Has This Been Tested?
Built successfully via:
bash build.sh systemvmtemplate
Checklist:
Testing