fm-orchestrator

#863 mbs-build local: Failed to find module in PDC
Closed: Invalid Opened by jaruga.

Closed: Invalid
Reopen Issue

I built for modules/ruby by mbs-build local.
And it was stopped.
Below DEBUG log looks the reason. But the reason is not clear for me.
No log category "ERROR" message in the output.

What is the reason? How to fix it?
and I wish the ERROR message is showed in this case.

2018-02-15 12:02:50,667 - PoolThread-twisted.internet.reactor-0 - module_build_service.scheduler - DEBUG - stop_condition checking <ModuleBuild ruby, id=1, stream=master, version=20180215110243, state 'failed', batch 0, state_reason u"Failed to find module in PDC {'active': True, 'variant_version': 'master', 'variant_id': 'platform'}">, got True

For detail.

$ rpm -qf /usr/bin/mbs-build
module-build-service-1.7.0-1.fc27.noarch
$ git remote -v
...
origin  ssh://pkgs.fedoraproject.org/modules/ruby.git (fetch)
origin  ssh://pkgs.fedoraproject.org/modules/ruby.git (push)
$ mbs-build local
mbs-build is deprecated in favor of fedpkg and rhpkg. Please transition to using those.
2018-02-15 12:02:43,414 - MainThread - module_build_service - DEBUG - Creating new module build
2018-02-15 12:02:43,455 - MainThread - module_build_service - WARNING - Hub not initialized.  Queueing on the side.
2018-02-15 12:02:43,455 - MainThread - module_build_service - INFO - jaruga submitted build of ruby, stream=master, version=20180215110243
2018-02-15 12:02:43,458 - MainThread - moksha.hub - INFO - Loading the Moksha Hub
2018-02-15 12:02:43,458 - MainThread - moksha.hub - WARNING - No 'zmq_publish_endpoints' set.  Are you sure?
2018-02-15 12:02:44,460 - MainThread - moksha.hub - INFO - Loading Consumers
2018-02-15 12:02:44,461 - MainThread - moksha.hub - DEBUG - Loading explicitly passed entry-points.
2018-02-15 12:02:44,461 - MainThread - module_build_service - DEBUG - Setting topics: *
2018-02-15 12:02:44,462 - MainThread - fedmsg.consumers - DEBUG - mbsconsumer is True
2018-02-15 12:02:44,462 - MainThread - fedmsg.consumers - INFO -   enabled by config  - module_build_service.scheduler.consumer:MBSConsumer
2018-02-15 12:02:44,463 - MainThread - moksha.hub - DEBUG - Subscribing to consumer topic *
2018-02-15 12:02:44,463 - MainThread - moksha.hub - DEBUG - Subscribing to  on 'ZmqEndpoint(type='connect', address='ipc:///dev/null')'
2018-02-15 12:02:44,464 - MainThread - moksha.hub - DEBUG - Creating new txzmq factory.
2018-02-15 12:02:44,465 - MainThread - moksha.hub - INFO - Blocking mode false for <module_build_service.scheduler.consumer.MBSConsumer object at 0x7f3078b05350>.  Messages to be queued and distributed to 1 threads.
2018-02-15 12:02:44,471 - MainThread - fedmsg.consumers - INFO - No backlog handling.  status: None, url: None
2018-02-15 12:02:44,471 - MainThread - moksha.hub - INFO - Loading Producers
2018-02-15 12:02:44,472 - MainThread - moksha.hub - DEBUG - Loading explicitly passed entry-points.
2018-02-15 12:02:44,472 - MainThread - moksha.hub - INFO - Running the MokshaHub reactor
2018-02-15 12:02:44,472 - MainThread - moksha.hub - INFO - Suggesting threadpool size at 2
2018-02-15 12:02:44,473 - PoolThread-twisted.internet.reactor-0 - moksha.hub - DEBUG - 'MBSConsumer' thread 139846125827840 | Worker thread picking a message.
2018-02-15 12:02:44,474 - PoolThread-twisted.internet.reactor-0 - module_build_service - DEBUG - Received MBSModule('1', 1, 0)
2018-02-15 12:02:44,475 - PoolThread-twisted.internet.reactor-0 - module_build_service - DEBUG - Received a message with an ID of "1" and of type "MBSModule"
2018-02-15 12:02:44,480 - PoolThread-twisted.internet.reactor-0 - module_build_service - INFO - Calling init: MBSModule, 1
2018-02-15 12:02:47,503 - PoolThread-twisted.internet.reactor-0 - root - DEBUG - get_module({'active': True, 'version': 'master', 'name': 'platform'}, strict=False)
2018-02-15 12:02:47,506 - PoolThread-twisted.internet.reactor-0 - urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): pdc.fedoraproject.org
2018-02-15 12:02:50,291 - PoolThread-twisted.internet.reactor-0 - urllib3.connectionpool - DEBUG - https://pdc.fedoraproject.org:443 "GET /rest_api/v1/unreleasedvariants/?active=True&variant_version=master&page_size=1&variant_id=platform HTTP/1.1" 200 63
2018-02-15 12:02:50,296 - PoolThread-twisted.internet.reactor-0 - root - DEBUG - get_module({'active': True, 'version': 'master', 'name': 'platform'}, strict=True)
2018-02-15 12:02:50,609 - PoolThread-twisted.internet.reactor-0 - urllib3.connectionpool - DEBUG - https://pdc.fedoraproject.org:443 "GET /rest_api/v1/unreleasedvariants/?active=True&variant_version=master&page_size=1&variant_id=platform HTTP/1.1" 200 63
2018-02-15 12:02:50,618 - PoolThread-twisted.internet.reactor-0 - module_build_service - INFO - <ModuleBuild ruby, id=1, stream=master, version=20180215110243, state 'failed', batch 0, state_reason "Failed to find module in PDC {'active': True, 'variant_version': 'master', 'variant_id': 'platform'}">, state 0->4
2018-02-15 12:02:50,649 - PoolThread-twisted.internet.reactor-0 - module_build_service - DEBUG - Done with init: MBSModule, 1
2018-02-15 12:02:50,652 - PoolThread-twisted.internet.reactor-0 - module_build_service.scheduler - DEBUG - stop_condition checking <ModuleBuild ruby, id=1, stream=master, version=20180215110243, state 'failed', batch 0, state_reason u"Failed to find module in PDC {'active': True, 'variant_version': 'master', 'variant_id': 'platform'}">, got True
2018-02-15 12:02:50,652 - PoolThread-twisted.internet.reactor-0 - module_build_service - INFO - Scheduling shutdown.
2018-02-15 12:02:50,652 - PoolThread-twisted.internet.reactor-0 - moksha.hub - DEBUG - 'MBSConsumer' thread 139846125827840 | Going back to waiting on the incoming queue.
2018-02-15 12:02:50,652 - PoolThread-twisted.internet.reactor-0 - moksha.hub - DEBUG - 'MBSConsumer' thread 139846125827840 | Worker thread picking a message.
2018-02-15 12:02:50,652 - MainThread - moksha.hub - DEBUG - Stopping the CentralMokshaHub
2018-02-15 12:02:50,653 - PoolThread-twisted.internet.reactor-0 - module_build_service - DEBUG - Received MBSModule('2', 1, 4)
2018-02-15 12:02:50,654 - PoolThread-twisted.internet.reactor-0 - module_build_service - DEBUG - Received a message with an ID of "2" and of type "MBSModule"
2018-02-15 12:02:50,655 - MainThread - moksha.hub - DEBUG - Stopping consumer <module_build_service.scheduler.consumer.MBSConsumer object at 0x7f3078b05350>
2018-02-15 12:02:50,656 - MainThread - moksha.hub - DEBUG - Stopping the CentralMokshaHub
2018-02-15 12:02:50,658 - PoolThread-twisted.internet.reactor-0 - module_build_service - INFO - Calling failed: MBSModule, 2
2018-02-15 12:02:50,664 - PoolThread-twisted.internet.reactor-0 - module_build_service - DEBUG - Done with failed: MBSModule, 2
2018-02-15 12:02:50,667 - PoolThread-twisted.internet.reactor-0 - module_build_service.scheduler - DEBUG - stop_condition checking <ModuleBuild ruby, id=1, stream=master, version=20180215110243, state 'failed', batch 0, state_reason u"Failed to find module in PDC {'active': True, 'variant_version': 'master', 'variant_id': 'platform'}">, got True
2018-02-15 12:02:50,667 - PoolThread-twisted.internet.reactor-0 - module_build_service - INFO - Scheduling shutdown.
2018-02-15 12:02:50,667 - PoolThread-twisted.internet.reactor-0 - moksha.hub - DEBUG - 'MBSConsumer' thread 139846125827840 | Going back to waiting on the incoming queue.
2018-02-15 12:02:50,667 - PoolThread-twisted.internet.reactor-0 - moksha.hub - DEBUG - 'MBSConsumer' thread 139846125827840 | Worker thread exiting.
2018-02-15 12:02:50,668 - MainThread - moksha.hub - INFO - MokshaHub reactor stopped

