[ovirt-devel] Re: Vdsm CI for el8 is broken

2020-06-23 Thread Tomáš Golembiovský 
On Tue, 23 Jun 2020 17:36:25 +0200
Dominik Holler  wrote:

> On Tue, Jun 23, 2020 at 5:22 PM Tomáš Golembiovský 
> wrote:
> 
> > On Tue, 23 Jun 2020 12:49:47 +0200
> > Dominik Holler  wrote:
> >  
> > > On Tue, Jun 23, 2020 at 12:07 PM Milan Zamazal   
> > wrote:  
> > >  
> > > > Dominik Holler  writes:
> > > >  
> > > > > On Mon, Jun 22, 2020 at 9:34 AM Milan Zamazal   
> >  
> > > > wrote:  
> > > > >  
> > > > >> Nir Soffer  writes:
> > > > >>  
> > > > >> > On Sun, Jun 21, 2020 at 1:18 PM Amit Bawer   
> > wrote:  
> > > > >> >>
> > > > >> >> Hi  
> > > > >> >  
> > > > >> >>
> > > > >> >> Seems that in the last few days the el8 CI for vdsm cannot run,  
> > were  
> > > > >> there any el8 repo changes?  
> > > > >> >>
> > > > >> >> [2020-06-21T09:20:03.003Z] Mock Version: 2.2
> > > > >> >> [2020-06-21T09:20:03.003Z] INFO: Mock Version: 2.2
> > > > >> >> [2020-06-21T09:20:03.987Z] Start: dnf install
> > > > >> >> [2020-06-21T09:20:12.326Z] ERROR: Command failed:
> > > > >> >> [2020-06-21T09:20:12.326Z] # /usr/bin/dnf --installroot
> > > > >> >>  
> > > >  
> > /var/lib/mock/epel-8-x86_64-8e9eeb575ab4da7bf0fbfdc80a25b9c0-30232/root/  
> > > > >> >> --releasever 8 --setopt=deltarpm=False --allowerasing
> > > > >> >> --disableplugin=local --disableplugin=spacewalk
> > > > >> >> --disableplugin=local --disableplugin=spacewalk install dnf tar
> > > > >> >> gcc-c++ redhat-rpm-config which xz sed make bzip2 gzip gcc  
> > coreutils  
> > > > >> >> unzip shadow-utils diffutils cpio bash gawk rpm-build info patch
> > > > >> >> util-linux findutils grep python36 autoconf automake createrepo  
> > dnf  
> > > > >> >> dnf-utils e2fsprogs gcc gdb git iproute-tc iscsi-initiator-utils
> > > > >> >> libguestfs-tools-c lshw make openvswitch ovirt-imageio-common
> > > > >> >> python3-augeas python3-blivet python3-coverage python3-dateutil
> > > > >> >> python3-dbus python3-decorator python3-devel python3-dmidecode
> > > > >> >> python3-inotify python3-ioprocess-1.4.1 python3-libselinux
> > > > >> >> python3-libvirt python3-magic python3-netaddr python3-nose
> > > > >> >> python3-pip python3-policycoreutils python3-pyyaml  
> > python3-requests  
> > > > >> >> python3-sanlock python3-six python3-yaml rpm-build rpmlint  
> > sanlock  
> > > > >> >> sudo systemd-udev xfsprogs --setopt=tsflags=nocontexts
> > > > >> >> [2020-06-21T09:20:12.326Z] No matches found for the following
> > > > >> >> disable plugin patterns: local, spacewalk
> > > > >> >> [2020-06-21T09:20:12.326Z] Last metadata expiration check:  
> > 0:00:02  
> > > > ago  
> > > > >> on Sun Jun 21 09:20:07 2020.  
> > > > >> >> [2020-06-21T09:20:12.326Z] No match for argument: openvswitch
> > > > >> >> [2020-06-21T09:20:12.326Z] Error: Unable to find a match:  
> > openvswitch  
> > > > >> >>  
> > > >  
> > >
> > > That
> > > https://gerrit.ovirt.org/#/c/109714/
> > > was required to fix this raises the question from which repo openvswitch
> > > was consumed before.
> > > But never mind, it is fixed now.  
> >
> > What exactly is fixed? It is still failing for me for the same reason.
> >
> >  
> The error
> [2020-06-21T09:20:12.326Z] No match for argument: openvswitch
> [2020-06-21T09:20:12.326Z] Error: Unable to find a match: openvswitch
> is fixed by adding the ovirt44testing repo.

Well the last CI state on that patch is -1, that does not look like a
fix too much. But if it is, could we rebease & merge it?

Tomas

