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ý" <msu...@redhat.com>
> Til: "copr-devel" <copr-devel@lists.fedorahosted.org>
> 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 -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org

Reply via email to