can't clone vm from export domain via rest/json
by Sven Kieske
Hi,
I need some devel power here:
this is on ovirt 3.3.3 el6 (yes I know, I need to upgrade..)
error while cloning a vm from export to local storage data domain:
POST
https://REDACTED/api/storagedomains/e89fdbcb-cb51-42b7-b42c-7f4f0ec1f580/...
{
"storageDomain":{"id":"15679d40-0f20-4a0e-9880-eb5795cb8d1e","name":"LOCAL_DATA_DOMAIN_NAME"},
"cluster":{"id":"e65dc5f5-61e6-4d17-a5bf-33c677d129c7"},
"vm":{"name":"VM_NAME_1"},
"clone":true
}
ANSWER:
{
"storageDomain":{
"name":"LOCAL_DATA_DOMAIN_NAME",
"id":"15679d40-0f20-4a0e-9880-eb5795cb8d1e"
},
"cluster":{
"id":"e65dc5f5-61e6-4d17-a5bf-33c677d129c7"
},
"vm":{
"name":"VM_NAME_2"
},
"clone":true,
"status":{
"state":"failed"
},
"fault":{
"reason":"Operation Failed",
"detail":"[action type failed import clone not collapsed]"
}
}
why does it fail?
this vm was exported from this storage domain onto the export
domain and should then get re-imported as another vm-name
is this because of lacking/inconsistent json support in 3.3.z?
until now we were able to reverse engineer all needed functionality
via json.
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
10 years, 1 month
Building vdsm within Fedora
by Dan Kenigsberg
Since Vdsm was open-sourced, it was built and deployed via
Fedora.
Recently [http://gerrit.ovirt.org/31214] vdsm introduced a spec-file
dependency onf qemu-kvm-rhev, and considered to backport it to the
ovirt-3.4 brach.
Requiring qemu-kvm-rhev, which is not part of Fedora's EPEL6 branch,
violates Fedora's standards.
So basically we have two options:
1. Revert the qemu-kvm-rhev dependency.
2. Drop vdsm from EPEL6 (or completely from Fedora); ship Vdsm only
within the oVirt repositories.
A third option would be to have one rpm, with qemu-kvm-rhev, shipped in
ovirt, and another without it - shipped in Fedora. I find this overly
complex and confusing.
I favor option 2. The Fedora deployment platform served us well for a
long time, but now that ovirt is maturing, we no longer need it for
building vdsm. This has the added benefit of removing the need to pass
through Fedora's ghastly gateway when adding a Vdsm dependency.
Sandro, what should be done in order to build Vdsm by ovirt, occording
to the most up-to-date tag in a stable branch?
Does anybody object this? If no one does, we would stop updating Vdsm in
Fedora, and obsolete it in the future.
Regards,
Dan.
10 years, 1 month
[QE][ACTION REQUIRED] oVirt 3.5.0 status - Go / No Go
by Sandro Bonazzola
Hi,
We are supposed to start composing oVirt 3.5.0 GA on Monday 2014-09-29.
Maintainers:
- Please be sure that 3.5 snapshot satisfy release criteria[9]
- Please be sure that no pending patches are going to block the release
- If any patch must block the GA release please raise the issue as soon as possible.
- If any packages need a rebase please raise the issue as soon as possible.
- Be aware that packages that doesn't need a rebase must be re-built with final release versioning from the RC3 tag.
And then:
- Please build your packages with final release versioning for Monday 2014-09-29 10:00 UTC if we agree on releasing GA.
The bug tracker [1] shows no blockers.
The following bugs are keyworded as Regression and not marked as blockers[10]
Bug ID Whiteboard Status Summary
1142647 gluster NEW supervdsm leaks memory when using glusterfs
1138144 storage NEW Failed to autorecover storage domain after unblocking connection with host
1118349 storage NEW [vdsm] Creating DataCenter 3.5 using master domain V1 fails with InquireNotSupportedError
1138314 virt POST Fail to start vm with payload.
Feature freeze is now effective, and branch has been created.
All new patches must be backported to 3.5 branch too.
Features completed are marked in green on Features Status Table [2]
There are still 66 bugs [3] targeted to 3.5.0.
Excluding node and documentation bugs we still have 43 bugs [4] targeted to 3.5.0.
More in detail [5]:
Whiteboard NEW ASSIGNED POST Total
docs 13 1 0 14
gluster 4 0 2 6
i18n 0 0 1 1
infra 1 0 0 1
integration 0 0 1 1 (3.5.0 Tracker)
node 8 4 0 12
ppc 2 0 4 6
sla 12 0 2 14
storage 1 0 2 3
virt 3 1 4 8
Total 44 6 16 66
Maintainers / Assignee:
- Please ensure that completed features are marked in green on Features Status Table [2]
- If you find a blocker bug please remember to add it to the tracker [1]
- Please fill release notes, the page has been created here [6]
- Please review results from Third Test Day on the etherpad [7] and on the mailing lists
- Please update the target to 3.5.1 or later for bugs that won't be in 3.5.0:
it will ease gathering the blocking bugs for next releases.
Community:
- You're welcome to join us testing last release candidate or nightly builds and getting involved in oVirt Quality Assurance[8]
[1] http://bugzilla.redhat.com/1073943
[2] http://goo.gl/4SuYdE
[3] http://red.ht/1pVEk7H
[4] http://red.ht/1zT2mSq
[5] http://red.ht/1q7SqNL
[6] http://www.ovirt.org/OVirt_3.5_Release_Notes
[7] http://etherpad.ovirt.org/p/3.5-testday-3
[8] http://www.ovirt.org/OVirt_Quality_Assurance
[9] http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria_.28WIP.29
[10] http://goo.gl/uavikG
Thanks,
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 1 month
Release notes / announcements and security fixes
by Sandro Bonazzola
Il 24/09/2014 09:31, Sven Kieske ha scritto:
>
>
> On 23/09/14 23:05, Sandro Bonazzola wrote:
>> [1] http://www.ovirt.org/OVirt_3.4.4_Release_Notes
>
> First, thanks for the new release, but I have one objection to make:
Thanks for the highlight, changed subject for making this more visible.
>
> Hidden in the release notes we find:
>
> BZ 1139000 - CVE-2014-3573 ovirt-engine-backend: oVirt Engine: XML
> eXternal Entity (XXE) flaw in backend module
>
> So I'd like to discuss if security fixes should not be highlighted
> somewhat more?
>
> I'd expect the following:
>
> a) Mention at least that CVEs where fixed in this release in the
> announcement.
> b) a category "security patches" (or similar) in the release notes
> where these fixes get listed.
> c) This new category should be at the top of the release notes.
>
> What do you think?
Make sense.
Updated 3.4.4 Release notes as per points b and c.
http://www.ovirt.org/OVirt_3.4.4_Release_Notes
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 2 months
[ovirt-users] [OVIRT-3.5-TEST-DAY-3] Optaplanner
by Piotr Kliczewski
Hi,
I followed deployment manual from [1] and configured two DCs with
single cluster each.
During configuration of the UI I noticed that in optimizer result tab there was:
Status: Data refresh failed: undefined
with Martin's help we found that when setting
security.mixed_content.block_active_content
to false in FF configuration it works and I can see:
Status: Solution received
During the installation of second host network configuration failed
and I opened BZ [2].
When I restored network configuration to the host I wanted to
provision vms to see optaplanner
suggestions but my rhel6 failed to start any vms due to:
Thread-8102::DEBUG::2014-09-17
16:36:16,216::libvirtconnection::143::root::(wrapper) Unknown
libvirterror: ecode: 38 edom: 0 level: 2 message: Child quit during
startup handshake: Input/output error
Thread-8102::DEBUG::2014-09-17
16:36:16,217::vm::2289::vm.Vm::(_startUnderlyingVm)
vmId=`9343ea99-4c27-47d3-a4b6-4bd37013ae99`::_ongoingCreations
released
Thread-8102::ERROR::2014-09-17
16:36:16,217::vm::2326::vm.Vm::(_startUnderlyingVm)
vmId=`9343ea99-4c27-47d3-a4b6-4bd37013ae99`::The vm start process
failed
Traceback (most recent call last):
File "/usr/share/vdsm/virt/vm.py", line 2266, in _startUnderlyingVm
self._run()
File "/usr/share/vdsm/virt/vm.py", line 3368, in _run
self._connection.createXML(domxml, flags),
File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py",
line 111, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2665, in createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)
libvirtError: Child quit during startup handshake: Input/output error
Thread-8102::DEBUG::2014-09-17
16:36:16,218::vm::2838::vm.Vm::(setDownStatus)
vmId=`9343ea99-4c27-47d3-a4b6-4bd37013ae99`::Changed state to Down:
Child quit during startup handshake: Input/output error (code=1)
Vdsm is not able to start any vms but engine still thinks that host is 'UP'.
Thanks,
Piotr
[1] http://www.ovirt.org/Features/Optaplanner
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1142909
10 years, 2 months
[ANN] oVirt 3.5.0 Third Release Candidate is now available for testing
by Sandro Bonazzola
The oVirt team is pleased to announce that the 3.5.0 Third Release Candidate is now
available for testing as of Sep 24th 2014.
The release candidate is available now for Fedora 19, Fedora 20 and Red Hat Enterprise Linux 6.5
(or similar) and allow you to use Red Hat Enterprise Linux 7 as node and run Hosted Engine.
This release of oVirt includes numerous bug fixes.
See the release notes [1] for a list of the new features and bugs fixed.
The existing repository ovirt-3.5-pre has been updated for delivering this
release without the need of enabling any other repository.
If you're already using oVirt 3.5 repository, please update ovirt-release35 rpm.
Please refer to release notes [1] for Installation / Upgrade instructions.
New oVirt Live, oVirt Guest Tools and oVirt Node ISO will be available soon as well[2].
Please note that mirrors may need usually one day before being synchronized.
If you want to be sure to use latest rpms and don't want to wait for the mirrors,
you can edit /etc/yum.repos.d/ovirt-3.5.repo commenting the mirror line and
removing the comment on baseurl line.
Please refer to the release notes for known issues in this release.
[1] http://www.ovirt.org/OVirt_3.5_Release_Notes
[2] http://resources.ovirt.org/pub/ovirt-3.5-pre/iso/
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 2 months
oVirt 3.4 entering security/critical fix only phase
by Sandro Bonazzola
Hi,
As you should know, we released oVirt 3.4.4 yesterday.
After this release, only security/critical fixes will be allowed on 3.4 branch and only a security/critical update will cause a new oVirt 3.4.z release.
It's time to focus on new features for 3.6.0!
Thanks,
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 2 months
