Hello all,
I also can't update, I'm trying from ovirt-node-ng-4.2.4 to
ovirt-node-ng-4.2.5.1
Thanks,
Paul S.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: htt
4.2.5 seems to have NFS issues for some users. What is your storage server?
On Thu, Aug 16, 2018, 4:49 PM Matt Simonsen 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
On 08/17/2018 09:00 AM, Vincent Royer wrote:
4.2.5 seems to have NFS issues for some users. What is your storage
server?
We have shared storage via NFS via a dedicated Cent7 server.
I'm not so much having issues using 4.2.5, the issue I'm having is that
4.2.3 isn't upgrading to 4.2.4 or 4.
On Thu, 2018-08-16 at 16:26 -0700, Matt Simonsen 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.
>
Adding Yuval.
> Since these
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 wrote:
> Hello all,
>
> I've emailed about similar trouble with an oVirt Node upgrade using the
> ISO install. I've attached the /tmp/i
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 fo
Hello,
I replied to a different email in this thread, noting I believe I may
have a workaround to this issue.
I did run this on a server that has not yet been upgraded, which
previously has failed at being updated, and the command returned "0"
with no output.
[ ~]# semanage permissive -a s
Hi again Matt,
I was wondering what `semanage permissive -a setfiles_t` looks like on the
host that failed to upgrade because I don't see the exact error in the log.
Thanks,
Yuval.
On Tue, Aug 21, 2018 at 12:04 AM, Matt Simonsen wrote:
> Hello,
>
> I replied to a different email in this thre
I ran this on a host that has the same exact failing upgrade. It
returned with no output.
I'm expecting if I manually remove the /boot kernel, the grub lines from
any other installs, and the other LV layers that the upgrade will work
but with myself and others experiencing this I'm happy to as
Hi Matt,
I just went over the log you sent, couldn't find anything else other than
the semanage failure which you say seems to be ok. Do you have any other
logs (perhaps from other machines) that we can look at it ?
Thanks,
Yuval.
On Tue, Aug 21, 2018 at 10:11 PM, Matt Simonsen wrote:
> I ran
I'm not sure I have logs from any instances that failed.
However having upgraded about 10 nodes, the trick for success seems to be:
- Manually cleaning grub.conf with any past node kernels (ie: when on
4.2.3, I remove 4.2.2)
- Manually removing any past kernel directories from /boot
- Removi
Well that would clean the old stuff, indeed, but you shouldn't have to do
all this stuff by yourself, too bad you can't find the logs. Btw, removing
the lvs and grub entries can be done using `imgbase base --remove
.0`
On Thu, Aug 30, 2018 at 7:33 PM, Matt Simonsen wrote:
> I'm not sure I have
Hello All,
I couldn't update to 4.2.5.1, there was an error in imgbased.log
AssertionError: Path is already a volume: /home
I found this worked
yum erase ovirt-node-ng-image-update-placeholder.noarch
yum erase ovirt-node-ng-image-update.noarch
yum install
https://resources.ovir
13 matches
Mail list logo