Ah, the old platform-master was disabled to reset development for F28.

You can find the active platform modules here: https://pdc.fedoraproject.org/rest_api/v1/modules/?name=platform&active=true

You probably want this:

diff --git a/ruby.yaml b/ruby.yaml
index 6635daa..2603677 100644
--- a/ruby.yaml
+++ b/ruby.yaml
@@ -20,10 +20,10 @@ data:
     tracker: https://bugs.ruby-lang.org/
     dependencies:
     buildrequires:
-            platform: master
+            platform: f28
         autotools: master
     requires:
-            platform: master
+            platform: f28
     components:
     # SRPMs
     rpms:
Edited by ralph

Metadata Update from @ralph:
- Issue status updated to: Closed (was: Open)

Thanks for the answer.
I patched your modification. and commited to my development branch branched out from master branch. But still something wrong.

$ git branch | grep ^\*
* feature/update-master-with-latest-specification
$ git show
commit b234e3e73b6f762f55ad2a202e803acf5dc01b72 (HEAD -> feature/update-master-with-latest-specification)
Author: Jun Aruga <jaruga@redhat.com>
Date:   Thu Feb 15 13:53:38 2018 +0100
    Update master branch with latest specification.
diff --git a/ruby.yaml b/ruby.yaml
index 6635daa..2603677 100644
--- a/ruby.yaml
+++ b/ruby.yaml
@@ -20,10 +20,10 @@ data:
         tracker: https://bugs.ruby-lang.org/
     dependencies:
         buildrequires:
