[libvirt_manager] Use /sysroot as path with xfs_growfs

[karelyatin]

With OCP 4.20 the task fails with:-
xfs_growfs: / is not a mounted XFS filesystem
As it's changed now:-
$ sudo df / --output=fstype
Type
overlay
$ sudo df /sysroot --output=fstype
Type
xfs

while with 4.18 it used to be:-
$ df /sysroot --output=fstype
Type
xfs
$ df / --output=fstype
Type
xfs

Changing the command to use /sysroot as path which works on both 4.20 and older OCP versions.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign rebtoor for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[amartyasinha]

LGTM!

should work with older OCP version deployments:

$ sudo df / --output=fstype
Type
xfs
$ sudo df /sysroot --output=fstype
Type
xfs

[karelyatin]

@abays mentioned in 4.20 this not working as read only
$ sudo xfs_growfs /sysroot
meta-data=/dev/sda4 isize=512 agcount=76, agsize=171712 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=0
= reflink=1 bigtime=1 inobtcount=1 nrext64=0
data = bsize=4096 blocks=12975867, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1
log =internal log bsize=4096 blocks=16384, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Read-only file system

[abays]

@karelyatin: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/images ee69e4a link true /test images

Full PR test history. Your PR dashboard.
Details

{  error occurred handling build ci-framework-image-amd64: the build ci-framework-image-amd64 failed after 2m20s with reason DockerBuildFailed: Dockerfile build strategy has failed.}

/test images

[abays]

@karelyatin: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/images ee69e4a link true /test images

Full PR test history. Your PR dashboard.
Details

ERROR! Failed to clone a Git repository from `https://github.com/ovirt/ovirt-ansible-collection`.
Starting galaxy collection install process
Process install dependency map
make: *** [Makefile:60: setup_molecule] Error 1
error: build error: building at STEP "RUN make setup_molecule USE_VENV=no": while running runtime: exit status 2}

/test images

[fultonj]

This /lgtm let's just get past the unrelated images check issue

[abays]

@karelyatin: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/images ee69e4a link true /test images

Full PR test history. Your PR dashboard.
Details

{  error occurred handling build ci-framework-image-amd64: the build ci-framework-image-amd64 failed after 2m20s with reason DockerBuildFailed: Dockerfile build strategy has failed.

ERROR! Failed to clone a Git repository from `https://github.com/ovirt/ovirt-ansible-collection`.
Starting galaxy collection install process
Process install dependency map
make: *** [Makefile:60: setup_molecule] Error 1
error: build error: building at STEP "RUN make setup_molecule USE_VENV=no": while running runtime: exit status 2}

Trying once again...

/test images

[abays]

/lgtm