VDO + HCI = failed reboots
I just spun up the latest and greatest ovirt has to offer, and I am building out an HCI cluster. The deployment went wonderfully. I had dns setup for everything, and it just worked. Great job team! I just wanted to add in something i noticed after rebooting the nodes. The gluster service, and volumes would not come back up after rebooting. I found that there needs to be an entry in the fstab for the gluster logical volumes to tell them to start the vdo service. So without this, the node will fail to boot if you are using vdo. inode64,noatime,nodiratime,discard,x-systemd.requires=vdo.service the defaults are this inode64,noatime,nodiratime Hopefully it helps someone else :) Cheers
On Mon, Aug 27, 2018 at 5:49 PM, Donny Davis <donny@fortnebula.com> wrote:
I just spun up the latest and greatest ovirt has to offer, and I am building out an HCI cluster. The deployment went wonderfully. I had dns setup for everything, and it just worked. Great job team!
I just wanted to add in something i noticed after rebooting the nodes. The gluster service, and volumes would not come back up after rebooting. I found that there needs to be an entry in the fstab for the gluster logical volumes to tell them to start the vdo service. So without this, the node will fail to boot if you are using vdo.
inode64,noatime,nodiratime,discard,x-systemd.requires=vdo.service
the defaults are this inode64,noatime,nodiratime
This was fixed in gdeploy - https://bugzilla.redhat.com/show_bug.cgi?id=1548399 Can you tell us the version of gdeploy you used? # rpm -qa | grep gdeploy
Hopefully it helps someone else
:) Cheers
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/K7MXXDAVPR23IR7ASXT5P73AA3W3AWVW/
gdeploy-2.0.8-1.el7.noarch On Tue, Aug 28, 2018 at 7:42 AM, Sahina Bose <sabose@redhat.com> wrote:
On Mon, Aug 27, 2018 at 5:49 PM, Donny Davis <donny@fortnebula.com> wrote:
I just spun up the latest and greatest ovirt has to offer, and I am building out an HCI cluster. The deployment went wonderfully. I had dns setup for everything, and it just worked. Great job team!
I just wanted to add in something i noticed after rebooting the nodes. The gluster service, and volumes would not come back up after rebooting. I found that there needs to be an entry in the fstab for the gluster logical volumes to tell them to start the vdo service. So without this, the node will fail to boot if you are using vdo.
inode64,noatime,nodiratime,discard,x-systemd.requires=vdo.service
the defaults are this inode64,noatime,nodiratime
This was fixed in gdeploy - https://bugzilla.redhat.com/ show_bug.cgi?id=1548399
Can you tell us the version of gdeploy you used?
# rpm -qa | grep gdeploy
Hopefully it helps someone else
:) Cheers
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/communit y/about/community-guidelines/ List Archives: https://lists.ovirt.org/archiv es/list/users@ovirt.org/message/K7MXXDAVPR23IR7ASXT5P73AA3W3AWVW/
I downloaded the latest build from jenkins On Tue, Aug 28, 2018 at 7:59 AM, Donny Davis <donny@fortnebula.com> wrote:
gdeploy-2.0.8-1.el7.noarch
On Tue, Aug 28, 2018 at 7:42 AM, Sahina Bose <sabose@redhat.com> wrote:
On Mon, Aug 27, 2018 at 5:49 PM, Donny Davis <donny@fortnebula.com> wrote:
I just spun up the latest and greatest ovirt has to offer, and I am building out an HCI cluster. The deployment went wonderfully. I had dns setup for everything, and it just worked. Great job team!
I just wanted to add in something i noticed after rebooting the nodes. The gluster service, and volumes would not come back up after rebooting. I found that there needs to be an entry in the fstab for the gluster logical volumes to tell them to start the vdo service. So without this, the node will fail to boot if you are using vdo.
inode64,noatime,nodiratime,discard,x-systemd.requires=vdo.service
the defaults are this inode64,noatime,nodiratime
This was fixed in gdeploy - https://bugzilla.redhat.com/sh ow_bug.cgi?id=1548399
Can you tell us the version of gdeploy you used?
# rpm -qa | grep gdeploy
Hopefully it helps someone else
:) Cheers
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/communit y/about/community-guidelines/ List Archives: https://lists.ovirt.org/archiv es/list/users@ovirt.org/message/K7MXXDAVPR23IR7ASXT5P73AA3W3AWVW/
nodectl info layers: ovirt-node-ng-4.2.5.1-0.20180825.0: ovirt-node-ng-4.2.5.1-0.20180825.0+1 bootloader: default: ovirt-node-ng-4.2.5.1-0.20180825.0+1 entries: ovirt-node-ng-4.2.5.1-0.20180825.0+1: index: 0 title: ovirt-node-ng-4.2.5.1-0.20180825.0+1 kernel: /boot/ovirt-node-ng-4.2.5.1-0.20180825.0+1/vmlinuz-3.10.0-862.11.6.el7.x86_64 args: "ro crashkernel=auto rd.lvm.lv=onn/swap rhgb quiet ixgbe.allow_unsupported_sfp=1 rd.lvm.lv=onn/ovirt-node-ng-4.2.5.1-0.20180825.0+1 img.bootid=ovirt-node-ng-4.2.5.1-0.20180825.0+1" initrd: /boot/ovirt-node-ng-4.2.5.1-0.20180825.0+1/initramfs-3.10.0-862.11.6.el7.x86_64.img root: /dev/onn/ovirt-node-ng-4.2.5.1-0.20180825.0+1 current_layer: ovirt-node-ng-4.2.5.1-0.20180825.0+1 On Tue, Aug 28, 2018 at 8:00 AM, Donny Davis <donny@fortnebula.com> wrote:
I downloaded the latest build from jenkins
On Tue, Aug 28, 2018 at 7:59 AM, Donny Davis <donny@fortnebula.com> wrote:
gdeploy-2.0.8-1.el7.noarch
On Tue, Aug 28, 2018 at 7:42 AM, Sahina Bose <sabose@redhat.com> wrote:
On Mon, Aug 27, 2018 at 5:49 PM, Donny Davis <donny@fortnebula.com> wrote:
I just spun up the latest and greatest ovirt has to offer, and I am building out an HCI cluster. The deployment went wonderfully. I had dns setup for everything, and it just worked. Great job team!
I just wanted to add in something i noticed after rebooting the nodes. The gluster service, and volumes would not come back up after rebooting. I found that there needs to be an entry in the fstab for the gluster logical volumes to tell them to start the vdo service. So without this, the node will fail to boot if you are using vdo.
inode64,noatime,nodiratime,discard,x-systemd.requires=vdo.service
the defaults are this inode64,noatime,nodiratime
This was fixed in gdeploy - https://bugzilla.redhat.com/sh ow_bug.cgi?id=1548399
Can you tell us the version of gdeploy you used?
# rpm -qa | grep gdeploy
Hopefully it helps someone else
:) Cheers
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/communit y/about/community-guidelines/ List Archives: https://lists.ovirt.org/archiv es/list/users@ovirt.org/message/K7MXXDAVPR23IR7ASXT5P73AA3W3AWVW/
participants (2)
-
Donny Davis -
Sahina Bose