SSL: UNKNOWN_PROTOCOL error when running Lago init during System Tests setup.
by raymond.francis＠oracle.com
Trying to nail down the setup in the System Test Setup guide
https://ovirt-system-tests.readthedocs.io/en/latest/general/installation/...
and i come to an issue when i run the suite.
lago init /Ray/ovirt-system-tests/deployment-basic-suite-4.3 /Ray/ovirt-system-tests/basic-suite-4.3/LagoInitFile --template-repo-path /Ray/ovirt-system-tests/basic-suite-4.3/template-repo.json
@ Initialize and populate prefix:
# Initialize prefix:
* Create prefix dirs:
* Create prefix dirs: Success (in 0:00:00)
* Generate prefix uuid:
* Generate prefix uuid: Success (in 0:00:00)
* Create ssh keys:
* Create ssh keys: Success (in 0:00:00)
* Tag prefix as initialized:
* Tag prefix as initialized: Success (in 0:00:00)
# Initialize prefix: Success (in 0:00:00)
# Create disks for VM lago-basic-suite-4-3-engine:
* Create disk root:
- Template phx_repo:el7.6-base-5:v1 not in cache, downloading
- Download image el7.6-base-5:
- Download image el7.6-base-5: ERROR (in 0:00:00)
* Create disk root: ERROR (in 0:00:00)
# Create disks for VM lago-basic-suite-4-3-engine: ERROR (in 0:00:00)
# Missing current link, setting it to default
@ Initialize and populate prefix: ERROR (in 0:00:01)
Error occured, aborting
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/lago/cmd.py", line 969, in main
cli_plugins[args.verb].do_run(args)
File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in do_run
self._do_run(**vars(args))
File "/usr/lib/python2.7/site-packages/lago/cmd.py", line 194, in do_init
do_build=not skip_build,
File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1113, in virt_conf_from_stream
do_build=do_build
File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1228, in virt_conf
template_store=template_store,
File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1133, in _prepare_domains_images
template_store=template_store,
File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1155, in _prepare_domain_image
template_store=template_store,
File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1183, in _create_disks
template_store=template_store,
File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 669, in _create_disk
template_store=template_store,
File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 798, in _handle_template
template_repo=template_repo,
File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 935, in _handle_lago_template
template_store.download(template_version)
File "/usr/lib/python2.7/site-packages/lago/templates.py", line 645, in download
temp_ver.download(temp_dest)
File "/usr/lib/python2.7/site-packages/lago/templates.py", line 528, in download
self._source.download_image(self._handle, destination)
File "/usr/lib/python2.7/site-packages/lago/templates.py", line 196, in download_image
self.open_url(url=handle, dest=dest)
File "/usr/lib/python2.7/site-packages/lago/templates.py", line 148, in open_url
dest=dest,
File "/usr/lib/python2.7/site-packages/lago/templates.py", line 153, in open_url
response = urllib.urlopen(full_url)
File "/usr/lib64/python2.7/urllib.py", line 87, in urlopen
return opener.open(url)
File "/usr/lib64/python2.7/urllib.py", line 210, in open
return getattr(self, name)(url)
File "/usr/lib64/python2.7/urllib.py", line 439, in open_https
h.endheaders(data)
File "/usr/lib64/python2.7/httplib.py", line 1052, in endheaders
self._send_output(message_body)
File "/usr/lib64/python2.7/httplib.py", line 890, in _send_output
self.send(msg)
File "/usr/lib64/python2.7/httplib.py", line 852, in send
self.connect()
File "/usr/lib64/python2.7/httplib.py", line 1275, in connect
server_hostname=sni_hostname)
File "/usr/lib64/python2.7/ssl.py", line 348, in wrap_socket
_context=self)
File "/usr/lib64/python2.7/ssl.py", line 609, in __init__
self.do_handshake()
File "/usr/lib64/python2.7/ssl.py", line 831, in do_handshake
self._sslobj.do_handshake()
IOError: [Errno socket error] [SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:618)
4 years, 6 months
Unable to Build (Unable to find 'org/ovirt/engine/ui/webadmin/WebAdmin.gwt.xml)
by Ritesh Chikatwar
Hey Guys,
Please do let me know what is causing me this issue.
*NOTE:* I have not changed anything in this file.
info register aspect org.ovirt.engine.ui.gwtaop.DontPrune
[INFO] Loading inherited module 'org.ovirt.engine.ui.webadmin.WebAdmin'
*[INFO] [ERROR] Unable to find
'org/ovirt/engine/ui/webadmin/WebAdmin.gwt.xml' on your classpath; could be
a typo, or maybe you forgot to include a classpath entry for source?*
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary for WebAdmin 4.4.0-SNAPSHOT:
[INFO]
[INFO] WebAdmin ........................................... FAILURE [
1.548 s]
[INFO] oVirt Server EAR ................................... SKIPPED
[INFO] ovirt-engine maven make ............................ SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 1.918 s
[INFO] Finished at: 2019-10-21T11:30:20+05:30
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.codehaus.mojo:gwt-maven-plugin:2.8.0:compile (default-cli) on project
webadmin: Command [[
[ERROR] /bin/sh -c '/usr/local/jdk-11.0.2/bin/java'
'-javaagent:/home/ritesh/.m2/repository/org/aspectj/aspectjweaver/1.9.3.RC1/aspectjweaver-1.9.3.RC1.jar'
'-Dgwt.jjs.permutationWorkerFactory=com.google.gwt.dev.ThreadedPermutationWorkerFactory'
'-Dgwt.jjs.maxThreads=4'
'-Djava.io.tmpdir=/home/ritesh/build/ovirt-engine/frontend/webadmin/modules/webadmin/target/tmp'
'-Djava.util.prefs.systemRoot=/home/ritesh/build/ovirt-engine/frontend/webadmin/modules/webadmin/target/tmp'
'-Djava.util.prefs.userRoot=/home/ritesh/build/ovirt-engine/frontend/webadmin/modules/webadmin/target/tmp'
'-Djava.util.logging.config.class=org.ovirt.engine.ui.gwtaop.JavaLoggingConfig'
'-Xms1024M' '-Xmx8192M'
'-Dgwt.dontPrune=org\.ovirt\.engine\.core\.(common|compat)\..*'
'com.google.gwt.dev.Compiler' '-logLevel' 'INFO' '-war'
'/home/ritesh/build/ovirt-engine/frontend/webadmin/modules/webadmin/target/webadmin-4.4.0-SNAPSHOT'
'-localWorkers' '8' '-failOnError' '-XfragmentCount' '-1' '-sourceLevel'
'auto' '-gen'
'/home/ritesh/build/ovirt-engine/frontend/webadmin/modules/webadmin/gen'
'org.ovirt.engine.ui.webadmin.WebAdmin'
[ERROR] ]] failed with status 1.
Thanks And Regards
Ritesh Chikatwar
4 years, 6 months
[oVirt] [CQ weekly status] [20-10-2019]
by Dusan Fodor
Hi,
This mail is to provide the current status of CQ and allow people to review
status before and after the weekend.
Please refer to below colour map for further information on the meaning of
the colours.
*CQ-4.3*: GREEN (#1)
Last failure was on 17-10 for ovirt-node-ng-image due to an issue with host
it was building on. Next run passed well.
.
*CQ-Master:* YELLOW (#1
Last failure was on 18-10 caused by known, random add storage domain
failure (test issue).
Current running jobs for 4.3 [1] and master [2] can be found here:
[1]
https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change...
[2]
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chan...
Have a nice week!
Dusan
-------------------------------------------------------------------------------------------------------------------
COLOUR MAP
Green = job has been passing successfully
** green for more than 3 days may suggest we need a review of our test
coverage
1.
1-3 days GREEN (#1)
2.
4-7 days GREEN (#2)
3.
Over 7 days GREEN (#3)
Yellow = intermittent failures for different projects but no lasting or
current regressions
** intermittent would be a healthy project as we expect a number of
failures during the week
** I will not report any of the solved failures or regressions.
1.
Solved job failures YELLOW (#1)
2.
Solved regressions YELLOW (#2)
Red = job has been failing
** Active Failures. The colour will change based on the amount of time the
project/s has been broken. Only active regressions would be reported.
1.
1-3 days RED (#1)
2.
4-7 days RED (#2)
3.
Over 7 days RED (#3)
_______________________________________________
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YCNCKRK3G4E...
4 years, 6 months
Add existing Affinity Label to Host
by scott.fitzgerald＠oracle.com
As the title, have tried to add it using
sysService.hostsService().hostService(hostID).affinityLabelsService().add().label(sysService.affinityLabelsService().labelService(labelID).get().send().label()).send();
and similar variants with no luck.
TIA
4 years, 6 months
Retrieve cluster status using the SDK
by Jamie Holohan
Using the SDK how can I retrieve a clusters (network) status. I am able to retrieve a cluster object using code like this:
Cluster cluster = sysService.clustersService().clusterService(DataCenterUtils.getClusterObjectFromName(sysService, DEFAULT_CLUSTER_NAME).id()).get().send().cluster();
However I cannot see any variables associated with this object type that relate to its Network Status.
The information i'm referring to can be found on the UI after creating a custom network. Starting on the left panel Navigate to Network -> Networks -> Custom Network -> Clusters Tab
4 years, 6 months
Clarifications on support@
by Marc Dequènes (Duck)
Quack,
We do as a community provide help on the MLs and reply to JIRA tickets
but there is no customer support as it is not a product but a community
project.
Historically, probably for some other purpose, support@ was created, but
noone remembers why. Anyway, the alias redirected to postmaster so it
was not very useful. There was also a ML which could not receive mails
because of the alias but probably got noticed in the new ML UI when we
migrated. Recently more people subscribed and posted requests using the UI.
After discussing with the infra team, and to avoid confusion and
unreplied requests on this channel, we decided to remove it. I thus
unsubscribed people from the list so that they would notice it and then
purged the list and alias.
Regards.
\_o<
4 years, 6 months
Problem with vdsm 'make check'
by Kaustav Majumder
Hi,
I am having an issue running make check on vdsm master.
`
if [ -n "$NOSE_WITH_COVERAGE" ]; then \
mv .coverage .coverage-nose-py27; \
fi
Traceback (most recent call last):
File "../tests/testrunner.py", line 70, in <module>
from vdsm import constants
File "/home/kmajumde/work/git/vdsm/lib/vdsm/constants.py", line 29, in
<module>
from vdsm.common.constants import * # NOQA: F401, F403
`
Am I missing something? Do I need to run tests differently?
--
Thanks,
Kaustav Majumder
4 years, 6 months
Re: Problem with vdsm 'make check'
by Prajith Kesava Prasad
hey,
even im facing a issue with make check, i have installed all the libraries,
the following occurs on fedora 29, IDE:Pycharm
could some one help me with this?
Thanks,
Prajith Kesava Prasad
4 years, 6 months
