On Wed, Jun 13, 2018 at 1:18 PM Leo David wrote:
> Finnally !!!
> Femi, thank you so much !!! I wouldn't have been able do solve this
> without your help.
> So, just as info:
> In this version ( iso ovirt-node-ng-installer-ovirt-4.2-2018053012 ) ,
> multipah.conf seems to be alrady configured
No problem Leo.
Glad it worked out ok!!
___
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:
Yes, it's working as per expectations. Thank you very much Femi, really
very helpfull !
On Wed, Jun 13, 2018, 16:16 femi adegoke wrote:
> Since this is a single node gluster install, you have to add the gluster
> volume.
>
> Log into the HE web gui
> go to Storage, Storage Domains, click on
Since this is a single node gluster install, you have to add the gluster volume.
Log into the HE web gui
go to Storage, Storage Domains, click on "New Domain" (it's located at the top
right side)
Storage Type: select GlusterFS
Export Path: enter in this format
Finnally !!!
Femi, thank you so much !!! I wouldn't have been able do solve this
without your help.
So, just as info:
In this version ( iso ovirt-node-ng-installer-ovirt-4.2-2018053012 ) ,
multipah.conf seems to be alrady configured to blacklist all devices.
It already has configured :
# VDSM
Gluster volumes are started, so I assume that the gluster part is fine.
Would'nt make more sense to add everything to black list, reboot the server
and continue with ovirt-engine vm setup ( and adding 10.10.8.111:/engine
for vm storage ) ?
ie:
blacklist {
devnode "*"
}
Thank you !
It's blacklist { not kblacklist (remove the "k")
run this command to find wwids: ls -la /dev/disk/by-id/
Is the existing gluster setup installed correctly?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Thank you,
The playbook just finnished successfully.
Now:
1. Should I create the blacklist acordingly:
kblacklist {
wwid INTEL_SSDSCKHB120G4_BTWM65160025120B
wwid eui.0025385171b04d62
wwid SAMSUNG_MZ7GE960HMHP-000AZ_S1P8NYAG123827
}
- but not sure what to put as wwid
2. How to deploy self-hosted
That was just me being stupid I was passing wrong values to the key for
volumes.
I am running again the playbook.
On Wed, Jun 13, 2018 at 10:22 AM, femi adegoke
wrote:
> Can you run command lsblk
> What's your output?
>
> What is the "-h" for?
> [script1]
> action=execute
>
Leo, you should still add the blacklist
___
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:
Can you run command lsblk
What's your output?
What is the "-h" for?
[script1]
action=execute
ignore_script_errors=no
file=/usr/share/gdeploy/scripts/grafton-sanity-check.sh -d sdb -h
Please look at this file & make sure yours is similar
https://pastebin.com/LTRQ78aJ
Fortunatelly, after node reinstallation nu more mpath devices are present:
multipath -ll
Jun 13 06:32:10 | DM multipath kernel driver not loaded
Jun 13 06:32:10 | DM multipath kernel driver not loaded
But now I am encountering this "invalid number format \"virt\" in option
\"brick-uid":
TASK
A blacklist is a list of the disks that the system should NOT mark as multipath
disks.
You need to create a file, you can name it local.conf, create it in this
location: /etc/multipath/conf.d/
Use the most current iso.
I think there might be a bug.
Thank you very much Semi. The reinstallation would not be an problem, being
the fact that i've spent so much in sorting this issue.
I don't understant the "setup a blacklist part" . What does this mean, how
should I do it ?
I have looked over the other oVirt nodes that I have in the network, and
0)
install ovirt node v4.2.3.1 (or higher)
1)
Create a blacklist here: /etc/multiapth/conf.d/local.conf (assuming local.conf
is the new file you create)
2)
local.conf should be similar to this (using your disks wwid)
blacklist {
wwid INTEL_SSDSCKHB120G4_BTWM65160025120B
wwid
It looks like the same error I had where oVirt keeps "trying" to use the
multipath disk as part of the install.
The solution (unfortunately) is to re-install the o/s, then setup a blacklist &
then proceed with the rest of the ovirt install.
There is no way to release that disk from multipath
16 matches
Mail list logo
