Was the task interrupted, or finished correctly? It seems, that only client's connection to hub was broken, which I would interpret as temporary network issue. But if task failed - there could be some real problem.

@tkopecek
Its task failed. connection is good.

When a cli command creates a task, the normal behavior is to "watch" the task. This is true for for a number of build commands as well as some others.

When the command shifts into watch mode, it no longer needs credentials since it is just polling for updates, so it logs out of its session and proceeds anonymously from there.

As a side effect of this, call retry behavior is different during the watch phase. The library does not retry anonymous rpc calls be default, unless the anon_retry option is set to True.

In this case, a network error occurred, something Koji has no control over. Because of the above factors, the call was not retried.

Also, it's helpful if you use more descriptive issue titles. Just "chain-build" tells the reader very little about the issue at hand.

Sure @mikem, I will be more descriptive when creating a issue

And what are the logs of failed task?

Here is the command output.

koji chain-build f29-build-3s9s ['git+ssh://root@localhost/mnt/brew/kojitest/git/kojitest-dummyrpm-6o8tx/#master'] : ['git+ssh://root@localhost/mnt/brew/kojitest/git/kojitest-dummyrpm-3as8f/#master'] : ['git+ssh://root@localhost/mnt/brew/kojitest/git/kojitest-dummyrpm-8x5jj/#master']
Created task: 9
Task info: https://10.8.245.18/koji/taskinfo?taskID=9
Watching tasks (this may be safely interrupted)...
9 chainbuild (f29-build-3s9s): free
9 chainbuild (f29-build-3s9s): free -> open (rmandadi-koji-biweekly-builder1-au6jnikhuuvh)
10 waitrepo (f29-build-3s9s, [git+ssh://root@localhost/mnt/brew/kojitest/git/kojitest-dummyrpm-6o8tx/#master]): open (rmandadi-koji-biweekly-builder1-au6jnikhuuvh)
2019-04-10 06:23:06,550 [ERROR] koji: ConnectionError: ('Connection aborted.', error("(104, 'ECONNRESET')",))

@rmandadi, that is the same console output you pasted above. Tomas is asking for the logs from the failed task.

Regardless, the "connection aborted" error is unrelated to whether the task failed or succeeded. That is due to a connection issue with the hub, which could be caused by many different factors.

more information required from @rmandadi

This issue is invalid because Ram created an issue for problem-related with the environment of Brew QE. I checked chain-build CLI method and it is working.
Therefore I closed an issue.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/koji/issues/1393

Please continue any further discussion there.