-            platform: master
+            platform: f28
             autotools: master
         requires:
-            platform: master
+            platform: f28
     components:
         # SRPMs
         rpms:
$ mbs-build local
mbs-build is deprecated in favor of fedpkg and rhpkg. Please transition to using those.
2018-02-15 13:54:07,370 - MainThread - module_build_service - DEBUG - Creating new module build
2018-02-15 13:54:07,412 - MainThread - module_build_service - WARNING - Hub not initialized.  Queueing on the side.
2018-02-15 13:54:07,412 - MainThread - module_build_service - INFO - jaruga submitted build of ruby, stream=feature/update-master-with-latest-specification, version=20180215125407
2018-02-15 13:54:07,414 - MainThread - moksha.hub - INFO - Loading the Moksha Hub
2018-02-15 13:54:07,414 - MainThread - moksha.hub - WARNING - No 'zmq_publish_endpoints' set.  Are you sure?
2018-02-15 13:54:08,416 - MainThread - moksha.hub - INFO - Loading Consumers
2018-02-15 13:54:08,416 - MainThread - moksha.hub - DEBUG - Loading explicitly passed entry-points.
2018-02-15 13:54:08,417 - MainThread - module_build_service - DEBUG - Setting topics: *
2018-02-15 13:54:08,418 - MainThread - fedmsg.consumers - DEBUG - mbsconsumer is True
2018-02-15 13:54:08,418 - MainThread - fedmsg.consumers - INFO -   enabled by config  - module_build_service.scheduler.consumer:MBSConsumer
2018-02-15 13:54:08,418 - MainThread - moksha.hub - DEBUG - Subscribing to consumer topic *
2018-02-15 13:54:08,419 - MainThread - moksha.hub - DEBUG - Subscribing to  on 'ZmqEndpoint(type='connect', address='ipc:///dev/null')'
2018-02-15 13:54:08,419 - MainThread - moksha.hub - DEBUG - Creating new txzmq factory.
2018-02-15 13:54:08,421 - MainThread - moksha.hub - INFO - Blocking mode false for <module_build_service.scheduler.consumer.MBSConsumer object at 0x7fa2f12ba350>.  Messages to be queued and distributed to 1 threads.
2018-02-15 13:54:08,428 - MainThread - fedmsg.consumers - INFO - No backlog handling.  status: None, url: None
2018-02-15 13:54:08,428 - MainThread - moksha.hub - INFO - Loading Producers
2018-02-15 13:54:08,428 - MainThread - moksha.hub - DEBUG - Loading explicitly passed entry-points.
2018-02-15 13:54:08,428 - MainThread - moksha.hub - INFO - Running the MokshaHub reactor
2018-02-15 13:54:08,429 - MainThread - moksha.hub - INFO - Suggesting threadpool size at 2
2018-02-15 13:54:08,429 - PoolThread-twisted.internet.reactor-0 - moksha.hub - DEBUG - 'MBSConsumer' thread 140337773446912 | Worker thread picking a message.
2018-02-15 13:54:08,431 - PoolThread-twisted.internet.reactor-0 - module_build_service - DEBUG - Received MBSModule('1', 1, 0)
2018-02-15 13:54:08,432 - PoolThread-twisted.internet.reactor-0 - module_build_service - DEBUG - Received a message with an ID of "1" and of type "MBSModule"
2018-02-15 13:54:08,437 - PoolThread-twisted.internet.reactor-0 - module_build_service - INFO - Calling init: MBSModule, 1
2018-02-15 13:54:11,459 - PoolThread-twisted.internet.reactor-0 - root - DEBUG - get_module({'active': True, 'version': 'f28', 'name': 'platform'}, strict=False)
2018-02-15 13:54:11,462 - PoolThread-twisted.internet.reactor-0 - urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): pdc.fedoraproject.org
2018-02-15 13:54:12,659 - PoolThread-twisted.internet.reactor-0 - urllib3.connectionpool - DEBUG - https://pdc.fedoraproject.org:443 "GET /rest_api/v1/unreleasedvariants/?active=True&variant_version=f28&page_size=1&variant_id=platform HTTP/1.1" 200 537
2018-02-15 13:54:13,078 - PoolThread-twisted.internet.reactor-0 - urllib3.connectionpool - DEBUG - https://pdc.fedoraproject.org:443 "GET /rest_api/v1/unreleasedvariants/?active=True&page=3&variant_version=f28&page_size=1&variant_id=platform HTTP/1.1" 200 554
2018-02-15 13:54:13,079 - PoolThread-twisted.internet.reactor-0 - root - DEBUG - get_module({'active': True, 'version': 'f28', 'name': 'platform'}, strict=True)
2018-02-15 13:54:13,374 - PoolThread-twisted.internet.reactor-0 - urllib3.connectionpool - DEBUG - https://pdc.fedoraproject.org:443 "GET /rest_api/v1/unreleasedvariants/?active=True&variant_version=f28&page_size=1&variant_id=platform HTTP/1.1" 200 537
2018-02-15 13:54:13,660 - PoolThread-twisted.internet.reactor-0 - urllib3.connectionpool - DEBUG - https://pdc.fedoraproject.org:443 "GET /rest_api/v1/unreleasedvariants/?active=True&page=3&variant_version=f28&page_size=1&variant_id=platform HTTP/1.1" 200 554
2018-02-15 13:54:13,674 - PoolThread-twisted.internet.reactor-0 - root - DEBUG - get_module({'active': True, 'version': 'master', 'name': 'autotools'}, strict=False)
2018-02-15 13:54:13,942 - PoolThread-twisted.internet.reactor-0 - urllib3.connectionpool - DEBUG - https://pdc.fedoraproject.org:443 "GET /rest_api/v1/unreleasedvariants/?active=True&variant_version=master&page_size=1&variant_id=autotools HTTP/1.1" 200 63
2018-02-15 13:54:13,944 - PoolThread-twisted.internet.reactor-0 - root - DEBUG - get_module({'active': True, 'version': 'master', 'name': 'autotools'}, strict=True)
2018-02-15 13:54:14,227 - PoolThread-twisted.internet.reactor-0 - urllib3.connectionpool - DEBUG - https://pdc.fedoraproject.org:443 "GET /rest_api/v1/unreleasedvariants/?active=True&variant_version=master&page_size=1&variant_id=autotools HTTP/1.1" 200 63
2018-02-15 13:54:14,240 - PoolThread-twisted.internet.reactor-0 - module_build_service - INFO - <ModuleBuild ruby, id=1, stream=feature/update-master-with-latest-specification, version=20180215125407, state 'failed', batch 0, state_reason "Failed to find module in PDC {'active': True, 'variant_version': 'master', 'variant_id': 'autotools'}">, state 0->4
2018-02-15 13:54:14,270 - PoolThread-twisted.internet.reactor-0 - module_build_service - DEBUG - Done with init: MBSModule, 1
2018-02-15 13:54:14,274 - PoolThread-twisted.internet.reactor-0 - module_build_service.scheduler - DEBUG - stop_condition checking <ModuleBuild ruby, id=1, stream=feature/update-master-with-latest-specification, version=20180215125407, state 'failed', batch 0, state_reason u"Failed to find module in PDC {'active': True, 'variant_version': 'master', 'variant_id': 'autotools'}">, got True
2018-02-15 13:54:14,274 - PoolThread-twisted.internet.reactor-0 - module_build_service - INFO - Scheduling shutdown.
2018-02-15 13:54:14,274 - PoolThread-twisted.internet.reactor-0 - moksha.hub - DEBUG - 'MBSConsumer' thread 140337773446912 | Going back to waiting on the incoming queue.
2018-02-15 13:54:14,275 - MainThread - moksha.hub - DEBUG - Stopping the CentralMokshaHub
2018-02-15 13:54:14,275 - PoolThread-twisted.internet.reactor-0 - moksha.hub - DEBUG - 'MBSConsumer' thread 140337773446912 | Worker thread picking a message.
2018-02-15 13:54:14,276 - PoolThread-twisted.internet.reactor-0 - module_build_service - DEBUG - Received MBSModule('2', 1, 4)
2018-02-15 13:54:14,276 - MainThread - moksha.hub - DEBUG - Stopping consumer <module_build_service.scheduler.consumer.MBSConsumer object at 0x7fa2f12ba350>
2018-02-15 13:54:14,277 - PoolThread-twisted.internet.reactor-0 - module_build_service - DEBUG - Received a message with an ID of "2" and of type "MBSModule"
2018-02-15 13:54:14,278 - MainThread - moksha.hub - DEBUG - Stopping the CentralMokshaHub
2018-02-15 13:54:14,281 - PoolThread-twisted.internet.reactor-0 - module_build_service - INFO - Calling failed: MBSModule, 2
2018-02-15 13:54:14,287 - PoolThread-twisted.internet.reactor-0 - module_build_service - DEBUG - Done with failed: MBSModule, 2
2018-02-15 13:54:14,290 - PoolThread-twisted.internet.reactor-0 - module_build_service.scheduler - DEBUG - stop_condition checking <ModuleBuild ruby, id=1, stream=feature/update-master-with-latest-specification, version=20180215125407, state 'failed', batch 0, state_reason u"Failed to find module in PDC {'active': True, 'variant_version': 'master', 'variant_id': 'autotools'}">, got True
2018-02-15 13:54:14,290 - PoolThread-twisted.internet.reactor-0 - module_build_service - INFO - Scheduling shutdown.
2018-02-15 13:54:14,290 - PoolThread-twisted.internet.reactor-0 - moksha.hub - DEBUG - 'MBSConsumer' thread 140337773446912 | Going back to waiting on the incoming queue.
2018-02-15 13:54:14,290 - PoolThread-twisted.internet.reactor-0 - moksha.hub - DEBUG - 'MBSConsumer' thread 140337773446912 | Worker thread exiting.
2018-02-15 13:54:14,291 - MainThread - moksha.hub - INFO - MokshaHub reactor stopped

