[ovirt-devel] Re: Uploading iso / ovirt-imageio

[Nir Soffer]

On Mon, Apr 27, 2020 at 11:05 PM Nir Soffer  wrote:
>
> On Mon, Apr 27, 2020 at 12:24 PM Artur Socha  wrote:
> >
> > Hi,
> > After a long break I am trying setup my engine so that I could upload images
> > (ISO) there and use them when spinning new VMs. First I tried recent master
> > (FC31) and then latest 4.4 beta from RPMs (Centos8).
> >
> > I have ovirt-imageio daemon running on the same host engine is running. 
> > (with
> > the simplest possible configuration - TLS disabled)
>
> We require TLS for imageio, it is not secure enough to use without TLS and
> we don't support it.
>
> > Unfortunately when I hit 'test connection' in admin ui/storage/domain I keep
> > seeing error message complaining about ovirt-imageio-proxy setup.
> > I know that recently there has been quite a lot of changes related to the 
> > next
> > version of imageio.
>
> Probably because engine was not ready for imgeio in the latest beta build.
>
> > Is there something else besides ovirt-imageio daemon that I should have
> > installed/configured?  Perhaps there is some documentation I could use?
>
> On master everything (but development setup) works:
>
> commit ce3a94aedcfc85ede5bd7090cab27a9b592b4187
> Author: Daniel Erez 
> Date:   Sun Apr 19 23:40:59 2020 +0300
>
> core: increase ticket timeout value
>
> Increased ImageTransferClientTicketValidityInSeconds to 300
>
> Change-Id: Iae3fb6ad0c6b5af1e2dc747bfbc67375a5cd7b2c
> Signed-off-by: Daniel Erez 
>
>
> But this commit fixed development setup but broke installation from rpms:
>
> commit 81a5e757fd8768ace825140ca7dc701cc2e011ce
> Author: Vojtech Juranek 
> Date:   Thu Apr 23 11:44:41 2020 +0200
>
> spec: allow imageio config in dev env
>
> Add $PREFIX into imageio config directory to allow imageio configuration
> in development environment when config files are installed into
> a specified directory.
> Currently it fails with:
>
> [Errno 13] Permission denied: '/etc/ovirt-imageio'
>
> Change-Id: I9e13bba0e97f681b0b07d5a135be76113e391ddc
> Signed-off-by: Vojtech Juranek 
>
> Fix is here:
> https://gerrit.ovirt.org/c/108672

Merged, so installing from master should work now.

> For development setup there is this patch in review:
> https://gerrit.ovirt.org/c/108620
>
> Until the patch is ready, this is the recommended way to set up
> development environment:
>
> 1. Install ovirt-imageio service
>
> dnf install ovit-imageio-daemon
>
> 2. Run engine setup
>
> This creates a working configuration file at
> $PREFIX/etc/ovirt-imagei/daemon.conf
>
> However it does not create a logger.conf file, so you need to create one.
> The default configuration will not work for you since you want to run
> ovirt-imageio as yourself, and you cannot write logs to
> /var/log/ovirt-imageio.
>
> 3. Create logger.conf for development
>
> $ curl 
> https://raw.githubusercontent.com/oVirt/ovirt-imageio/master/daemon/test/conf/logger.conf
> >  $PREFIX/etc/ovirt-imageio/logger.conf
>
> Now run imageio using:
>
> $ ./ovirt-imageio --conf-dir $PREFIX/etc/ovirt-imageio
>
>
>
>
> >
> >
> > thanks!
> >
> > --
> > Artur Socha
> > Senior Software Engineer, RHV
> > Red Hat
> >
> > ___
> > Devel mailing list -- devel@ovirt.org
> > To unsubscribe send an email to devel-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > oVirt Code of Conduct: 
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives: 
> > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/JDDVTQC6K7U56D5WAIYOQ4HDGORAVELR/
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/WMZ7MOC6O7KU6W6MNDDBNVXILCEEQI2V/

[ovirt-devel] Re: Uploading iso / ovirt-imageio

[Nir Soffer]

On Mon, Apr 27, 2020 at 12:24 PM Artur Socha  wrote:
>
> Hi,
> After a long break I am trying setup my engine so that I could upload images
> (ISO) there and use them when spinning new VMs. First I tried recent master
> (FC31) and then latest 4.4 beta from RPMs (Centos8).
>
> I have ovirt-imageio daemon running on the same host engine is running. (with
> the simplest possible configuration - TLS disabled)

We require TLS for imageio, it is not secure enough to use without TLS and
we don't support it.

> Unfortunately when I hit 'test connection' in admin ui/storage/domain I keep
> seeing error message complaining about ovirt-imageio-proxy setup.
> I know that recently there has been quite a lot of changes related to the next
> version of imageio.

Probably because engine was not ready for imgeio in the latest beta build.

> Is there something else besides ovirt-imageio daemon that I should have
> installed/configured?  Perhaps there is some documentation I could use?

On master everything (but development setup) works:

commit ce3a94aedcfc85ede5bd7090cab27a9b592b4187
Author: Daniel Erez 
Date:   Sun Apr 19 23:40:59 2020 +0300

core: increase ticket timeout value

Increased ImageTransferClientTicketValidityInSeconds to 300

Change-Id: Iae3fb6ad0c6b5af1e2dc747bfbc67375a5cd7b2c
Signed-off-by: Daniel Erez 


But this commit fixed development setup but broke installation from rpms:

commit 81a5e757fd8768ace825140ca7dc701cc2e011ce
Author: Vojtech Juranek 
Date:   Thu Apr 23 11:44:41 2020 +0200

spec: allow imageio config in dev env

Add $PREFIX into imageio config directory to allow imageio configuration
in development environment when config files are installed into
a specified directory.
Currently it fails with:

[Errno 13] Permission denied: '/etc/ovirt-imageio'

Change-Id: I9e13bba0e97f681b0b07d5a135be76113e391ddc
Signed-off-by: Vojtech Juranek 

Fix is here:
https://gerrit.ovirt.org/c/108672

For development setup there is this patch in review:
https://gerrit.ovirt.org/c/108620

Until the patch is ready, this is the recommended way to set up
development environment:

1. Install ovirt-imageio service

dnf install ovit-imageio-daemon

2. Run engine setup

This creates a working configuration file at
$PREFIX/etc/ovirt-imagei/daemon.conf

However it does not create a logger.conf file, so you need to create one.
The default configuration will not work for you since you want to run
ovirt-imageio as yourself, and you cannot write logs to
/var/log/ovirt-imageio.

3. Create logger.conf for development

$ curl 
https://raw.githubusercontent.com/oVirt/ovirt-imageio/master/daemon/test/conf/logger.conf
>  $PREFIX/etc/ovirt-imageio/logger.conf

Now run imageio using:

$ ./ovirt-imageio --conf-dir $PREFIX/etc/ovirt-imageio




>
>
> thanks!
>
> --
> Artur Socha
> Senior Software Engineer, RHV
> Red Hat
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/JDDVTQC6K7U56D5WAIYOQ4HDGORAVELR/
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/5GGKBNEK3TEFV2AAUIJKNOJQ3BZGNM6U/

[ovirt-devel] Re: PoC - using pre-built VM images in OST

[Nir Soffer]

