Re: [ovirt-devel] [rhev-devel] Fwd: [ACTION REQUIRED] upgrade to Fedora 27 for otopi on master

2018-02-28 Thread Yedidyah Bar David
(Re-adding devel)

On Thu, Mar 1, 2018 at 4:52 AM, Greg Sheremeta  wrote:
> Setup worked for me immediately after upgrade. I'll forward you my repos in
> a separate email.
>
> This was an interesting sequence:
>
> greg@dauntless:/etc/yum.repos.d % sudo dnf update otopi -y
> Failed to synchronize cache for repo 'region51-chrome-gnome-shell',
> disabling.
> Failed to synchronize cache for repo 'rcm-tools-fedora-rpms', disabling.
> Last metadata expiration check: 0:29:21 ago on Wed 28 Feb 2018 09:16:13 PM
> EST.
> Package otopi available, but not installed.
> No match for argument: otopi
> Error: No packages marked for upgrade.
> greg@dauntless:/etc/yum.repos.d % sudo dnf install otopi -y
> Failed to synchronize cache for repo 'region51-chrome-gnome-shell',
> disabling.
> Failed to synchronize cache for repo 'rcm-tools-fedora-rpms', disabling.
> Last metadata expiration check: 0:29:36 ago on Wed 28 Feb 2018 09:16:13 PM
> EST.
> Package python2-otopi-1.8.0-0.0.master.20180228112959.git6eccc31.fc27.noarch
> is already installed, skipping.
> Dependencies resolved.
> Nothing to do.
> Complete!

Adding Yuval for review.

Yuval recently re-introduced python3 support to otopi, and following the
fedora python packaging guidelines. Yuval, reading the guidelines again,
it seems like it's valid to keep the package name 'otopi' and make it
Provide: python2-otopi, instead of the opposite. WDYT?

>
>
>
> On Wed, Feb 28, 2018 at 5:20 PM, Alexander Wels  wrote:
>>
>> On Wednesday, February 28, 2018 12:02:11 PM EST Greg Sheremeta wrote:
>>
>> > -- Forwarded message --
>>
>> > From: Greg Sheremeta 
>>
>> > Date: Wed, Feb 28, 2018 at 12:01 PM
>>
>> > Subject: [ACTION REQUIRED] upgrade to Fedora 27 for otopi on master
>>
>> > To: Yedidyah Bar David 
>>
>> > Cc: Eli Mesika , devel 
>>
>> >
>>
>> >
>>
>> > [changing subject]
>>
>> >
>>
>> > Looks like we all have to upgrade Fedora devel machines to Fedora 27.
>>
>> >
>>
>> > Greg
>>
>> >
>>
>>
>>
>> I upgraded to F27 and now I am getting something about:
>>
>>
>>
>> [awels@awels ovirt-engine]$ ./bin/engine-setup
>> ***L:ERROR Internal error: No module named ovirt_setup_lib
>>
>> I tried removing ovirt-engine, and re-installing it, and dnf is telling
>> me:
>>
>>
>>
>> Error:
>> Problem: conflicting requests
>>  - nothing provides rubygem-fluent-plugin-rewrite-tag-filter needed by
>> ovirt-engine-4.3.0-0.0.master.20180225182524.git8b8f3a52a6.fc27.noarch
>>  - nothing provides rubygem-fluent-plugin-rewrite-tag-filter needed by
>> ovirt-engine-4.3.0-0.0.master.20180226201906.git5831910bef.fc27.noarch
>>  - nothing provides rubygem-fluent-plugin-rewrite-tag-filter needed by
>> ovirt-engine-4.3.0-0.0.master.20180227170348.git8b617da448.fc27.noarch
>>
>> What am I missing repo wise?
>>
>>
>>
>> > On Wed, Feb 28, 2018 at 11:05 AM, Yedidyah Bar David 
>>
>> >
>>
>> > wrote:
>>
>> > > (Adding devel, was asked twice already)
>>
>> > >
>>
>> > > On Wed, Feb 28, 2018 at 4:52 PM, Eli Mesika 
>> > > wrote:
>>
>> > > > Hi Didi
>>
>> > > >
>>
>> > > > I am getting :
>>
>> > > >
>>
>> > > >
>>
>> > > > ***L:ERROR Internal error: type object 'Stages' has no attribute
>>
>> > > > 'ANSWER_FILE_GENERATED'
>>
>> > > >
>>
>> > > > Traceback (most recent call last):
>>
>> > > > File "/usr/lib/python2.7/site-packages/otopi/__main__.py", line 88,
>> > > > in
>>
>> > > >
>>
>> > > > main
>>
>> > > >
>>
>> > > > installer.execute()
>>
>> > > >
>>
>> > > > File "/usr/lib/python2.7/site-packages/otopi/main.py", line 153, in
>>
>> > > >
>>
>> > > > execute
>>
>> > > >
>>
>> > > > sys.exc_info()[2],
>>
>> > > >
>>
>> > > > File "/usr/lib/python2.7/site-packages/otopi/util.py", line 81, in
>>
>> > > >
>>
>> > > > raiseExceptionInformation
>>
>> > > >
>>
>> > > > exec('raise info[1], None, info[2]')
>>
>> > > >
>>
>> > > > File "/usr/lib/python2.7/site-packages/otopi/main.py", line 147, in
>>
>> > > >
>>
>> > > > execute
>>
>> > > >
>>
>> > > > self.context.loadPlugins()
>>
>> > > >
>>
>> > > > File "/usr/lib/python2.7/site-packages/otopi/context.py", line 859,
>> > > > in
>>
>> > > >
>>
>> > > > loadPlugins
>>
>> > > >
>>
>> > > > self._loadPluginGroups(plugindir, needgroups, loadedgroups)
>>
>> > > >
>>
>> > > > File "/usr/lib/python2.7/site-packages/otopi/context.py", line 113,
>> > > > in
>>
>> > > >
>>
>> > > > _loadPluginGroups
>>
>> > > >
>>
>> > > > self._loadPlugins(path, path, groupname)
>>
>> > > >
>>
>> > > > File "/usr/lib/python2.7/site-packages/otopi/context.py", line 70,
>> > > > in
>>
>> > > >
>>
>> > > > _loadPlugins
>>
>> > > >
>>
>> > > > self._loadPlugins(base, d, groupname)
>>
>> > > >
>>
>> > > > File "/usr/lib/python2.7/site-packages/otopi/context.py", line 70,
>> > > > in
>>
>> > > >
>>
>> > > > _loadPlugins
>>
>> > > >
>>
>> > > > self._loadPlugins(base, d, groupname)
>>
>> > > >
>>
>> > > > File 

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2/Master (ovirt-engine-metrics) ] [ 28-02-2018 ] [ 002_bootstrap.verify_add_hosts]

