Re: [ovirt-users] Single server hosted engine... almost there

2016-12-10 Thread Yedidyah Bar David 
On Thu, Dec 8, 2016 at 5:24 PM, Mark Steckel  wrote:
> [Apologize. Accidentally hit send instead of save. Continuing below...]
>
>> - Yedidyah Bar David  wrote:
>> > On Thu, Dec 8, 2016 at 12:42 AM, Mark Steckel  wrote:
>> > > Hi,
>> > >
>> > > OK, I reset things and tried again but was more more careful regarding 
>> > > the DNS setup which I believe was correct this. In other words, the 
>> > > FQDNs were resolved from both the host and the HE VM.
>> > >
>> > > After the latest failure I execute 'ip address' to see the state of the 
>> > > interfaces. And lo and behold the /29 IP I had on eth0:1 no longer 
>> > > exists.
>> > >
>> > > So some context.
>> > >
>> > > The server's primary IP is a /24 with the gw being the x.y.z.1.
>> > >
>> > > I have have a /29 subnet to use for the VMs.
>> > >
>> > > I have been presuming that I place the a.b.c.1/29 on eth0:1 for the 
>> > > subnet's gw and OVirt will ether keep it in place or migrate it to the 
>> > > ovirtmgmt device. Instead it is deleted during "hosted-engine 
>> > > --deploy".(Note, when the .1/29 is assigned to eth0:1, the IP address is 
>> > > reachable from the the Internet.)
>> > >
>> > > Dnsmasq is configured to a) serve a.b.c.2/29 a.b.c.6/29 via DHCP and b) 
>> > > to resolve unique FQDNs for each IP. The he VM set to receive the 
>> > > a.b.c.2/29 address.
>> > >
>> > > Am I missing and or just misunderstanding something here?
>> >
>> > "eth0:1" is not really a different interface.
>> >
>> > Part of the deploy process is to take the interface you have chosen,
>> > create a new bridge, copy part of the configuration from the nic to
>> > the bridge, and add the nic to the bridge. This is one of the most
>> > delicate parts of the process, the one that if fails might leave you
>> > with no network access, the one due to which we recommend to run this
>> > inside 'screen'. You can't do this to "eth0" and keep "eth0:1"
>> > untouched. You need either a vlan interface or a separate physical
>> > nic. If you feel like this, please open a bug to make 'hosted-engine
>> > --deploy' notice and prevent what you tried to do. Currently it does
>> > not check IP aliases.
>
> I was creating the /29 gw IP on eth0:1 because it seems the simplest thing to 
> do. There is no requirement for it to hang off of eth0.
>
> Given that I have to hang the entire /29 subnet on the host (and VMs), and I 
> am presuming that the gw IP of the /29 must be on the host, do you have a 
> suggestion of how to configure this? (And to be explicit about it, do I need 
> the /29 gw IP on the host to ensure the vm networking operates?)

Not sure, but even if you do, I think you can do that after --deploy finishes.
Can you please detail (again, perhaps) your intention/plan? How many NICs you
have, can you use VLANs, etc.? Also, if if it's a single host that will remain
single, you might find it simpler to use virt-manager. oVirt is intended for
managing larger setups.

>
> Without the vm engine logs it is difficult to determine why the engine vm 
> fails when resolving its fqdn. At this point I'm presuming it's due to a 
> networking/routing issue, but am open to suggestions.
>
>
>> > Another point - the script that failed is 'engine-setup'. This one
>> > runs inside the engine vm, and keeps its logs in
>> > /var/log/ovirt-engine/setup. If it fails again, please check/post also
>> > these, if at all possible (that is, if you can access the vm).
>> > Thinking about this, it might be possible for 'hosted-engine --deploy'
>> > to get this log, perhaps through the virtual serial connection it
>> > opens to show you the output, and save it on the host side, for easier
>> > debugging. Please open a bug for this too :-)
>>
>
> When the engine vm setup fails I am unable to connect to it via 
> "hosted-engine --console". Should console access to the engine vm exist at 
> this point? If so, what is the best way to access the engine vm console?
>
> The lack access to the engine vm logs is very painful for trying to diagnose 
> what is going wrong. Ideas welcomed!
>

If the vm is still up, you can see its qemu process on the host
with 'ps'.

I detailed most of what I know about accessing the console in:

http://www.ovirt.org/documentation/admin-guide/hosted-engine-console/

Please note that in recent versions, '--console' connects you to the
serial console, not graphical one. We did this so that we do not
need to enforce installing a graphical env on mostly-headless hosts.

Best,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Single server hosted engine... almost there