On Mon, Apr 27, 2020 at 7:21 PM Barak Korren  wrote:
>
>
>
> בתאריך יום ב׳, 27 באפר׳ 2020, 17:15, מאת Marcin Sobczyk 
> ‏:
>>
>> Hi,
>>
>> recently I've been working on a PoC for OST that replaces the usage
>> of lago templates with pre-built, layered VM images packed in RPMs [2][7].
>>
>>
>> What's the motivation?
>>
>> There are two big pains around OST - first one is that it's slow
>> and the second one is it uses lago, which is unmaintained.
>>
>>
>> How is OST working currently?
>>
>> Lago launches VMs based on templates. It actually has its own mechanism for 
>> VM
>> templating - you can find the ones that we currently use here [1]. How these
>> templates are created? There is a multiple-page doc somewhere that describes 
>> the process,
>> but few are familiar with it. These templates are nothing special really - 
>> just a xzipped
>> qcow with some metadata attached. The proposition here is to replace those 
>> templates with
>> RPMs with qcows inside. The RPMs themselves would be built by a CI pipeline. 
>> An example
>> of a pipeline like this can be found here [2].
>>
>>
>> Why RPMs?
>>
>> It ticks all the boxes really. RPMs provide:
>> - tried and well known mechanisms for packaging, versioning, and 
>> distribution instead
>>   of lago's custom ones
>> - dependencies which permit to layer the VM images in a controllable way
>> - we already install RPMs when running OST, so using the new ones is a 
>> matter of adding
>>   some dependencies
>>
>>
>> How the image building pipeline works? [3]
>>
>> - we download a dvd iso for installation of the distro
>> - we use 'virt-install' with the dvd iso + kickstart file to build a 'base' 
>> layer
>>   qcow image
>> - we create another qcow image that has the 'base' image as the backing one. 
>> In this
>>   image we use 'virt-customize' to run 'dnf upgrade'.  This is our 'upgrade' 
>> layer.
>> - we create two more qcow images that have the 'upgrade' image as the 
>> backing one. On one
>>   of them we install the 'ovirt-host' package and on the other the 
>> 'ovirt-engine'. These are
>>   our 'host-installed' and 'engine-installed' layers.
>> - we create 4 RPMs for these qcows:
>>   * ost-images-base
>>   * ost-images-upgrade
>>   * ost-images-host-installed
>>   * ost-images-engine-installed
>> - we publish the RPMs to templates.ovirt.org/yum/ DNF repository (not 
>> implemented yet)
>>
>> Each of those RPMs holds their respective qcow image. They also have proper 
>> dependencies
>> set up - since 'upgrade' layer requires 'base' layer to be functional, it 
>> has an RPM
>> requirement to that package. Same thing happens for '*-installed' packages 
>> which depend on
>> 'upgrade' package.
>>
>> Since this is only a PoC there's still a lot of room for improvement around 
>> the pipeline.
>> The 'base' RPM would be actually built very rarely, since it's a bare 
>> distro, and the
>> 'upgrade' and '*-installed' RPMs would be built nightly. This would allow us 
>> to simply
>> type 'dnf upgrade' on any machine and have a fresh set of VMs ready to be 
>> used with OST.
>>
>>
>> Advantages:
>>
>> - we have CI for building OST images instead of current, obscure template 
>> creating process
>> - we get rid of lots of unnecessary preparations that are done during each 
>> OST run
>>   by moving stuff from 'deploy scripts' [4] to image-building pipeline - 
>> this should
>>   speed up the runs a lot
>> - if the nightly pipeline for building images is not successful, the RPMs 
>> won't be
>>   published - OST will use the older ones. This makes a nice "early error 
>> detection"
>>   mechanism and can partially mitigate situations where everything is 
>> blocked because
>>   of some, i.e. dependency issues.
>> - it's another step for removing responsibilities from lago
>> - the pre-built VM images can be used for much more than OST - functional 
>> testing of
>>   vdsm/engine on a VM? We have an image for that
>> - we can build images for multiple distros, both u/s and d/s, easily
>>
>>
>> Caveats:
>>
>> - we have to download the RPMs before running OST and that takes time, since 
>> they're big.
>>   This can be handled by having them cached on the CI slaves though.
>> - current limitations of CI and lago force us to make a copy of the images 
>> after
>>   installation so they can be seen both by the processes in the chroot and 
>> libvirt, which
>>   is running outside of chroot. Right now they're placed in '/dev/shm' 
>> (which would
>>   actually make some sense if they could be shared among all OST runs on the 
>> slave, but
>>   that's another story). There are some possible workarounds around that 
>> problem too (like
>>   running pipelines on bare metal machines with libvirt running inside 
>> chroot)
>> - multiple qcow layers can slow down the runs because there's a lot of 
>> jumping around.
>>   This can be handled by i.e. introducing a meta package that squashes all 
>> the layers into
>>   one.
>> - we need a way to run OST with custom-built 

[ovirt-devel] Re: PoC - using pre-built VM images in OST

[Barak Korren]

בתאריך יום ב׳, 27 באפר׳ 2020, 17:15, מאת Marcin Sobczyk ‏<
msobc...@redhat.com>:

> Hi,
>
> recently I've been working on a PoC for OST that replaces the usage
> of lago templates with pre-built, layered VM images packed in RPMs [2][7].
>
>
> What's the motivation?
>
> There are two big pains around OST - first one is that it's slow
> and the second one is it uses lago, which is unmaintained.
>
>
> How is OST working currently?
>
> Lago launches VMs based on templates. It actually has its own mechanism
> for VM
> templating - you can find the ones that we currently use here [1]. How
> these
> templates are created? There is a multiple-page doc somewhere that
> describes the process,
> but few are familiar with it. These templates are nothing special really -
> just a xzipped
> qcow with some metadata attached. The proposition here is to replace those
> templates with
> RPMs with qcows inside. The RPMs themselves would be built by a CI
> pipeline. An example
> of a pipeline like this can be found here [2].
>
>
> Why RPMs?
>
> It ticks all the boxes really. RPMs provide:
> - tried and well known mechanisms for packaging, versioning, and
> distribution instead
>   of lago's custom ones
> - dependencies which permit to layer the VM images in a controllable way
> - we already install RPMs when running OST, so using the new ones is a
> matter of adding
>   some dependencies
>
>
> How the image building pipeline works? [3]
>
> - we download a dvd iso for installation of the distro
> - we use 'virt-install' with the dvd iso + kickstart file to build a
> 'base' layer
>   qcow image
> - we create another qcow image that has the 'base' image as the backing
> one. In this
>   image we use 'virt-customize' to run 'dnf upgrade'.  This is our
> 'upgrade' layer.
> - we create two more qcow images that have the 'upgrade' image as the
> backing one. On one
>   of them we install the 'ovirt-host' package and on the other the
> 'ovirt-engine'. These are
>   our 'host-installed' and 'engine-installed' layers.
> - we create 4 RPMs for these qcows:
>   * ost-images-base
>   * ost-images-upgrade
>   * ost-images-host-installed
>   * ost-images-engine-installed
> - we publish the RPMs to templates.ovirt.org/yum/ DNF repository (not
> implemented yet)
>
> Each of those RPMs holds their respective qcow image. They also have
> proper dependencies
> set up - since 'upgrade' layer requires 'base' layer to be functional, it
> has an RPM
> requirement to that package. Same thing happens for '*-installed' packages
> which depend on
> 'upgrade' package.
>
> Since this is only a PoC there's still a lot of room for improvement
> around the pipeline.
> The 'base' RPM would be actually built very rarely, since it's a bare
> distro, and the
> 'upgrade' and '*-installed' RPMs would be built nightly. This would allow
> us to simply
> type 'dnf upgrade' on any machine and have a fresh set of VMs ready to be
> used with OST.
>
>
> Advantages:
>
> - we have CI for building OST images instead of current, obscure template
> creating process
> - we get rid of lots of unnecessary preparations that are done during each
> OST run
>   by moving stuff from 'deploy scripts' [4] to image-building pipeline -
> this should
>   speed up the runs a lot
> - if the nightly pipeline for building images is not successful, the RPMs
> won't be
>   published - OST will use the older ones. This makes a nice "early error
> detection"
>   mechanism and can partially mitigate situations where everything is
> blocked because
>   of some, i.e. dependency issues.
> - it's another step for removing responsibilities from lago
> - the pre-built VM images can be used for much more than OST - functional
> testing of
>   vdsm/engine on a VM? We have an image for that
> - we can build images for multiple distros, both u/s and d/s, easily
>
>
> Caveats:
>
> - we have to download the RPMs before running OST and that takes time,
> since they're big.
>   This can be handled by having them cached on the CI slaves though.
> - current limitations of CI and lago force us to make a copy of the images
> after
>   installation so they can be seen both by the processes in the chroot and
> libvirt, which
>   is running outside of chroot. Right now they're placed in '/dev/shm'
> (which would
>   actually make some sense if they could be shared among all OST runs on
> the slave, but
>   that's another story). There are some possible workarounds around that
> problem too (like
>   running pipelines on bare metal machines with libvirt running inside
> chroot)
> - multiple qcow layers can slow down the runs because there's a lot of
> jumping around.
>   This can be handled by i.e. introducing a meta package that squashes all
> the layers into
>   one.
> - we need a way to run OST with custom-built artifacts. There are multiple
> ways we can
>   approach it:
>   * use 'upgrade' layer and not '*-installed' one
>   * first build your artifacts, then build VM image RPMs that have your
> artifacts
> 

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Vojtech Juranek]

> > I'll, but need to look more into it, replacing $(PREFIX) with
> > $(SYSCONF_DIR)
> > doesn't seem to work as SYSCONF_DIR=$(PREFIX)/etc (see https://github.com/
> > oVirt/ovirt-engine/blob/master/Makefile#L41
> > ), so we
> > will end up again with /
> > usr/etc. We will probably have to do it as VMCONSOLE_* variable - hardcode
> > config file and define new just install-dev environment (and do the proper
> > testing before merge)
> 
> No. SYSCONF_DIR=$(PREFIX)/etc allow you to set PREFIX for developer work.

isn't it overwritten here:
https://github.com/oVirt/ovirt-engine/blob/master/Makefile#L37
?

I posted https://gerrit.ovirt.org//c/108672/ which does it in the same way as 
ovirt-vmconsole, but if you prefer using SYSCONFIG_DIR and it work in all 
cases, no problem to change it this way

> But then in spec file it's overridden:
> SYSCONF_DIR=%{_sysconfdir}
> $ rpm --eval "%{_sysconfdir}"
> /etc


signature.asc
Description: This is a digitally signed message part.
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/CXYYQNFYIST2NRARPPH345UVTB5G2UL7/

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Sandro Bonazzola]

Il giorno lun 27 apr 2020 alle ore 16:58 Vojtech Juranek <
vjura...@redhat.com> ha scritto:

> On pondělí 27. dubna 2020 16:47:56 CEST Nir Soffer wrote:
> > On Mon, Apr 27, 2020 at 5:37 PM Sandro Bonazzola 
> wrote:
> > > Il giorno lun 27 apr 2020 alle ore 16:28 Nir Soffer <
> nsof...@redhat.com>
> ha scritto:
> > >> On Mon, Apr 27, 2020 at 5:22 PM Vojtech Juranek 
>
> wrote:
> > >> > On pondělí 27. dubna 2020 16:10:11 CEST Nir Soffer wrote:
> > >> > > On Mon, Apr 27, 2020 at 5:01 PM Liran Rotenberg <
> lrote...@redhat.com>
> wrote:
> > >> > > > On Mon, Apr 27, 2020 at 4:58 PM Sandro Bonazzola
> > >> > > > 
> > >> > > >
> > >> > > > wrote:
> > >> > > >> Il giorno lun 27 apr 2020 alle ore 15:52 Nir Soffer
> > >> > > >> 
> > >> > > >>
> > >> > > >> ha scritto:
> > >> > > >>> On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola
> > >> > > >>> 
> > >> > > >>>
> > >> > > >>> wrote:
> > >> > >  Failing job is
> > >> > > 
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
> > >> > > 
> > >> > >  Here's the relevant log in engine-setup:
> > >> > > 
> > >> > > 
> > >> > >  2020-04-27 09:25:35,457-0400 DEBUG
> > >> > >  otopi.plugins.otopi.services.systemd
> > >> > >  plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop',
> > >> > >  'ovirt-imageio.service'), executable='None', cwd='None',
> > >> > >  env=None
> > >> > >  2020-04-27 09:25:35,652-0400 DEBUG
> > >> > >  otopi.plugins.otopi.services.systemd plugin.executeRaw:863
> > >> > >  execute-result: ('/usr/bin/systemctl', 'stop',
> > >> > >  'ovirt-imageio.service'), rc=0 2020-04-27 09:25:35,653-0400
> > >> > >  DEBUG
> > >> > >  otopi.plugins.otopi.services.systemd plugin.execute:921
> > >> > >  execute-output: ('/usr/bin/systemctl', 'stop',
> > >> > >  'ovirt-imageio.service') stdout:
> > >> > > 
> > >> > > 
> > >> > >  2020-04-27 09:25:35,653-0400 DEBUG
> > >> > >  otopi.plugins.otopi.services.systemd
> > >> > >  plugin.execute:926 execute-output: ('/usr/bin/systemctl',
> > >> > >  'stop',
> > >> > >  'ovirt-imageio.service') stderr:
> > >> > > 
> > >> > > 
> > >> > >  2020-04-27 09:25:35,653-0400 DEBUG
> > >> > >  otopi.plugins.otopi.services.systemd
> > >> > >  systemd.state:170 starting service ovirt-imageio 2020-04-27
> > >> > >  09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd
> > >> > >  plugin.executeRaw:813 execute: ('/usr/bin/systemctl',
> 'start',
> > >> > >  'ovirt-imageio.service'), executable='None', cwd='None',
> > >> > >  env=None
> > >> > >  2020-04-27 09:25:36,631-0400 DEBUG
> > >> > >  otopi.plugins.otopi.services.systemd plugin.executeRaw:863
> > >> > >  execute-result: ('/usr/bin/systemctl', 'start',
> > >> > >  'ovirt-imageio.service'), rc=1 2020-04-27 09:25:36,632-0400
> > >> > >  DEBUG
> > >> > >  otopi.plugins.otopi.services.systemd plugin.execute:921
> > >> > >  execute-output: ('/usr/bin/systemctl', 'start',
> > >> > >  'ovirt-imageio.service') stdout:
> > >> > > 
> > >> > > 
> > >> > >  2020-04-27 09:25:36,632-0400 DEBUG
> > >> > >  otopi.plugins.otopi.services.systemd
> > >> > >  plugin.execute:926 execute-output: ('/usr/bin/systemctl',
> > >> > >  'start',
> > >> > >  'ovirt-imageio.service') stderr: Job for
> ovirt-imageio.service
> > >> > >  failed
> > >> > >  because the control process exited with error code. See
> > >> > >  "systemctl
> > >> > >  status ovirt-imageio.service" and "journalctl -xe" for
> details.
> > >> > > 
> > >> > >  2020-04-27 09:25:36,633-0400 DEBUG otopi.context
> > >> > >  context._executeMethod:145 method exception
> > >> > > 
> > >> > >  Traceback (most recent call last):
> > >> > >    File "/usr/lib/python3.6/site-packages/otopi/context.py",
> line
> > >> > >    132,
> > >> > >    in _executeMethod
> > >> > > 
> > >> > >  method['method']()
> > >> > > 
> > >> > >    File
> > >> > > 
>  "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-set
> > >> > >    up/ovi
> > >> > >    rt_imageio/config.py", line 190, in
> > >> > >    _closeup_resatrt_service
> > >> > > 
> > >> > >  state=state,
> > >> > > 
> > >> > >    File "/usr/share/otopi/plugins/otopi/services/systemd.py",
> > >> > >    line 181,
> > >> > >    in state
> > >> > > 
> > >> > >  service=name,
> > >> > > 
> > >> > >  RuntimeError: Failed to start service 'ovirt-imageio'
> > >> > >  2020-04-27 09:25:36,636-0400 ERROR otopi.context
> > >> > >  context._executeMethod:154 Failed to execute stage 'Closing
> up':
> > >> > >  Failed to start service 'ovirt-imageio'>>>
> > >> > > >>>
> > >> > > >>> Looking at the logs at:
> > >> > > >>>
> > >> > > >>>
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/arti
> > >> > > >>> fact/ex
> > >> > > >>>
> 

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Vojtech Juranek]