2018-02-28 Thread Dafna Ron
Hi,

Shirly looked at the issue and she thinks that its related to bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1540260



On Wed, Feb 28, 2018 at 12:36 PM, Dafna Ron  wrote:

> Hi,
>
> We have a failure in test 002_bootstrap.verify_add_hosts.
>
> the issue seems to be a miss-configured role in ansible
>
>
> *Link and headline of suspected patches: *
>
>
>
>
>
>
> *Remove use of end_play and fail module -
> https://gerrit.ovirt.org/#/c/88250/
> Link to
> Job:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/950/
> Link to
> all
> logs:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/950/artifacts
> (Relevant)
> error snippet from the log: *
>
> 2018-02-28 05:01:29,984 p=17139 u=ovirt |  TASK 
> [oVirt.ovirt-include-vars-files : Include oVirt metrics config.yml.d vars 
> directory] ***
> 2018-02-28 05:01:30,007 p=17139 u=ovirt |  ok: [lago-basic-suite-4-2-host-0 
> -> localhost] => {
> "ansible_facts": {},
> "ansible_included_var_files": [],
> "changed": false
> }
> 2018-02-28 05:01:30,016 p=17139 u=ovirt |  TASK 
> [oVirt.ovirt-initial-validations/validate-config-yml : If output plugin is 
> elasticsearch, validate host address is set] ***
> 2018-02-28 05:01:30,047 p=17139 u=ovirt |  changed: 
> [lago-basic-suite-4-2-host-0 -> localhost] => {}
>
> MSG:
>
> ERROR oVirt Metrics store is not configured. This host will not be configured 
> to send metrics
>
> 2018-02-28 05:01:30,056 p=17139 u=ovirt |  TASK 
> [oVirt.ovirt-initial-validations/validate-config-yml : If output plugin is 
> fluentd, validate host address is set] ***
> 2018-02-28 05:01:30,073 p=17139 u=ovirt |  skipping: 
> [lago-basic-suite-4-2-host-0] => {
> "changed": false,
> "skip_reason": "Conditional result was False"
> }
> 2018-02-28 05:01:30,082 p=17139 u=ovirt |  TASK 
> [oVirt.ovirt-initial-validations/validate-config-yml : Validate 
> viaq_metrics_store parameter is set] ***
> 2018-02-28 05:01:30,111 p=17139 u=ovirt |  changed: 
> [lago-basic-suite-4-2-host-0 -> localhost] => {}
>
> MSG:
>
> ERROR viaq_metrics_store parameter is mandatory. Please set the parameter to 
> 'true' or 'false'.
>
> 2018-02-28 05:01:30,119 p=17139 u=ovirt |  TASK 
> [oVirt.ovirt-initial-validations/validate-config-yml : Validate 
> viaq_metrics_store parameter] ***
> 2018-02-28 05:01:30,137 p=17139 u=ovirt |  skipping: 
> [lago-basic-suite-4-2-host-0] => {
> "changed": false,
> "skip_reason": "Conditional result was False"
> }
> 2018-02-28 05:01:30,146 p=17139 u=ovirt |  TASK 
> [oVirt.ovirt-initial-validations/validate-config-yml : Validate 
> openshift_deployment_type parameter is set] ***
> 2018-02-28 05:01:30,168 p=17139 u=ovirt |  fatal: 
> [lago-basic-suite-4-2-host-0]: FAILED! => {}
>
> MSG:
>
> The conditional check 'viaq_metrics_store == true' failed. The error was: 
> error while evaluating conditional (viaq_metrics_store == true): 
> 'viaq_metrics_store' is undefined
>
> The error appears to have been in 
> '/usr/share/ansible/roles/oVirt.metrics/roles/oVirt.ovirt-initial-validations/validate-config-yml/tasks/main.yml':
>  line 48, column 3, but may
> be elsewhere in the file depending on the exact syntax problem.
>
> The offending line appears to be:
>
>
> - name: "Validate openshift_deployment_type parameter is set"
>   ^ here
>
>
> **
>
>
>
>
>
> *Thanks, Dafna*
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Exception: java.lang.IllegalArgumentException: OvsSupported has no value for version: 4.3

