ci: disk in github action increased to 75G from 64G

[subhamkrai]

the disk size in the github action machine has
increased from 64G to 75G.

Checklist:

• Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
• Reviewed the developer guide on Submitting a Pull Request
• Pending release notes updated with breaking and/or notable changes for the next minor release.
• Documentation has been updated, if necessary.
• Unit tests have been added, if necessary.
• Integration tests have been added, if necessary.

[sp98]

@subhamkrai Can you check if this is something we can fix on the fly? So don't have to fix it again if the disk size increases in future.

[sp98]

@subhamkrai Can you check if this is something we can fix on the fly? So don't have to fix it again if the disk size increases in future.

Other option would have have this is a global variable. So future change in the disk size can go only in file only.

[subhamkrai]

@subhamkrai Can you check if this is something we can fix on the fly? So don't have to fix it again if the disk size increases in future.

Other option would have have this is a global variable. So future change in the disk size can go only in file only.

I agree we need do better work handling this, will work on this in separate PR later

[travisn]

As discussed we will get this merged to handle the new disk size, then follow up to investigate the remaining CI failures. At least this gives us green CI for some of the integration tests where a single OSD is used.

[subhamkrai]

sudo lsblk --paths --list | grep -P '\s+/mnt$' | grep -Po '^[/a-z]+'|

This not working once we do formatting or partition change for canary-tests

[subhamkrai]

I tried few things, but that didn't worked so I guess ready for review

[travisn]

I tried few things, but that didn't worked so I guess ready for review

Ok, we can follow up separately on how to avoid the size-based filter. Will merge once the CI is completed.

[BlaineEXE]

This is the second time GH has changed the disk size in 3ish months I think. We probably should figure out how to use a different filter for selecting the disk.

[travisn]

I tried few things, but that didn't worked so I guess ready for review

@subhamkrai Which tests do you expect to fail even after the size change? Just some canary tests? Looks like some upgrade and other integration tests are also failing, even though I thought I had seen them pass on a previous run.

[subhamkrai]

I tried few things, but that didn't worked so I guess ready for review

@subhamkrai Which tests do you expect to fail even after the size change? Just some canary tests?

Yes,

Looks like some upgrade and other integration tests are also failing, even though I thought I had seen them pass on a previous run.

@travisn seems like those tested are cancelled in the middle not failed.

[subhamkrai]

seems like the CI started with debug mode and then cancelled

[travisn]

seems like the CI started with debug mode and then cancelled

Going ahead with the merge, and will keep investigating the remaining issues with a separate PR...