Ask Your Question
0

Deploying TripleO using RDO Instack on top of Havana

asked 2014-05-03 08:00:17 -0500

cloudssky gravatar image

updated 2014-05-03 17:43:10 -0500

I' following this guide on the RDO site to discover TripleO on top of Havana using the latest Fedora 20 guest image with 200 GB disk and 16GB RAM and 8 vCPUs:

http://openstack.redhat.com/Deploying...

At Step 6 I'm getting the following by running "virsh start instack":

[stack@instack ~]$ virsh start instack

error: Failed to start domain instack

error: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.

And if I run:

[stack@tripleo ~]$ sudo systemctl status libvirtd

libvirtd.service - Virtualization daemon
   Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)
   Active: active (running) since Sat 2014-05-03 22:29:07 UTC; 4min 6s ago
     Docs: man:libvirtd(8)
           http://libvirt.org
 Main PID: 730 (libvirtd)
   CGroup: /system.slice/libvirtd.service
           ├─730 /usr/sbin/libvirtd
           └─887 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf

May 03 22:29:08 tripleo.novalocal dnsmasq[887]: reading /etc/resolv.conf
May 03 22:29:08 tripleo.novalocal dnsmasq[887]: using nameserver 8.8.8.8#53
May 03 22:29:08 tripleo.novalocal dnsmasq[887]: using local addresses only for unqualified names
May 03 22:29:08 tripleo.novalocal dnsmasq[887]: read /etc/hosts - 2 addresses
May 03 22:29:08 tripleo.novalocal dnsmasq[887]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
May 03 22:29:08 tripleo.novalocal dnsmasq-dhcp[887]: read /var/lib/libvirt/dnsmasq/default.hostsfile
May 03 22:33:09 tripleo.novalocal libvirtd[730]: libvirt version: 1.1.3.4, package: 4.fc20 (Fedora Project, 2014-03-18-18:53:51, buildvm-21.phx2.fedoraproject.org)
May 03 22:33:09 tripleo.novalocal libvirtd[730]: unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
May 03 22:33:09 tripleo.novalocal libvirtd[730]: internal error: Child process (ovs-vsctl --timeout=5 -- --if-exists del-port) unexpected exit status 1: ovs-vsctl: 'del-port' command requires at least 1 arguments
May 03 22:33:09 tripleo.novalocal libvirtd[730]: Unable to delete port (null) from OVS: Operation not permitted

So I guess there must be a way to force using QEMU instead KVM, If yes, how?

Note: I'd to uncomment: export NODE_DIST="fedora selinux-permissive" in /usr/libexec/openstack-tripleo/devtest_variables.sh to get "instack-virt-setup" working in step 5.

Thanks!

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
1

answered 2014-05-04 02:58:32 -0500

cloudssky gravatar image

updated 2014-05-04 16:18:55 -0500

I'd to change the domain type form kvm to qemu by running:

[stack@tripleo ~]$ sudo virsh edit instack

    and replaced "kvm" with "qemu" in the root tag from <domain type='kvm'> to <domain type='qemu'>
    and had to delete the SATA controller tag, since I got:

        [stack@tripleo ~]$ sudo virsh start instack
        error: Failed to start domain instack
        error: unsupported configuration: SATA is not supported with this QEMU binary

And changed <target dev='sda' bus='sata'/> to <target dev='vda' bus='ide'/>

And now I can run instack:

[stack@tripleo ~]$ sudo virsh start instack
Domain instack started

and get the IP address of the undercloud VM:

[stack@tripleo ~]$ cat /var/lib/libvirt/dnsmasq/default.leases | grep $(tripleo get-vm-mac instack) | awk '{print $3;}'
192.168.122.165

and finally cloud proceed to the next step to deploy the undercloud described here:

http://openstack.redhat.com/Deploying...

and got to Step 5 running as my stack user on the instack VM (I renamed it from localhost to instack and here was my failure (read on what happens):

[stack@instack ~] instack-install-undercloud-packages

and hoped that I'd get "install-undercloud Complete!" at the End as described on that page, the installation took near to 2 hours :-) and I can see that all OpenStack Services are running in my instack VM, but the installation aborted at the End, I guess by the last step by installing tuskar:

    2014-05-04 07:38:34.124 29752 INFO sqlalchemy.engine.base.Engine [-] SELECT migrate_version.repository_id, migrate_version.repository_path, migrate_version.version 
FROM migrate_version 
WHERE migrate_version.repository_id = ?
2014-05-04 07:38:34.142 29752 INFO sqlalchemy.engine.base.Engine [-] ('tuskar',)
+ service openstack-tuskar-api restart
Redirecting to /bin/systemctl restart  openstack-tuskar-api.service
+ sleep 5
+ tuskar overcloud-role-create controller --description 'Controller Node' --image-name overcloud-control
ERROR:tuskarclient.shell:Exiting due to an error:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/tuskarclient/shell.py", line 224, in main
    TuskarShell(sys.argv[1:]).run()
  File "/usr/lib/python2.7/site-packages/tuskarclient/shell.py", line 71, in run
    args.func(tuskar_client, args)
  File "/usr/lib/python2.7/site-packages/tuskarclient/v1/overcloud_roles_shell.py", line 45, in do_overcloud_role_create
    overcloud_role = tuskar.overcloud_roles.create(**overcloud_role_dict)
  File "/usr/lib/python2.7/site-packages/tuskarclient/v1/overcloud_roles.py", line 70, in create
    return self._create(self._path(), fields)
  File "/usr/lib/python2.7/site-packages/tuskarclient/common/base.py", line 78, in _create
    resp, body = self.api.json_request('POST', url, body=body)
  File "/usr/lib/python2.7/site-packages/tuskarclient/common/http.py", line 196, in json_request
    resp, body_iter = self._http_request(url, method, **kwargs)
  File "/usr/lib/python2.7/site-packages/tuskarclient/common/http.py", line 158, in _http_request
    'endpoint': self.endpoint, 'e': e})
CommunicationError: Error communicating with http://localhost:8585/ [Errno 111] Connection refused
[2014-05-04 07:39:31,342] (os-refresh-config) [ERROR] during post-configure phase. [Command '['dib-run-parts', '/opt/stack/os-config-refresh/post-configure.d']' returned non-zero exit status 1]

[2014-05-04 07:39:31,799] (os-refresh-config) [ERROR] Aborting...

And here was the installation aborted, but as I mentioned all services where running.

So decided to proceed to the next step ... (more)

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-05-03 08:00:17 -0500

Seen: 953 times

Last updated: May 04 '14