2018-02-28 Thread Nir Soffer
On Thu, Mar 1, 2018 at 1:02 AM Nir Soffer  wrote:

> Adding a host running vdsm master fail now with this error in engine
> 4.2.2.1-1.el7.centos
>
> 2018-02-28 22:52:07,847+02 ERROR
> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
> (EE-ManagedThreadFactory-engineScheduled-Thread-21) [] Unable to
> RefreshCapabilities: IllegalArgumentException: OvsSupported has no value
> for version: 4.3
>
> Engine is stuck in a loop, sending Host.getCapabilties, and failing.
>
> See error can be seen in OST when running vdsm master with engine 4.2:
>
> Engine:
>
> http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/2261/artifact/exported-artifacts/test_logs/basic-suite-4.2/post-002_bootstrap.py/lago-basic-suite-4-2-engine/_var_log/ovirt-engine/engine.log
>
> Vdsm:
>
> http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/2261/artifact/exported-artifacts/test_logs/basic-suite-4.2/post-002_bootstrap.py/lago-basic-suite-4-2-host-0/_var_log/vdsm/vdsm.log
>
> Adding same host running vdsm-4.19.2 works.
>
> Is this known issue?
>

Ok found https://bugzilla.redhat.com/1548819
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] Exception: java.lang.IllegalArgumentException: OvsSupported has no value for version: 4.3

2018-02-28 Thread Nir Soffer
Adding a host running vdsm master fail now with this error in engine
4.2.2.1-1.el7.centos

2018-02-28 22:52:07,847+02 ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
(EE-ManagedThreadFactory-engineScheduled-Thread-21) [] Unable to
RefreshCapabilities: IllegalArgumentException: OvsSupported has no value
for version: 4.3

Engine is stuck in a loop, sending Host.getCapabilties, and failing.

See error can be seen in OST when running vdsm master with engine 4.2:

Engine:
http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/2261/artifact/exported-artifacts/test_logs/basic-suite-4.2/post-002_bootstrap.py/lago-basic-suite-4-2-engine/_var_log/ovirt-engine/engine.log