On pondělí 27. dubna 2020 16:47:56 CEST Nir Soffer wrote:
> On Mon, Apr 27, 2020 at 5:37 PM Sandro Bonazzola  
wrote:
> > Il giorno lun 27 apr 2020 alle ore 16:28 Nir Soffer  
ha scritto:
> >> On Mon, Apr 27, 2020 at 5:22 PM Vojtech Juranek  
wrote:
> >> > On pondělí 27. dubna 2020 16:10:11 CEST Nir Soffer wrote:
> >> > > On Mon, Apr 27, 2020 at 5:01 PM Liran Rotenberg  
wrote:
> >> > > > On Mon, Apr 27, 2020 at 4:58 PM Sandro Bonazzola
> >> > > > 
> >> > > > 
> >> > > > wrote:
> >> > > >> Il giorno lun 27 apr 2020 alle ore 15:52 Nir Soffer
> >> > > >> 
> >> > > >> 
> >> > > >> ha scritto:
> >> > > >>> On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola
> >> > > >>> 
> >> > > >>> 
> >> > > >>> wrote:
> >> > >  Failing job is
> >> > >  https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
> >> > >  
> >> > >  Here's the relevant log in engine-setup:
> >> > >  
> >> > >  
> >> > >  2020-04-27 09:25:35,457-0400 DEBUG
> >> > >  otopi.plugins.otopi.services.systemd
> >> > >  plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop',
> >> > >  'ovirt-imageio.service'), executable='None', cwd='None',
> >> > >  env=None
> >> > >  2020-04-27 09:25:35,652-0400 DEBUG
> >> > >  otopi.plugins.otopi.services.systemd plugin.executeRaw:863
> >> > >  execute-result: ('/usr/bin/systemctl', 'stop',
> >> > >  'ovirt-imageio.service'), rc=0 2020-04-27 09:25:35,653-0400
> >> > >  DEBUG
> >> > >  otopi.plugins.otopi.services.systemd plugin.execute:921
> >> > >  execute-output: ('/usr/bin/systemctl', 'stop',
> >> > >  'ovirt-imageio.service') stdout:
> >> > >  
> >> > >  
> >> > >  2020-04-27 09:25:35,653-0400 DEBUG
> >> > >  otopi.plugins.otopi.services.systemd
> >> > >  plugin.execute:926 execute-output: ('/usr/bin/systemctl',
> >> > >  'stop',
> >> > >  'ovirt-imageio.service') stderr:
> >> > >  
> >> > >  
> >> > >  2020-04-27 09:25:35,653-0400 DEBUG
> >> > >  otopi.plugins.otopi.services.systemd
> >> > >  systemd.state:170 starting service ovirt-imageio 2020-04-27
> >> > >  09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd
> >> > >  plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start',
> >> > >  'ovirt-imageio.service'), executable='None', cwd='None',
> >> > >  env=None
> >> > >  2020-04-27 09:25:36,631-0400 DEBUG
> >> > >  otopi.plugins.otopi.services.systemd plugin.executeRaw:863
> >> > >  execute-result: ('/usr/bin/systemctl', 'start',
> >> > >  'ovirt-imageio.service'), rc=1 2020-04-27 09:25:36,632-0400
> >> > >  DEBUG
> >> > >  otopi.plugins.otopi.services.systemd plugin.execute:921
> >> > >  execute-output: ('/usr/bin/systemctl', 'start',
> >> > >  'ovirt-imageio.service') stdout:
> >> > >  
> >> > >  
> >> > >  2020-04-27 09:25:36,632-0400 DEBUG
> >> > >  otopi.plugins.otopi.services.systemd
> >> > >  plugin.execute:926 execute-output: ('/usr/bin/systemctl',
> >> > >  'start',
> >> > >  'ovirt-imageio.service') stderr: Job for ovirt-imageio.service
> >> > >  failed
> >> > >  because the control process exited with error code. See
> >> > >  "systemctl
> >> > >  status ovirt-imageio.service" and "journalctl -xe" for details.
> >> > >  
> >> > >  2020-04-27 09:25:36,633-0400 DEBUG otopi.context
> >> > >  context._executeMethod:145 method exception
> >> > >  
> >> > >  Traceback (most recent call last):
> >> > >    File "/usr/lib/python3.6/site-packages/otopi/context.py", line
> >> > >    132,
> >> > >    in _executeMethod
> >> > >    
> >> > >  method['method']()
> >> > >    
> >> > >    File
> >> > >    "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-set
> >> > >    up/ovi
> >> > >    rt_imageio/config.py", line 190, in
> >> > >    _closeup_resatrt_service
> >> > >    
> >> > >  state=state,
> >> > >    
> >> > >    File "/usr/share/otopi/plugins/otopi/services/systemd.py",
> >> > >    line 181,
> >> > >    in state
> >> > >    
> >> > >  service=name,
> >> > >  
> >> > >  RuntimeError: Failed to start service 'ovirt-imageio'
> >> > >  2020-04-27 09:25:36,636-0400 ERROR otopi.context
> >> > >  context._executeMethod:154 Failed to execute stage 'Closing up':
> >> > >  Failed to start service 'ovirt-imageio'>>>
> >> > > >>> 
> >> > > >>> Looking at the logs at:
> >> > > >>> 
> >> > > >>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/arti
> >> > > >>> fact/ex
> >> > > >>> ported-artifacts/test_logs/basic-suite-master/post-001_initialize
> >> > > >>> _engine
> >> > > >>> _pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-imageio/
> >> > > >>> daemon.
> >> > > >>> log
> >> > > >>> 
> >> > > >>> 2020-04-27 09:25:39,887 INFO(MainThread) [server] Starting
> >> > > >>> (pid=17137, version=2.0.5) 2020-04-27 

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Nir Soffer]

