Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix setup script #443

Merged
merged 1 commit into from
May 28, 2024
Merged

Fix setup script #443

merged 1 commit into from
May 28, 2024

Conversation

Yarboa
Copy link
Collaborator

@Yarboa Yarboa commented May 23, 2024

resolve #439

Setup script or qm rpm does not call qm-storage-settings,
qm-storage-settings set qm storage.conf

Some more bash shell check fixes added

@Yarboa
Copy link
Collaborator Author

Yarboa commented May 23, 2024

PLEASE do not merge,
need to VERIFY rpm manually export USE_QM_COPR=packit/containers-qm-443

@Yarboa Yarboa force-pushed the fix-storge-setup branch 2 times, most recently from 0eb28f3 to a21bee0 Compare May 26, 2024 09:04
@Yarboa Yarboa marked this pull request as ready for review May 26, 2024 09:33
@Yarboa
Copy link
Collaborator Author

Yarboa commented May 26, 2024

/packit test --identifier e2e-ffi

setup Outdated Show resolved Hide resolved
@@ -38,18 +37,18 @@ exec_command() {
fi

# print the output of QM ROOTFS
echo $($COMMAND)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe the idea here was just print, not execute. With the result of this echo the other function would do something.

Copy link
Collaborator Author

@Yarboa Yarboa May 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Look here
some how it returned as an input value and the output
19:28:08 out: Exiting... unable to find /usr/share/qm/qm-rootfs/etc/containers/storage.conf

At the end if no exec run the output is the /usr/share/qm/qm-rootfs
so there is a need to run it

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would just leave the bash header as it's and this one as well but I will check tomorrow. I might be little "snow" as it's holiday here but I will check.

@Yarboa Yarboa force-pushed the fix-storge-setup branch 3 times, most recently from 9c5401a to 316d8e2 Compare May 26, 2024 19:19
setup Outdated Show resolved Hide resolved
@Yarboa Yarboa force-pushed the fix-storge-setup branch 2 times, most recently from 71b3eb4 to 78462b0 Compare May 27, 2024 08:55
STORAGE_CONFIG="/run/osbuild/tree/${STORAGE_CONFIG}"
if [ ! -f "${STORAGE_CONFIG}" ]; then
echo "Exiting /etc/containers/storage.conf in the ROOTFS"
echo "Exiting /etc/containers/storage.confnot found under /run/osbuild/tree/"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing a space.

@dougsland
Copy link
Collaborator

just cosmetic comments but looks good, CI/CD seems to agree as well. :)

Also remove gh cli,
it's repo returns 443 lately

Signed-off-by: Yariv Rachmani <yrachman@redhat.com>
@Yarboa Yarboa merged commit ca075b9 into containers:main May 28, 2024
7 checks passed
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

when pull container image within qm, always got a "no space left on device" error
2 participants