2016-12-10 Thread Yedidyah Bar David 
On Thu, Dec 8, 2016 at 6:45 PM, Derek Atkins  wrote:
> Hi,
>
> On Thu, December 8, 2016 11:37 am, Mark Steckel wrote:
>>
>>> Yeah, I suspect you will need to set up your engine NOT using the
>>> appliance, but instead install CentOS and then the engine inside the VM.
>>> This will give you more direct access to the engine VM, and should give
>>> you the opportunity to set up the bridge routing during the process.
>>
>> Makes sense, at least in concept.
>>
>> But are you suggesting that I manually set up the vm for the engine (ie
>> not use "hosted-engine --deploy")
>
> No, you should still use hosted-engine --deploy, but use a CentOS install
> media instead of a virtual appliance.
>
>> and then manually run engine setup from w/i the vm?
>
> Yes.  You will need to do that.  But this should give you the opportunity
> to test networking, DNS, routing, etc on the host and VM prior to running
> engine-setup.

Not sure you really need much more control on the engine vm or
engine-setup for that - you mainly need to tell --deploy to not touch
iptables, and then handle that yourself.

Also, you can use the appliance without using cloud-init - then you can
do everything manually, and just save yourself from having to yum install
stuff inside the engine vm.

Best,
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt 4.1 beta - Install problems ( storage )

2016-12-10 Thread Maton, Brett 
Yup that was it, I hadn't opened port 49152 which was causing gluster to
fail.

On 10 December 2016 at 17:44, Maton, Brett  wrote:

> Ok so I now think the problem is that the gluster file systems are being
> mounted read only
>
> On 10 December 2016 at 15:09, Maton, Brett 
> wrote:
>
>> Hi,
>>
>>   I'm trying to install Ovirt 4.1 beta using glusterfs as the storage
>> domain.
>>   First time I've tried it so there could be some real simple mistakes in
>> my config :)
>>
>> # gluster volume info
>>
>> Volume Name: ovirt
>> Type: Replicate
>> Volume ID: 8d9d480c-dfc8-4099-acbc-2eb1a01afc9d
>> Status: Started
>> Snapshot Count: 0
>> Number of Bricks: 1 x 3 = 3
>> Transport-type: tcp
>> Bricks:
>> Brick1: 192.168.0.1:/u01/.bricks/ovirt
>> Brick2: 192.168.0.2:/u01/.bricks/ovirt
>> Brick3: 192.168.0.3:/u01/.bricks/ovirt
>> Options Reconfigured:
>> transport.address-family: inet
>> performance.readdir-ahead: on
>> nfs.disable: on
>>
>>
>> I wasn't sure what path to put for the gluster storage so I've been
>> trying with localhost
>>
>>   Please specify the storage you would like to use (glusterfs,
>> iscsi, fc, nfs3, nfs4)[nfs3]: glusterfs
>> [ INFO  ] Please note that Replica 3 support is required for the shared
>> storage.
>>   Please specify the full shared storage connection path to use
>> (example: host:/path): localhost:/ovirt
>>
>>
>> hosted-engine --deploy gets as far as trying to create the storage domain
>> and then fails.
>>
>> [ INFO  ] Stage: Transaction setup
>> [ INFO  ] Stage: Misc configuration
>> [ INFO  ] Stage: Package installation
>> [ INFO  ] Stage: Misc configuration
>> [ INFO  ] Configuring libvirt
>> [ INFO  ] Configuring VDSM
>> [ INFO  ] Starting vdsmd
>> [ INFO  ] Creating Storage Domain
>> [ ERROR ] Failed to execute stage 'Misc configuration': Error creating a
>> storage domain: (u'storageType=7, 
>> sdUUID=40db955e-e9a1-4279-929b-b63d96ca8161,
>> domainName=hosted_storage, domClass=1, typeSpecificArg=localhost:ovirt
>> domVersion=3',)
>> [ INFO  ] Yum Performing yum transaction rollback
>> [ INFO  ] Stage: Clean up
>> [ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-
>> setup/answers/answers-20161210145440.conf'
>> [ INFO  ] Stage: Pre-termination
>> [ INFO  ] Stage: Termination
>> [ ERROR ] Hosted Engine deployment failed: this system is not reliable,
>> please check the issue,fix and redeploy
>>   Log file is located at /var/log/ovirt-hosted-engine-s
>> etup/ovirt-hosted-engine-setup-20161210144910-rbql1i.log
>>
>>
>
___
Users mailing list
Users@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt 4.1 beta - Install problems ( storage )

2016-12-10 Thread Maton, Brett 
Ok so I now think the problem is that the gluster file systems are being
mounted read only

On 10 December 2016 at 15:09, Maton, Brett  wrote:

> Hi,
>
>   I'm trying to install Ovirt 4.1 beta using glusterfs as the storage
> domain.
>   First time I've tried it so there could be some real simple mistakes in
> my config :)
>
> # gluster volume info
>
> Volume Name: ovirt
> Type: Replicate
> Volume ID: 8d9d480c-dfc8-4099-acbc-2eb1a01afc9d
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 1 x 3 = 3
> Transport-type: tcp
> Bricks:
> Brick1: 192.168.0.1:/u01/.bricks/ovirt
> Brick2: 192.168.0.2:/u01/.bricks/ovirt
> Brick3: 192.168.0.3:/u01/.bricks/ovirt
> Options Reconfigured:
> transport.address-family: inet
> performance.readdir-ahead: on
> nfs.disable: on
>
>
> I wasn't sure what path to put for the gluster storage so I've been trying
> with localhost
>
>   Please specify the storage you would like to use (glusterfs,
> iscsi, fc, nfs3, nfs4)[nfs3]: glusterfs
> [ INFO  ] Please note that Replica 3 support is required for the shared
> storage.
>   Please specify the full shared storage connection path to use
> (example: host:/path): localhost:/ovirt
>
>
> hosted-engine --deploy gets as far as trying to create the storage domain
> and then fails.
>
> [ INFO  ] Stage: Transaction setup
> [ INFO  ] Stage: Misc configuration
> [ INFO  ] Stage: Package installation
> [ INFO  ] Stage: Misc configuration
> [ INFO  ] Configuring libvirt
> [ INFO  ] Configuring VDSM
> [ INFO  ] Starting vdsmd
> [ INFO  ] Creating Storage Domain
> [ ERROR ] Failed to execute stage 'Misc configuration': Error creating a
> storage domain: (u'storageType=7, sdUUID=40db955e-e9a1-4279-929b-b63d96ca8161,
> domainName=hosted_storage, domClass=1, typeSpecificArg=localhost:ovirt
> domVersion=3',)
> [ INFO  ] Yum Performing yum transaction rollback
> [ INFO  ] Stage: Clean up
> [ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-
> setup/answers/answers-20161210145440.conf'
> [ INFO  ] Stage: Pre-termination
> [ INFO  ] Stage: Termination
> [ ERROR ] Hosted Engine deployment failed: this system is not reliable,
> please check the issue,fix and redeploy
>   Log file is located at /var/log/ovirt-hosted-engine-
> setup/ovirt-hosted-engine-setup-20161210144910-rbql1i.log
>
>
___
Users mailing list
Users@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Ovirt 4.1 beta - Install problems ( storage )

2016-12-10 Thread Maton, Brett 
Saw this in /var/log/messages possibly related

Dec 10 16:48:41 lp05 systemd: mom-vdsm.service holdoff time over,
scheduling restart.
Dec 10 16:48:41 lp05 systemd: Started MOM instance configured for VDSM
purposes.
Dec 10 16:48:41 lp05 systemd: Starting MOM instance configured for VDSM
purposes...
Dec 10 16:48:41 lp05 systemd: Started /usr/bin/mount -t glusterfs -o
backup-volfile-servers=10.10.30.5:10.10.30.6:10.10.30.8 localhost:/ovirt
/rhev/data-center/mnt/glusterSD/localhost:_ovirt.
Dec 10 16:48:41 lp05 systemd: Starting /usr/bin/mount -t glusterfs -o
backup-volfile-servers=10.10.30.5:10.10.30.6:10.10.30.8 localhost:/ovirt
/rhev/data-center/mnt/glusterSD/localhost:_ovirt.
Dec 10 16:48:46 lp05 kernel: EXT4-fs (loop11): mounting ext3 file system
using the ext4 subsystem
Dec 10 16:48:46 lp05 kernel: EXT4-fs (loop11): mounted filesystem with
ordered data mode. Opts: (null)
Dec 10 16:48:46 lp05 systemd: Device
dev-disk-by\x2duuid-50642dea\x2d9bfc\x2d4624\x2d9255\x2d80ef82c78214.device
appeared twice with different sysfs paths /sys/devices/virtual/block/loop10
and /sys/devices/virtual/block/loop11
Dec 10 16:48:46 lp05 systemd: Device
dev-disk-by\x2duuid-50642dea\x2d9bfc\x2d4624\x2d9255\x2d80ef82c78214.device
appeared twice with different sysfs paths /sys/devices/virtual/block/loop10
and /sys/devices/virtual/block/loop11
Dec 10 16:48:47 lp05 journal: vdsm vds.dispatcher ERROR SSL error receiving
from : unexpected eof



On 10 December 2016 at 15:09, Maton, Brett  wrote:

> Hi,
>
>   I'm trying to install Ovirt 4.1 beta using glusterfs as the storage
> domain.
>   First time I've tried it so there could be some real simple mistakes in
> my config :)
>
> # gluster volume info
>
> Volume Name: ovirt
> Type: Replicate
> Volume ID: 8d9d480c-dfc8-4099-acbc-2eb1a01afc9d
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 1 x 3 = 3
> Transport-type: tcp
> Bricks:
> Brick1: 192.168.0.1:/u01/.bricks/ovirt
> Brick2: 192.168.0.2:/u01/.bricks/ovirt
> Brick3: 192.168.0.3:/u01/.bricks/ovirt
> Options Reconfigured:
> transport.address-family: inet
> performance.readdir-ahead: on
> nfs.disable: on
>
>
> I wasn't sure what path to put for the gluster storage so I've been trying
> with localhost
>
>   Please specify the storage you would like to use (glusterfs,
> iscsi, fc, nfs3, nfs4)[nfs3]: glusterfs
> [ INFO  ] Please note that Replica 3 support is required for the shared
> storage.
>   Please specify the full shared storage connection path to use
> (example: host:/path): localhost:/ovirt
>
>
> hosted-engine --deploy gets as far as trying to create the storage domain
> and then fails.
>
> [ INFO  ] Stage: Transaction setup
> [ INFO  ] Stage: Misc configuration
> [ INFO  ] Stage: Package installation
> [ INFO  ] Stage: Misc configuration
> [ INFO  ] Configuring libvirt
> [ INFO  ] Configuring VDSM
> [ INFO  ] Starting vdsmd
> [ INFO  ] Creating Storage Domain
> [ ERROR ] Failed to execute stage 'Misc configuration': Error creating a
> storage domain: (u'storageType=7, sdUUID=40db955e-e9a1-4279-929b-b63d96ca8161,
> domainName=hosted_storage, domClass=1, typeSpecificArg=localhost:ovirt
> domVersion=3',)
> [ INFO  ] Yum Performing yum transaction rollback
> [ INFO  ] Stage: Clean up
> [ INFO  ] Generating answer file '/var/lib/ovirt-hosted-engine-
> setup/answers/answers-20161210145440.conf'
> [ INFO  ] Stage: Pre-termination
> [ INFO  ] Stage: Termination
> [ ERROR ] Hosted Engine deployment failed: this system is not reliable,
> please check the issue,fix and redeploy
>   Log file is located at /var/log/ovirt-hosted-engine-
> setup/ovirt-hosted-engine-setup-20161210144910-rbql1i.log
>
>
___
Users mailing list
Users@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/users

[ovirt-users] Ovirt 4.1 beta - Install problems ( storage )

2016-12-10 Thread Maton, Brett 
Hi,

  I'm trying to install Ovirt 4.1 beta using glusterfs as the storage
domain.
  First time I've tried it so there could be some real simple mistakes in
my config :)

# gluster volume info

Volume Name: ovirt
Type: Replicate
Volume ID: 8d9d480c-dfc8-4099-acbc-2eb1a01afc9d
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: 192.168.0.1:/u01/.bricks/ovirt
Brick2: 192.168.0.2:/u01/.bricks/ovirt
Brick3: 192.168.0.3:/u01/.bricks/ovirt
Options Reconfigured:
transport.address-family: inet
performance.readdir-ahead: on
nfs.disable: on


I wasn't sure what path to put for the gluster storage so I've been trying
with localhost

  Please specify the storage you would like to use (glusterfs,
iscsi, fc, nfs3, nfs4)[nfs3]: glusterfs
[ INFO  ] Please note that Replica 3 support is required for the shared
storage.
  Please specify the full shared storage connection path to use
(example: host:/path): localhost:/ovirt


hosted-engine --deploy gets as far as trying to create the storage domain
and then fails.

[ INFO  ] Stage: Transaction setup
[ INFO  ] Stage: Misc configuration
[ INFO  ] Stage: Package installation
[ INFO  ] Stage: Misc configuration
[ INFO  ] Configuring libvirt
[ INFO  ] Configuring VDSM
[ INFO  ] Starting vdsmd
[ INFO  ] Creating Storage Domain
[ ERROR ] Failed to execute stage 'Misc configuration': Error creating a
storage domain: (u'storageType=7,
sdUUID=40db955e-e9a1-4279-929b-b63d96ca8161, domainName=hosted_storage,
domClass=1, typeSpecificArg=localhost:ovirt domVersion=3',)
[ INFO  ] Yum Performing yum transaction rollback
[ INFO  ] Stage: Clean up
[ INFO  ] Generating answer file
'/var/lib/ovirt-hosted-engine-setup/answers/answers-20161210145440.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Hosted Engine deployment failed: this system is not reliable,
please check the issue,fix and redeploy
  Log file is located at
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20161210144910-rbql1i.log
___
Users mailing list
Users@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/users