Hey Christian, a more recent ISO should fix the issue you were seeing back then.
- fabian On Thu, Aug 4, 2016 at 11:37 AM, Grundmann, Christian <[email protected]> wrote: > Hi, > > I installed ovirt-node-ng-installer-ovirt-4.0-2016080104.iso > > with default partitioning Layout > > with the result after Installation: > > > > Status: FAILED > > Mount points ... FAILED - This can happen if the installation was performed > incorrectly > > Separate /var ... FAILED - /var got unmounted, or was not setup to use a > separate volume > > Discard is used ... FAILED - 'discard' mount option was not added or got > removed > > Basic storage ... OK > > Initialized VG ... OK > > Initialized Thin Pool ... OK > > Initialized LVs ... OK > > Thin storage ... OK > > Checking available space in thinpool ... OK > > Checking thinpool auto-extend ... OK > > > > No LV for /var created at all. > > > > What’s the right way installing an working node? > > > > Thx a lot > > Christian > > > > > > Von: [email protected] [mailto:[email protected]] Im Auftrag von > Fabian Deutsch > Gesendet: Mittwoch, 27. Juli 2016 13:25 > An: Peter Michael Calum <[email protected]> > Cc: [email protected] > Betreff: Re: [ovirt-users] Problems installing Ovirt 4.02 Node > > > > > > > > On Wed, Jul 27, 2016 at 7:59 AM, Peter Michael Calum <[email protected]> wrote: > > Hi, > > I tried the changes in /etc/fstab and rebooted. > Now imgbase status: OK > > But I see this in /var/log/messages after the change : Starting kdump: > [FAILED] > > Jul 27 07:44:08 khk9dsk34 dracut: *** Including module: base *** > Jul 27 07:44:08 khk9dsk34 dracut: *** Including module: fs-lib *** > Jul 27 07:44:08 khk9dsk34 dracut: *** Including module: kdumpbase *** > Jul 27 07:44:08 khk9dsk34 kernel: device-mapper: table: 253:8: multipath: > error getting device > Jul 27 07:44:08 khk9dsk34 kernel: device-mapper: ioctl: error adding target > to table > Jul 27 07:44:08 khk9dsk34 multipathd: dm-8: remove map (uevent) > Jul 27 07:44:08 khk9dsk34 multipathd: dm-8: remove map (uevent) > > Jul 27 07:44:08 khk9dsk34 kdumpctl: Bad kdump location: khk9dsg34.ip.tdk.dk > Jul 27 07:44:09 khk9dsk34 kdumpctl: mkdumprd: failed to make kdump initrd > Jul 27 07:44:09 khk9dsk34 kdumpctl: Starting kdump: [FAILED] > Jul 27 07:44:09 khk9dsk34 systemd: kdump.service: main process exited, > code=exited, status=1/FAILURE > Jul 27 07:44:09 khk9dsk34 systemd: Failed to start Crash recovery kernel > arming. > > Jul 27 07:44:09 khk9dsk34 systemd: Startup finished in 5.673s (kernel) + > 8.024s (initrd) + 43.476s (userspace) = 57.173s. > Jul 27 07:44:09 khk9dsk34 systemd: Unit kdump.service entered failed state. > Jul 27 07:44:09 khk9dsk34 systemd: kdump.service failed. > Jul 27 07:44:32 khk9dsk34 systemd: Starting Stop Read-Ahead Data > Collection... > Jul 27 07:44:32 khk9dsk34 systemd: Started Stop Read-Ahead Data Collection. > Jul 27 07:44:32 khk9dsk34 systemd-logind: New session 1 of user root. > Jul 27 07:44:32 khk9dsk34 systemd: Created slice user-0.slice. > Jul 27 07:44:32 khk9dsk34 systemd: Starting user-0.slice. > Jul 27 07:44:32 khk9dsk34 systemd: Started Session 1 of user root. > Jul 27 07:44:32 khk9dsk34 systemd: Starting Session 1 of user root. > Jul 27 07:44:45 khk9dsk34 kernel: device-mapper: table: 253:8: multipath: > error getting device > Jul 27 07:44:45 khk9dsk34 kernel: device-mapper: ioctl: error adding target > to table > Jul 27 07:44:45 khk9dsk34 multipathd: dm-8: remove map (uevent) > Jul 27 07:44:45 khk9dsk34 multipathd: dm-8: remove map (uevent) > > I checked messages in my other hypervisor where /etc/fstab was not modified, > KDUMP was OK there. > > The question about registrating the host in the manager i got solved, it is > now done from the manager. > (I come from the Redhat 3.5, and are just started on Ovirt 4) > > > > Nice that the status issue could be solved. > > For adding Node, you can either add the host by gpoing to Engine and then > add the host, or you can use vdsm register on the host to register it to > Engine. > > - fabian > > > > Thanks for helping > Peter > > -----Oprindelig meddelelse----- > Fra: Giorgio Biacchi [mailto:[email protected]] > Sendt: 27. juli 2016 00:05 > Til: Peter Michael Calum <[email protected]>; [email protected] > Emne: Re: [ovirt-users] Problems installing Ovirt 4.02 Node > > > On 26/07/2016 08:51, Peter Michael Calum wrote: > >> imgbase status: DEGRADED >> >> Please check the status manually using `imgbase check` > > Got the same problem, add discard option to fstab for / and /var like this: > > # > # /etc/fstab > # Created by anaconda on Fri Jul 22 11:08:40 2016 # # Accessible > filesystems, by reference, are maintained under '/dev/disk' > # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info > # > /dev/HostVG/ovirt-node-ng-4.0.2-0.20160721.0+1 / ext4 defaults,discard 1 1 > UUID=a96d5a4c-bc4b-481c-bf6e-af47318d8b7b /boot ext4 > defaults 1 2 > /dev/mapper/HostVG-var /var ext4 defaults,discard 1 2 > /dev/mapper/HostVG-swap swap swap defaults 0 0 > > then remount or reboot. > >> >> Another question : Where do I define the Ovirt manager address. > > For this one I can't help, but you can add the new host from the manager.. > >> >> >> >> Venlig hilsen / Kind regards >> >> *Peter Calum * >> >> Tlf: +45 66 69 36 82 >> Mobil: +45 40 41 71 85 >> E-mail [email protected] <mailto:[email protected]> >> >> >> TDC Group >> Teknologi & Kapacitet >> Systemer, OTMS >> Teglholmsgade 1, >> F-059 2450 København SV >> >> >> >> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.ovirt.org/mailman/listinfo/users >> > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users -- Fabian Deutsch <[email protected]> RHEV Hypervisor Red Hat _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