Vdsm:
http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/2261/artifact/exported-artifacts/test_logs/basic-suite-4.2/post-002_bootstrap.py/lago-basic-suite-4-2-host-0/_var_log/vdsm/vdsm.log

Adding same host running vdsm-4.19.2 works.

Is this known issue?

Nir
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 (ovirt-hosted-engine-setup) ] [ 28-02-2018 ] [ 002_bootstrap.verify_add_all_hosts ]

2018-02-28 Thread Dafna Ron
Hi,
We failed test 002_bootstrap.verify_add_all_hosts. it seems that host1 did
not see master storage domain and the installation failed.

Please note that I found an error in the host messages log from firewalld
on eth0

*Link and headline of suspected patches: *






*ansible: enable gluster at cluster level -
https://gerrit.ovirt.org/#/c/88303/
Link to
Job:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/960/
Link to
all
logs:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/960/artifacts
(Relevant)
error snippet from the log: messages: *

Feb 28 11:55:17 lago-basic-suite-4-2-host-1 firewalld[564]: ERROR:
UNKNOWN_INTERFACE: 'eth0' is not in any zone

lago:

'1 hosts failed installation:\nlago-basic-suite-4-2-host-1:
non_operational\n\n >> begin captured logging <<
\novirtlago.testlib: ERROR: * Unhandled
exception in  at 0x2b6fe60>\nTraceback (most recent
call last):\n  File
"/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in
assert_equals_within\nres = func()\n  File
"/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test-scenarios/002_bootstrap.py",
line 426, in \nlambda: _all_hosts_up(hosts_service,
total_hosts),\n  File
"/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test-scenarios/002_bootstrap.py",
line 133, in _all_hosts_up\n
_check_problematic_hosts(hosts_service)\n  File
"/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test-scenarios/002_bootstrap.py",
line 153, in _check_problematic_hosts\nraise
RuntimeError(dump_hosts)\nRuntimeError: 1 hosts failed
installation:\nlago-basic-suite-4-2-host-1:
non_operational\n\n- >> end captured logging <<
-'

**
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [ACTION REQUIRED] upgrade to Fedora 27 for otopi on master

2018-02-28 Thread Greg Sheremeta
[changing subject]

Looks like we all have to upgrade Fedora devel machines to Fedora 27.

Greg

On Wed, Feb 28, 2018 at 11:05 AM, Yedidyah Bar David 
wrote:

> (Adding devel, was asked twice already)
>
> On Wed, Feb 28, 2018 at 4:52 PM, Eli Mesika  wrote:
> > Hi Didi
> >
> > I am getting :
> >
> >
> > ***L:ERROR Internal error: type object 'Stages' has no attribute
> > 'ANSWER_FILE_GENERATED'
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.7/site-packages/otopi/__main__.py", line 88, in
> > main
> > installer.execute()
> >   File "/usr/lib/python2.7/site-packages/otopi/main.py", line 153, in
> > execute
> > sys.exc_info()[2],
> >   File "/usr/lib/python2.7/site-packages/otopi/util.py", line 81, in
> > raiseExceptionInformation
> > exec('raise info[1], None, info[2]')
> >   File "/usr/lib/python2.7/site-packages/otopi/main.py", line 147, in
> > execute
> > self.context.loadPlugins()
> >   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 859, in
> > loadPlugins
> > self._loadPluginGroups(plugindir, needgroups, loadedgroups)
> >   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 113, in
> > _loadPluginGroups
> > self._loadPlugins(path, path, groupname)
> >   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 70, in
> > _loadPlugins
> > self._loadPlugins(base, d, groupname)
> >   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 70, in
> > _loadPlugins
> > self._loadPlugins(base, d, groupname)
> >   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 101, in
> > _loadPlugins
> > os.path.basename(path),
> >   File "/usr/lib/python2.7/site-packages/otopi/util.py", line 105, in
> > loadModule
> > mod_desc
> >   File
> > "/home/emesika/ovirt-engine-1481197/share/ovirt-engine/
> setup/bin/../plugins/ovirt-engine-common/base/core/__init__.py",
> > line 24, in 
> > from . import answerfile
> >   File
> > "/home/emesika/ovirt-engine-1481197/share/ovirt-engine/
> setup/bin/../plugins/ovirt-engine-common/base/core/answerfile.py",
> > line 38, in 
> > class Plugin(plugin.PluginBase):
> >   File
> > "/home/emesika/ovirt-engine-1481197/share/ovirt-engine/
> setup/bin/../plugins/ovirt-engine-common/base/core/answerfile.py",
> > line 60, in Plugin
> > otopicons.Stages.ANSWER_FILE_GENERATED,
> > PluginLoadException: type object 'Stages' has no attribute
> > 'ANSWER_FILE_GENERATED'
> >
>
> Please update otopi.
>
> If you are on fedora, you'll need to upgrade to fc27 first.
>
> Good luck,
> --
> Didi
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] problem in engine-setup after sync