On Mon, Apr 27, 2020 at 5:37 PM Sandro Bonazzola  wrote:
>
>
>
> Il giorno lun 27 apr 2020 alle ore 16:28 Nir Soffer  ha 
> scritto:
>>
>> On Mon, Apr 27, 2020 at 5:22 PM Vojtech Juranek  wrote:
>> >
>> > On pondělí 27. dubna 2020 16:10:11 CEST Nir Soffer wrote:
>> > > On Mon, Apr 27, 2020 at 5:01 PM Liran Rotenberg  
>> > > wrote:
>> > > > On Mon, Apr 27, 2020 at 4:58 PM Sandro Bonazzola 
>> > > >
>> > > > wrote:
>> > > >> Il giorno lun 27 apr 2020 alle ore 15:52 Nir Soffer 
>> > > >> 
>> > > >>
>> > > >> ha scritto:
>> > > >>> On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola 
>> > > >>> 
>> > > >>>
>> > > >>> wrote:
>> > >  Failing job is
>> > >  https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
>> > > 
>> > >  Here's the relevant log in engine-setup:
>> > > 
>> > > 
>> > >  2020-04-27 09:25:35,457-0400 DEBUG 
>> > >  otopi.plugins.otopi.services.systemd
>> > >  plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop',
>> > >  'ovirt-imageio.service'), executable='None', cwd='None', env=None
>> > >  2020-04-27 09:25:35,652-0400 DEBUG
>> > >  otopi.plugins.otopi.services.systemd plugin.executeRaw:863
>> > >  execute-result: ('/usr/bin/systemctl', 'stop',
>> > >  'ovirt-imageio.service'), rc=0 2020-04-27 09:25:35,653-0400 DEBUG
>> > >  otopi.plugins.otopi.services.systemd plugin.execute:921
>> > >  execute-output: ('/usr/bin/systemctl', 'stop',
>> > >  'ovirt-imageio.service') stdout:
>> > > 
>> > > 
>> > >  2020-04-27 09:25:35,653-0400 DEBUG 
>> > >  otopi.plugins.otopi.services.systemd
>> > >  plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'stop',
>> > >  'ovirt-imageio.service') stderr:
>> > > 
>> > > 
>> > >  2020-04-27 09:25:35,653-0400 DEBUG 
>> > >  otopi.plugins.otopi.services.systemd
>> > >  systemd.state:170 starting service ovirt-imageio 2020-04-27
>> > >  09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd
>> > >  plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start',
>> > >  'ovirt-imageio.service'), executable='None', cwd='None', env=None
>> > >  2020-04-27 09:25:36,631-0400 DEBUG
>> > >  otopi.plugins.otopi.services.systemd plugin.executeRaw:863
>> > >  execute-result: ('/usr/bin/systemctl', 'start',
>> > >  'ovirt-imageio.service'), rc=1 2020-04-27 09:25:36,632-0400 DEBUG
>> > >  otopi.plugins.otopi.services.systemd plugin.execute:921
>> > >  execute-output: ('/usr/bin/systemctl', 'start',
>> > >  'ovirt-imageio.service') stdout:
>> > > 
>> > > 
>> > >  2020-04-27 09:25:36,632-0400 DEBUG 
>> > >  otopi.plugins.otopi.services.systemd
>> > >  plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start',
>> > >  'ovirt-imageio.service') stderr: Job for ovirt-imageio.service 
>> > >  failed
>> > >  because the control process exited with error code. See "systemctl
>> > >  status ovirt-imageio.service" and "journalctl -xe" for details.
>> > > 
>> > >  2020-04-27 09:25:36,633-0400 DEBUG otopi.context
>> > >  context._executeMethod:145 method exception
>> > >  Traceback (most recent call last):
>> > >    File "/usr/lib/python3.6/site-packages/otopi/context.py", line 
>> > >  132,
>> > >    in _executeMethod
>> > >  method['method']()
>> > > 
>> > >    File
>> > >    
>> > >  "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovi
>> > >    rt_imageio/config.py", line 190, in _closeup_resatrt_service
>> > >  state=state,
>> > > 
>> > >    File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 
>> > >  181,
>> > >    in state
>> > >  service=name,
>> > > 
>> > >  RuntimeError: Failed to start service 'ovirt-imageio'
>> > >  2020-04-27 09:25:36,636-0400 ERROR otopi.context
>> > >  context._executeMethod:154 Failed to execute stage 'Closing up':
>> > >  Failed to start service 'ovirt-imageio'>>>
>> > > >>> Looking at the logs at:
>> > > >>>
>> > > >>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/ex
>> > > >>> ported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine
>> > > >>> _pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-imageio/daemon.
>> > > >>> log
>> > > >>>
>> > > >>> 2020-04-27 09:25:39,887 INFO(MainThread) [server] Starting
>> > > >>> (pid=17137, version=2.0.5) 2020-04-27 09:25:39,944 ERROR   
>> > > >>> (MainThread)
>> > > >>> [server] Server failed>>>
>> > > >>> Traceback (most recent call last):
>> > > >>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
>> > > >>>   line 37, in main>>>
>> > > >>> server = Server(cfg)
>> > > >>>
>> > > >>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
>> > > >>>   line 76, in __init__>>>
>> > > >>> self.remote_service = services.RemoteService(self.config, 
>> > > >>> 

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Sandro Bonazzola]

Il giorno lun 27 apr 2020 alle ore 16:28 Nir Soffer  ha
scritto:

> On Mon, Apr 27, 2020 at 5:22 PM Vojtech Juranek 
> wrote:
> >
> > On pondělí 27. dubna 2020 16:10:11 CEST Nir Soffer wrote:
> > > On Mon, Apr 27, 2020 at 5:01 PM Liran Rotenberg 
> wrote:
> > > > On Mon, Apr 27, 2020 at 4:58 PM Sandro Bonazzola <
> sbona...@redhat.com>
> > > >
> > > > wrote:
> > > >> Il giorno lun 27 apr 2020 alle ore 15:52 Nir Soffer <
> nsof...@redhat.com>
> > > >>
> > > >> ha scritto:
> > > >>> On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola <
> sbona...@redhat.com>
> > > >>>
> > > >>> wrote:
> > >  Failing job is
> > >  https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
> > > 
> > >  Here's the relevant log in engine-setup:
> > > 
> > > 
> > >  2020-04-27 09:25:35,457-0400 DEBUG
> otopi.plugins.otopi.services.systemd
> > >  plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop',
> > >  'ovirt-imageio.service'), executable='None', cwd='None', env=None
> > >  2020-04-27 09:25:35,652-0400 DEBUG
> > >  otopi.plugins.otopi.services.systemd plugin.executeRaw:863
> > >  execute-result: ('/usr/bin/systemctl', 'stop',
> > >  'ovirt-imageio.service'), rc=0 2020-04-27 09:25:35,653-0400 DEBUG
> > >  otopi.plugins.otopi.services.systemd plugin.execute:921
> > >  execute-output: ('/usr/bin/systemctl', 'stop',
> > >  'ovirt-imageio.service') stdout:
> > > 
> > > 
> > >  2020-04-27 09:25:35,653-0400 DEBUG
> otopi.plugins.otopi.services.systemd
> > >  plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'stop',
> > >  'ovirt-imageio.service') stderr:
> > > 
> > > 
> > >  2020-04-27 09:25:35,653-0400 DEBUG
> otopi.plugins.otopi.services.systemd
> > >  systemd.state:170 starting service ovirt-imageio 2020-04-27
> > >  09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd
> > >  plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start',
> > >  'ovirt-imageio.service'), executable='None', cwd='None', env=None
> > >  2020-04-27 09:25:36,631-0400 DEBUG
> > >  otopi.plugins.otopi.services.systemd plugin.executeRaw:863
> > >  execute-result: ('/usr/bin/systemctl', 'start',
> > >  'ovirt-imageio.service'), rc=1 2020-04-27 09:25:36,632-0400 DEBUG
> > >  otopi.plugins.otopi.services.systemd plugin.execute:921
> > >  execute-output: ('/usr/bin/systemctl', 'start',
> > >  'ovirt-imageio.service') stdout:
> > > 
> > > 
> > >  2020-04-27 09:25:36,632-0400 DEBUG
> otopi.plugins.otopi.services.systemd
> > >  plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start',
> > >  'ovirt-imageio.service') stderr: Job for ovirt-imageio.service
> failed
> > >  because the control process exited with error code. See "systemctl
> > >  status ovirt-imageio.service" and "journalctl -xe" for details.
> > > 
> > >  2020-04-27 09:25:36,633-0400 DEBUG otopi.context
> > >  context._executeMethod:145 method exception
> > >  Traceback (most recent call last):
> > >    File "/usr/lib/python3.6/site-packages/otopi/context.py", line
> 132,
> > >    in _executeMethod
> > >  method['method']()
> > > 
> > >    File
> > > 
>  "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovi
> > >    rt_imageio/config.py", line 190, in _closeup_resatrt_service
> > >  state=state,
> > > 
> > >    File "/usr/share/otopi/plugins/otopi/services/systemd.py", line
> 181,
> > >    in state
> > >  service=name,
> > > 
> > >  RuntimeError: Failed to start service 'ovirt-imageio'
> > >  2020-04-27 09:25:36,636-0400 ERROR otopi.context
> > >  context._executeMethod:154 Failed to execute stage 'Closing up':
> > >  Failed to start service 'ovirt-imageio'>>>
> > > >>> Looking at the logs at:
> > > >>>
> > > >>>
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/ex
> > > >>>
> ported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine
> > > >>> _
> pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-imageio/daemon.
> > > >>> log
> > > >>>
> > > >>> 2020-04-27 09:25:39,887 INFO(MainThread) [server] Starting
> > > >>> (pid=17137, version=2.0.5) 2020-04-27 09:25:39,944 ERROR
>  (MainThread)
> > > >>> [server] Server failed>>>
> > > >>> Traceback (most recent call last):
> > > >>>   File
> "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
> > > >>>   line 37, in main>>>
> > > >>> server = Server(cfg)
> > > >>>
> > > >>>   File
> "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
> > > >>>   line 76, in __init__>>>
> > > >>> self.remote_service = services.RemoteService(self.config,
> self.auth)
> > > >>>
> > > >>>   File
> "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py",
> > > >>>   line 80, in __init__>>>
> > > >>> self._secure_server()
> > > >>>
> > > >>>   File
> 

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Nir Soffer]

On Mon, Apr 27, 2020 at 5:29 PM Sandro Bonazzola 
wrote:

>
>
> Il giorno lun 27 apr 2020 alle ore 16:07 Nir Soffer 
> ha scritto:
>
>> On Mon, Apr 27, 2020 at 4:57 PM Sandro Bonazzola 
>> wrote:
>>
>>>
>>>
>>> Il giorno lun 27 apr 2020 alle ore 15:52 Nir Soffer 
>>> ha scritto:
>>>
 On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola 
 wrote:

> Failing job is 
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
>
> Here's the relevant log in engine-setup:
>
>
> 2020-04-27 09:25:35,457-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop', 
> 'ovirt-imageio.service'), executable='None', cwd='None', env=None
> 2020-04-27 09:25:35,652-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'stop', 
> 'ovirt-imageio.service'), rc=0
> 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'stop', 
> 'ovirt-imageio.service') stdout:
>
>
> 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'stop', 
> 'ovirt-imageio.service') stderr:
>
>
> 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
> systemd.state:170 starting service ovirt-imageio
> 2020-04-27 09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start', 
> 'ovirt-imageio.service'), executable='None', cwd='None', env=None
> 2020-04-27 09:25:36,631-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'start', 
> 'ovirt-imageio.service'), rc=1
> 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'start', 
> 'ovirt-imageio.service') stdout:
>
>
> 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 
> 'ovirt-imageio.service') stderr:
> Job for ovirt-imageio.service failed because the control process exited 
> with error code.
> See "systemctl status ovirt-imageio.service" and "journalctl -xe" for 
> details.
>
> 2020-04-27 09:25:36,633-0400 DEBUG otopi.context 
> context._executeMethod:145 method exception
> Traceback (most recent call last):
>   File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in 
> _executeMethod
> method['method']()
>   File 
> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt_imageio/config.py",
>  line 190, in _closeup_resatrt_service
> state=state,
>   File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 181, in 
> state
> service=name,
> RuntimeError: Failed to start service 'ovirt-imageio'
> 2020-04-27 09:25:36,636-0400 ERROR otopi.context 
> context._executeMethod:154 Failed to execute stage 'Closing up': Failed 
> to start service 'ovirt-imageio'
>
>
 Looking at the logs at:

 https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-imageio/daemon.log

 2020-04-27 09:25:39,887 INFO(MainThread) [server] Starting (pid=17137, 
 version=2.0.5)
 2020-04-27 09:25:39,944 ERROR   (MainThread) [server] Server failed
 Traceback (most recent call last):
   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line 
 37, in main
 server = Server(cfg)
   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line 
 76, in __init__
 self.remote_service = services.RemoteService(self.config, self.auth)
   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", 
 line 80, in __init__
 self._secure_server()
   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", 
 line 95, in _secure_server
 raise errors.TlsConfigurationError(*required_config)
 ovirt_imageio.errors.TlsConfigurationError: TLS enabled (see [tls] section 
 in daemon.conf), but not configured: ca_file = , cert_file = , key_file =

 This means engine-setup did not create correct configuration file.

 Looking in
 https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
 I don't see /etc/ovirt-imageio directory, maybe the collections scripts
 need update?

 This works in real setup, so I guess this is another OST environment
 issue.

