Hello all,
I believe I have fixed this for several hosts - or at the very least I
have successfully upgraded from 4.2.3 to 4.2.5 successfully on servers
that previously failed.
This is documented from memory, but I believe I didn't do anything else.
What I did is, first removed the old LV for the new install and/or any
old installs also (we had one on 4.2.2) like this:
lvremove /dev/onn/ovirt-node-ng-4.2.x
lvremove /dev/onn/ovirt-node-ng-4.2.x+1
lvremove /dev/onn/var_crash
The nodes were running with 4.2.3, and were were previously on 4.2.2.
The LVs remained. I had previously removed only the 4.2.2 LVs & yum
updated, and I do not believe this caused an upgrade to complete
properly (ie: grub wasn't updated at the very least).
In my searching, I noticed a suggestion somewhere about removing grub
entries and the old info in /bootovirt-node-ng-4.2.x*
Removing the directory from the previous install in /boot & manually
removing the old boot-loader info in /boot/grub2/grub.cfg, along with
any other LVs that may have remained from previous installs seems to
"work" -- the yum update following doing this succeed & grub is updated.
Following this I upgraded from 4.2.3 to 4.2.5 on several hosts, and the
process went perfectly on 3 in a row that previously failed.
I believe I can now successfully upgrade our remaining hosts from 4.2.3
to 4.2.5, I'm happy to provide more info it it will help identify
exactly what caused this.
Thanks,
Matt
PS- I will also be in #ovirt for about 3 hours if anyone would like to
work there with me
On 08/20/2018 08:19 AM, Yuval Turgeman wrote:
Hi Matt,
Can you attach the output from the following line
# semanage permissive -a setfiles_t
Thanks,
Yuval.
On Fri, Aug 17, 2018 at 2:26 AM, Matt Simonsen <m...@khoza.com
<mailto:m...@khoza.com>> wrote:
Hello all,
I've emailed about similar trouble with an oVirt Node upgrade
using the ISO install. I've attached the /tmp/imgbased.log file in
hopes it will help give a clue as to why the trouble.
Since these use NFS storage I can rebuild, but would like to know,
ideally, what caused the upgrade to break.
Truthfully following the install, I don't think I have done *that*
much to these systems, so I'm not sure what would have caused the
problem.
I have done several successful upgrades in the past and most of my
standalone systems have been working great.
I've been really happy with oVirt, so kudos to the team.
Thanks for any help,
Matt
_______________________________________________
Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
To unsubscribe send an email to users-le...@ovirt.org
<mailto:users-le...@ovirt.org>
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
<https://www.ovirt.org/site/privacy-policy/>
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
<https://www.ovirt.org/community/about/community-guidelines/>
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/G6P7CHKTBD7ESE33MIXEDKV44QXITDJP/
<https://lists.ovirt.org/archives/list/users@ovirt.org/message/G6P7CHKTBD7ESE33MIXEDKV44QXITDJP/>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/C2S4LHNR2CSWBD64PLLCR6CD4XQ42WVQ/
