| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…es, vmware hardware version updated to 13, fsck added in grub
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #9625 +/- ##
===========================================
Coverage 15.57% 15.57%
- Complexity 12047 12049 +2
===========================================
Files 5505 5505
Lines 482621 482621
Branches 61174 62592 +1418
===========================================
+ Hits 75176 75184 +8
+ Misses 399141 399133 -8
Partials 8304 8304
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry.
|
Sorry, something went wrong.
|
Packaging isn't required as changes are only in systemvmtemplate codebase. I've kicked Jenkins builds, which should be available shortly at https://build.yadav.cloud/systemvm/ |
Sorry, something went wrong.
|
build OK |
Sorry, something went wrong.
There was a problem hiding this comment.
tested the new systemvm template on ubuntu24 and vmware80u3 manually
#9470 shows that smoke tests worked with the new systemvm template
Sorry, something went wrong.
|
Merged based on 2lgtms and manual build/tests. |
Sorry, something went wrong.
…pache#9625) * systemvm template changes, to explicitly update the module dependencies, vmware hardware version updated to 13, fsck added in grub * Update systemvm template debian version to 12.7
| Back | FazBrowse Home | New Git URL |
Description
This PR updates SystemVM template debian version to 12.7.0 and other changes below.
VMware hardware version updated to 13 - compatible with latest VMware version supported (https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-vm-administration/GUID-64D4B1C9-CD5D-4C68-8B50-585F6A87EBA0.html)
Updated grub config with fsck.mode=force fsck.repair=yes - resolves the file system read-only issue observed in VRs.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?