Metadata Update from @jaruga:
- Issue status updated to: Open (was: Closed)

All the old modules were disabled when we switched to the hybrid model. There's no more autotools:master. Fedora Everything (aka platform:f28) provides these tools -- just drop it from your build dependencies.

Metadata Update from @psabata:
- Issue status updated to: Closed (was: Open)

Ok, thanks. I think we need clear error message in the output text for this case.
The debug message is not enough.

2018-02-15 13:54:13,674 - PoolThread-twisted.internet.reactor-0 - root - DEBUG - get_module({'active': True, 'version': 'master', 'name': 'autotools'}, strict=False)

Metadata Update from @jaruga:
- Issue status updated to: Open (was: Closed)

On above branch that I created.

$ mbs-build local

$ vi ~/modulebuild/builds/module-ruby-feature/update-master-with-latest-specification-20180215132649/results/
ruby-mock-stderr.log
...
ERROR: Can't find spec file /tmp/tmpjvuuce5v.mock-scm.ruby/ruby/ruby.spec
...

There is no directory.

$ ls /tmp/tmpjvuuce5v.mock-scm.ruby/
ls: cannot access '/tmp/tmpjvuuce5v.mock-scm.ruby/': No such file or directory

How to fix?

Well, that looks like the referenced repository for rpms/ruby doesn't include ruby.spec. It's really hard to tell from this.

