gine hosts, in that all four hosts are capable
of running the engine.. so we'd need to bring both clusters (i.e.: all
hosts) down.
Having said that, it seems like a safer plan... as long as business
requirements can accommodate.
Thanks again.
-C
Cam Wright - Systems and Technical Resour
Upgrading_Resources/
- it seems the 'hosted-engine --upgrade-appliance' path is the best
way to do this... but because our hosts are running Fedora instead of
EL, I think that makes this option moot to us.
Is what I've suggested a valid upgrade path, or is there a more sane
way of going a
root@bne-ovirtengine01 ~]# cat /etc/redhat-release
Fedora release 22 (Twenty Two)
[root@bne-ovirtengine01 ~]# uname -r
4.0.4-301.fc22.x86_64
oVirt Engine Version: 3.6.0-1.fc22
Any assistance would be appreciated.
Cam Wright | Systems Administrator
CUTTINGEDGE
90 Victoria St, West End, Brisbane,
his server the
> 'hostname' and 'hostname -f' commands return the same fqdn as well.
>
> There must be some other means by which ovirt-3.5 is trying to reverse
> resolve the IP. Still pondering what it is.
>
> -Kripa
>
> On Jan 31, 2015, at 3:25 AM, Cam Wright
f you have received this
> message in error, notify sender immediately and delete this message
> immediately.”
>
--
Cam Wright | IT Support Officer / SysAdmin / Trawler of Logs
*CUTTING**EDGE*
90 Victoria St, West End, Brisbane, QLD, 4101
T +61 7 3013
Hi Kripa,
When you set up the oVirt engine it looks like it tries to resolve the fqdn
of the machine (which in this case looks like you either haven't updated
/etc/sysconfig/network to match the fqdn you provided in the setup or you
have and haven't rebooted / reset your network stack).
I found t
6 matches
Mail list logo
