Question regarding support of incremental backups in 4.3.?
by Anton E
Hi everyone,
I'm quite confusing regarding Incremental backups support in 4.3. Could you please clarify it for me.
The REST API contains a /backups link in links section of a VM, also the UI allows to enable incremental backup for a disk.
However, the /backups returns empty result for any VM. It looks like it is a stump for future development, is that correct?
Thanks in advance.
Regards,
Anton.
4 years
Question regarding support of incremental backups in 4.3.2
by Anton E
Hi,
It seems there is an incomplete or missing support for incremental backup in 4.3.2. Need your clarifications in this regard.
The API for a VM (/ovirt-engine/api/vms/<vm-id>) shows the links to <vm-id>/backups service. Also there is an option to enable incremental backup for a disk in the user interface.
This makes me believe the incremental backups are supported, however accessing the <vm-id>/backups service gives an empty output.
Could you please clarify, whether incremental backup feature is supported in 4.3.2 and I'm trying to use it incorrectly or is this service just a stub for now?
Many thanks and regards,
Anton Erdman.
4 years
[NOTICE] Failing randomly on get_host_hooks with a NullPointerException
by Dafna Ron
Hi,
we are randomly failing on get_host_hooks test for at least 3 weeks.
its not a specific branch or project and there are no commonalities that I
can see, aside from not being able to communicate with the host.
this week its started happening at least once a day (this morning, 2 out of
3 failures were due to that test).
This test has been added by Yaniv Kaul over a year ago and he is no longer
working on ovirt I think someone else should take ownership of this test
and fix it.
Please let me know if you are intending to investigate and either fix the
failure or fix the test if not I will add a skip to the test,
Thanks,
Dafna
4 years
the mess with uploading files
by Hetz Ben Hamo
Hi,
Since both export and ISO domain are being deprecated, the only place to
upload remains the data domain.
This method works, however, it doesn't "look" good. Uploading few ISO files
and you won't see any problem. Upload 50-70 files, and the "directory"
looks very messy.
So, my question, will there be any "structure" then can be created, like
"folders" to put those uploaded files?
Thanks
Hetz
4 years
FYI - Many nightly suites, including Network, HE and HC are failing since 2-3 days ago
by Eyal Edri
Not sure if all the same issue, but seems to failing around the same time:
  ovirt-system-tests_hc-basic-suite-4.2 1 day 12 hr - #824 12 hr - #825 57
min  integ-tests
  ovirt-system-tests_hc-basic-suite-master 2 days 12 hr - #1043 12 hr -
#1045 51 min  integ-tests
  ovirt-system-tests_he-basic-ansible-suite-4.3 N/A 11 hr - #11 24 sec 
integ-tests
  ovirt-system-tests_he-basic-ipv6-suite-master N/A 12 hr - #11 10 min 
integ-tests
  ovirt-system-tests_he-basic-iscsi-suite-master 2 days 10 hr - #871 10
hr - #873 1 hr 36 min  integ-tests
  ovirt-system-tests_he-basic-suite-master 2 days 11 hr - #1147 11 hr -
#1149 1 hr 26 min  integ-tests
  ovirt-system-tests_he-node-ng-suite-master 2 days 12 hr - #727 12 hr -
#729 1 hr 54 min  integ-tests
  ovirt-system-tests_network-suite-master 3 days 12 hr - #926 12 hr - #929 45
min  integ-tests
  ovirt-system-tests_openshift-on-ovirt-suite-4.2 3 days 10 hr - #187 10