>>>
>>>
>>> looking at dnf logs:
>>> 

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Sandro Bonazzola]

Il giorno lun 27 apr 2020 alle ore 16:07 Nir Soffer  ha
scritto:

> On Mon, Apr 27, 2020 at 4:57 PM Sandro Bonazzola 
> wrote:
>
>>
>>
>> Il giorno lun 27 apr 2020 alle ore 15:52 Nir Soffer 
>> ha scritto:
>>
>>> On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola 
>>> wrote:
>>>
 Failing job is 
 https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/

 Here's the relevant log in engine-setup:


 2020-04-27 09:25:35,457-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop', 
 'ovirt-imageio.service'), executable='None', cwd='None', env=None
 2020-04-27 09:25:35,652-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'stop', 
 'ovirt-imageio.service'), rc=0
 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'stop', 
 'ovirt-imageio.service') stdout:


 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'stop', 
 'ovirt-imageio.service') stderr:


 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
 systemd.state:170 starting service ovirt-imageio
 2020-04-27 09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start', 
 'ovirt-imageio.service'), executable='None', cwd='None', env=None
 2020-04-27 09:25:36,631-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'start', 
 'ovirt-imageio.service'), rc=1
 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'start', 
 'ovirt-imageio.service') stdout:


 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 
 'ovirt-imageio.service') stderr:
 Job for ovirt-imageio.service failed because the control process exited 
 with error code.
 See "systemctl status ovirt-imageio.service" and "journalctl -xe" for 
 details.

 2020-04-27 09:25:36,633-0400 DEBUG otopi.context 
 context._executeMethod:145 method exception
 Traceback (most recent call last):
   File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in 
 _executeMethod
 method['method']()
   File 
 "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt_imageio/config.py",
  line 190, in _closeup_resatrt_service
 state=state,
   File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 181, in 
 state
 service=name,
 RuntimeError: Failed to start service 'ovirt-imageio'
 2020-04-27 09:25:36,636-0400 ERROR otopi.context 
 context._executeMethod:154 Failed to execute stage 'Closing up': Failed to 
 start service 'ovirt-imageio'


>>> Looking at the logs at:
>>>
>>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-imageio/daemon.log
>>>
>>> 2020-04-27 09:25:39,887 INFO(MainThread) [server] Starting (pid=17137, 
>>> version=2.0.5)
>>> 2020-04-27 09:25:39,944 ERROR   (MainThread) [server] Server failed
>>> Traceback (most recent call last):
>>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line 
>>> 37, in main
>>> server = Server(cfg)
>>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line 
>>> 76, in __init__
>>> self.remote_service = services.RemoteService(self.config, self.auth)
>>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", line 
>>> 80, in __init__
>>> self._secure_server()
>>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", line 
>>> 95, in _secure_server
>>> raise errors.TlsConfigurationError(*required_config)
>>> ovirt_imageio.errors.TlsConfigurationError: TLS enabled (see [tls] section 
>>> in daemon.conf), but not configured: ca_file = , cert_file = , key_file =
>>>
>>> This means engine-setup did not create correct configuration file.
>>>
>>> Looking in https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
>>> I don't see /etc/ovirt-imageio directory, maybe the collections scripts
>>> need update?
>>>
>>> This works in real setup, so I guess this is another OST environment
>>> issue.
>>>
>>
>>
>> looking at dnf logs:
>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_pytest.py/lago-basic-suite-master-engine/_var_log/dnf.rpm.log
>>
>> 2020-04-27T13:16:13Z SUBDEBUG 

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Nir Soffer]

On Mon, Apr 27, 2020 at 5:22 PM Vojtech Juranek  wrote:
>
> On pondělí 27. dubna 2020 16:10:11 CEST Nir Soffer wrote:
> > On Mon, Apr 27, 2020 at 5:01 PM Liran Rotenberg  wrote:
> > > On Mon, Apr 27, 2020 at 4:58 PM Sandro Bonazzola 
> > >
> > > wrote:
> > >> Il giorno lun 27 apr 2020 alle ore 15:52 Nir Soffer 
> > >>
> > >> ha scritto:
> > >>> On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola 
> > >>>
> > >>> wrote:
> >  Failing job is
> >  https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
> > 
> >  Here's the relevant log in engine-setup:
> > 
> > 
> >  2020-04-27 09:25:35,457-0400 DEBUG otopi.plugins.otopi.services.systemd
> >  plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop',
> >  'ovirt-imageio.service'), executable='None', cwd='None', env=None
> >  2020-04-27 09:25:35,652-0400 DEBUG
> >  otopi.plugins.otopi.services.systemd plugin.executeRaw:863
> >  execute-result: ('/usr/bin/systemctl', 'stop',
> >  'ovirt-imageio.service'), rc=0 2020-04-27 09:25:35,653-0400 DEBUG
> >  otopi.plugins.otopi.services.systemd plugin.execute:921
> >  execute-output: ('/usr/bin/systemctl', 'stop',
> >  'ovirt-imageio.service') stdout:
> > 
> > 
> >  2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd
> >  plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'stop',
> >  'ovirt-imageio.service') stderr:
> > 
> > 
> >  2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd
> >  systemd.state:170 starting service ovirt-imageio 2020-04-27
> >  09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd
> >  plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start',
> >  'ovirt-imageio.service'), executable='None', cwd='None', env=None
> >  2020-04-27 09:25:36,631-0400 DEBUG
> >  otopi.plugins.otopi.services.systemd plugin.executeRaw:863
> >  execute-result: ('/usr/bin/systemctl', 'start',
> >  'ovirt-imageio.service'), rc=1 2020-04-27 09:25:36,632-0400 DEBUG
> >  otopi.plugins.otopi.services.systemd plugin.execute:921
> >  execute-output: ('/usr/bin/systemctl', 'start',
> >  'ovirt-imageio.service') stdout:
> > 
> > 
> >  2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd
> >  plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start',
> >  'ovirt-imageio.service') stderr: Job for ovirt-imageio.service failed
> >  because the control process exited with error code. See "systemctl
> >  status ovirt-imageio.service" and "journalctl -xe" for details.
> > 
> >  2020-04-27 09:25:36,633-0400 DEBUG otopi.context
> >  context._executeMethod:145 method exception
> >  Traceback (most recent call last):
> >    File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132,
> >    in _executeMethod
> >  method['method']()
> > 
> >    File
> >    "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovi
> >    rt_imageio/config.py", line 190, in _closeup_resatrt_service
> >  state=state,
> > 
> >    File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 181,
> >    in state
> >  service=name,
> > 
> >  RuntimeError: Failed to start service 'ovirt-imageio'
> >  2020-04-27 09:25:36,636-0400 ERROR otopi.context
> >  context._executeMethod:154 Failed to execute stage 'Closing up':
> >  Failed to start service 'ovirt-imageio'>>>
> > >>> Looking at the logs at:
> > >>>
> > >>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/ex
> > >>> ported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine
> > >>> _pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-imageio/daemon.
> > >>> log
> > >>>
> > >>> 2020-04-27 09:25:39,887 INFO(MainThread) [server] Starting
> > >>> (pid=17137, version=2.0.5) 2020-04-27 09:25:39,944 ERROR   (MainThread)
> > >>> [server] Server failed>>>
> > >>> Traceback (most recent call last):
> > >>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
> > >>>   line 37, in main>>>
> > >>> server = Server(cfg)
> > >>>
> > >>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
> > >>>   line 76, in __init__>>>
> > >>> self.remote_service = services.RemoteService(self.config, self.auth)
> > >>>
> > >>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py",
> > >>>   line 80, in __init__>>>
> > >>> self._secure_server()
> > >>>
> > >>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py",
> > >>>   line 95, in _secure_server>>>
> > >>> raise errors.TlsConfigurationError(*required_config)
> > >>>
> > >>> ovirt_imageio.errors.TlsConfigurationError: TLS enabled (see [tls]
> > >>> section in daemon.conf), but not configured: ca_file = , cert_file = ,
> > >>> key_file =
> > >>>
> > >>> This means engine-setup did not 

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Vojtech Juranek]