2018-02-28 Thread Yedidyah Bar David
(Adding devel, was asked twice already)

On Wed, Feb 28, 2018 at 4:52 PM, Eli Mesika  wrote:
> Hi Didi
>
> I am getting :
>
>
> ***L:ERROR Internal error: type object 'Stages' has no attribute
> 'ANSWER_FILE_GENERATED'
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/otopi/__main__.py", line 88, in
> main
> installer.execute()
>   File "/usr/lib/python2.7/site-packages/otopi/main.py", line 153, in
> execute
> sys.exc_info()[2],
>   File "/usr/lib/python2.7/site-packages/otopi/util.py", line 81, in
> raiseExceptionInformation
> exec('raise info[1], None, info[2]')
>   File "/usr/lib/python2.7/site-packages/otopi/main.py", line 147, in
> execute
> self.context.loadPlugins()
>   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 859, in
> loadPlugins
> self._loadPluginGroups(plugindir, needgroups, loadedgroups)
>   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 113, in
> _loadPluginGroups
> self._loadPlugins(path, path, groupname)
>   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 70, in
> _loadPlugins
> self._loadPlugins(base, d, groupname)
>   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 70, in
> _loadPlugins
> self._loadPlugins(base, d, groupname)
>   File "/usr/lib/python2.7/site-packages/otopi/context.py", line 101, in
> _loadPlugins
> os.path.basename(path),
>   File "/usr/lib/python2.7/site-packages/otopi/util.py", line 105, in
> loadModule
> mod_desc
>   File
> "/home/emesika/ovirt-engine-1481197/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/base/core/__init__.py",
> line 24, in 
> from . import answerfile
>   File
> "/home/emesika/ovirt-engine-1481197/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/base/core/answerfile.py",
> line 38, in 
> class Plugin(plugin.PluginBase):
>   File
> "/home/emesika/ovirt-engine-1481197/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-common/base/core/answerfile.py",
> line 60, in Plugin
> otopicons.Stages.ANSWER_FILE_GENERATED,
> PluginLoadException: type object 'Stages' has no attribute
> 'ANSWER_FILE_GENERATED'
>

Please update otopi.

If you are on fedora, you'll need to upgrade to fc27 first.

Good luck,
-- 
Didi
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel


[ovirt-devel] [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [28-02-2018 ] [ 001_upgrade_engine.test_initialize_engine ]

2018-02-28 Thread Dafna Ron
Hi,

We are failing 001_upgrade_engine.test_initialize_engine.
Please note that I tested a change to the repo and added the missing
package to the include list but we failed the check-patch on AssertionError
on metrics deploy.
we may need a different version of the package then what we have or it may
be connected to a different metrics issue.
can you please have a look? here is my patch:
https://gerrit.ovirt.org/#/c/88285/


*Link and headline of suspected patches: *



*gluster: Create role for brick creation -
https://gerrit.ovirt.org/#/c/87902/
Link to
Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5895
Link to
all logs:*
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5895/artifacts


*(Relevant) error snippet from the log: *

[ INFO  ] Checking for an update for Setup...
[ ERROR ] Yum 
[u'ovirt-engine-tools-4.3.0-0.0.master.20180228083846.giteda138a.el7.centos.noarch
requires gdeploy']
[ INFO  ] Yum Performing yum transaction rollback
[ ERROR ] Failed to execute stage 'Environment customization':
[u'ovirt-engine-tools-4.3.0-0.0.master.20180228083846.giteda138a.el7.centos.noarch
requires gdeploy']
[ INFO  ] Stage: Clean up
  Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20180228045320-vriokc.log
[ INFO  ] Generating answer file
'/var/lib/ovirt-engine/setup/answers/20180228045325-setup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed
("FATAL Internal error (main):
[u'ovirt-engine-tools-4.3.0-0.0.master.20180228083846.giteda138a.el7.centos.noarch
requires gdeploy']",)

lago.ssh: DEBUG: Command 354050da on
lago-upgrade-from-release-suite-master-engine  errors:
 Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/otopi/__main__.py", line 88, in main
installer.execute()
  File "/usr/lib/python2.7/site-packages/otopi/main.py", line 157, in execute
self.context.runSequence()
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 771,
in runSequence
util.raiseExceptionInformation(infos[0])
  File "/usr/lib/python2.7/site-packages/otopi/util.py", line 81, in
raiseExceptionInformation
exec('raise info[1], None, info[2]')
  File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133,
in _executeMethod
method['method']()
  File 
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-common/distro-rpm/packages.py",
line 417, in _customization
) = self._checkForProductUpdate()
  File 
"/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-common/distro-rpm/packages.py",
line 248, in _checkForProductUpdate
if mpm.buildTransaction():
  File "/usr/lib/python2.7/site-packages/otopi/miniyum.py", line 920,
in buildTransaction
raise yum.Errors.YumBaseError(msg)
YumBaseError: 
[u'ovirt-engine-tools-4.3.0-0.0.master.20180228083846.giteda138a.el7.centos.noarch
requires gdeploy']


**
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [ OST Failure Report ] [ oVirt 4.2/Master (ovirt-engine-metrics) ] [ 28-02-2018 ] [ 002_bootstrap.verify_add_hosts]

2018-02-28 Thread Dafna Ron
Hi,

We have a failure in test 002_bootstrap.verify_add_hosts.

the issue seems to be a miss-configured role in ansible


*Link and headline of suspected patches: *






*Remove use of end_play and fail module -
https://gerrit.ovirt.org/#/c/88250/
Link to
Job:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/950/
Link to
all
logs:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/950/artifacts
(Relevant)
error snippet from the log: *

2018-02-28 05:01:29,984 p=17139 u=ovirt |  TASK
[oVirt.ovirt-include-vars-files : Include oVirt metrics config.yml.d
vars directory] ***
2018-02-28 05:01:30,007 p=17139 u=ovirt |  ok:
[lago-basic-suite-4-2-host-0 -> localhost] => {
"ansible_facts": {},
"ansible_included_var_files": [],
"changed": false
}
2018-02-28 05:01:30,016 p=17139 u=ovirt |  TASK
[oVirt.ovirt-initial-validations/validate-config-yml : If output
plugin is elasticsearch, validate host address is set] ***
2018-02-28 05:01:30,047 p=17139 u=ovirt |  changed:
[lago-basic-suite-4-2-host-0 -> localhost] => {}

MSG:

ERROR oVirt Metrics store is not configured. This host will not be
configured to send metrics

2018-02-28 05:01:30,056 p=17139 u=ovirt |  TASK
[oVirt.ovirt-initial-validations/validate-config-yml : If output
plugin is fluentd, validate host address is set] ***
2018-02-28 05:01:30,073 p=17139 u=ovirt |  skipping:
[lago-basic-suite-4-2-host-0] => {
"changed": false,
"skip_reason": "Conditional result was False"
}
2018-02-28 05:01:30,082 p=17139 u=ovirt |  TASK
[oVirt.ovirt-initial-validations/validate-config-yml : Validate
viaq_metrics_store parameter is set] ***
2018-02-28 05:01:30,111 p=17139 u=ovirt |  changed:
[lago-basic-suite-4-2-host-0 -> localhost] => {}

MSG:

ERROR viaq_metrics_store parameter is mandatory. Please set the
parameter to 'true' or 'false'.

2018-02-28 05:01:30,119 p=17139 u=ovirt |  TASK
[oVirt.ovirt-initial-validations/validate-config-yml : Validate
viaq_metrics_store parameter] ***
2018-02-28 05:01:30,137 p=17139 u=ovirt |  skipping:
[lago-basic-suite-4-2-host-0] => {
"changed": false,
"skip_reason": "Conditional result was False"
}
2018-02-28 05:01:30,146 p=17139 u=ovirt |  TASK
[oVirt.ovirt-initial-validations/validate-config-yml : Validate
openshift_deployment_type parameter is set] ***
2018-02-28 05:01:30,168 p=17139 u=ovirt |  fatal:
[lago-basic-suite-4-2-host-0]: FAILED! => {}

MSG:

The conditional check 'viaq_metrics_store == true' failed. The error
was: error while evaluating conditional (viaq_metrics_store == true):
'viaq_metrics_store' is undefined

The error appears to have been in
'/usr/share/ansible/roles/oVirt.metrics/roles/oVirt.ovirt-initial-validations/validate-config-yml/tasks/main.yml':
line 48, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:


- name: "Validate openshift_deployment_type parameter is set"
  ^ here


**





*Thanks, Dafna*
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] engine master failing build on fcraw

2018-02-28 Thread Yedidyah Bar David
On Mon, Feb 26, 2018 at 2:55 PM, Sandro Bonazzola 
wrote:

>
>
> 2018-02-26 12:59 GMT+01:00 Eyal Edri :
>
>>
>>
>> On Mon, Feb 26, 2018 at 1:23 PM, Gobinda Das  wrote:
>>
>>> I have couple of patches, build failing due to same issue.
>>> https://gerrit.ovirt.org/#/c/85885/
>>> https://gerrit.ovirt.org/#/c/87964/
>>>
>>> org.ovirt.engine.core.dal.dbbroker.DbConnectionUtilTest  Time elapsed: 1437 
>>> sec  <<< FAILURE!*16:36:08* java.lang.AssertionError: Unable to init 
>>> tests*16:36:08*at 
>>> org.ovirt.engine.core.dao.BaseDaoTestCase.initTestCase(BaseDaoTestCase.java:84)*16:36:08*
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
>>> Method)*16:36:08*at 
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*16:36:08*
>>>   at 
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>
>>> .
>>>
>>> .
>>>
>>> .
>>>
>>>
>>> Is it necessary, all patches need to pass on fcraw?
>>>
>>>
>>
>> Yes, if ovirt-engine has build-artifacts for fcraw, it has to pass,
>> otherwise no new engine build will be deployed to tested repo until it's
>> fixed.
>> If it can't be fixed, the fcraw build-artifacts job needs to be removed.
>>
>
> As a side note, retriggering the fcraw build on a different slave usually
> is enough for getting the job passing.
>

Can you give an example?


> I think it's not a fcraw bug but either an env or test bug.
>

Perhaps. Filed [1] to track this.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1550033


>
>
>>
>>
>>>
>>>
>>>
>>> On Wed, Feb 14, 2018 at 11:35 PM, Eli Mesika  wrote:
>>>
 May this be related to the PG JDBC driver issue [1]


 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1459499 ???

 On Fri, Feb 9, 2018 at 2:47 PM, Sandro Bonazzola 
 wrote:

> Hi,
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch
> -fcraw-x86_64/114/consoleFull
>
> failed on fcraw with:
>
> *10:59:21* Failed tests:   
> org.ovirt.engine.core.dal.dbbroker.DbConnectionUtilTest: Unable to init 
> tests
>
>
> Test output was:
>
> *10:59:11* Running 
> org.ovirt.engine.core.dal.dbbroker.DbConnectionUtilTest*10:59:13* Tests 
> run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.296 sec <<< 
> FAILURE!*10:59:13* 
> org.ovirt.engine.core.dal.dbbroker.DbConnectionUtilTest  Time elapsed: 
> 2287 sec  <<< FAILURE!*10:59:13* java.lang.AssertionError: Unable to init 
> tests*10:59:13*at 
> org.ovirt.engine.core.dao.BaseDaoTestCase.initTestCase(BaseDaoTestCase.java:84)*10:59:13*
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)*10:59:13*at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*10:59:13*
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*10:59:13*
>   at java.lang.reflect.Method.invoke(Method.java:498)*10:59:13*   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)*10:59:13*
>at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)*10:59:13*
> at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)*10:59:13*
>  at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)*10:59:13*
>   at 
> org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)*10:59:13*
>at 
> org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)*10:59:13*
>  at 
> org.junit.runners.ParentRunner.run(ParentRunner.java:363)*10:59:13*  at 
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:191)*10:59:13*
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)*10:59:13*
>at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)*10:59:13*
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)*10:59:13*
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)*10:59:13*at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*10:59:13*
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*10:59:13*
>   at java.lang.reflect.Method.invoke(Method.java:498)*10:59:13*   at 
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)*10:59:13*
>  at 
> 