hr - #190 45 min  integ-tests
Links to jobs can be found here: https://jenkins.ovirt.org/
--
Eyal edri
MANAGER
RHV/CNV DevOps
EMEA VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
4 years
Lago's local sync repo not available in OST
by Sandro Bonazzola
Hi,
just seen:
2019-03-25 10:41:36,062-04 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-hostUpdatesChecker-Thread-2) [] EVENT_ID:
HOST_AVAILABLE_UPDATES_FAILED(839), Failed to check for available updates
on host lago-basic-suite-master-host-1 with message 'Failed to run
check-update of host 'lago-basic-suite-master-host-1'. Error: fatal:
[lago-basic-suite-master-host-1]: FAILED! => {"changed": false, "msg": "
http://192.168.201.1:8585/default/el7/repodata/repomd.xml: [Errno 14]
curl#7 - \"Failed connect to 192.168.201.1:8585; Connection
refused\"\nTrying other mirror.\nhttp://
192.168.201.1:8585/default/el7/repodata/repomd.xml: [Errno 14] curl#7 -
\"Failed connect to 192.168.201.1:8585; Connection refused\"\nTrying other
mirror.\nhttp://192.168.201.1:8585/default/el7/repodata/repomd.xml: [Errno
14] curl#7 - \"Failed connect to 192.168.201.1:8585; Connection
refused\"\nTrying other mirror.\nhttp://
192.168.201.1:8585/default/el7/repodata/repomd.xml: [Errno 14] curl#7 -
\"Failed connect to 192.168.201.1:8585; Connection refused\"\nTrying other
mirror.\nhttp://192.168.201.1:8585/default/el7/repodata/repomd.xml: [Errno
14] curl#7 - \"Failed connect to 192.168.201.1:8585; Connection
refused\"\nTrying other mirror.\nhttp://
192.168.201.1:8585/default/el7/repodata/repomd.xml: [Errno 14] curl#7 -
\"Failed connect to 192.168.201.1:8585; Connection refused\"\nTrying other
mirror.\nhttp://192.168.201.1:8585/default/el7/repodata/repomd.xml: [Errno
14] curl#7 - \"Failed connect to 192.168.201.1:8585; Connection
refused\"\nTrying other mirror.\nhttp://
192.168.201.1:8585/default/el7/repodata/repomd.xml: [Errno 14] curl#7 -
\"Failed connect to 192.168.201.1:8585; Connection refused\"\nTrying other
mirror.\nhttp://192.168.201.1:8585/default/el7/repodata/repomd.xml: [Errno
14] curl#7 - \"Failed connect to 192.168.201.1:8585; Connection
refused\"\nTrying other mirror.\nhttp://
192.168.201.1:8585/default/el7/repodata/repomd.xml: [Errno 14] curl#7 -
\"Failed connect to 192.168.201.1:8585; Connection refused\"\nTrying other
mirror.\n\n\n One of the configured repositories failed (Latest oVirt
nightly),\n and yum doesn't have enough cached data to continue. At this
point the only\n safe thing yum can do is fail. There are a few ways to
work \"fix\" this:\n\n 1. Contact the upstream for the repository and
get them to fix the problem.\n\n 2. Reconfigure the baseurl/etc. for
the repository, to point to a working\n upstream. This is most often
useful if you are using a newer\n distribution release than is
supported by the repository (and the\n packages for the previous
distribution release still work).\n\n 3. Run the command with the
repository temporarily disabled\n yum --disablerepo=alocalsync
...\n\n 4. Disable the repository permanently, so yum won't use it by
default. Yum\n will then just ignore the repository until you
permanently enable it\n again or use --enablerepo for temporary
usage:\n\n yum-config-manager --disable alocalsync\n
or\n subscription-manager repos --disable=alocalsync\n\n 5.
Configure the failing repository to be skipped, if it is unavailable.\n
Note that yum will try to contact the repo. when it runs most
commands,\n so will have to try and fail each time (and thus. yum
will be be much\n slower). If it is a very temporary problem though,
this is often a nice\n compromise:\n\n yum-config-manager
--save --setopt=alocalsync.skip_if_unavailable=true\n\nfailure:
repodata/repomd.xml from alocalsync: [Errno 256] No more mirrors to
try.\nhttp://192.168.201.1:8585/default/el7/repodata/repomd.xml: [Errno 14]
curl#7 - \"Failed connect to 192.168.201.1:8585; Connection
refused\"\nhttp://192.168.201.1:8585/default/el7/repodata/repomd.xml:
[Errno 14] curl#7 - \"Failed connect to 192.168.201.1:8585; Connection
refused\"\nhttp://192.168.201.1:8585/default/el7/repodata/repomd.xml:
[Errno 14] curl#7 - \"Failed connect to 192.168.201.1:8585; Connection
refused\"\nhttp://192.168.201.1:8585/default/el7/repodata/repomd.xml:
[Errno 14] curl#7 - \"Failed connect to 192.168.201.1:8585; Connection
refused\"\nhttp://192.168.201.1:8585/default/el7/repodata/repomd.xml:
[Errno 14] curl#7 - \"Failed connect to 192.168.201.1:8585; Connection
refused\"\nhttp://192.168.201.1:8585/default/el7/repodata/repomd.xml:
[Errno 14] curl#7 - \"Failed connect to 192.168.201.1:8585; Connection
refused\"\nhttp://192.168.201.1:8585/default/el7/repodata/repomd.xml:
[Errno 14] curl#7 - \"Failed connect to 192.168.201.1:8585; Connection
refused\"\nhttp://192.168.201.1:8585/default/el7/repodata/repomd.xml:
[Errno 14] curl#7 - \"Failed connect to 192.168.201.1:8585; Connection
refused\"\nhttp://192.168.201.1:8585/default/el7/repodata/repomd.xml:
[Errno 14] curl#7 - \"Failed connect to 192.168.201.1:8585; Connection
refused\"\nhttp://192.168.201.1:8585/default/el7/repodata/repomd.xml:
[Errno 14] curl#7 - \"Failed connect to 192.168.201.1:8585; Connection
refused\"\nCannot upload enabled repos report, is this client
registered?\n", "rc": 1, "results": []}
while looking at
https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/386...
for https://gerrit.ovirt.org/98862
Can you please have a look?
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://red.ht/sig>
4 years