On pondělí 27. dubna 2020 16:10:11 CEST Nir Soffer wrote:
> On Mon, Apr 27, 2020 at 5:01 PM Liran Rotenberg  wrote:
> > On Mon, Apr 27, 2020 at 4:58 PM Sandro Bonazzola 
> > 
> > wrote:
> >> Il giorno lun 27 apr 2020 alle ore 15:52 Nir Soffer 
> >> 
> >> ha scritto:
> >>> On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola 
> >>> 
> >>> wrote:
>  Failing job is
>  https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
>  
>  Here's the relevant log in engine-setup:
>  
>  
>  2020-04-27 09:25:35,457-0400 DEBUG otopi.plugins.otopi.services.systemd
>  plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop',
>  'ovirt-imageio.service'), executable='None', cwd='None', env=None
>  2020-04-27 09:25:35,652-0400 DEBUG
>  otopi.plugins.otopi.services.systemd plugin.executeRaw:863
>  execute-result: ('/usr/bin/systemctl', 'stop',
>  'ovirt-imageio.service'), rc=0 2020-04-27 09:25:35,653-0400 DEBUG
>  otopi.plugins.otopi.services.systemd plugin.execute:921
>  execute-output: ('/usr/bin/systemctl', 'stop',
>  'ovirt-imageio.service') stdout:
>  
>  
>  2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd
>  plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'stop',
>  'ovirt-imageio.service') stderr:
>  
>  
>  2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd
>  systemd.state:170 starting service ovirt-imageio 2020-04-27
>  09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd
>  plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start',
>  'ovirt-imageio.service'), executable='None', cwd='None', env=None
>  2020-04-27 09:25:36,631-0400 DEBUG
>  otopi.plugins.otopi.services.systemd plugin.executeRaw:863
>  execute-result: ('/usr/bin/systemctl', 'start',
>  'ovirt-imageio.service'), rc=1 2020-04-27 09:25:36,632-0400 DEBUG
>  otopi.plugins.otopi.services.systemd plugin.execute:921
>  execute-output: ('/usr/bin/systemctl', 'start',
>  'ovirt-imageio.service') stdout:
>  
>  
>  2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd
>  plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start',
>  'ovirt-imageio.service') stderr: Job for ovirt-imageio.service failed
>  because the control process exited with error code. See "systemctl
>  status ovirt-imageio.service" and "journalctl -xe" for details.
>  
>  2020-04-27 09:25:36,633-0400 DEBUG otopi.context
>  context._executeMethod:145 method exception 
>  Traceback (most recent call last):
>    File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132,
>    in _executeMethod   
>  method['method']()
>    
>    File
>    "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovi
>    rt_imageio/config.py", line 190, in _closeup_resatrt_service   
>  state=state,
>    
>    File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 181,
>    in state   
>  service=name,
>  
>  RuntimeError: Failed to start service 'ovirt-imageio'
>  2020-04-27 09:25:36,636-0400 ERROR otopi.context
>  context._executeMethod:154 Failed to execute stage 'Closing up':
>  Failed to start service 'ovirt-imageio'>>> 
> >>> Looking at the logs at:
> >>> 
> >>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/ex
> >>> ported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine
> >>> _pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-imageio/daemon.
> >>> log
> >>> 
> >>> 2020-04-27 09:25:39,887 INFO(MainThread) [server] Starting
> >>> (pid=17137, version=2.0.5) 2020-04-27 09:25:39,944 ERROR   (MainThread)
> >>> [server] Server failed>>> 
> >>> Traceback (most recent call last):
> >>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
> >>>   line 37, in main>>>   
> >>> server = Server(cfg)
> >>>   
> >>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
> >>>   line 76, in __init__>>>   
> >>> self.remote_service = services.RemoteService(self.config, self.auth)
> >>>   
> >>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py",
> >>>   line 80, in __init__>>>   
> >>> self._secure_server()
> >>>   
> >>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py",
> >>>   line 95, in _secure_server>>>   
> >>> raise errors.TlsConfigurationError(*required_config)
> >>> 
> >>> ovirt_imageio.errors.TlsConfigurationError: TLS enabled (see [tls]
> >>> section in daemon.conf), but not configured: ca_file = , cert_file = ,
> >>> key_file =
> >>> 
> >>> This means engine-setup did not create correct configuration file.
> >>> 
> >>> Looking in https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
> >>> I don't see /etc/ovirt-imageio directory, maybe the collections scripts
> >>> need 

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Nir Soffer]

On Mon, Apr 27, 2020 at 5:01 PM Liran Rotenberg  wrote:

>
>
> On Mon, Apr 27, 2020 at 4:58 PM Sandro Bonazzola 
> wrote:
>
>>
>>
>> Il giorno lun 27 apr 2020 alle ore 15:52 Nir Soffer 
>> ha scritto:
>>
>>> On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola 
>>> wrote:
>>>
 Failing job is 
 https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/

 Here's the relevant log in engine-setup:


 2020-04-27 09:25:35,457-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop', 
 'ovirt-imageio.service'), executable='None', cwd='None', env=None
 2020-04-27 09:25:35,652-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'stop', 
 'ovirt-imageio.service'), rc=0
 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'stop', 
 'ovirt-imageio.service') stdout:


 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'stop', 
 'ovirt-imageio.service') stderr:


 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
 systemd.state:170 starting service ovirt-imageio
 2020-04-27 09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start', 
 'ovirt-imageio.service'), executable='None', cwd='None', env=None
 2020-04-27 09:25:36,631-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'start', 
 'ovirt-imageio.service'), rc=1
 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'start', 
 'ovirt-imageio.service') stdout:


 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 
 'ovirt-imageio.service') stderr:
 Job for ovirt-imageio.service failed because the control process exited 
 with error code.
 See "systemctl status ovirt-imageio.service" and "journalctl -xe" for 
 details.

 2020-04-27 09:25:36,633-0400 DEBUG otopi.context 
 context._executeMethod:145 method exception
 Traceback (most recent call last):
   File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in 
 _executeMethod
 method['method']()
   File 
 "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt_imageio/config.py",
  line 190, in _closeup_resatrt_service
 state=state,
   File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 181, in 
 state
 service=name,
 RuntimeError: Failed to start service 'ovirt-imageio'
 2020-04-27 09:25:36,636-0400 ERROR otopi.context 
 context._executeMethod:154 Failed to execute stage 'Closing up': Failed to 
 start service 'ovirt-imageio'


>>> Looking at the logs at:
>>>
>>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-imageio/daemon.log
>>>
>>> 2020-04-27 09:25:39,887 INFO(MainThread) [server] Starting (pid=17137, 
>>> version=2.0.5)
>>> 2020-04-27 09:25:39,944 ERROR   (MainThread) [server] Server failed
>>> Traceback (most recent call last):
>>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line 
>>> 37, in main
>>> server = Server(cfg)
>>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line 
>>> 76, in __init__
>>> self.remote_service = services.RemoteService(self.config, self.auth)
>>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", line 
>>> 80, in __init__
>>> self._secure_server()
>>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", line 
>>> 95, in _secure_server
>>> raise errors.TlsConfigurationError(*required_config)
>>> ovirt_imageio.errors.TlsConfigurationError: TLS enabled (see [tls] section 
>>> in daemon.conf), but not configured: ca_file = , cert_file = , key_file =
>>>
>>> This means engine-setup did not create correct configuration file.
>>>
>>> Looking in https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
>>> I don't see /etc/ovirt-imageio directory, maybe the collections scripts
>>> need update?
>>>
>>> This works in real setup, so I guess this is another OST environment
>>> issue.
>>>
>>
>>
>> looking at dnf logs:
>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_pytest.py/lago-basic-suite-master-engine/_var_log/dnf.rpm.log
>>
>> 2020-04-27T13:16:13Z SUBDEBUG 

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Nir Soffer]

On Mon, Apr 27, 2020 at 4:57 PM Sandro Bonazzola 
wrote:

>
>
> Il giorno lun 27 apr 2020 alle ore 15:52 Nir Soffer 
> ha scritto:
>
>> On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola 
>> wrote:
>>
>>> Failing job is https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
>>>
>>> Here's the relevant log in engine-setup:
>>>
>>>
>>> 2020-04-27 09:25:35,457-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop', 
>>> 'ovirt-imageio.service'), executable='None', cwd='None', env=None
>>> 2020-04-27 09:25:35,652-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'stop', 
>>> 'ovirt-imageio.service'), rc=0
>>> 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'stop', 
>>> 'ovirt-imageio.service') stdout:
>>>
>>>
>>> 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'stop', 
>>> 'ovirt-imageio.service') stderr:
>>>
>>>
>>> 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> systemd.state:170 starting service ovirt-imageio
>>> 2020-04-27 09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start', 
>>> 'ovirt-imageio.service'), executable='None', cwd='None', env=None
>>> 2020-04-27 09:25:36,631-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'start', 
>>> 'ovirt-imageio.service'), rc=1
>>> 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'start', 
>>> 'ovirt-imageio.service') stdout:
>>>
>>>
>>> 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 
>>> 'ovirt-imageio.service') stderr:
>>> Job for ovirt-imageio.service failed because the control process exited 
>>> with error code.
>>> See "systemctl status ovirt-imageio.service" and "journalctl -xe" for 
>>> details.
>>>
>>> 2020-04-27 09:25:36,633-0400 DEBUG otopi.context context._executeMethod:145 
>>> method exception
>>> Traceback (most recent call last):
>>>   File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in 
>>> _executeMethod
>>> method['method']()
>>>   File 
>>> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt_imageio/config.py",
>>>  line 190, in _closeup_resatrt_service
>>> state=state,
>>>   File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 181, in 
>>> state
>>> service=name,
>>> RuntimeError: Failed to start service 'ovirt-imageio'
>>> 2020-04-27 09:25:36,636-0400 ERROR otopi.context context._executeMethod:154 
>>> Failed to execute stage 'Closing up': Failed to start service 
>>> 'ovirt-imageio'
>>>
>>>
>> Looking at the logs at:
>>
>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-imageio/daemon.log
>>
>> 2020-04-27 09:25:39,887 INFO(MainThread) [server] Starting (pid=17137, 
>> version=2.0.5)
>> 2020-04-27 09:25:39,944 ERROR   (MainThread) [server] Server failed
>> Traceback (most recent call last):
>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line 
>> 37, in main
>> server = Server(cfg)
>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line 
>> 76, in __init__
>> self.remote_service = services.RemoteService(self.config, self.auth)
>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", line 
>> 80, in __init__
>> self._secure_server()
>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", line 
>> 95, in _secure_server
>> raise errors.TlsConfigurationError(*required_config)
>> ovirt_imageio.errors.TlsConfigurationError: TLS enabled (see [tls] section 
>> in daemon.conf), but not configured: ca_file = , cert_file = , key_file =
>>
>> This means engine-setup did not create correct configuration file.
>>
>> Looking in https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
>> I don't see /etc/ovirt-imageio directory, maybe the collections scripts
>> need update?
>>
>> This works in real setup, so I guess this is another OST environment
>> issue.
>>
>
>
> looking at dnf logs:
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_pytest.py/lago-basic-suite-master-engine/_var_log/dnf.rpm.log
>
> 2020-04-27T13:16:13Z SUBDEBUG Installed: 
> ovirt-imageio-common-2.0.5-0.202004260154.gitaf86468.el8.x86_64
> 2020-04-27T13:16:13Z SUBDEBUG Installed: 
> 

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Benny Zlotnik]

you don't need to do this with this patch applied:
https://gerrit.ovirt.org/#/c/108582/

On Mon, Apr 27, 2020 at 5:02 PM Liran Rotenberg  wrote:

>
>
> On Mon, Apr 27, 2020 at 4:58 PM Sandro Bonazzola 
> wrote:
>
>>
>>
>> Il giorno lun 27 apr 2020 alle ore 15:52 Nir Soffer 
>> ha scritto:
>>
>>> On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola 
>>> wrote:
>>>
 Failing job is 
 https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/

 Here's the relevant log in engine-setup:


 2020-04-27 09:25:35,457-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop', 
 'ovirt-imageio.service'), executable='None', cwd='None', env=None
 2020-04-27 09:25:35,652-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'stop', 
 'ovirt-imageio.service'), rc=0
 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'stop', 
 'ovirt-imageio.service') stdout:


 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'stop', 
 'ovirt-imageio.service') stderr:


 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
 systemd.state:170 starting service ovirt-imageio
 2020-04-27 09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start', 
 'ovirt-imageio.service'), executable='None', cwd='None', env=None
 2020-04-27 09:25:36,631-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'start', 
 'ovirt-imageio.service'), rc=1
 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'start', 
 'ovirt-imageio.service') stdout:


 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
 plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 
 'ovirt-imageio.service') stderr:
 Job for ovirt-imageio.service failed because the control process exited 
 with error code.
 See "systemctl status ovirt-imageio.service" and "journalctl -xe" for 
 details.

 2020-04-27 09:25:36,633-0400 DEBUG otopi.context 
 context._executeMethod:145 method exception
 Traceback (most recent call last):
   File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in 
 _executeMethod
 method['method']()
   File 
 "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt_imageio/config.py",
  line 190, in _closeup_resatrt_service
 state=state,
   File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 181, in 
 state
 service=name,
 RuntimeError: Failed to start service 'ovirt-imageio'
 2020-04-27 09:25:36,636-0400 ERROR otopi.context 
 context._executeMethod:154 Failed to execute stage 'Closing up': Failed to 
 start service 'ovirt-imageio'


