Description of problem: We cannot reuse an existing sandbox ID. [stack@director ~]$ sudo rhcert-ci run --key-file /home/stack/key.file --debug high Error: could not get vendor product info from the catalog: You have not use xmlrpc call to login user bkopilov Catalog: https://hardware.redhat.com/xmlrpc.cgi (Fault code: -32000) Continue? (yes|no) Version-Release number of selected component (if applicable): Steps to Reproduce: 1. Connect to the interface 2. Generate a sandbox_id 3. Redeploy the environment 4. Try to reuse the sandbox_id Actual results: - The rhcert-ci CLI tool freeze - We cannot do a non interactive run of rhcert-ci Additional info: I put the severity to urgent because this break the Distributed-CI integration.
Peng, could you take a look at this? Perhaps there is some permissions issue with the account?
Please try the new build at https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=534569 This should fix the issue with a new parameter added in test_config.json named undercloud_stackrc which can be configured before running rhcert-ci
Please Ignore the last comment as its related to some other bug
is this key.file generated by bz account or sso account ? CWE has stop the bz account support, and if this is generated by sso account, is it been added as vendor member of that vendor ?
Hi, I have a workaround for this case. you could regenerated a ci key. it should be work. Thanks, Kun Yan
I regenerated by sandbox_id 3 time in a row with my account (gleboude), but when I try to use it, I always get: "You have not use xmlrpc call to login user bkopilov"
Now I get this with my key: [stack@director ~]$ sudo rhcert-ci run --key-file /home/stack/key.file --debug high Error: could not get vendor product info from the catalog: malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "X[W\x{346}\x{1a9}\x{987b}...") at /usr/lib/perl5/vendor_perl/5.8.8/JSON.pm line 154. Catalog: https://hardware.redhat.com/xmlrpc.cgi (Fault code: -32000) Continue? (yes|no)
It works fine know with my key. I think I did some of my test yesterday with a malformed key file. Thanks for you help.
OK if I close this then?