Martin, I think you go in the right direction. If you follow /usr/share/copr/coprs_frontend/coprs/views/backend_ns/backend_general.py", line 71 back to the cause, you will come to branch_to_os_version method that does support epel but not rhel. That might as well be the cause of the problem. M.
On Tue, Jan 31, 2017 at 12:55 PM, Martin Juhl <[email protected]> wrote: > Hmmm > > After digging a bit, I think that problem is actually with the import to > dist-git... Works fine with epel, but with RHEL it fails: > > ==> httpd/error_log <== > [Tue Jan 31 12:52:33.152277 2017] [:error] [pid 1029] > ------------------------------------------------------------ > -------------------- > [Tue Jan 31 12:52:33.152313 2017] [:error] [pid 1029] DEBUG in > backend_general [/usr/share/copr/coprs_frontend/coprs/views/backend_ > ns/backend_general.py:68]: > [Tue Jan 31 12:52:33.152316 2017] [:error] [pid 1029] {"pkg_version": > "1.36-1.fc22", "git_hash": "3231f204b083b4532ee25757c45afe21fced9a75", > "pkg_name": "copr-selinux", "task_id": "23-rhel7", "repo_name": > "mj/Ting/copr-selinux"} > [Tue Jan 31 12:52:33.152318 2017] [:error] [pid 1029] > ------------------------------------------------------------ > -------------------- > [Tue Jan 31 12:52:33.152944 2017] [:error] [pid 1029] > DEBUG:coprs:{"pkg_version": "1.36-1.fc22", "git_hash": " > 3231f204b083b4532ee25757c45afe21fced9a75", "pkg_name": "copr-selinux", > "task_id": "23-rhel7", "repo_name": "mj/Ting/copr-selinux"} > > ==> copr-frontend/frontend.log <== > 2017-01-31 12:52:33,152 [DEBUG][/usr/share/copr/coprs_ > frontend/coprs/views/backend_ns/backend_general.py:68| > backend_general:dist_git_upload_completed] {"pkg_version": "1.36-1.fc22", > "git_hash": "3231f204b083b4532ee25757c45afe21fced9a75", "pkg_name": > "copr-selinux", "task_id": "23-rhel7", "repo_name": "mj/Ting/copr-selinux"} > > ==> httpd/error_log <== > [Tue Jan 31 12:52:33.164589 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] Traceback (most recent call last): > [Tue Jan 31 12:52:33.164614 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] File "/usr/lib/python2.7/site-packages/flask/app.py", > line 1836, in __call__ > [Tue Jan 31 12:52:33.164617 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] return self.wsgi_app(environ, start_response) > [Tue Jan 31 12:52:33.164619 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] File "/usr/lib/python2.7/site-packages/flask/app.py", > line 1820, in wsgi_app > [Tue Jan 31 12:52:33.164621 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] response = self.make_response(self.handle_exception(e)) > [Tue Jan 31 12:52:33.164622 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] File > "/usr/share/copr/coprs_frontend/coprs/rest_api/__init__.py", > line 44, in error_router > [Tue Jan 31 12:52:33.164624 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] return original_handler(e) > [Tue Jan 31 12:52:33.164626 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] File "/usr/lib/python2.7/site-packages/flask/app.py", > line 1403, in handle_exception > [Tue Jan 31 12:52:33.164627 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] reraise(exc_type, exc_value, tb) > [Tue Jan 31 12:52:33.164629 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] File "/usr/lib/python2.7/site-packages/flask/app.py", > line 1817, in wsgi_app > [Tue Jan 31 12:52:33.164630 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] response = self.full_dispatch_request() > [Tue Jan 31 12:52:33.164632 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] File "/usr/lib/python2.7/site-packages/flask/app.py", > line 1477, in full_dispatch_request > [Tue Jan 31 12:52:33.164633 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] rv = self.handle_user_exception(e) > [Tue Jan 31 12:52:33.164635 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] File > "/usr/share/copr/coprs_frontend/coprs/rest_api/__init__.py", > line 44, in error_router > [Tue Jan 31 12:52:33.164636 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] return original_handler(e) > [Tue Jan 31 12:52:33.164638 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] File "/usr/lib/python2.7/site-packages/flask/app.py", > line 1381, in handle_user_exception > [Tue Jan 31 12:52:33.164639 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] reraise(exc_type, exc_value, tb) > [Tue Jan 31 12:52:33.164641 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] File "/usr/lib/python2.7/site-packages/flask/app.py", > line 1475, in full_dispatch_request > [Tue Jan 31 12:52:33.164642 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] rv = self.dispatch_request() > [Tue Jan 31 12:52:33.164644 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] File "/usr/lib/python2.7/site-packages/flask/app.py", > line 1461, in dispatch_request > [Tue Jan 31 12:52:33.164645 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] return self.view_functions[rule. > endpoint](**req.view_args) > [Tue Jan 31 12:52:33.164647 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] File "/usr/share/copr/coprs_frontend/coprs/views/misc.py", > line 293, in decorated_function > [Tue Jan 31 12:52:33.164648 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] return f(*args, **kwargs) > [Tue Jan 31 12:52:33.164650 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] File > "/usr/share/copr/coprs_frontend/coprs/views/backend_ns/backend_general.py", > line 71, in dist_git_upload_completed > [Tue Jan 31 12:52:33.164652 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] build = build_chroots[0].build > [Tue Jan 31 12:52:33.164653 2017] [:error] [pid 1029] [remote > 127.0.0.1:196] IndexError: list index out of range > > Do I somehow need to add the repo to dist-git????? or somewhere in the > database??? > > > Btw, still running 1.94 on both backend and frontend... > > /Martin > > ----- Original meddelelse ----- > Fra: "praiskup" <[email protected]> > Til: "copr-devel" <[email protected]> > Cc: "mj" <[email protected]> > Sendt: tirsdag, 31. januar 2017 11:52:27 > Emne: Re: mockremote with RHEL?? > > On Tuesday, January 31, 2017 11:22:18 AM CET Martin Juhl wrote: > > > > > Add it with manage.py to copr db is one step, but you must make sure > the > > > config exist on builders VMs. So put it in ansible playbook, which > spawns > > > the builder. > > > > Sooo.. where exactly should I put it?? > > > > I'm using the /usr/share/doc/copr-backend-1.94/playbooks/spawn_local.yml > playbook... ??? > > Well, if your group...spawn_playbook option refers to this playbook (and > you haven't made a change to this file) it looks like it is enough to have > the rhel-7-x86.cfg installed on backend machine directly. > > > > Ok. this is another issue. It seems that ansible is not able to ssh > connect > > > to your localhost. Are you sure you have there ssh keys for copr user? > > > > It works with epel-7-x86_64.cfg??? so I guess it's because the vm is > spawned incorrectly?? > > If you use spawn_local, there's no special builder VM. And it is really > suspicious that ssh works with epel-7 and not with rhel-7. Haven't you > upgraded your copr-backend package in the meantime? The latest release > brings different ssh-layer into backend code (not using ansible now but > using > python-paramiko directly). This probably requires you to specify the: > > [ssh] > identity_file=/path/to/your/ssh_private_key > > (in backend's config) > > Pavel > > > ----- Original meddelelse ----- > > Fra: "Miroslav Suchý" <[email protected]> > > Til: "copr-devel" <[email protected]> > > Sendt: tirsdag, 31. januar 2017 11:08:29 > > Emne: Re: mockremote with RHEL?? > > > > Dne 24.1.2017 v 11:31 Martin Juhl napsal(a): > > > Does anyone know howto use this with copr and mockremote??? > > > > > > Right now I have created a /etc/mock/rhel-7-x86_64.cfg, and added the > profile with the manage.py script... > > > > Add it with manage.py to copr db is one step, but you must make sure the > config exist on builders VMs. So put it in > > ansible playbook, which spawns the builder. > > > > > > > [2017-01-24 09:56:59,846][ DEBUG][vmm.event_handler][ > event_handle.py:on_health_check_result:106] recording check fail: > {u'vm_ip': u'127.0.0.1', u'vm_name': u'Copr builder 596711858', u'topic': > u'health_check', u'result': u'failed', u'msg': u'VM is not responding to > the testing playbook.Runner options: {\'remote_user\': \'mockbuilder\', > \'timeout\': 5, \'pattern\': \'127.0.0.1\', \'forks\': 1, \'host_list\': > \'127.0.0.1,\', \'transport\': u\'paramiko\'}Ansible raw > response:\n{\'dark\': {\'127.0.0.1\': {\'msg\': "Failed to open session: > (1, \'Administratively prohibited\')", \'failed\': True}}, \'contacted\': > {}}'} > > > > Ok. this is another issue. It seems that ansible is not able to ssh > connect to > > your localhost. Are you sure you have there ssh keys for copr user? > > > > > > > > _______________________________________________ > copr-devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] > _______________________________________________ > copr-devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ copr-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