>>> Looking at the logs at:
>>>
>>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-imageio/daemon.log
>>>
>>> 2020-04-27 09:25:39,887 INFO(MainThread) [server] Starting (pid=17137, 
>>> version=2.0.5)
>>> 2020-04-27 09:25:39,944 ERROR   (MainThread) [server] Server failed
>>> Traceback (most recent call last):
>>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line 
>>> 37, in main
>>> server = Server(cfg)
>>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line 
>>> 76, in __init__
>>> self.remote_service = services.RemoteService(self.config, self.auth)
>>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", line 
>>> 80, in __init__
>>> self._secure_server()
>>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", line 
>>> 95, in _secure_server
>>> raise errors.TlsConfigurationError(*required_config)
>>> ovirt_imageio.errors.TlsConfigurationError: TLS enabled (see [tls] section 
>>> in daemon.conf), but not configured: ca_file = , cert_file = , key_file =
>>>
>>> This means engine-setup did not create correct configuration file.
>>>
>>> Looking in https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
>>> I don't see /etc/ovirt-imageio directory, maybe the collections scripts
>>> need update?
>>>
>>> This works in real setup, so I guess this is another OST environment
>>> issue.
>>>
>>
>>
>> looking at dnf logs:
>> 

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Liran Rotenberg]

On Mon, Apr 27, 2020 at 4:58 PM Sandro Bonazzola 
wrote:

>
>
> Il giorno lun 27 apr 2020 alle ore 15:52 Nir Soffer 
> ha scritto:
>
>> On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola 
>> wrote:
>>
>>> Failing job is https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
>>>
>>> Here's the relevant log in engine-setup:
>>>
>>>
>>> 2020-04-27 09:25:35,457-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop', 
>>> 'ovirt-imageio.service'), executable='None', cwd='None', env=None
>>> 2020-04-27 09:25:35,652-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'stop', 
>>> 'ovirt-imageio.service'), rc=0
>>> 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'stop', 
>>> 'ovirt-imageio.service') stdout:
>>>
>>>
>>> 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'stop', 
>>> 'ovirt-imageio.service') stderr:
>>>
>>>
>>> 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> systemd.state:170 starting service ovirt-imageio
>>> 2020-04-27 09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start', 
>>> 'ovirt-imageio.service'), executable='None', cwd='None', env=None
>>> 2020-04-27 09:25:36,631-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'start', 
>>> 'ovirt-imageio.service'), rc=1
>>> 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'start', 
>>> 'ovirt-imageio.service') stdout:
>>>
>>>
>>> 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
>>> plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 
>>> 'ovirt-imageio.service') stderr:
>>> Job for ovirt-imageio.service failed because the control process exited 
>>> with error code.
>>> See "systemctl status ovirt-imageio.service" and "journalctl -xe" for 
>>> details.
>>>
>>> 2020-04-27 09:25:36,633-0400 DEBUG otopi.context context._executeMethod:145 
>>> method exception
>>> Traceback (most recent call last):
>>>   File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in 
>>> _executeMethod
>>> method['method']()
>>>   File 
>>> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt_imageio/config.py",
>>>  line 190, in _closeup_resatrt_service
>>> state=state,
>>>   File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 181, in 
>>> state
>>> service=name,
>>> RuntimeError: Failed to start service 'ovirt-imageio'
>>> 2020-04-27 09:25:36,636-0400 ERROR otopi.context context._executeMethod:154 
>>> Failed to execute stage 'Closing up': Failed to start service 
>>> 'ovirt-imageio'
>>>
>>>
>> Looking at the logs at:
>>
>> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-imageio/daemon.log
>>
>> 2020-04-27 09:25:39,887 INFO(MainThread) [server] Starting (pid=17137, 
>> version=2.0.5)
>> 2020-04-27 09:25:39,944 ERROR   (MainThread) [server] Server failed
>> Traceback (most recent call last):
>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line 
>> 37, in main
>> server = Server(cfg)
>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line 
>> 76, in __init__
>> self.remote_service = services.RemoteService(self.config, self.auth)
>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", line 
>> 80, in __init__
>> self._secure_server()
>>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", line 
>> 95, in _secure_server
>> raise errors.TlsConfigurationError(*required_config)
>> ovirt_imageio.errors.TlsConfigurationError: TLS enabled (see [tls] section 
>> in daemon.conf), but not configured: ca_file = , cert_file = , key_file =
>>
>> This means engine-setup did not create correct configuration file.
>>
>> Looking in https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
>> I don't see /etc/ovirt-imageio directory, maybe the collections scripts
>> need update?
>>
>> This works in real setup, so I guess this is another OST environment
>> issue.
>>
>
>
> looking at dnf logs:
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_pytest.py/lago-basic-suite-master-engine/_var_log/dnf.rpm.log
>
> 2020-04-27T13:16:13Z SUBDEBUG Installed: 
> ovirt-imageio-common-2.0.5-0.202004260154.gitaf86468.el8.x86_64
> 2020-04-27T13:16:13Z SUBDEBUG Installed: 
> 

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Sandro Bonazzola]

Il giorno lun 27 apr 2020 alle ore 15:52 Nir Soffer  ha
scritto:

> On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola 
> wrote:
>
>> Failing job is https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
>>
>> Here's the relevant log in engine-setup:
>>
>>
>> 2020-04-27 09:25:35,457-0400 DEBUG otopi.plugins.otopi.services.systemd 
>> plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop', 
>> 'ovirt-imageio.service'), executable='None', cwd='None', env=None
>> 2020-04-27 09:25:35,652-0400 DEBUG otopi.plugins.otopi.services.systemd 
>> plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'stop', 
>> 'ovirt-imageio.service'), rc=0
>> 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
>> plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'stop', 
>> 'ovirt-imageio.service') stdout:
>>
>>
>> 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
>> plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'stop', 
>> 'ovirt-imageio.service') stderr:
>>
>>
>> 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
>> systemd.state:170 starting service ovirt-imageio
>> 2020-04-27 09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd 
>> plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start', 
>> 'ovirt-imageio.service'), executable='None', cwd='None', env=None
>> 2020-04-27 09:25:36,631-0400 DEBUG otopi.plugins.otopi.services.systemd 
>> plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'start', 
>> 'ovirt-imageio.service'), rc=1
>> 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
>> plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'start', 
>> 'ovirt-imageio.service') stdout:
>>
>>
>> 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
>> plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 
>> 'ovirt-imageio.service') stderr:
>> Job for ovirt-imageio.service failed because the control process exited with 
>> error code.
>> See "systemctl status ovirt-imageio.service" and "journalctl -xe" for 
>> details.
>>
>> 2020-04-27 09:25:36,633-0400 DEBUG otopi.context context._executeMethod:145 
>> method exception
>> Traceback (most recent call last):
>>   File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in 
>> _executeMethod
>> method['method']()
>>   File 
>> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt_imageio/config.py",
>>  line 190, in _closeup_resatrt_service
>> state=state,
>>   File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 181, in 
>> state
>> service=name,
>> RuntimeError: Failed to start service 'ovirt-imageio'
>> 2020-04-27 09:25:36,636-0400 ERROR otopi.context context._executeMethod:154 
>> Failed to execute stage 'Closing up': Failed to start service 'ovirt-imageio'
>>
>>
> Looking at the logs at:
>
> https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-imageio/daemon.log
>
> 2020-04-27 09:25:39,887 INFO(MainThread) [server] Starting (pid=17137, 
> version=2.0.5)
> 2020-04-27 09:25:39,944 ERROR   (MainThread) [server] Server failed
> Traceback (most recent call last):
>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line 37, 
> in main
> server = Server(cfg)
>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py", line 76, 
> in __init__
> self.remote_service = services.RemoteService(self.config, self.auth)
>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", line 
> 80, in __init__
> self._secure_server()
>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py", line 
> 95, in _secure_server
> raise errors.TlsConfigurationError(*required_config)
> ovirt_imageio.errors.TlsConfigurationError: TLS enabled (see [tls] section in 
> daemon.conf), but not configured: ca_file = , cert_file = , key_file =
>
> This means engine-setup did not create correct configuration file.
>
> Looking in https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
> I don't see /etc/ovirt-imageio directory, maybe the collections scripts
> need update?
>
> This works in real setup, so I guess this is another OST environment issue.
>


looking at dnf logs:
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_pytest.py/lago-basic-suite-master-engine/_var_log/dnf.rpm.log

2020-04-27T13:16:13Z SUBDEBUG Installed:
ovirt-imageio-common-2.0.5-0.202004260154.gitaf86468.el8.x86_64
2020-04-27T13:16:13Z SUBDEBUG Installed:
ovirt-imageio-common-2.0.5-0.202004260154.gitaf86468.el8.x86_64
2020-04-27T13:16:13Z SUBDEBUG Installed:
ovirt-imageio-daemon-2.0.5-0.202004260154.gitaf86468.el8.x86_64
2020-04-27T13:16:14Z SUBDEBUG Installed:

[ovirt-devel] Re: engine-setup failing on restarting ovirt-imageio

[Nir Soffer]

On Mon, Apr 27, 2020 at 4:42 PM Sandro Bonazzola 
wrote:

