[Call for Testing] oVirt 4.3.0
by Sandro Bonazzola
Hi,
we are planning to release a 4.3.0 RC2 tomorrow morning, January 16th 2019.
We have a scheduled final release for oVirt 4.3.0 on January 29th: this is
the time when testing is most effective to ensure the release will be as
much stable as possible. Please join us testing the RC2 release this week
and reporting issues to
https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
Please remember this is still pre-release material, we recommend not
installing it on production environments yet.
Thanks,
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://red.ht/sig>
5 years, 9 months
Error while executing action Attach Storage Domain: AcquireHostIdFailure
by Fedor Gavrilov
Hi,
I'm setting up iSCSI domain on freshly installed ovirt and hitting subj when I try adding new data domain. After it's added it's in Unattached state and can't be removed either.
I found something in bugzilla about NFS storage and sanlock, could it be related? I allocated iSCSI fileio storage on the same machine where host is (so I'm connecting 127.0.0.1:3260), was that my mistake?
Thanks in advance,
Fedor Gavrilov
5 years, 9 months
SSO with lightdm
by jeremiah52＠naver.com
I knows there are the GDM plugin and KDM plugin of ovirt-guest-agent that makes SSO in linux is possible.
I want to make SSO with lightdm is possble. To add lightdm plugin to ovirt-guest-agent is enough? or something more is needed?
I don't know how to develop SSO with lightdm.
5 years, 9 months
Hard disk requirement
by Hetz Ben Hamo
Hi,
The old oVirt (3.x?) ISO image wasn't requiring a big hard disk in order to
install the node part on a physical machine, since the HE and other parts
were running using NFS/iSCSI etc.
oVirt 4.X if I understand correctly - does require hard disk on the node.
Can this requirement be avoided and just use an SD Card? Whats the minimum
storage for the local node?
Thanks,
Hetz
5 years, 9 months
[Ovirt] [CQ weekly status] [11-01-2019]
by Dafna Ron
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.2*: GREEN (#3)
we have not had any failures since before the holidays.
*CQ-Master:* YELLOW (#2)
- We had two different code regressions for ovirt-engine and vdsm
both were reported and solved during the week.
- we had missing packages which were fixed with this patch:
https://gerrit.ovirt.org/#/c/96831/
Last successful build for vdsm and ovirt-engine was today (11th Jan).
Current status for 4.2 [1] and master [2] can be found here:
[1]
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-...
[2]
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chan...
Happy week!
Dafna
-------------------------------------------------------------------------------------------------------------------
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)
5 years, 9 months
