ing. 'Inappropriate IOCTL on device' might mean that you
try to read/write on tty you do not have access to but not sure if this
information will help you in any way.
/Martin
>
>
> - Original meddelelse -
> Fra: "Michal Novotny"
> Til: "copr-devel
ndt: mandag, 5. december 2016 16:09:03
Emne: Re: python-novaclient package??
On Monday, December 5, 2016 1:49:22 PM CET Martin Juhl wrote:
> Hi
>
> Manually:
>
> ansible-playbook -i inventory -c ssh
> /usr/share/doc/copr-backend-1.94/playbooks/spawn_local.yml/usr/lib/p
user be created?? I have created the user myself,
but am I missing a package???
/Martin
- Original meddelelse -
Fra: "Michal Novotny"
Til: "copr-devel"
Sendt: mandag, 5. december 2016 15:12:47
Emne: Re: python-novaclient package??
On Mon, Dec 5, 2016 at 2:58
On Monday, December 5, 2016 1:49:22 PM CET Martin Juhl wrote:
> Hi
>
> Manually:
>
> ansible-playbook -i inventory -c ssh
> /usr/share/doc/copr-backend-1.94/playbooks/spawn_local.yml/usr/lib/python2.7/site-packages/novaclient/v1_1/__init__.py:30:
> UserWarning: Module novaclient.v1_1 is deprecate
erate]
> accelerate_port = 5099
> accelerate_timeout = 30
> accelerate_connect_timeout = 5.0
>
> # The daemon timeout is measured in minutes. This time is measured
> # from the last activity to the accelerate daemon.
> accelerate_daemon_timeout = 30
>
> # If set to yes, acc
with security context
# the default behaviour that copies the existing context or uses the user
default
# needs to be changed to use the file system dependant context.
#special_context_filesystems=nfs,vboxsf,fuse
- Original meddelelse -
Fra: "Michal Novotny"
Til: "copr-dev
0126240 queued for
> termination
>
> Any ideas
>
>
I saw this error ('Inappropriate ioctl for device') when ansible2 default
config was used by ansible1.9 being installed after ansible2. Can you show
us your /etc/ansible/ansible.cfg? Is it default conf for ansible1.9
???
/Martin
- Original meddelelse -
Fra: "praiskup"
Til: "copr-devel"
Cc: "mj"
Sendt: mandag, 5. december 2016 12:46:51
Emne: Re: python-novaclient package??
On Monday, December 5, 2016 11:47:59 AM CET Martin Juhl wrote:
> Ok... Might have fixed that m
On Monday, December 5, 2016 11:47:59 AM CET Martin Juhl wrote:
> Ok... Might have fixed that myself...
>
> Using the /centos/7.2.1511/cloud/x86_64/openstack-kilo/ it seems to work...
>
> Now i'm getting:
>
> ==> /var/log/copr-backend/vmm.log <==
> [2016-12-05 11:15:37,384][
> INFO][vmm.event
On Monday, December 5, 2016 10:53:35 AM CET Martin Juhl wrote:
> Hi guys
>
> Still playing around with getting COPR to work on RHEL/CentOS..
>
> I'm very close.. Only think I have one issue left.. When ansible is spawning a
> new build instance it fails...
we talked about this with Mirek and Val
e}},
\'contacted\': {}}'}
[2016-12-05 11:18:37,257][
INFO][vmm.event_handler][manager.py:start_vm_termination:283] VM Copr builder
760126240 queued for termination
Any ideas
Fra: "mj"
Til: "copr-devel"
Sendt: mandag, 5. december 2016 10:53:35
Emne:
We use python-novaclient 2.23.3 currently on our backend machines. The
os_nova.py filter plugin is actually not needed for local spawning so I
usually just move it to os_nova.py.off. We need to implement support for
newer python-novaclient.
On Mon, Dec 5, 2016 at 10:53 AM, Martin Juhl wrote:
> H
Hi guys
Still playing around with getting COPR to work on RHEL/CentOS..
I'm very close.. Only think I have one issue left.. When ansible is spawning a
new build instance it fails...
[root@copr02 playbooks]# ansible-playbook -i inventory -c ssh
/usr/share/doc/copr-backend-1.94/playbooks/spawn_l
13 matches
Mail list logo
