Well that was interesting. When I ran hosted-engine --connect-storage, the Data Center went green, and I could see an unattached ISO domain and ovirt-image-repository (but no Data domain). But after restarting ovirt-ha-broker and ovirt-ha-agent, the storage disappeared again and the Data Center went red.
In retrospect, there appears to be a problem with iptables/firewalld that could be related. I noticed two things: - firewalld is stopped and disabled on the host - I could not manually NFS mount (v3 or v4) from the host to the engine, unless I did "service iptables stop" So it doesn't appear to me that hosted-engine did the right things with firewalld/iptables. If these problems occurred during the --deploy, could that result in this situation? I have temporarily disabled iptables until I get things working, but clearly that's insufficient to resolve the problem at this point. -Bob On 05/20/2014 05:18 AM, Jiri Moskovcak wrote: > On 05/20/2014 03:33 AM, Bob Doolittle wrote: >> I have successfully completed hosted-engine --deploy with 3.4.1, and set >> up my Engine. This is with F19 for both the host and engine >> (with the sos package workarounds stated). >> >> However, it does not seem to have initialized any Storage Domains, and >> the Datacenter cannot initialize. >> >> I've attached my setup and vdsm logs. >> >> Any guidance appreciated. >> >> Thanks, >> Bob >> > Hi Bob, > can you try to run: > > $ hosted-engine --connect-storage > $ service ovirt-ha-broker restart > $ service ovirt-ha-agent restart > > and see if it helps? > > Thanks, > Jirka > >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.ovirt.org/mailman/listinfo/users >> > _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
