Re: [ovirt-users] How to update ovirt on a single-host hosted-engine host

Hi, "Derek Atkins" writes: > Hi, > > All storage is NFS storage exported by the host itself. i didn't mention > it because it shouldn't have mattered -- the HE export mounted but the > others didn't.. Although it appears this may all have been due to the > network issues

Re: [ovirt-users] How to update ovirt on a single-host hosted-engine host

Hi, On Fri, November 25, 2016 1:02 pm, Gianluca Cecchi wrote: > Il 24/Nov/2016 20:34, "Derek Atkins" ha scritto: >> >> Hi, >> >> I've got ovirt running on a single host (with hosted-engine). I just >> upgraded the engine from 4.0.4 to 4.0.5. That was pretty easy; I just >> put

Re: [ovirt-users] How to update ovirt on a single-host hosted-engine host

Il 24/Nov/2016 20:34, "Derek Atkins" ha scritto: > > Hi, > > I've got ovirt running on a single host (with hosted-engine). I just > upgraded the engine from 4.0.4 to 4.0.5. That was pretty easy; I just > put the system into global maintenance mode, then yum update, then >

Re: [ovirt-users] How to update ovirt on a single-host hosted-engine host

HELP!!! I just did this, but now my storage isn't showing up! According to "mount", only the HE domain is mounted, but none of my other domains mounted. Running 'hosted-engine --connect-storage' does not seem to mount the storage domains. If I bring the engine up, it still wont access those

Re: [ovirt-users] How to update ovirt on a single-host hosted-engine host

On Fri, Nov 25, 2016 at 3:53 PM, Derek Atkins wrote: > Hi Simone, > > On Fri, November 25, 2016 4:34 am, Simone Tiraboschi wrote: > > On Thu, Nov 24, 2016 at 8:33 PM, Derek Atkins wrote: > > [snip] > >> So what IS the process to properly update a single-host

Re: [ovirt-users] How to update ovirt on a single-host hosted-engine host

Hi Simone, On Fri, November 25, 2016 4:34 am, Simone Tiraboschi wrote: > On Thu, Nov 24, 2016 at 8:33 PM, Derek Atkins wrote: [snip] >> So what IS the process to properly update a single-host host? My guess >> is: >> >> * shutdown all the VMs >> > * go into global maint mode