> Failing job is https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
>
> Here's the relevant log in engine-setup:
>
>
> 2020-04-27 09:25:35,457-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'stop', 
> 'ovirt-imageio.service'), executable='None', cwd='None', env=None
> 2020-04-27 09:25:35,652-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'stop', 
> 'ovirt-imageio.service'), rc=0
> 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'stop', 
> 'ovirt-imageio.service') stdout:
>
>
> 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'stop', 
> 'ovirt-imageio.service') stderr:
>
>
> 2020-04-27 09:25:35,653-0400 DEBUG otopi.plugins.otopi.services.systemd 
> systemd.state:170 starting service ovirt-imageio
> 2020-04-27 09:25:35,654-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start', 
> 'ovirt-imageio.service'), executable='None', cwd='None', env=None
> 2020-04-27 09:25:36,631-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'start', 
> 'ovirt-imageio.service'), rc=1
> 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'start', 
> 'ovirt-imageio.service') stdout:
>
>
> 2020-04-27 09:25:36,632-0400 DEBUG otopi.plugins.otopi.services.systemd 
> plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 
> 'ovirt-imageio.service') stderr:
> Job for ovirt-imageio.service failed because the control process exited with 
> error code.
> See "systemctl status ovirt-imageio.service" and "journalctl -xe" for details.
>
> 2020-04-27 09:25:36,633-0400 DEBUG otopi.context context._executeMethod:145 
> method exception
> Traceback (most recent call last):
>   File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132, in 
> _executeMethod
> method['method']()
>   File 
> "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt_imageio/config.py",
>  line 190, in _closeup_resatrt_service
> state=state,
>   File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 181, in 
> state
> service=name,
> RuntimeError: Failed to start service 'ovirt-imageio'
> 2020-04-27 09:25:36,636-0400 ERROR otopi.context context._executeMethod:154 
> Failed to execute stage 'Closing up': Failed to start service 'ovirt-imageio'
>
>
Looking at the logs at:
https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/artifact/exported-artifacts/test_logs/basic-suite-master/post-001_initialize_engine_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-imageio/daemon.log

2020-04-27 09:25:39,887 INFO(MainThread) [server] Starting
(pid=17137, version=2.0.5)
2020-04-27 09:25:39,944 ERROR   (MainThread) [server] Server failed
Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
line 37, in main
server = Server(cfg)
  File "/usr/lib64/python3.6/site-packages/ovirt_imageio/server.py",
line 76, in __init__
self.remote_service = services.RemoteService(self.config, self.auth)
  File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py",
line 80, in __init__
self._secure_server()
  File "/usr/lib64/python3.6/site-packages/ovirt_imageio/services.py",
line 95, in _secure_server
raise errors.TlsConfigurationError(*required_config)
ovirt_imageio.errors.TlsConfigurationError: TLS enabled (see [tls]
section in daemon.conf), but not configured: ca_file = , cert_file = ,
key_file =

This means engine-setup did not create correct configuration file.

Looking in https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/
I don't see /etc/ovirt-imageio directory, maybe the collections scripts
need update?

This works in real setup, so I guess this is another OST environment issue.

Nir

-- 
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
>
> Red Hat EMEA 
>
> sbona...@redhat.com
> *
> *
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.*
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/2ZZNXTIEJC3EBHOOJ5RGHLABAQ7AK74F/

[ovirt-devel] engine-setup failing on restarting ovirt-imageio

[Sandro Bonazzola]

Failing job is https://jenkins.ovirt.org/job/ovirt-system-tests_manual/6794/

Here's the relevant log in engine-setup:


2020-04-27 09:25:35,457-0400 DEBUG
otopi.plugins.otopi.services.systemd plugin.executeRaw:813 execute:
('/usr/bin/systemctl', 'stop', 'ovirt-imageio.service'),
executable='None', cwd='None', env=None
2020-04-27 09:25:35,652-0400 DEBUG
otopi.plugins.otopi.services.systemd plugin.executeRaw:863
execute-result: ('/usr/bin/systemctl', 'stop',
'ovirt-imageio.service'), rc=0
2020-04-27 09:25:35,653-0400 DEBUG
otopi.plugins.otopi.services.systemd plugin.execute:921
execute-output: ('/usr/bin/systemctl', 'stop',
'ovirt-imageio.service') stdout:


2020-04-27 09:25:35,653-0400 DEBUG
otopi.plugins.otopi.services.systemd plugin.execute:926
execute-output: ('/usr/bin/systemctl', 'stop',
'ovirt-imageio.service') stderr:


2020-04-27 09:25:35,653-0400 DEBUG
otopi.plugins.otopi.services.systemd systemd.state:170 starting
service ovirt-imageio
2020-04-27 09:25:35,654-0400 DEBUG
otopi.plugins.otopi.services.systemd plugin.executeRaw:813 execute:
('/usr/bin/systemctl', 'start', 'ovirt-imageio.service'),
executable='None', cwd='None', env=None
2020-04-27 09:25:36,631-0400 DEBUG
otopi.plugins.otopi.services.systemd plugin.executeRaw:863
execute-result: ('/usr/bin/systemctl', 'start',
'ovirt-imageio.service'), rc=1
2020-04-27 09:25:36,632-0400 DEBUG
otopi.plugins.otopi.services.systemd plugin.execute:921
execute-output: ('/usr/bin/systemctl', 'start',
'ovirt-imageio.service') stdout:


2020-04-27 09:25:36,632-0400 DEBUG
otopi.plugins.otopi.services.systemd plugin.execute:926
execute-output: ('/usr/bin/systemctl', 'start',
'ovirt-imageio.service') stderr:
Job for ovirt-imageio.service failed because the control process
exited with error code.
See "systemctl status ovirt-imageio.service" and "journalctl -xe" for details.

2020-04-27 09:25:36,633-0400 DEBUG otopi.context
context._executeMethod:145 method exception
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/otopi/context.py", line 132,
in _executeMethod
method['method']()
  File 
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt_imageio/config.py",
line 190, in _closeup_resatrt_service
state=state,
  File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 181, in state
service=name,
RuntimeError: Failed to start service 'ovirt-imageio'
2020-04-27 09:25:36,636-0400 ERROR otopi.context
context._executeMethod:154 Failed to execute stage 'Closing up':
Failed to start service 'ovirt-imageio'


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com
*
*
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SXZFV4YKGDOBAP5UGH5M3AAHCJKPEUME/

[ovirt-devel] Re: Uploading iso / ovirt-imageio

[Artur Socha]

On Mon, 2020-04-27 at 13:20 +0200, Artur Socha wrote:
> Upload solved with: 
> https://github.com/oVirt/ovirt-engine-/blob/master/sdk/examples/upload_disk.py

The url above is incomplete.  Here is the corrected one.

https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_disk.py


Artur



> 
> Artur
> 
> On Mon, 2020-04-27 at 11:23 +0200, Artur Socha wrote:
> > Hi,
> > After a long break I am trying setup my engine so that I could upload images
> > (ISO) there and use them when spinning new VMs. First I tried recent master
> > (FC31) and then latest 4.4 beta from RPMs (Centos8).
> > 
> > I have ovirt-imageio daemon running on the same host engine is running.
> > (with
> > the simplest possible configuration - TLS disabled)
> > 
> > Unfortunately when I hit 'test connection' in admin ui/storage/domain I keep
> > seeing error message complaining about ovirt-imageio-proxy setup. 
> > I know that recently there has been quite a lot of changes related to the
> > next
> > version of imageio. 
> > 
> > Is there something else besides ovirt-imageio daemon that I should have
> > installed/configured?  Perhaps there is some documentation I could use?
> > 
> > 
> > thanks!
> > 


signature.asc
Description: This is a digitally signed message part
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/FFPEIFI7RVJ7FD234ZF7OSLIHZHVIE2I/

[ovirt-devel] Re: Uploading iso / ovirt-imageio

[Artur Socha]

Upload solved with: 
https://github.com/oVirt/ovirt-engine-/blob/master/sdk/examples/upload_disk.py

Artur

On Mon, 2020-04-27 at 11:23 +0200, Artur Socha wrote:
> Hi,
> After a long break I am trying setup my engine so that I could upload images
> (ISO) there and use them when spinning new VMs. First I tried recent master
> (FC31) and then latest 4.4 beta from RPMs (Centos8).
> 
> I have ovirt-imageio daemon running on the same host engine is running. (with
> the simplest possible configuration - TLS disabled)
> 
> Unfortunately when I hit 'test connection' in admin ui/storage/domain I keep
> seeing error message complaining about ovirt-imageio-proxy setup. 
> I know that recently there has been quite a lot of changes related to the next
> version of imageio. 
> 
> Is there something else besides ovirt-imageio daemon that I should have
> installed/configured?  Perhaps there is some documentation I could use?
> 
> 
> thanks!
> 


signature.asc
Description: This is a digitally signed message part
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/44NG3LJFF5I6C65VDYDJGQW6LAGF7YUD/

[ovirt-devel] package conflicts when executing dnf update

[Dana Elfassy]

Hi,
I'm working on CentOS 8.1
Whenever I'm trying to dnf update, I'm getting this error:
Error:
 Problem: package qemu-kvm-core-15:4.1.0-23.el8.1.x86_64 requires
libvirglrenderer.so.0()(64bit), but none of the providers can be installed
  - cannot install both
virglrenderer-0.8.0-1.20191002git4ac3a04c.el8.x86_64 and
virglrenderer-0.6.0-5.20180814git491d3b705.el8.x86_64
  - cannot install both
virglrenderer-0.6.0-5.20180814git491d3b705.el8.x86_64 and
virglrenderer-0.8.0-1.20191002git4ac3a04c.el8.x86_64
  - cannot install the best update candidate for package
virglrenderer-0.6.0-5.20180814git491d3b705.el8.x86_64
  - cannot install the best update candidate for package
qemu-kvm-core-15:4.1.0-23.el8.1.x86_64
(try to add '--allowerasing' to command line to replace conflicting
packages or '--skip-broken' to skip uninstallable packages or '--nobest' to
use not only best candidate packages)

I've tried the --allowerasing and --skip-broken, which lead to the same
error. I also tried updating virglrenderer and got the same error. The only
way I was able to update was removing qemu-kvm-core (and all of its
dependencies), and then had to reinstall it again

Did anyone face this issue?  Any suggestions about how to resolve it?
Thanks,
Dana
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/RRC723XDPTFZENISCRU5GDLR62NB4YJO/

[ovirt-devel] Uploading iso / ovirt-imageio

[Artur Socha]

Hi,
After a long break I am trying setup my engine so that I could upload images
(ISO) there and use them when spinning new VMs. First I tried recent master
(FC31) and then latest 4.4 beta from RPMs (Centos8).

I have ovirt-imageio daemon running on the same host engine is running. (with
the simplest possible configuration - TLS disabled)

Unfortunately when I hit 'test connection' in admin ui/storage/domain I keep
seeing error message complaining about ovirt-imageio-proxy setup. 
I know that recently there has been quite a lot of changes related to the next
version of imageio. 

Is there something else besides ovirt-imageio daemon that I should have
installed/configured?  Perhaps there is some documentation I could use?


thanks!

-- 
Artur Socha
Senior Software Engineer, RHV
Red Hat



signature.asc
Description: This is a digitally signed message part
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/JDDVTQC6K7U56D5WAIYOQ4HDGORAVELR/