> 
> 
> 
> > Tomas
> >  
> > >
> > >  
> > > > >> >> Taken from  
> > > > >>  
> > > >  
> > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/21966/consoleText
> >  
> > > > >> >
> > > > >> > I think this is a result of trying to move to CentOS 8.2 before  
> > all  
> > > > >> > the packages are
> > > > >> > ready.  
> > > > >>
> > > > >> There are problems with openvswitch package since the CentOS 8.2  
> > update.  
> > > > >> It also blocks Vdsm builds.  Sandro and Dominik work on solving it.
> > > > >>
> > > > >>  
> > > > > This seems to be something unrelated in the build system.
> > > > > CI should work since last Tuesday again.  
> > > >
> > > > I'm not sure which CI you mean, but Vdsm CI on master is still broken,
> > > > even with Sandro's patch adding the oVirt 4.4 virt repo
> > > > (https://gerrit.ovirt.org/109714):
> > > >
> > > >   Running transaction check
> > > >   [2020-06-22T08:54:51.868Z] warning: Generating 18 missing index(es),
> > > > please wait...
> > > >   [2020-06-22T08:54:51.868Z] Error: transaction check vs depsolve:
> > > >   [2020-06-22T08:54:51.868Z] /bin/sh is needed by
> > > > ovirt-openvswitch-2.11-0.2020061801.el8.noarch
> > > >   [2020-06-22T08:54:51.868Z] bash is needed by
> > > > ovirt-openvswitch-2.11-0.2020061801.el8.noarch
> > > >   [2020-06-22T08:54:51.868Z] systemd is needed by
> > > > ovirt-openvswitch-2.11-0.2020061801.el8.noarch
> > > >   [2020-06-22T08:54:51.868Z] To diagnose the problem, try running: 'rpm
> > > > -Va --nofiles --nodigest'.
> > > >   [2020-06-22T08:54:51.868Z] You

[ovirt-devel] Re: Bug 1522926 - [RFE] Integrate lvm filter configuration in vdsm-tool configure step

2020-06-23 Thread Nir Soffer 
On Tue, Jun 23, 2020 at 6:39 PM Amit Bawer  wrote:
>
> I am not sure how "vdsm-tool config-lvm-filter -y" should be carried as part 
> of host-deployment as it is not part of the configurators executed by 
> "vdsm-tool configure".
> Should it be another task in ansible or an addition to host deploy package[1] 
> after doing configuration?

Yes, it should be another command running before or after vdsm-tool
configure --force.

The command should be allowed to fail, but we should see the output of
the command on failures.

> [1] 
> https://github.com/oVirt/ovirt-host-deploy/blob/master/src/plugins/ovirt-host-deploy/vdsm/packages.py#L138
>
> On Tue, Jun 23, 2020 at 4:30 PM Nir Soffer  wrote:
>>
>> On Tue, Jun 23, 2020 at 4:28 PM Yedidyah Bar David  wrote:
>> >
>> > On Tue, Jun 23, 2020 at 4:11 PM Amit Bawer  wrote:
>> > >
>> > >
>> > >
>> > > On Tue, Jun 23, 2020 at 2:55 PM Nir Soffer  wrote:
>> > >>
>> > >> On Tue, Jun 23, 2020 at 2:47 PM Tal Nisan  wrote:
>> > >> >
>> > >> > BTW: Nir wrote somewhere that it can be done in a day so it shouldn't 
>> > >> > be a problem ;)
>> > >> >
>> > >> > On Tue, Jun 23, 2020 at 2:02 PM Tal Nisan  wrote:
>> > >> >>
>> > >> >> Hey guys,
>> > >> >> I've talked to Michal and we have to get this change in 4.4.1 so 
>> > >> >> we'll need to start to work on it ASAP, I've asked Amit to take it 
>> > >> >> so let's try and understand together what we need to do here
>> > >>
>> > >> I think we should:
>> > >>
>> > >> - fix the exit code of the tool, currently it always exits with 0, so
>> > >> there is no way to handle errors.
>> > >>   I commented about it in the bug
>> > >>
>> > >> - run the tool when deploying a host, after or before we run
>> > >> "vdsm-tool configure --force"
>> > >>   I don't know where is the code running when deploying a host, it may
>> > >> be in some ansible
>> > >>   script. Best ask on devel and CC Didi.
>> > >
>> > >
>> > > Probably invoked from playbook for ovirt-host-deploy.yml, calling the 
>> > > following package code:
>> > > https://github.com/oVirt/ovirt-host-deploy/blob/master/src/plugins/ovirt-host-deploy/vdsm/packages.py#L138
>> > >
>> > > +Yedidyah Bar David  could you confirm?
>> >
>> > Yes, AFAIK - but this code is maintained by Infra team, not
>> > Integration. Adding Dana, who is the main/original author (and
>> > probably main maintainer?).
>>
>> Great.
>>
>> Amit, please continue the technical discussion on devel.
>>
>> > > From ovirt-host-deploy log in engine:
>> > >
>> > > 2020-05-25 16:49:32 EDT - TASK [ovirt-host-deploy-vdsm : Verify minimum 
>> > > vdsm version exists] *
>> > > 2020-05-25 16:49:32 EDT - TASK [ovirt-host-deploy-vdsm : Reconfigure 
>> > > vdsm tool] **
>> > > 2020-05-25 16:50:08 EDT - changed: [10.35.18.187]
>> > > 2020-05-25 16:50:08 EDT - {
>> > >   "status" : "OK",
>> > >   "msg" : "",
>> > >   "data" : {
>> > > "uuid" : "13daab0a-a4d8-4a67-8266-3a350efeb36a",
>> > > "counter" : 52,
>> > > "stdout" : "changed: [10.35.18.187]",
>> > > "start_line" : 46,
>> > > "end_line" : 47,
>> > > "runner_ident" : "2ef6527a-9ec9-11ea-82a6-525400200635",
>> > > "event" : "runner_on_ok",
>> > > "pid" : 30013,
>> > > "created" : "2020-05-25T20:50:06.341271",
>> > > "parent_uuid" : "52540020-0635-d1d2-2820-0199",
>> > > "event_data" : {
>> > >   "playbook" : "ovirt-host-deploy.yml",
>> > >   "playbook_uuid" : "b9cdaec8-402d-4705-81d0-973775a69e18",
>> > >   "play" : "all",
>> > >   "play_uuid" : "52540020-0635-d1d2-2820-0006",
>> > >   "play_pattern" : "all",
>> > >   "task" : "Reconfigure vdsm tool",
>> > >   "task_uuid" : "52540020-0635-d1d2-2820-0199",
>> > >   "task_action" : "command",
>> > >   "task_args" : "",
>> > >   "task_path" : 
>> > > "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/packages.yml:18",
>> > >   "role" : "ovirt-host-deploy-vdsm",
>> > >   "host" : "10.35.18.187",
>> > >   "remote_addr" : "10.35.18.187",
>> > >  "res" : {
>> > > "cmd" : "vdsm-tool configure --force",
>> > > "stdout" : "\nChecking configuration status...\n\nCurrent 
>> > > revision of multipath.conf detected, preserving\nabrt is already 
>> > > configured for vdsm\nlvm is configured for vdsm\nManaged volume database 
>> > > is already configured\nlibvirt is already configured for vdsm\nSUCCESS: 
>> > > ssl configured to true. No conflicts\n\nRunning 
>> > > configure...\nReconfiguration of abrt is done.\nReconfiguration of 
>> > > passwd is done.\nReconfiguration of libvirt is done.\n\nDone configuring 
>> > > modules to VDSM.",
>> > > "stderr" : "",
>> > > "rc" : 0,
>> > > "start" : "2020-05-25 16:49:31.421596",
>> > > "end" : "2020-05-25 16:50:06.225412",
>> > > "delta" : "0:00:34.803816",
>> > > "changed" : true,
>> > > "invocation" : {
>> > >

[ovirt-devel] Re: Bug 1522926 - [RFE] Integrate lvm filter configuration in vdsm-tool configure step

2020-06-23 Thread Amit Bawer 
I am not sure how "vdsm-tool config-lvm-filter -y" should be carried as
part of host-deployment as it is not part of the configurators executed by
"vdsm-tool configure".
Should it be another task in ansible or an addition to host deploy
package[1] after doing configuration?

[1]
https://github.com/oVirt/ovirt-host-deploy/blob/master/src/plugins/ovirt-host-deploy/vdsm/packages.py#L138

On Tue, Jun 23, 2020 at 4:30 PM Nir Soffer  wrote:

> On Tue, Jun 23, 2020 at 4:28 PM Yedidyah Bar David 
> wrote:
> >
> > On Tue, Jun 23, 2020 at 4:11 PM Amit Bawer  wrote:
> > >
> > >
> > >
> > > On Tue, Jun 23, 2020 at 2:55 PM Nir Soffer  wrote:
> > >>
> > >> On Tue, Jun 23, 2020 at 2:47 PM Tal Nisan  wrote:
> > >> >
> > >> > BTW: Nir wrote somewhere that it can be done in a day so it
> shouldn't be a problem ;)
> > >> >
> > >> > On Tue, Jun 23, 2020 at 2:02 PM Tal Nisan 
> wrote:
> > >> >>
> > >> >> Hey guys,
> > >> >> I've talked to Michal and we have to get this change in 4.4.1 so
> we'll need to start to work on it ASAP, I've asked Amit to take it so let's
> try and understand together what we need to do here
> > >>
> > >> I think we should:
> > >>
> > >> - fix the exit code of the tool, currently it always exits with 0, so
> > >> there is no way to handle errors.
> > >>   I commented about it in the bug
> > >>
> > >> - run the tool when deploying a host, after or before we run
> > >> "vdsm-tool configure --force"
> > >>   I don't know where is the code running when deploying a host, it may
> > >> be in some ansible
> > >>   script. Best ask on devel and CC Didi.
> > >
> > >
> > > Probably invoked from playbook for ovirt-host-deploy.yml, calling the
> following package code:
> > >
> https://github.com/oVirt/ovirt-host-deploy/blob/master/src/plugins/ovirt-host-deploy/vdsm/packages.py#L138
> > >
> > > +Yedidyah Bar David  could you confirm?
> >
> > Yes, AFAIK - but this code is maintained by Infra team, not
> > Integration. Adding Dana, who is the main/original author (and
> > probably main maintainer?).
>
> Great.
>
> Amit, please continue the technical discussion on devel.
>
> > > From ovirt-host-deploy log in engine:
> > >
> > > 2020-05-25 16:49:32 EDT - TASK [ovirt-host-deploy-vdsm : Verify
> minimum vdsm version exists] *
> > > 2020-05-25 16:49:32 EDT - TASK [ovirt-host-deploy-vdsm : Reconfigure
> vdsm tool] **
> > > 2020-05-25 16:50:08 EDT - changed: [10.35.18.187]
> > > 2020-05-25 16:50:08 EDT - {
> > >   "status" : "OK",
> > >   "msg" : "",
> > >   "data" : {
> > > "uuid" : "13daab0a-a4d8-4a67-8266-3a350efeb36a",
> > > "counter" : 52,
> > > "stdout" : "changed: [10.35.18.187]",
> > > "start_line" : 46,
> > > "end_line" : 47,
> > > "runner_ident" : "2ef6527a-9ec9-11ea-82a6-525400200635",
> > > "event" : "runner_on_ok",
> > > "pid" : 30013,
> > > "created" : "2020-05-25T20:50:06.341271",
> > > "parent_uuid" : "52540020-0635-d1d2-2820-0199",
> > > "event_data" : {
> > >   "playbook" : "ovirt-host-deploy.yml",
> > >   "playbook_uuid" : "b9cdaec8-402d-4705-81d0-973775a69e18",
> > >   "play" : "all",
> > >   "play_uuid" : "52540020-0635-d1d2-2820-0006",
> > >   "play_pattern" : "all",
> > >   "task" : "Reconfigure vdsm tool",
> > >   "task_uuid" : "52540020-0635-d1d2-2820-0199",
> > >   "task_action" : "command",
> > >   "task_args" : "",
> > >   "task_path" :
> "/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-deploy-vdsm/tasks/packages.yml:18",
> > >   "role" : "ovirt-host-deploy-vdsm",
> > >   "host" : "10.35.18.187",
> > >   "remote_addr" : "10.35.18.187",
> > >  "res" : {
> > > "cmd" : "vdsm-tool configure --force",
> > > "stdout" : "\nChecking configuration status...\n\nCurrent
> revision of multipath.conf detected, preserving\nabrt is already configured
> for vdsm\nlvm is configured for vdsm\nManaged volume database is already
> configured\nlibvirt is already configured for vdsm\nSUCCESS: ssl configured
> to true. No conflicts\n\nRunning configure...\nReconfiguration of abrt is
> done.\nReconfiguration of passwd is done.\nReconfiguration of libvirt is
> done.\n\nDone configuring modules to VDSM.",
> > > "stderr" : "",
> > > "rc" : 0,
> > > "start" : "2020-05-25 16:49:31.421596",
> > > "end" : "2020-05-25 16:50:06.225412",
> > > "delta" : "0:00:34.803816",
> > > "changed" : true,
> > > "invocation" : {
> > >   "module_args" : {
> > > "_raw_params" : "vdsm-tool configure --force",
> > > "_uses_shell" : true,
> > > "warn" : true,
> > > "stdin_add_newline" : true,
> > > "strip_empty_ends" : true,
> > > "argv" : null,
> > > "chdir" : null,
> > > "executable" : null,
> > > "creates" : null,
> > > "removes" : null,
> > >

[ovirt-devel] Re: Vdsm CI for el8 is broken

2020-06-23 Thread Dominik Holler 
On Tue, Jun 23, 2020 at 5:22 PM Tomáš Golembiovský 
wrote:

> On Tue, 23 Jun 2020 12:49:47 +0200
> Dominik Holler  wrote:
>
> > On Tue, Jun 23, 2020 at 12:07 PM Milan Zamazal 
> wrote:
> >
> > > Dominik Holler  writes:
> > >
> > > > On Mon, Jun 22, 2020 at 9:34 AM Milan Zamazal 
>
> > > wrote:
> > > >
> > > >> Nir Soffer  writes:
> > > >>
> > > >> > On Sun, Jun 21, 2020 at 1:18 PM Amit Bawer 
> wrote:
> > > >> >>
> > > >> >> Hi
> > > >> >
> > > >> >>
> > > >> >> Seems that in the last few days the el8 CI for vdsm cannot run,
> were
> > > >> there any el8 repo changes?
> > > >> >>
> > > >> >> [2020-06-21T09:20:03.003Z] Mock Version: 2.2
> > > >> >> [2020-06-21T09:20:03.003Z] INFO: Mock Version: 2.2
> > > >> >> [2020-06-21T09:20:03.987Z] Start: dnf install
> > > >> >> [2020-06-21T09:20:12.326Z] ERROR: Command failed:
> > > >> >> [2020-06-21T09:20:12.326Z] # /usr/bin/dnf --installroot
> > > >> >>
> > >
> /var/lib/mock/epel-8-x86_64-8e9eeb575ab4da7bf0fbfdc80a25b9c0-30232/root/
> > > >> >> --releasever 8 --setopt=deltarpm=False --allowerasing
> > > >> >> --disableplugin=local --disableplugin=spacewalk
> > > >> >> --disableplugin=local --disableplugin=spacewalk install dnf tar
> > > >> >> gcc-c++ redhat-rpm-config which xz sed make bzip2 gzip gcc
> coreutils
> > > >> >> unzip shadow-utils diffutils cpio bash gawk rpm-build info patch
> > > >> >> util-linux findutils grep python36 autoconf automake createrepo
> dnf
> > > >> >> dnf-utils e2fsprogs gcc gdb git iproute-tc iscsi-initiator-utils
> > > >> >> libguestfs-tools-c lshw make openvswitch ovirt-imageio-common
> > > >> >> python3-augeas python3-blivet python3-coverage python3-dateutil
> > > >> >> python3-dbus python3-decorator python3-devel python3-dmidecode
> > > >> >> python3-inotify python3-ioprocess-1.4.1 python3-libselinux
> > > >> >> python3-libvirt python3-magic python3-netaddr python3-nose
> > > >> >> python3-pip python3-policycoreutils python3-pyyaml
> python3-requests
> > > >> >> python3-sanlock python3-six python3-yaml rpm-build rpmlint
> sanlock
> > > >> >> sudo systemd-udev xfsprogs --setopt=tsflags=nocontexts
> > > >> >> [2020-06-21T09:20:12.326Z] No matches found for the following
> > > >> >> disable plugin patterns: local, spacewalk
> > > >> >> [2020-06-21T09:20:12.326Z] Last metadata expiration check:
> 0:00:02
> > > ago
> > > >> on Sun Jun 21 09:20:07 2020.
> > > >> >> [2020-06-21T09:20:12.326Z] No match for argument: openvswitch
> > > >> >> [2020-06-21T09:20:12.326Z] Error: Unable to find a match:
> openvswitch
> > > >> >>
> > >
> >
> > That
> > https://gerrit.ovirt.org/#/c/109714/
> > was required to fix this raises the question from which repo openvswitch
> > was consumed before.
> > But never mind, it is fixed now.
>
> What exactly is fixed? It is still failing for me for the same reason.
>
>
The error
[2020-06-21T09:20:12.326Z] No match for argument: openvswitch
[2020-06-21T09:20:12.326Z] Error: Unable to find a match: openvswitch
is fixed by adding the ovirt44testing repo.



> Tomas
>
> >
> >
> > > >> >> Taken from
> > > >>
> > >
> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/21966/consoleText
>
> > > >> >
> > > >> > I think this is a result of trying to move to CentOS 8.2 before
> all
> > > >> > the packages are
> > > >> > ready.
> > > >>
> > > >> There are problems with openvswitch package since the CentOS 8.2
> update.
> > > >> It also blocks Vdsm builds.  Sandro and Dominik work on solving it.
> > > >>
> > > >>
> > > > This seems to be something unrelated in the build system.
> > > > CI should work since last Tuesday again.
> > >
> > > I'm not sure which CI you mean, but Vdsm CI on master is still broken,
> > > even with Sandro's patch adding the oVirt 4.4 virt repo
> > > (https://gerrit.ovirt.org/109714):
> > >
> > >   Running transaction check
> > >   [2020-06-22T08:54:51.868Z] warning: Generating 18 missing index(es),
> > > please wait...
> > >   [2020-06-22T08:54:51.868Z] Error: transaction check vs depsolve:
> > >   [2020-06-22T08:54:51.868Z] /bin/sh is needed by
> > > ovirt-openvswitch-2.11-0.2020061801.el8.noarch
> > >   [2020-06-22T08:54:51.868Z] bash is needed by
> > > ovirt-openvswitch-2.11-0.2020061801.el8.noarch
> > >   [2020-06-22T08:54:51.868Z] systemd is needed by
> > > ovirt-openvswitch-2.11-0.2020061801.el8.noarch
> > >   [2020-06-22T08:54:51.868Z] To diagnose the problem, try running: 'rpm
> > > -Va --nofiles --nodigest'.
> > >   [2020-06-22T08:54:51.868Z] You probably have corrupted RPMDB, running
> > > 'rpm --rebuilddb' might fix the issue.
> > >   [2020-06-22T08:54:51.868Z] The downloaded packages were saved in
> cache
> > > until the next successful transaction.
> > >   [2020-06-22T08:54:51.868Z] You can remove cached packages by
> executing
> > > 'dnf clean packages'.
> > >
> > > Besides it puts -1 on each patch, we can't have any Vdsm builds until
> it
> > > is fixed.  Without the Sandro's patch, we get the error posted by Amit
> > > above.
> > >
> > > Any ideas how to proceed?  Why is RPMDB

[ovirt-devel] oVirt - Outreachy initiative

2020-06-23 Thread Sandro Bonazzola 
Hi,
oVirt project didn't participate in Outreachy Internships for the Mid-year
internships.
Application for End of year internships will open in September.
Last time oVirt project participated[1] +Milan Zamazal ,
Jakub Niedermertl and +Jason Brooks  stepped in for
mentoring applicants.
Is there any volunteer willing to take an active role for Outreachy this
upcoming round?
If we have no volunteers I'll drop the page[1] on July 3rd 2020.

[1] https://ovirt.org/community/activities/outreachy.html

Thanks,
-- 

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/ROXJQ7DMIUKYR25XIPYATZLPP44R2KF2/

[ovirt-devel] oVirt - Google Summer of Code

2020-06-23 Thread Sandro Bonazzola 
Hi,
this is the 3rd year in a row oVirt is not participating in Google Summer
of Code.
Within the oVirt community we have a page tracking the initiative[1] which
mentions administrators +Greg Sheremeta  and +Tomas
Jelinek  but both are not actively working on oVirt
projects anymore.
Is anybody willing to step in for taking the lead of this initiative for
next year?
If nobody step in, I'll drop the pages [1][2] from the website on July 3rd
2020.

[1] https://ovirt.org/community/activities/summer-of-code.html
[2] https://ovirt.org/community/activities/summer-of-code-students.html
-- 

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/CEUH525ILA75RR2VMU6D5TLGSYIPJAFO/

[ovirt-devel] Re: Vdsm CI for el8 is broken

2020-06-23 Thread Tomáš Golembiovský 
On Tue, 23 Jun 2020 12:49:47 +0200
Dominik Holler  wrote:

> On Tue, Jun 23, 2020 at 12:07 PM Milan Zamazal  wrote:
> 
> > Dominik Holler  writes:
> >  
> > > On Mon, Jun 22, 2020 at 9:34 AM Milan Zamazal   
> > wrote:  
> > >  
> > >> Nir Soffer  writes:
> > >>  
> > >> > On Sun, Jun 21, 2020 at 1:18 PM Amit Bawer  wrote:  
> > >> >>
> > >> >> Hi  
> > >> >  
> > >> >>
> > >> >> Seems that in the last few days the el8 CI for vdsm cannot run, were  
> > >> there any el8 repo changes?  
> > >> >>
> > >> >> [2020-06-21T09:20:03.003Z] Mock Version: 2.2
> > >> >> [2020-06-21T09:20:03.003Z] INFO: Mock Version: 2.2
> > >> >> [2020-06-21T09:20:03.987Z] Start: dnf install
> > >> >> [2020-06-21T09:20:12.326Z] ERROR: Command failed:
> > >> >> [2020-06-21T09:20:12.326Z] # /usr/bin/dnf --installroot
> > >> >>  
> > /var/lib/mock/epel-8-x86_64-8e9eeb575ab4da7bf0fbfdc80a25b9c0-30232/root/  
> > >> >> --releasever 8 --setopt=deltarpm=False --allowerasing
> > >> >> --disableplugin=local --disableplugin=spacewalk
> > >> >> --disableplugin=local --disableplugin=spacewalk install dnf tar
> > >> >> gcc-c++ redhat-rpm-config which xz sed make bzip2 gzip gcc coreutils
> > >> >> unzip shadow-utils diffutils cpio bash gawk rpm-build info patch
> > >> >> util-linux findutils grep python36 autoconf automake createrepo dnf
> > >> >> dnf-utils e2fsprogs gcc gdb git iproute-tc iscsi-initiator-utils
> > >> >> libguestfs-tools-c lshw make openvswitch ovirt-imageio-common
> > >> >> python3-augeas python3-blivet python3-coverage python3-dateutil
> > >> >> python3-dbus python3-decorator python3-devel python3-dmidecode
> > >> >> python3-inotify python3-ioprocess-1.4.1 python3-libselinux
> > >> >> python3-libvirt python3-magic python3-netaddr python3-nose
> > >> >> python3-pip python3-policycoreutils python3-pyyaml python3-requests
> > >> >> python3-sanlock python3-six python3-yaml rpm-build rpmlint sanlock
> > >> >> sudo systemd-udev xfsprogs --setopt=tsflags=nocontexts
> > >> >> [2020-06-21T09:20:12.326Z] No matches found for the following
> > >> >> disable plugin patterns: local, spacewalk
> > >> >> [2020-06-21T09:20:12.326Z] Last metadata expiration check: 0:00:02  
> > ago  
> > >> on Sun Jun 21 09:20:07 2020.  
> > >> >> [2020-06-21T09:20:12.326Z] No match for argument: openvswitch
> > >> >> [2020-06-21T09:20:12.326Z] Error: Unable to find a match: openvswitch
> > >> >>  
> >  
> 
> That
> https://gerrit.ovirt.org/#/c/109714/
> was required to fix this raises the question from which repo openvswitch
> was consumed before.
> But never mind, it is fixed now.

What exactly is fixed? It is still failing for me for the same reason.

Tomas

> 
> 
> > >> >> Taken from  
> > >>  
> > https://jenkins.ovirt.org/job/vdsm_standard-check-patch/21966/consoleText  
> > >> >
> > >> > I think this is a result of trying to move to CentOS 8.2 before all
> > >> > the packages are
> > >> > ready.  
> > >>
> > >> There are problems with openvswitch package since the CentOS 8.2 update.
> > >> It also blocks Vdsm builds.  Sandro and Dominik work on solving it.
> > >>
> > >>  
> > > This seems to be something unrelated in the build system.
> > > CI should work since last Tuesday again.  
> >
> > I'm not sure which CI you mean, but Vdsm CI on master is still broken,
> > even with Sandro's patch adding the oVirt 4.4 virt repo
> > (https://gerrit.ovirt.org/109714):
> >
> >   Running transaction check
> >   [2020-06-22T08:54:51.868Z] warning: Generating 18 missing index(es),
> > please wait...
> >   [2020-06-22T08:54:51.868Z] Error: transaction check vs depsolve:
> >   [2020-06-22T08:54:51.868Z] /bin/sh is needed by
> > ovirt-openvswitch-2.11-0.2020061801.el8.noarch
> >   [2020-06-22T08:54:51.868Z] bash is needed by
> > ovirt-openvswitch-2.11-0.2020061801.el8.noarch
> >   [2020-06-22T08:54:51.868Z] systemd is needed by
> > ovirt-openvswitch-2.11-0.2020061801.el8.noarch
> >   [2020-06-22T08:54:51.868Z] To diagnose the problem, try running: 'rpm
> > -Va --nofiles --nodigest'.
> >   [2020-06-22T08:54:51.868Z] You probably have corrupted RPMDB, running
> > 'rpm --rebuilddb' might fix the issue.
> >   [2020-06-22T08:54:51.868Z] The downloaded packages were saved in cache
> > until the next successful transaction.
> >   [2020-06-22T08:54:51.868Z] You can remove cached packages by executing
> > 'dnf clean packages'.
> >
> > Besides it puts -1 on each patch, we can't have any Vdsm builds until it
> > is fixed.  Without the Sandro's patch, we get the error posted by Amit
> > above.
> >
> > Any ideas how to proceed?  Why is RPMDB reported as corrupted, were
> > caches on the CI flushed?
> >
> >  
> Anton and Evgheni, can you please help us?
> 
> 
> 
> > > Is the list of allowed packages for the CI limited, or is every package
> > > from ovirt-repo allowed?
> > >
> > >  
> > >> > Please use Travis until this issue is resolved. You should use it
> > >> > anyway for storage
> > >> > patches.
> > >> >
> > >> > Nir  
> > >>
> > >>  
> >
> >  


-- 
Tomáš Golembiovský

[ovirt-devel] oVirt Gamification

2020-06-23 Thread Sandro Bonazzola 
Hi,
while reviewing oVirt community content I stumbled upon gamification
initiative[1].
Initiative leaders +Eyal Edri  and +Vojtech Szocs
 are not actively working on oVirt projects anymore and
the activity seems not really active for a long time.
Is there anyone willing to revive this initiative? If nobody will step in I
would drop the page from the website on July 3rd 2020.

[1] https://ovirt.org/community/activities/gamification.html

-- 

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/GGEEIKRKINVOVKYAGGCL5FPREB36FLWQ/

[ovirt-devel] Re: Proposing Ales Musil as VDSM network maintainer

2020-06-23 Thread Amit Bawer 
+1

On Tue, Jun 23, 2020 at 2:53 PM Petr Horacek  wrote:

>
>
> út 23. 6. 2020 v 13:32 odesílatel Nir Soffer  napsal:
>
>> On Mon, Jun 22, 2020 at 1:13 PM Marcin Sobczyk 
>> wrote:
>> > On 6/22/20 11:00 AM, Edward Haas wrote:
>> >
>> > Hello to all VDSM maintainers,
>>
>> These discussions should be public.
>> Adding devel@ovirt.org
>>
>> > I hope I did not miss any active maintainers.
>> >
>> > I'd like to nominate Ales Musil to formally take over the vdsm-network
>> vertical as a maintainer
>> > after acting as such in the last period.
>> >
>> > Would you approve adding him to the vdsm-master-maintainers
>> > https://gerrit.ovirt.org/#/admin/groups/106,members list,
>> > so he will not be blocked on my availability?
>> >
>> > +1
>>
>> I don't see any problem, so +1.
>>
>
> +1, well deserved.
>
>
>>
>> Let's wait a few days for more feedback on devel.
>>
>> Nir
>> ___
>> 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/UH3YAS67MICAL34RHH6QZVC5Y3PRZ3OF/
>>
> ___
> 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/V62Z27EJJQJB5PXMZSKQVQZ6RXRJNBCE/
>
___
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/UQ7GJAFKBH2RNW2IYOGJAR7XTXD3JT3L/

[ovirt-devel] Re: Support OVN in rename (was: Change in ovirt-system-tests[master]: basic-suite: Run rename right after engine-setup)

2020-06-23 Thread Yedidyah Bar David 
On Tue, Jun 23, 2020 at 2:47 PM Yedidyah Bar David  wrote:
>
> On Tue, Jun 23, 2020 at 1:01 PM Yedidyah Bar David  wrote:
> >
> > On Tue, Jun 23, 2020 at 12:44 PM Dominik Holler  wrote:
> > >
> > > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9863/artifact/check-patch.basic_suite_master.el7.x86_64/test_logs/basic-suite-master/post-098_ovirt_provider_ovn_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-provider-ovn.log
> > >
> > > says:
> > >
> > > SSLError(CertificateError("hostname 'oldenginename' doesn't match 
> > > 'engine'",),))
> > >
> > >
> > > Maybe the cert used by engine is still for hostname 'engine' ?
> >
> > Thanks, didn't notice this. I see this also on my own system, and
> > restarting the provider fixed it. Will send a patch for this.

With this patch:

https://gerrit.ovirt.org/109835 packaging: rename: Restart ovirt-provider-ovn

It's passing:

https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/6996/

log does not have the above error anymore:

https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/6996/artifact/exported-artifacts/test_logs/basic-suite-master/post-100_basic_ui_sanity_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-provider-ovn.log

It does have this after restart, not sure it's important:

2020-06-23 08:41:14,956 ovsdbapp.backend.ovs_idl.vlog
ssl:127.0.0.1:6641: no response to inactivity probe after 5.01
seconds, disconnecting

It also has some errors before that, probably because it was starting
in parallel to the running rename. I guess I should stop it in the
beginning, updating the patch now.

Is this enough for verification? Anything else I should try?

>
> BTW, now checked and saw that the same error appears also in the job that did
> succeed, so perhaps failure of current is due to some other issue:
>
> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/6978/
>
> https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/6978/artifact/exported-artifacts/test_logs/basic-suite-master/post-100_basic_ui_sanity_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-provider-ovn.log
>
> >
> > >
> > > On Tue, Jun 23, 2020 at 11:03 AM Yedidyah Bar David  
> > > wrote:
> > >>
> > >> On Mon, Jun 22, 2020 at 11:07 AM Code Review  wrote:
> > >> >
> > >> > From Jenkins CI :
> > >> >
> > >> > Jenkins CI has posted comments on this change.
> > >> >
> > >> > Change subject: basic-suite: Run rename right after engine-setup
> > >> > ..
> > >> >
> > >> >
> > >> > Patch Set 3:
> > >> >
> > >> > Build Failed
> > >> >
> > >> > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9863/
> > >> >  : FAILURE
> > >>
> > >> This failed with:
> > >>
> > >> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9863/testReport/junit/basic-suite-master.test-scenarios/098_ovirt_provider_ovn_pytest/Invoking_jobs___check_patch_basic_suite_master_el7_x86_64___test_use_ovn_provider/
> > >>
> > >> prefix = 
> > >> api_v4 = 
> > >>
> > >> @versioning.require_version(4, 2)
> > >> def test_use_ovn_provider(prefix, api_v4):
> > >> engine = api_v4.system_service()
> > >> engine_ip = prefix.virt_env.engine_vm().ip()
> > >> provider_id = 
> > >> network_utils_v4.get_default_ovn_provider_id(engine)
> > >>
> > >> >   token_id = _get_auth_token(engine_ip)
> > >>
> > >> ../basic-suite-master/test-scenarios/098_ovirt_provider_ovn_pytest.py:444:
> > >> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> > >> _ _ _ _
> > >>
> > >> engine_name = '192.168.201.4'
> > >>
> > >> def _get_auth_token(engine_name):
> > >> response_json = _request_auth_token(engine_name)
> > >> >   token_id = response_json['access']['token']['id']
> > >> E   KeyError: 'access'
> > >>
> > >> ../basic-suite-master/test-scenarios/098_ovirt_provider_ovn_pytest.py:105:
> > >> KeyError
> > >>
> > >> Is there a chance that it's due to my patch?
> > >>
> > >> >
> > >> > --
> > >> > To view, visit https://gerrit.ovirt.org/109734
> > >>
> > >> This patch runs initial setup with FQDN 'oldenginename', then runs
> > >> rename with fqdn 'engine'.
> > >>
> > >> Above check-patch ran with whatever that was in the repos at the time.
> > >> I also ran it with the manual job, only basic-suite-master, and the
> > >> CI-built results of my then-pending patches, and it passed.
> > >>
> > >> This was yesterday. I then merged all patches, and now rebased this
> > >> (OST) patch, to test again, still did not finish:
> > >>
> > >> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9894/
> > >>
> > >> That said, even if it passes, I am still not completely ok with my
> > >> patches. What needs to be done to comprehensively test OVN (with or
> > >> without rename)?
> > >>
> > >> If network suite passes, is this

[ovirt-devel] Re: Proposing Ales Musil as VDSM network maintainer

2020-06-23 Thread Vojtech Juranek 
On úterý 23. června 2020 13:30:30 CEST Nir Soffer wrote:
> On Mon, Jun 22, 2020 at 1:13 PM Marcin Sobczyk  wrote:
> > On 6/22/20 11:00 AM, Edward Haas wrote:
> >
> >
> >
> > Hello to all VDSM maintainers,
> 
> 
> These discussions should be public.
> Adding devel@ovirt.org
> 
> 
> > I hope I did not miss any active maintainers.
> >
> >
> >
> > I'd like to nominate Ales Musil to formally take over the vdsm-network
> > vertical as a maintainer
 after acting as such in the last period.
> >
> >
> >
> > Would you approve adding him to the vdsm-master-maintainers
> > https://gerrit.ovirt.org/#/admin/groups/106,members list,
> > so he will not be blocked on my availability?
> >
> >
> >
> > +1
> 
> 
> I don't see any problem, so +1.

+1


> Let's wait a few days for more feedback on devel.
> 
> Nir
> ___
> 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/UH3YAS67MICAL
> 34RHH6QZVC5Y3PRZ3OF/



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/LNP2CEOYPSGQWFRGOGCQCDISNRHIVOHL/

[ovirt-devel] Re: Proposing Ales Musil as VDSM network maintainer

2020-06-23 Thread Petr Horacek 
út 23. 6. 2020 v 13:32 odesílatel Nir Soffer  napsal:

> On Mon, Jun 22, 2020 at 1:13 PM Marcin Sobczyk 
> wrote:
> > On 6/22/20 11:00 AM, Edward Haas wrote:
> >
> > Hello to all VDSM maintainers,
>
> These discussions should be public.
> Adding devel@ovirt.org
>
> > I hope I did not miss any active maintainers.
> >
> > I'd like to nominate Ales Musil to formally take over the vdsm-network
> vertical as a maintainer
> > after acting as such in the last period.
> >
> > Would you approve adding him to the vdsm-master-maintainers
> > https://gerrit.ovirt.org/#/admin/groups/106,members list,
> > so he will not be blocked on my availability?
> >
> > +1
>
> I don't see any problem, so +1.
>

+1, well deserved.


>
> Let's wait a few days for more feedback on devel.
>
> Nir
> ___
> 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/UH3YAS67MICAL34RHH6QZVC5Y3PRZ3OF/
>
___
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/V62Z27EJJQJB5PXMZSKQVQZ6RXRJNBCE/

[ovirt-devel] Re: Support OVN in rename (was: Change in ovirt-system-tests[master]: basic-suite: Run rename right after engine-setup)

2020-06-23 Thread Yedidyah Bar David 
On Tue, Jun 23, 2020 at 1:01 PM Yedidyah Bar David  wrote:
>
> On Tue, Jun 23, 2020 at 12:44 PM Dominik Holler  wrote:
> >
> > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9863/artifact/check-patch.basic_suite_master.el7.x86_64/test_logs/basic-suite-master/post-098_ovirt_provider_ovn_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-provider-ovn.log
> >
> > says:
> >
> > SSLError(CertificateError("hostname 'oldenginename' doesn't match 
> > 'engine'",),))
> >
> >
> > Maybe the cert used by engine is still for hostname 'engine' ?
>
> Thanks, didn't notice this. I see this also on my own system, and
> restarting the provider fixed it. Will send a patch for this.

BTW, now checked and saw that the same error appears also in the job that did
succeed, so perhaps failure of current is due to some other issue:

https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/6978/

https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/6978/artifact/exported-artifacts/test_logs/basic-suite-master/post-100_basic_ui_sanity_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-provider-ovn.log

>
> >
> > On Tue, Jun 23, 2020 at 11:03 AM Yedidyah Bar David  wrote:
> >>
> >> On Mon, Jun 22, 2020 at 11:07 AM Code Review  wrote:
> >> >
> >> > From Jenkins CI :
> >> >
> >> > Jenkins CI has posted comments on this change.
> >> >
> >> > Change subject: basic-suite: Run rename right after engine-setup
> >> > ..
> >> >
> >> >
> >> > Patch Set 3:
> >> >
> >> > Build Failed
> >> >
> >> > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9863/
> >> >  : FAILURE
> >>
> >> This failed with:
> >>
> >> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9863/testReport/junit/basic-suite-master.test-scenarios/098_ovirt_provider_ovn_pytest/Invoking_jobs___check_patch_basic_suite_master_el7_x86_64___test_use_ovn_provider/
> >>
> >> prefix = 
> >> api_v4 = 
> >>
> >> @versioning.require_version(4, 2)
> >> def test_use_ovn_provider(prefix, api_v4):
> >> engine = api_v4.system_service()
> >> engine_ip = prefix.virt_env.engine_vm().ip()
> >> provider_id = network_utils_v4.get_default_ovn_provider_id(engine)
> >>
> >> >   token_id = _get_auth_token(engine_ip)
> >>
> >> ../basic-suite-master/test-scenarios/098_ovirt_provider_ovn_pytest.py:444:
> >> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> >> _ _ _
> >>
> >> engine_name = '192.168.201.4'
> >>
> >> def _get_auth_token(engine_name):
> >> response_json = _request_auth_token(engine_name)
> >> >   token_id = response_json['access']['token']['id']
> >> E   KeyError: 'access'
> >>
> >> ../basic-suite-master/test-scenarios/098_ovirt_provider_ovn_pytest.py:105:
> >> KeyError
> >>
> >> Is there a chance that it's due to my patch?
> >>
> >> >
> >> > --
> >> > To view, visit https://gerrit.ovirt.org/109734
> >>
> >> This patch runs initial setup with FQDN 'oldenginename', then runs
> >> rename with fqdn 'engine'.
> >>
> >> Above check-patch ran with whatever that was in the repos at the time.
> >> I also ran it with the manual job, only basic-suite-master, and the
> >> CI-built results of my then-pending patches, and it passed.
> >>
> >> This was yesterday. I then merged all patches, and now rebased this
> >> (OST) patch, to test again, still did not finish:
> >>
> >> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9894/
> >>
> >> That said, even if it passes, I am still not completely ok with my
> >> patches. What needs to be done to comprehensively test OVN (with or
> >> without rename)?
> >>
> >> If network suite passes, is this enough?
> >>
> >> Thanks,
> >> --
> >> Didi
> >>
>
>
> --
> Didi



-- 
Didi
___
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/PWETAPFACD3L6OW5IHI6TB3CF5R3GBY7/

[ovirt-devel] Re: Proposing Ales Musil as VDSM network maintainer

2020-06-23 Thread Nir Soffer 
On Mon, Jun 22, 2020 at 1:13 PM Marcin Sobczyk  wrote:
> On 6/22/20 11:00 AM, Edward Haas wrote:
>
> Hello to all VDSM maintainers,

These discussions should be public.
Adding devel@ovirt.org

> I hope I did not miss any active maintainers.
>
> I'd like to nominate Ales Musil to formally take over the vdsm-network 
> vertical as a maintainer
> after acting as such in the last period.
>
> Would you approve adding him to the vdsm-master-maintainers
> https://gerrit.ovirt.org/#/admin/groups/106,members list,
> so he will not be blocked on my availability?
>
> +1

I don't see any problem, so +1.

Let's wait a few days for more feedback on devel.

Nir
___
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/UH3YAS67MICAL34RHH6QZVC5Y3PRZ3OF/

[ovirt-devel] Re: Vdsm CI for el8 is broken

2020-06-23 Thread Dominik Holler 
On Tue, Jun 23, 2020 at 12:07 PM Milan Zamazal  wrote:

> Dominik Holler  writes:
>
> > On Mon, Jun 22, 2020 at 9:34 AM Milan Zamazal 
> wrote:
> >
> >> Nir Soffer  writes:
> >>
> >> > On Sun, Jun 21, 2020 at 1:18 PM Amit Bawer  wrote:
> >> >>
> >> >> Hi
> >> >
> >> >>
> >> >> Seems that in the last few days the el8 CI for vdsm cannot run, were
> >> there any el8 repo changes?
> >> >>
> >> >> [2020-06-21T09:20:03.003Z] Mock Version: 2.2
> >> >> [2020-06-21T09:20:03.003Z] INFO: Mock Version: 2.2
> >> >> [2020-06-21T09:20:03.987Z] Start: dnf install
> >> >> [2020-06-21T09:20:12.326Z] ERROR: Command failed:
> >> >> [2020-06-21T09:20:12.326Z] # /usr/bin/dnf --installroot
> >> >>
> /var/lib/mock/epel-8-x86_64-8e9eeb575ab4da7bf0fbfdc80a25b9c0-30232/root/
> >> >> --releasever 8 --setopt=deltarpm=False --allowerasing
> >> >> --disableplugin=local --disableplugin=spacewalk
> >> >> --disableplugin=local --disableplugin=spacewalk install dnf tar
> >> >> gcc-c++ redhat-rpm-config which xz sed make bzip2 gzip gcc coreutils
> >> >> unzip shadow-utils diffutils cpio bash gawk rpm-build info patch
> >> >> util-linux findutils grep python36 autoconf automake createrepo dnf
> >> >> dnf-utils e2fsprogs gcc gdb git iproute-tc iscsi-initiator-utils
> >> >> libguestfs-tools-c lshw make openvswitch ovirt-imageio-common
> >> >> python3-augeas python3-blivet python3-coverage python3-dateutil
> >> >> python3-dbus python3-decorator python3-devel python3-dmidecode
> >> >> python3-inotify python3-ioprocess-1.4.1 python3-libselinux
> >> >> python3-libvirt python3-magic python3-netaddr python3-nose
> >> >> python3-pip python3-policycoreutils python3-pyyaml python3-requests
> >> >> python3-sanlock python3-six python3-yaml rpm-build rpmlint sanlock
> >> >> sudo systemd-udev xfsprogs --setopt=tsflags=nocontexts
> >> >> [2020-06-21T09:20:12.326Z] No matches found for the following
> >> >> disable plugin patterns: local, spacewalk
> >> >> [2020-06-21T09:20:12.326Z] Last metadata expiration check: 0:00:02
> ago
> >> on Sun Jun 21 09:20:07 2020.
> >> >> [2020-06-21T09:20:12.326Z] No match for argument: openvswitch
> >> >> [2020-06-21T09:20:12.326Z] Error: Unable to find a match: openvswitch
> >> >>
>

That
https://gerrit.ovirt.org/#/c/109714/
was required to fix this raises the question from which repo openvswitch
was consumed before.
But never mind, it is fixed now.


> >> >> Taken from
> >>
> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/21966/consoleText
> >> >
> >> > I think this is a result of trying to move to CentOS 8.2 before all
> >> > the packages are
> >> > ready.
> >>
> >> There are problems with openvswitch package since the CentOS 8.2 update.
> >> It also blocks Vdsm builds.  Sandro and Dominik work on solving it.
> >>
> >>
> > This seems to be something unrelated in the build system.
> > CI should work since last Tuesday again.
>
> I'm not sure which CI you mean, but Vdsm CI on master is still broken,
> even with Sandro's patch adding the oVirt 4.4 virt repo
> (https://gerrit.ovirt.org/109714):
>
>   Running transaction check
>   [2020-06-22T08:54:51.868Z] warning: Generating 18 missing index(es),
> please wait...
>   [2020-06-22T08:54:51.868Z] Error: transaction check vs depsolve:
>   [2020-06-22T08:54:51.868Z] /bin/sh is needed by
> ovirt-openvswitch-2.11-0.2020061801.el8.noarch
>   [2020-06-22T08:54:51.868Z] bash is needed by
> ovirt-openvswitch-2.11-0.2020061801.el8.noarch
>   [2020-06-22T08:54:51.868Z] systemd is needed by
> ovirt-openvswitch-2.11-0.2020061801.el8.noarch
>   [2020-06-22T08:54:51.868Z] To diagnose the problem, try running: 'rpm
> -Va --nofiles --nodigest'.
>   [2020-06-22T08:54:51.868Z] You probably have corrupted RPMDB, running
> 'rpm --rebuilddb' might fix the issue.
>   [2020-06-22T08:54:51.868Z] The downloaded packages were saved in cache
> until the next successful transaction.
>   [2020-06-22T08:54:51.868Z] You can remove cached packages by executing
> 'dnf clean packages'.
>
> Besides it puts -1 on each patch, we can't have any Vdsm builds until it
> is fixed.  Without the Sandro's patch, we get the error posted by Amit
> above.
>
> Any ideas how to proceed?  Why is RPMDB reported as corrupted, were
> caches on the CI flushed?
>
>
Anton and Evgheni, can you please help us?



> > Is the list of allowed packages for the CI limited, or is every package
> > from ovirt-repo allowed?
> >
> >
> >> > Please use Travis until this issue is resolved. You should use it
> >> > anyway for storage
> >> > patches.
> >> >
> >> > Nir
> >>
> >>
>
>
___
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/DXI7DYZDQHHCHF7TIBJTM3NK6X2MVJRJ/

[ovirt-devel] Re: Vdsm CI for el8 is broken

2020-06-23 Thread Nir Soffer 
On Tue, Jun 23, 2020 at 1:07 PM Milan Zamazal  wrote:
>
> Dominik Holler  writes:
>
> > On Mon, Jun 22, 2020 at 9:34 AM Milan Zamazal  wrote:
> >
> >> Nir Soffer  writes:
> >>
> >> > On Sun, Jun 21, 2020 at 1:18 PM Amit Bawer  wrote:
> >> >>
> >> >> Hi
> >> >
> >> >>
> >> >> Seems that in the last few days the el8 CI for vdsm cannot run, were
> >> there any el8 repo changes?
> >> >>
> >> >> [2020-06-21T09:20:03.003Z] Mock Version: 2.2
> >> >> [2020-06-21T09:20:03.003Z] INFO: Mock Version: 2.2
> >> >> [2020-06-21T09:20:03.987Z] Start: dnf install
> >> >> [2020-06-21T09:20:12.326Z] ERROR: Command failed:
> >> >> [2020-06-21T09:20:12.326Z] # /usr/bin/dnf --installroot
> >> >> /var/lib/mock/epel-8-x86_64-8e9eeb575ab4da7bf0fbfdc80a25b9c0-30232/root/
> >> >> --releasever 8 --setopt=deltarpm=False --allowerasing
> >> >> --disableplugin=local --disableplugin=spacewalk
> >> >> --disableplugin=local --disableplugin=spacewalk install dnf tar
> >> >> gcc-c++ redhat-rpm-config which xz sed make bzip2 gzip gcc coreutils
> >> >> unzip shadow-utils diffutils cpio bash gawk rpm-build info patch
> >> >> util-linux findutils grep python36 autoconf automake createrepo dnf
> >> >> dnf-utils e2fsprogs gcc gdb git iproute-tc iscsi-initiator-utils
> >> >> libguestfs-tools-c lshw make openvswitch ovirt-imageio-common
> >> >> python3-augeas python3-blivet python3-coverage python3-dateutil
> >> >> python3-dbus python3-decorator python3-devel python3-dmidecode
> >> >> python3-inotify python3-ioprocess-1.4.1 python3-libselinux
> >> >> python3-libvirt python3-magic python3-netaddr python3-nose
> >> >> python3-pip python3-policycoreutils python3-pyyaml python3-requests
> >> >> python3-sanlock python3-six python3-yaml rpm-build rpmlint sanlock
> >> >> sudo systemd-udev xfsprogs --setopt=tsflags=nocontexts
> >> >> [2020-06-21T09:20:12.326Z] No matches found for the following
> >> >> disable plugin patterns: local, spacewalk
> >> >> [2020-06-21T09:20:12.326Z] Last metadata expiration check: 0:00:02 ago
> >> on Sun Jun 21 09:20:07 2020.
> >> >> [2020-06-21T09:20:12.326Z] No match for argument: openvswitch
> >> >> [2020-06-21T09:20:12.326Z] Error: Unable to find a match: openvswitch
> >> >>
> >> >> Taken from
> >> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/21966/consoleText
> >> >
> >> > I think this is a result of trying to move to CentOS 8.2 before all
> >> > the packages are
> >> > ready.
> >>
> >> There are problems with openvswitch package since the CentOS 8.2 update.
> >> It also blocks Vdsm builds.  Sandro and Dominik work on solving it.
> >>
> >>
> > This seems to be something unrelated in the build system.
> > CI should work since last Tuesday again.
>
> I'm not sure which CI you mean, but Vdsm CI on master is still broken,
> even with Sandro's patch adding the oVirt 4.4 virt repo
> (https://gerrit.ovirt.org/109714):
>
>   Running transaction check
>   [2020-06-22T08:54:51.868Z] warning: Generating 18 missing index(es), please 
> wait...
>   [2020-06-22T08:54:51.868Z] Error: transaction check vs depsolve:
>   [2020-06-22T08:54:51.868Z] /bin/sh is needed by 
> ovirt-openvswitch-2.11-0.2020061801.el8.noarch
>   [2020-06-22T08:54:51.868Z] bash is needed by 
> ovirt-openvswitch-2.11-0.2020061801.el8.noarch
>   [2020-06-22T08:54:51.868Z] systemd is needed by 
> ovirt-openvswitch-2.11-0.2020061801.el8.noarch
>   [2020-06-22T08:54:51.868Z] To diagnose the problem, try running: 'rpm -Va 
> --nofiles --nodigest'.
>   [2020-06-22T08:54:51.868Z] You probably have corrupted RPMDB, running 'rpm 
> --rebuilddb' might fix the issue.
>   [2020-06-22T08:54:51.868Z] The downloaded packages were saved in cache 
> until the next successful transaction.
>   [2020-06-22T08:54:51.868Z] You can remove cached packages by executing 'dnf 
> clean packages'.
>
> Besides it puts -1 on each patch, we can't have any Vdsm builds until it
> is fixed.  Without the Sandro's patch, we get the error posted by Amit
> above.
>
> Any ideas how to proceed?  Why is RPMDB reported as corrupted, were
> caches on the CI flushed?
>
> > Is the list of allowed packages for the CI limited, or is every package
> > from ovirt-repo allowed?

ovirt-imageio and ioprocess builds fine on copr. Maybe it is time to add vdsm
copr builds?

For example:
https://copr.fedorainfracloud.org/coprs/nsoffer/ovirt-imageio-preview/build/1496710/

Built automatically after I merged every patch, zero effort on my
side, zero effort
for developers that want to consume this build since the repo is added by
ovirt-release-master.rpm.

Here is the patches that added copr builds to imageio:
https://gerrit.ovirt.org/c/108903

> >
> >
> >> > Please use Travis until this issue is resolved. You should use it
> >> > anyway for storage
> >> > patches.
> >> >
> >> > Nir
> >>
> >>
>
___
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:

[ovirt-devel] Re: Vdsm CI for el8 is broken

2020-06-23 Thread Milan Zamazal 
Dominik Holler  writes:

> On Mon, Jun 22, 2020 at 9:34 AM Milan Zamazal  wrote:
>
>> Nir Soffer  writes:
>>
>> > On Sun, Jun 21, 2020 at 1:18 PM Amit Bawer  wrote:
>> >>
>> >> Hi
>> >
>> >>
>> >> Seems that in the last few days the el8 CI for vdsm cannot run, were
>> there any el8 repo changes?
>> >>
>> >> [2020-06-21T09:20:03.003Z] Mock Version: 2.2
>> >> [2020-06-21T09:20:03.003Z] INFO: Mock Version: 2.2
>> >> [2020-06-21T09:20:03.987Z] Start: dnf install
>> >> [2020-06-21T09:20:12.326Z] ERROR: Command failed:
>> >> [2020-06-21T09:20:12.326Z] # /usr/bin/dnf --installroot
>> >> /var/lib/mock/epel-8-x86_64-8e9eeb575ab4da7bf0fbfdc80a25b9c0-30232/root/
>> >> --releasever 8 --setopt=deltarpm=False --allowerasing
>> >> --disableplugin=local --disableplugin=spacewalk
>> >> --disableplugin=local --disableplugin=spacewalk install dnf tar
>> >> gcc-c++ redhat-rpm-config which xz sed make bzip2 gzip gcc coreutils
>> >> unzip shadow-utils diffutils cpio bash gawk rpm-build info patch
>> >> util-linux findutils grep python36 autoconf automake createrepo dnf
>> >> dnf-utils e2fsprogs gcc gdb git iproute-tc iscsi-initiator-utils
>> >> libguestfs-tools-c lshw make openvswitch ovirt-imageio-common
>> >> python3-augeas python3-blivet python3-coverage python3-dateutil
>> >> python3-dbus python3-decorator python3-devel python3-dmidecode
>> >> python3-inotify python3-ioprocess-1.4.1 python3-libselinux
>> >> python3-libvirt python3-magic python3-netaddr python3-nose
>> >> python3-pip python3-policycoreutils python3-pyyaml python3-requests
>> >> python3-sanlock python3-six python3-yaml rpm-build rpmlint sanlock
>> >> sudo systemd-udev xfsprogs --setopt=tsflags=nocontexts
>> >> [2020-06-21T09:20:12.326Z] No matches found for the following
>> >> disable plugin patterns: local, spacewalk
>> >> [2020-06-21T09:20:12.326Z] Last metadata expiration check: 0:00:02 ago
>> on Sun Jun 21 09:20:07 2020.
>> >> [2020-06-21T09:20:12.326Z] No match for argument: openvswitch
>> >> [2020-06-21T09:20:12.326Z] Error: Unable to find a match: openvswitch
>> >>
>> >> Taken from
>> https://jenkins.ovirt.org/job/vdsm_standard-check-patch/21966/consoleText
>> >
>> > I think this is a result of trying to move to CentOS 8.2 before all
>> > the packages are
>> > ready.
>>
>> There are problems with openvswitch package since the CentOS 8.2 update.
>> It also blocks Vdsm builds.  Sandro and Dominik work on solving it.
>>
>>
> This seems to be something unrelated in the build system.
> CI should work since last Tuesday again.

I'm not sure which CI you mean, but Vdsm CI on master is still broken,
even with Sandro's patch adding the oVirt 4.4 virt repo
(https://gerrit.ovirt.org/109714):

  Running transaction check
  [2020-06-22T08:54:51.868Z] warning: Generating 18 missing index(es), please 
wait...
  [2020-06-22T08:54:51.868Z] Error: transaction check vs depsolve:
  [2020-06-22T08:54:51.868Z] /bin/sh is needed by 
ovirt-openvswitch-2.11-0.2020061801.el8.noarch
  [2020-06-22T08:54:51.868Z] bash is needed by 
ovirt-openvswitch-2.11-0.2020061801.el8.noarch
  [2020-06-22T08:54:51.868Z] systemd is needed by 
ovirt-openvswitch-2.11-0.2020061801.el8.noarch
  [2020-06-22T08:54:51.868Z] To diagnose the problem, try running: 'rpm -Va 
--nofiles --nodigest'.
  [2020-06-22T08:54:51.868Z] You probably have corrupted RPMDB, running 'rpm 
--rebuilddb' might fix the issue.
  [2020-06-22T08:54:51.868Z] The downloaded packages were saved in cache until 
the next successful transaction.
  [2020-06-22T08:54:51.868Z] You can remove cached packages by executing 'dnf 
clean packages'.

Besides it puts -1 on each patch, we can't have any Vdsm builds until it
is fixed.  Without the Sandro's patch, we get the error posted by Amit
above.

Any ideas how to proceed?  Why is RPMDB reported as corrupted, were
caches on the CI flushed?

> Is the list of allowed packages for the CI limited, or is every package
> from ovirt-repo allowed?
>
>
>> > Please use Travis until this issue is resolved. You should use it
>> > anyway for storage
>> > patches.
>> >
>> > Nir
>>
>>
___
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/AUZNNT4ZM6M4ICN6H5RUADNBXZJGZ7BT/

[ovirt-devel] Re: Support OVN in rename (was: Change in ovirt-system-tests[master]: basic-suite: Run rename right after engine-setup)

2020-06-23 Thread Yedidyah Bar David 
On Tue, Jun 23, 2020 at 12:44 PM Dominik Holler  wrote:
>
> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9863/artifact/check-patch.basic_suite_master.el7.x86_64/test_logs/basic-suite-master/post-098_ovirt_provider_ovn_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-provider-ovn.log
>
> says:
>
> SSLError(CertificateError("hostname 'oldenginename' doesn't match 
> 'engine'",),))
>
>
> Maybe the cert used by engine is still for hostname 'engine' ?

Thanks, didn't notice this. I see this also on my own system, and
restarting the provider fixed it. Will send a patch for this.

>
> On Tue, Jun 23, 2020 at 11:03 AM Yedidyah Bar David  wrote:
>>
>> On Mon, Jun 22, 2020 at 11:07 AM Code Review  wrote:
>> >
>> > From Jenkins CI :
>> >
>> > Jenkins CI has posted comments on this change.
>> >
>> > Change subject: basic-suite: Run rename right after engine-setup
>> > ..
>> >
>> >
>> > Patch Set 3:
>> >
>> > Build Failed
>> >
>> > https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9863/
>> >  : FAILURE
>>
>> This failed with:
>>
>> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9863/testReport/junit/basic-suite-master.test-scenarios/098_ovirt_provider_ovn_pytest/Invoking_jobs___check_patch_basic_suite_master_el7_x86_64___test_use_ovn_provider/
>>
>> prefix = 
>> api_v4 = 
>>
>> @versioning.require_version(4, 2)
>> def test_use_ovn_provider(prefix, api_v4):
>> engine = api_v4.system_service()
>> engine_ip = prefix.virt_env.engine_vm().ip()
>> provider_id = network_utils_v4.get_default_ovn_provider_id(engine)
>>
>> >   token_id = _get_auth_token(engine_ip)
>>
>> ../basic-suite-master/test-scenarios/098_ovirt_provider_ovn_pytest.py:444:
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
>> _ _
>>
>> engine_name = '192.168.201.4'
>>
>> def _get_auth_token(engine_name):
>> response_json = _request_auth_token(engine_name)
>> >   token_id = response_json['access']['token']['id']
>> E   KeyError: 'access'
>>
>> ../basic-suite-master/test-scenarios/098_ovirt_provider_ovn_pytest.py:105:
>> KeyError
>>
>> Is there a chance that it's due to my patch?
>>
>> >
>> > --
>> > To view, visit https://gerrit.ovirt.org/109734
>>
>> This patch runs initial setup with FQDN 'oldenginename', then runs
>> rename with fqdn 'engine'.
>>
>> Above check-patch ran with whatever that was in the repos at the time.
>> I also ran it with the manual job, only basic-suite-master, and the
>> CI-built results of my then-pending patches, and it passed.
>>
>> This was yesterday. I then merged all patches, and now rebased this
>> (OST) patch, to test again, still did not finish:
>>
>> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9894/
>>
>> That said, even if it passes, I am still not completely ok with my
>> patches. What needs to be done to comprehensively test OVN (with or
>> without rename)?
>>
>> If network suite passes, is this enough?
>>
>> Thanks,
>> --
>> Didi
>>


-- 
Didi
___
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/SDZH6XXAWMTVGGXY7BRNVWWSTWUTVV6H/

[ovirt-devel] Re: Support OVN in rename (was: Change in ovirt-system-tests[master]: basic-suite: Run rename right after engine-setup)

2020-06-23 Thread Dominik Holler 
https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9863/artifact/check-patch.basic_suite_master.el7.x86_64/test_logs/basic-suite-master/post-098_ovirt_provider_ovn_pytest.py/lago-basic-suite-master-engine/_var_log/ovirt-provider-ovn.log

says:

SSLError(CertificateError("hostname 'oldenginename' doesn't match 'engine'",),))


Maybe the cert used by engine is still for hostname 'engine' ?

On Tue, Jun 23, 2020 at 11:03 AM Yedidyah Bar David  wrote:

> On Mon, Jun 22, 2020 at 11:07 AM Code Review  wrote:
> >
> > From Jenkins CI :
> >
> > Jenkins CI has posted comments on this change.
> >
> > Change subject: basic-suite: Run rename right after engine-setup
> > ..
> >
> >
> > Patch Set 3:
> >
> > Build Failed
> >
> >
> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9863/
> : FAILURE
>
> This failed with:
>
>
> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9863/testReport/junit/basic-suite-master.test-scenarios/098_ovirt_provider_ovn_pytest/Invoking_jobs___check_patch_basic_suite_master_el7_x86_64___test_use_ovn_provider/
>
> prefix = 
> api_v4 = 
>
> @versioning.require_version(4, 2)
> def test_use_ovn_provider(prefix, api_v4):
> engine = api_v4.system_service()
> engine_ip = prefix.virt_env.engine_vm().ip()
> provider_id = network_utils_v4.get_default_ovn_provider_id(engine)
>
> >   token_id = _get_auth_token(engine_ip)
>
> ../basic-suite-master/test-scenarios/098_ovirt_provider_ovn_pytest.py:444:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _ _ _
>
> engine_name = '192.168.201.4'
>
> def _get_auth_token(engine_name):
> response_json = _request_auth_token(engine_name)
> >   token_id = response_json['access']['token']['id']
> E   KeyError: 'access'
>
> ../basic-suite-master/test-scenarios/098_ovirt_provider_ovn_pytest.py:105:
> KeyError
>
> Is there a chance that it's due to my patch?
>
> >
> > --
> > To view, visit https://gerrit.ovirt.org/109734
>
> This patch runs initial setup with FQDN 'oldenginename', then runs
> rename with fqdn 'engine'.
>
> Above check-patch ran with whatever that was in the repos at the time.
> I also ran it with the manual job, only basic-suite-master, and the
> CI-built results of my then-pending patches, and it passed.
>
> This was yesterday. I then merged all patches, and now rebased this
> (OST) patch, to test again, still did not finish:
>
> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9894/
>
> That said, even if it passes, I am still not completely ok with my
> patches. What needs to be done to comprehensively test OVN (with or
> without rename)?
>
> If network suite passes, is this enough?
>
> Thanks,
> --
> Didi
>
>
___
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/KYTQO3VDC6DBD5FNWV4NLHB3YV7NBP74/

[ovirt-devel] Re: [ovirt-users] Change Hosted engine VM cluster compatibility version throws error

2020-06-23 Thread Lucia Jelinkova 
Ritesh, is this error occurring on master? There was a similar issue some
time ago and was fixed. As for the blank compatibility version combo box,
are you talking about the field in edit VM or is it blank in edit cluster?

Michal, I agree, the patch is awaiting your response to clarify what the
new error message should look like :-)

On Fri, Jun 19, 2020 at 7:20 PM Michal Skrivanek <
michal.skriva...@redhat.com> wrote:

>
>
> On 19 Jun 2020, at 16:40, Ritesh Chikatwar  wrote:
>
> 
>
>
> On Fri, Jun 19, 2020, 7:26 PM Michal Skrivanek <
> michal.skriva...@redhat.com> wrote:
>
>>
>>
>> On 19 Jun 2020, at 13:41, Ritesh Chikatwar  wrote:
>>
>>
>>
>> On Thu, Jun 18, 2020 at 11:59 PM Michal Skrivanek <
>> michal.skriva...@redhat.com> wrote:
>>
>>>
>>>
>>> On 18 Jun 2020, at 08:59, Ritesh Chikatwar  wrote:
>>>
>>> Hello Team,
>>>
>>>
>>> When i try to change Cluster compatible version HE it throws error As
>>>
>>>
>>> what exactly are you changing where?
>>>
>>
>> I am trying to change the cluster compatible version for the Hosted
>> engine in Ui. The drop down did not set any value and I am trying to set to
>> 4.4.
>>
>>
>> which drop down?
>> Why are you changing cluster compatibility level of HE?
>>
>> maybe that’s the best question for starts - what’s the current situation
>> and what are you trying to get to?:)
>>
>
> Yeah correct Michal I should have explained that in the beginning of mail
> itself. Apologize for that.
>
> I have 4.4 rhhi setup with storage as gluster. But in this setup gluster
> service is not enable by default. I can make it enable from the UI by
> editing cluster and when try the same I get the error as
>
>  Error while executing action: Update of cluster compatibility version
> failed because there are VMs/Templates [HostedEngine]
>
>
> Ah ok, that explains a lot. The message is misleading, it has nothing to
> do with cluster version.
> Can you please share your engine.log with that failure to check what
> exactly failed there?
>
> Lucia, the message is definitely confusing and your patch should be
> finalized and merged:)
>
> Thanks,
> michal
>
> with incorrect configuration. To fix the issue, please go to each of them,
> edit, change the Custom Compatibility Version of the VM/Template to the
> cluster level you want to update the cluster to and press OK. If the save
> does not pass, fix the dialog validation. After successful cluster update,
> you can revert your Custom Compatibility Version change.
>
> This is the reason I am changing vm's compatibility version.
>
>
> I also have one doubt here when vm got created , why vm's not settled the
> value for cluster compatible version.
>
>
>
>
>> Thanks,
>> michal
>>
>>
>>>
>>> Error while executing action:
>>>
>>> HostedEngine:
>>>
>>>- There was an attempt to change Hosted Engine VM values that are
>>>locked.
>>>
>>> I am trying to change the version to 4.4 it was showing blank.
>>>
>>> Any suggestions on how I can edit.
>>>
>>> The VM other than HE is able to editi.
>>>
>>>
>>>
>>> *Ritesh*
>>> ___
>>> Users mailing list -- us...@ovirt.org
>>> To unsubscribe send an email to users-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/us...@ovirt.org/message/3EBGCBFDUBHNI6G5E3NG4DCD7RQJLUNC/
>>>
>>>
>>>
>>
___
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/5B6QEIZLR6WGZUNEQSACVOPYNLAUCIYO/

[ovirt-devel] Support OVN in rename (was: Change in ovirt-system-tests[master]: basic-suite: Run rename right after engine-setup)

2020-06-23 Thread Yedidyah Bar David 
On Mon, Jun 22, 2020 at 11:07 AM Code Review  wrote:
>
> From Jenkins CI :
>
> Jenkins CI has posted comments on this change.
>
> Change subject: basic-suite: Run rename right after engine-setup
> ..
>
>
> Patch Set 3:
>
> Build Failed
>
> https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9863/ : 
> FAILURE

This failed with:

https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9863/testReport/junit/basic-suite-master.test-scenarios/098_ovirt_provider_ovn_pytest/Invoking_jobs___check_patch_basic_suite_master_el7_x86_64___test_use_ovn_provider/

prefix = 
api_v4 = 

@versioning.require_version(4, 2)
def test_use_ovn_provider(prefix, api_v4):
engine = api_v4.system_service()
engine_ip = prefix.virt_env.engine_vm().ip()
provider_id = network_utils_v4.get_default_ovn_provider_id(engine)

>   token_id = _get_auth_token(engine_ip)

../basic-suite-master/test-scenarios/098_ovirt_provider_ovn_pytest.py:444:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

engine_name = '192.168.201.4'

def _get_auth_token(engine_name):
response_json = _request_auth_token(engine_name)
>   token_id = response_json['access']['token']['id']
E   KeyError: 'access'

../basic-suite-master/test-scenarios/098_ovirt_provider_ovn_pytest.py:105:
KeyError

Is there a chance that it's due to my patch?

>
> --
> To view, visit https://gerrit.ovirt.org/109734

This patch runs initial setup with FQDN 'oldenginename', then runs
rename with fqdn 'engine'.

Above check-patch ran with whatever that was in the repos at the time.
I also ran it with the manual job, only basic-suite-master, and the
CI-built results of my then-pending patches, and it passed.

This was yesterday. I then merged all patches, and now rebased this
(OST) patch, to test again, still did not finish:

https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/9894/

That said, even if it passes, I am still not completely ok with my
patches. What needs to be done to comprehensively test OVN (with or
without rename)?

If network suite passes, is this enough?

Thanks,
-- 
Didi
___
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/7LMHRVLSSKPMHC7I2BLXPBTS23SY3WWF/