conan install fails even if there is a valid community package

Summary

conan install fails even if there is a valid community package.

Steps to reproduce

Execute the following commands:

conan remote add gitlab https://gitlab.com/api/v4/packages/conan --insert

conan user -p "CI_RW_PACKAGES_PASSWORD" -r gitlab "CI_RW_PACKAGES_USER". # substitute your login and password

conan remote add conan-community https://api.bintray.com/conan/conan-community/conan --insert

conan remote add bincrafters https://api.bintray.com/conan/bincrafters/public-conan --insert

conan remote add conan-center https://conan.bintray.com --insert

conan search "zlib*" -r all # result is several valid packages

conan install zlib/1.2.11@ --build "*"

Example Project

https://gitlab.com/reactivereality/core/core_builder_ubuntu_image/-/jobs/730733486

What is the current bug behavior?

conan install command fails

What is the expected correct behavior?

conan shall install a package

Relevant logs and/or screenshots

` $ conan install zlib/1.2.11@ --build "*"

Configuration:

[settings]

arch=x86_64

arch_build=x86_64

build_type=Release

compiler=gcc

compiler.cppstd=14

compiler.libcxx=libstdc++11

compiler.version=9

os=Linux

os_build=Linux

[options] *:shared=False [build_requires] [env]

zlib/1.2.11: Not found in local cache, looking in remotes...

zlib/1.2.11: Trying with 'bincrafters'...

zlib/1.2.11: Trying with 'conan-community'...

zlib/1.2.11: Trying with 'gitlab'...

ERROR: {"error":"package_username is invalid, package_channel is invalid"}. [Remote: gitlab] `

Edited by Andrei Malashkin