ruby.spec exists in rpms/ruby master branch.
https://src.fedoraproject.org/rpms/ruby/blob/master/f/ruby.spec

And I show more logs. How about this?

$ vi ~/modulebuild/builds/module-ruby-feature/update-master-with-latest-specification-20180215132649/results/ruby-mock-stderr.log
...
DEBUG: Initializing SCM integration...
DEBUG: SCM checkout command: sh -c 'fedpkg clone --anonymous ruby''; git -C ruby checkout faaad7b7c55df8f0f145e9d2ee48257d2ec0a6c8'
DEBUG: SCM checkout post command: fedpkg --release module sources
DEBUG: SCM checkout directory: /tmp/tmpjvuuce5v.mock-scm.ruby
DEBUG: child environment: None
DEBUG: Executing command: ['sh', '-c', 'fedpkg clone --anonymous ruby; git -C ruby checkout faaad7b7c55df8f0f145e9d2ee48257d2ec0a6c8'] with env environ({'DISPLAY': ':0', 'LANG': 'en_US.UTF-8', 'LC_ALL': 'en_US.UTF-8', 'SHELL': '/bin/bash', 'TERM': 'xterm-color', 'PATH': '/usr/sbin:/usr/bin:/sbin:/bin:/root/bin', 'LOGNAME': 'root', 'USER': 'root', 'SSH_AUTH_SOCK': '/run/user/28707/keyring/ssh', 'USERHELPER_UID': '28707', 'HOME': '/home/jaruga'}) and shell False
DEBUG: Cloning into 'ruby'...
DEBUG: Note: checking out 'faaad7b7c55df8f0f145e9d2ee48257d2ec0a6c8'.
DEBUG: You are in 'detached HEAD' state. You can look around, make experimental
DEBUG: changes and commit them, and you can discard any commits you make in this
DEBUG: state without impacting any branches by performing another checkout.
DEBUG: If you want to create a new branch to retain commits you create, you may
DEBUG: do so (now or later) by using -b with the checkout command again. Example:
DEBUG:   git checkout -b <new-branch-name>
DEBUG: HEAD is now at faaad7b... Fix thread_safe test suite segfaults.
DEBUG: Child return code was: 0
DEBUG: child environment: None
DEBUG: Executing command: ['fedpkg', '--release', 'module', 'sources'] with env environ({'DISPLAY': ':0', 'LANG': 'en_US.UTF-8', 'LC_ALL': 'en_US.UTF-8', 'SHELL': '/bin/bash', 'TERM': 'xterm-color', 'PATH': '/usr/sbin:/usr/bin:/sbin:/bin:/root/bin', 'LOGNAME': 'root', 'USER': 'root', 'SSH_AUTH_SOCK': '/run/user/28707/keyring/ssh', 'USERHELPER_UID': '28707', 'HOME': '/home/jaruga'}) and shell False
DEBUG: Child return code was: 0
DEBUG: Fetched sources from SCM
DEBUG: Preparing SCM sources
ERROR: Can't find spec file /tmp/tmpjvuuce5v.mock-scm.ruby/ruby/ruby.spec
DEBUG: Clean SCM checkout directory

ruby.yaml I used is here.

https://src.fedoraproject.org/fork/jaruga/modules/ruby/blob/feature/update-master-with-latest-specification/f/ruby.yaml

On above branch that I created.
$ mbs-build local

$ vi ~/modulebuild/builds/module-ruby-feature/update-master-with-latest-specification-20180215132649/results/
ruby-mock-stderr.log
...
ERROR: Can't find spec file /tmp/tmpjvuuce5v.mock-scm.ruby/ruby/ruby.spec
...

There is no directory.
$ ls /tmp/tmpjvuuce5v.mock-scm.ruby/
ls: cannot access '/tmp/tmpjvuuce5v.mock-scm.ruby/': No such file or directory

How to fix?

This is due to a bug in mock which is tracked at:
https://pagure.io/fm-orchestrator/issue/840

Anyways, you have two options. You can either update to the unreleased version of mock (1.4.9) [1], or you can downgrade mock to version 1.4.6.

1 - https://bodhi.fedoraproject.org/updates/FEDORA-2018-c17daa06f6

Metadata Update from @mprahl:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

@mprahl It looks working with the mock 1.4.9. Thanks.

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

Please continue any further discussion there.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.