MAXSAT problem with no solution found when generate rpmtree when `make rpm-deps` in kubevirt

[Longchuanzheng]

Hi, I want to change rpm deps in kubevirt with make rpm-deps. I change basesystem to --basesystem bclinux-release in hack/rpm-deps
like

    bazel run \
        --config=${ARCHITECTURE} \
        //:bazeldnf -- rpmtree \
        --public --nobest \
        --name testimage_x86_64 \
        --basesystem bclinux-release \
        ${bazeldnf_repos} \
        $centos_base \
        $centos_extra \
        $testimage_base

I solve bclinux-release not found by adding repositories in rpm/repo.yaml, while MAXSAT problem with no solution found.

INFO[0010] Selecting which: which-0:2.21-16.bclinux.21.10U4
INFO[0010] Selecting bclinux-release: bclinux-release-0:21.10U4-57.1.oe2203sp3.bclinux
INFO[0010] Solving.
INFO[0010] Loading the Partial weighted MAXSAT problem.
INFO[0014] Solving the Partial weighted MAXSAT problem.
INFO[0014] No solution found.
Error: no solution found
Usage:
  bazeldnf rpmtree [flags]

Flags:
...
...

no solution found
+ '[' true = true ']'

In my opinion, it may cause by --basesystem bclinux-release. But I don't have a specific understanding of this error.

I want know what is MAXSAT problem and why it happends and try to solve it.

By the way there is nothing between Loading the Partial weighted MAXSAT problem and Solving the Partial weighted MAXSAT problem. I think problems should show between these two lines.

[manuelnaranjo]

Can you provide a project we can reproduce your issue? And please don't share images, share text escaped with markdown

[Longchuanzheng]

Hi @manuelnaranjo, thanks for your attention. bclinux release has some private RPM repository. I can't provide one online, but it usually can run normally.While when I use --basesystem centos-stream-release I can't get no solution found and the command keep running. So I think it is --basesystem bclinux-release problem.
If I understand the potential mistake, I will use the clues to try to resolve the issue.

[manuelnaranjo]

Without knowing your configuration and what you're requesting it's impossible to help you, you can try running with BAZELDNF_LOG_LEVEL=debug to see if you can find what's going on. Most of the time what happens is that you're requesting something that depends on something that's not available through your repo.yaml

[Huang-zic]

@Longchuanzheng Hello, I also encountered the same problem when updating rpm deps in kubevirt,like

bazel run \ 
        --config=${ARCHITECTURE} \  
        //:bazeldnf -- rpmtree \  
        --public --nobest \  
        --name testimage_riscv64 --arch riscv64 \  
        --basesystem openEuler-release \  
        ${bazeldnf_repos} \  
        $openeuler_main \  
        $openeuler_extra \  
        $testimage_main_riscv64 

Then report an error

INFO[0004] Adding required packages to the resolver.
INFO[0004] Selecting curl: curl-0:8.4.0-3.oe2403
INFO[0004] Selecting openEuler-release: openEuler-release-0:24.03LTS-55.oe2403
INFO[0004] Solving.
INFO[0004] Loading the Partial weighted MAXSAT problem.
INFO[0004] Solving the Partial weighted MAXSAT problem.
INFO[0004] No solution found.
Error: no solution found

and my repo.yaml is

- arch: riscv64
  baseurl: https://mirrors.aliyun.com/openeuler/openEuler-24.03-LTS/everything/riscv64/
  name: openEuler/everything-riscv64
  gpgkey: https://mirrors.aliyun.com/openeuler/openEuler-24.03-LTS/everything/riscv64/RPM-GPG-KEY-openEuler`
- arch: riscv64
  baseurl: https://mirrors.aliyun.com/openeuler/openEuler-24.03-LTS/OS/riscv64
  name: openEuler/OS-riscv64
  gpgkey: https://mirrors.aliyun.com/openeuler/openEuler-24.03-LTS/OS/riscv64/RPM-GPG-KEY-openEuler
- arch: riscv64
  baseurl: https://mirrors.aliyun.com/openeuler/openEuler-24.03-LTS/EPOL/main/riscv64/
  name: openEuler/EPOL-riscv64
  gpgkey: https://mirrors.aliyun.com/openeuler/openEuler-24.03-LTS/EPOL/main/riscv64/RPM-GPG-KEY-openEuler

Have you solved the problem,thanks!

[manuelnaranjo]

@Huang-zic what's the value of your env variables? Which version of bazel and bazeldnf are you using?

[Longchuanzheng]

@Huang-zic HIi, Due to deadline, I was unable to replace the base image according to the kubevirt method. I just add qemu libvirt in virt-lanucher base image.

[Longchuanzheng]

In my opinion, this problem is nothing to do with bazeldnf. It's just that we don't fully understand bazeldnf and the make rpm-deps method of kubevirt. Maybe rpm management is too unfamiliar to me.

[Huang-zic]

@manuelnaranjo Thanks for your attention！
Due to the need for zstd support, the bazeldnf I use is not an existing distribution, but was built using the latest bazeldnf source code bazeldnf-20250329-linux-arm64.And version of bazel is 5.4.1.
If you'd like to reproduce my issue,you can do the following (only in arm64,since I only built the arm64 bazeldnf)

git clone https://gitee.com/huang_a/kubevirt-riscv.git
cd kubevirt-riscv
./apply_patches.sh
cd kubevirt 
sudo SINGLE_ARCH=riscv64 make rpm-deps

For more info,you can go to the docker container named kubevirt-bazel-server,after running sudo SINGLE_ARCH=riscv64 make rpm-deps.Then execute the bazel instruction directly,like
bazel run --config=aarch64 //:bazeldnf -- rpmtree --public --nobest --name testimage_riscv64 --arch riscv64 --basesystem openEuler-repos --repofile rpm/repo.yaml curl .
I don't think there's anything wrong with the bazeldnf I built,because the command like bazel run --config=aarch64 //:bazeldnf -- rpmtree --public --nobest --name testimage_aarch64 --arch aarch64 --basesystem centos-stream-release --repofile rpm/repo.yaml curl ... runs successfully.
Please let me know if there is any solution, thank you very much!

[WangJia-UR]

@manuelnaranjo Thanks for your attention！ Due to the need for zstd support, the bazeldnf I use is not an existing distribution, but was built using the latest bazeldnf source code bazeldnf-20250329-linux-arm64.And version of bazel is 5.4.1. If you'd like to reproduce my issue,you can do the following (only in arm64,since I only built the arm64 bazeldnf)

git clone https://gitee.com/huang_a/kubevirt-riscv.git
cd kubevirt-riscv
./apply_patches.sh
cd kubevirt 
sudo SINGLE_ARCH=riscv64 make rpm-deps

For more info,you can go to the docker container named kubevirt-bazel-server,after running sudo SINGLE_ARCH=riscv64 make rpm-deps.Then execute the bazel instruction directly,like bazel run --config=aarch64 //:bazeldnf -- rpmtree --public --nobest --name testimage_riscv64 --arch riscv64 --basesystem openEuler-repos --repofile rpm/repo.yaml curl . I don't think there's anything wrong with the bazeldnf I built,because the command like bazel run --config=aarch64 //:bazeldnf -- rpmtree --public --nobest --name testimage_aarch64 --arch aarch64 --basesystem centos-stream-release --repofile rpm/repo.yaml curl ... runs successfully. Please let me know if there is any solution, thank you very much!

I have the same problem too, the difference is that it still fails even when the --nobest option is added. my bazel version is 8.2.1.