adding users list, infra is for infrastructure and CI.
On Mon, Feb 18, 2019, 05:40 Mohd Hanief Harun Hi all,
>
> Im new in rhv and oVirt, hope there some space for the noob question :)
>
> Let say I have 2 hypervisors and 1 storage server. Where is the best
> practice to install self-hosted
Hi all,
Im new in rhv and oVirt, hope there some space for the noob question :)
Let say I have 2 hypervisors and 1 storage server. Where is the best practice
to install self-hosted engine? In hypervisors or storage? I have experienced
installing self-hosted engine in 2 storages. If something
A system test invoked by the "ovirt-master" change queue including change
66932,31 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 97775,2 (vdsm) that this change depends on or is based on,
was detected as the cause of the testing failures.
This change
Change 7d67266 (ovirt-web-ui) is probably the reason behind recent system test
failures in the "ovirt-master" change queue and needs to be fixed.
This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.
For further details
Good morning!
Attached is the HTML page with the jenkins status report. You can see it also
here:
-
http://jenkins.ovirt.org/job/system_jenkins-report/739//artifact/exported-artifacts/upstream_report.html
Cheers,
Jenkins
A system test invoked by the "ovirt-master" change queue including change
96835,27 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 97775,2 (vdsm) that this change depends on or is based on,
was detected as the cause of the testing failures.
This change
A system test invoked by the "ovirt-master" change queue including change
96829,28 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 97775,2 (vdsm) that this change depends on or is based on,
was detected as the cause of the testing failures.
This change
A system test invoked by the "ovirt-master" change queue including change
96554,34 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 97719,3 (ovirt-engine) that this change depends
on or is based on, was detected as the cause of the testing
I don't think anything changed in the ost conf file in the last few days :)
but missing selinux-policy can cause the same issue... trying to add that
first
On Sun, Feb 17, 2019 at 5:57 PM Greg Sheremeta wrote:
> Any way you can check the label on the conf file within OST (edit the
> script I
Any way you can check the label on the conf file within OST (edit the
script I guess)? It probably needs 'postgresql_db_t'
mine (not using SCL)
ls -laZ /var/lib/pgsql/data/postgresql.conf
-rw---. 1 postgres postgres unconfined_u:object_r:postgresql_db_t:s0
22572 May 22 2018
yes, I actually see that vdsm is failing as well on same issue.
and selinux-policy is not appearing in master repo anymore.
On Sun, Feb 17, 2019 at 5:41 PM Greg Sheremeta wrote:
>
>
> On Sun, Feb 17, 2019 at 12:37 PM Dafna Ron wrote:
>
>> Hi,
>>
>> we are failing upgrade from release suite
On Sun, Feb 17, 2019 at 12:37 PM Dafna Ron wrote:
> Hi,
>
> we are failing upgrade from release suite on ovirt-engine master.
>
> CQ points below patch as root cause:
> https://gerrit.ovirt.org/#/c/97719/ - webadmin: don't allow trimming
> whitespace for the kernel cmdline
>
Not related. This
A system test invoked by the "ovirt-master" change queue including change
96550,33 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 97719,3 (ovirt-engine) that this change depends
on or is based on, was detected as the cause of the testing
A system test invoked by the "ovirt-master" change queue including change
96549,33 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 97719,3 (ovirt-engine) that this change depends
on or is based on, was detected as the cause of the testing
Failed to run project_setup.sh for:
#3616 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on
Failed to run project_setup.sh for:
#3611 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on
16 matches
Mail list logo
