Re: ovirt upgrade 4.3 - dashboard is dispalyed 2x in top left corner menu
by Greg Sheremeta
On Thu, Feb 7, 2019 at 7:39 AM Martin Humaj <mhumaj(a)gmail.com> wrote:
> Hi Greg,
>
> Thanks a lot for quick reply.
>
> yum update ovirt-engine-ui-extensions, fixed the issue
>
> The duplicate is gone.
>
Good to hear, thanks. For posterity, can you tell me if you did the update
today or a couple days ago? And, are you using hosted engine? I want to
make sure it's not still broken for everyone else :)
>
> martin
>
> On Thu, Feb 7, 2019 at 1:32 PM Greg Sheremeta <gshereme(a)redhat.com> wrote:
>
>> It should be fixed now. When did you update?
>>
>> Are you using hosted engine?
>>
>> On Thu, Feb 7, 2019, 6:36 AM <mhumaj(a)gmail.com> wrote:
>>
>>> After the upgrade to ovirt 4.3, I can see two entry for dashboard in top
>>> left corner menu. Is there any way how to get rid of the duplicity?
>>>
>>> thanks
>>> _______________________________________________
>>> Users mailing list -- users(a)ovirt.org
>>> To unsubscribe send an email to users-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/users@ovirt.org/message/GN4ER4YD6KT...
>>>
>>
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
<https://www.redhat.com/>
gshereme(a)redhat.com IRC: gshereme
<https://red.ht/sig>
5 years, 9 months
qxl issue on OVirt 4.3.0
by Robert Crawford
On 4.3.0 with the 1809 CentOS image from the ISO Domain the VM Guest will fail to boot and freeze on initialized qxl 0.1.0
5 years, 9 months
Cluster upgrade
by Misak Khachatryan
Hi,
I've successfully upgraded to 4.3, but when I'm trying to upgrade Cluster
version I'm getting this:
"Error while executing action: Cannot change Cluster Compatibility Version
to higher version when there are active Hosts with lower version.
-Please move Host virt2 with lower version to maintenance first."
Any clues?
Best regards,
Misak Khachatryan
5 years, 9 months
upgrade bug
by ada per
After upgrading my hosts from 4.2.7.1 to 4.2.8 the external networks
stopped working!
When im starting a VM using external network it does not boot up at all!!!!!
The error message is:
"VM is down with error. Exit message: unsupported configuration: filterref
is not supported for network interfaces with virtualport type openvswitch"
I rolled it back to 4.2.7.1 for 1 of my hosts just as a test and the VMs on
that host can now bootup using external networks as they are supposed to!!
Please advice as i would like to use the upgrade!!!
5 years, 9 months
"Volume Option cluster.granular-entry-heal=enable could not be set" when using "Optimize for Virt store"
by Jorick Astrego
Hi again,
When using the option "Optimize for Virt store", I get the following error:
2019-02-06 10:25:02,353+01 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engine-Thread-15727)
[051cfc8c-9efc-427c-9e2e-9127e3e0a86d] EVENT_ID:
GLUSTER_VOLUME_OPTION_SET_FAILED(4,003), Volume Option
cluster.granular-entry-heal=enable could not be set on ssd9 of
cluster GlusterFS-storage.
This looks like the same issue as
https://bugzilla.redhat.com/show_bug.cgi?id=1635684
Volume set option 'granular-entry-heal' is not longer set via
gluster volume set option.
Is this a known issue or should I open a bug for this?
Met vriendelijke groet, With kind regards,
Jorick Astrego
Netbulae Virtualization Experts
----------------
Tel: 053 20 30 270 info(a)netbulae.eu Staalsteden 4-3A KvK 08198180
Fax: 053 20 30 271 www.netbulae.eu 7547 TA Enschede BTW NL821234584B01
----------------
5 years, 9 months
ovirt-node 4.3 hyperconverged - fails on VM deployment - all nodes broken
by feral
Boring 3 vanilla node deployment. Default options except for gluster volume
size. All three nodes on static IP on LAN. All three have each other listed
in /etc/hosts as well as dns.
Gluster wizard complete successfully, deploy VM. VM deployment fails after
copying to the gluster storage. At that point, rebooting any node results
in node not coming back to life. No networking, so no other services.
Only error I can get is to check the engine.log, which I cannot do as the
engine fails to come up.
Anyone else seeing this with a vanilla install/deployment?
--
_____
Fact:
1. Ninjas are mammals.
2. Ninjas fight ALL the time.
3. The purpose of the ninja is to flip out and kill people.
5 years, 9 months
ovirt-node 4.2 iso - hyperconverged wizard doesn't write gdeployConfig settings
by feral
New install of ovirt-node 4.2 (from iso). Setup each node with networking
and ssh keys, and use the hyperconverged gluster deployment wizard. None of
the user specified settings are ever reflected in the gdeployConfig.conf.
Anyone running into this?
--
_____
Fact:
1. Ninjas are mammals.
2. Ninjas fight ALL the time.
3. The purpose of the ninja is to flip out and kill people.
5 years, 9 months