Re: [ovirt-devel] FC27 updates broken for ovirt-4.2

2018-02-28 Thread Dan Horák
On Tue, 27 Feb 2018 16:26:28 -0500
Cole Robinson  wrote:

> On 02/27/2018 08:03 AM, Dan Horák wrote:
> > On Tue, 27 Feb 2018 13:54:06 +0100
> > Viktor Mihajlovski  wrote:
> > 
> >> On 27.02.2018 13:35, Nir Soffer wrote:
> >>> בתאריך יום ג׳, 27 בפבר׳ 2018, 13:25, מאת Dan Horák
> >>>  ‏:
> >>>
>  On Tue, 27 Feb 2018 10:13:15 +0100
>  Viktor Mihajlovski  wrote:
> 
> > On 27.02.2018 01:26, Nir Soffer wrote:
> >> בתאריך יום ב׳, 26 בפבר׳ 2018, 22:10, מאת Yaniv Kaul
> >>  ‏:
> >>
> >>> On Mon, Feb 26, 2018 at 7:17 PM, Viktor Mihajlovski <
> >>> mihaj...@linux.vnet.ibm.com> wrote:
> >>>
>  I just tried to update the ovirt packages on my FC27 host,
>  but failed due to https://gerrit.ovirt.org/#/c/87628/
> 
>  vdsm now requires libvirt >= 3.10.0-132 but Fedora 27 has
>  only 3.7.0-4 the moment.
> 
>  It's generic Fedora 27, but since I run on s390,
>  cross-posting to s390 list.
> 
>  I guess there's good reason to require libvirt 3.10. Is there
>  any chance that we can get libvirt updated for Fedora 27?
> 
> >>>
> >>> Perhaps use the virt-preview[1] repo for now?
> >>>
> >>
> >> Yes, we require virt-preview for Fedora. This is why that patch
> >> did not fail in the CI.
> > Makes sense, unfortunately virt-preview doesn't contains s390
> > binaries at this point in time. Would be great if at least
> > libvirt and qemu could be built for s390.
> 
>  looks like it's even x86_64 only, /me wonders what it would
>  require to offer other arches (aarch64, ppc64le, s390x) as well
> 
> >>>
> >>> If we need to support platform not supported in virt-preview, we
> >>> need to chage the requirement so it is used only on x86_64.
> >>>
> >>> Victor, would you like to send a patch?
> >> I believe there was a good reason to bump the libvirt requirement
> >> in the vdsm package (some bugfix). Ideally, virt-preview should be
> >> build for s390 as well.
> >> If I'm not mistaking, the script
> >> https://github.com/crobinso/build-fedora-virt-preview is used to
> >> build the RPMs and populate the repository.
> >>
> >> Dan, Cole: what would it take to run this on the fedora-390 build
> >> machine?
> > 
> > after a brief look the script needs to be made multi-arch-aware (it
> > hard-codes x86_64 in some places), when it calls mock, and then it
> > needs some HW (we have ppc64le and s390x even now, aarch64 might
> > take a while), overall it looks doable to me. Cole, what do you
> > think?
> > 
> 
> I'm open to the idea in theory but in practice right now the script
> uses mock locally so it's basically tied to the one build machine I
> use which is x86. I have arm32 and aarch64 hardware locally but TBH I
> have very little interest in running a build farm and dealing with
> all the issues of connecting to remote machines, pulling down build
> output, etc. In fact I've been meaning to move virt-preview to copr
> for a long while which is going to tie it even deeper to x86, this
> would make virt-preview easier to enable and let me scrap much of my
> custom code for building/uploading repo contents.

copr would give us ppc64le and probably aarch64 too in addition to x86,
but can't help with s390. We already have build infra internally
covering all arches driven by Jenkins, with plans to move the workloads
to CentOS infra. I'll look whether or how it could be used for
multi-arch virt-preview repos. 

> We could re-implement it using koji scratch builds which have multiple
> arch support nowadays but I did that in the past for x86 and I recall
> feeling it was quite brittle, though I don't remember the details,
> maybe it was just my implementation.

I suspect the problem with koji scratch builds in this case is that
they can't be used in buildroots, which the virt-preview stack requires.


Dan
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel