Ask Your Question

sidx64's profile - activity

2017-06-11 04:00:41 -0600 received badge  Famous Question (source)
2017-06-03 11:15:00 -0600 received badge  Supporter (source)
2017-06-03 02:28:54 -0600 received badge  Notable Question (source)
2017-06-02 18:07:47 -0600 received badge  Popular Question (source)
2017-06-02 08:46:40 -0600 asked a question Ocata, VNC shows Cirros instance stuck at "GRUB"

Hello! I am working on building an openstack setup using the documentation at: https://docs.openstack.org/ocata/install-guide-rdo/. I am running two VMs on VMWare on a device with physical RAM 32GB and a Core i7 4810Q proccy. Both VMs are running on CentOS 7.3. Controller node has 8GB of RAM and the Compute Node has 16GB RAM

Currently facing an issue when building an instance of cirros. Issue: Cirros Instance stuck at "Booting from Harddisk GRUB" in the console VNC.

Can someone help me identify this issue?

Steps taken so far:

  1. I checked and ensured that nested virtualization is enabled on the VMWare Workstation [went to processor and enabled "Virtualize VT -x" option on both compute and controller node]

  2. I followed the documentation to the T (used provider network only option for neutron)

  3. The document asked me to check egrep -c '(vmx|svm)' /proc/cpuinfo and the result was "8". Hence did not set virt_type in /etc/nova/nova.conf

Some Command Outputs

Compute node CPUINFO

[root@okvm qemu]# egrep -c '(vmx|svm)' /proc/cpuinfo
8

hypervisor list

 [root@octl ~]# openstack hypervisor list
    +----+---------------------+-----------------+----------------+-------+
    | ID | Hypervisor Hostname | Hypervisor Type | Host IP        | State |
    +----+---------------------+-----------------+----------------+-------+
    |  1 | okvm                | QEMU            | 192.168.44.102 | up    |
    +----+---------------------+-----------------+----------------+-------+

Compute Services

 [root@octl ~]# openstack compute service list
    +----+------------------+------+----------+---------+-------+----------------------------+
    | ID | Binary           | Host | Zone     | Status  | State | Updated At                 |
    +----+------------------+------+----------+---------+-------+----------------------------+
    |  1 | nova-scheduler   | octl | internal | enabled | up    | 2017-06-02T12:46:12.000000 |
    |  2 | nova-consoleauth | octl | internal | enabled | up    | 2017-06-02T12:46:22.000000 |
    |  3 | nova-conductor   | octl | internal | enabled | up    | 2017-06-02T12:46:20.000000 |
    |  8 | nova-compute     | okvm | nova     | enabled | up    | 2017-06-02T12:46:14.000000 |
    +----+------------------+------+----------+---------+-------+----------------------------+

Nova Status

[root@octl ~]#  nova-status upgrade check
+---------------------------+
| Upgrade Check Results     |
+---------------------------+
| Check: Cells v2           |
| Result: Success           |
| Details: None             |
+---------------------------+
| Check: Placement API      |
| Result: Success           |
| Details: None             |
+---------------------------+
| Check: Resource Providers |
| Result: Success           |
| Details: None             |
+---------------------------+

Server says it is built successfully and is ACTIVE

[root@octl ~]# openstack server list
+--------------------------------------+-------------+--------+------------------------+------------+
| ID                                   | Name        | Status | Networks               | Image Name |
+--------------------------------------+-------------+--------+------------------------+------------+
| b3fd3f9d-e8f4-40ba-b433-457303ba768d | cirros-test | ACTIVE | provider=192.168.44.93 | cirros     |
+--------------------------------------+-------------+--------+------------------------+------------+

Instance Log

2017-06-02 13:05:38.688+0000: starting up libvirt version: 2.0.0, package: 10.el7_3.9 (CentOS BuildSystem <http://bugs.centos.org>, 2017-05-25-20:52:28, c1bm.rdu2.centos.org), qemu version: 2.6.0 (qemu-kvm-ev-2.6.0-28.el7_3.9.1), hostname: okvm
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -name guest=instance-00000004,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-instance-00000004/master-key.aes -machine pc-i440fx-rhel7.3.0,accel=kvm,usb=off -cpu Haswell-noTSX,+vme,+ds,+ss,+ht,+vmx,+osxsave,+f16c,+rdrand,+hypervisor,+arat,+tsc_adjust,+xsaveopt,+pdpe1gb,+abm -m 64 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid ad2f8a18-7e91-4016-b80d-2539b2a43877 -smbios 'type=1,manufacturer=RDO,product=OpenStack Compute,version=15.0.3-2.el7,serial=ac0bec73-3ef5-4a89-a439-690339e1121d,uuid=ad2f8a18-7e91-4016-b80d-2539b2a43877,family=Virtual Machine' -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-instance-00000004/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id ...
(more)
2016-04-20 19:05:14 -0600 received badge  Famous Question (source)
2016-03-08 23:16:18 -0600 commented answer VNC Console in Dashboard fails to connect ot server (code: 1006)

I restarted all the services :P

And I had ".localdomain" attached to the hostname of my vncserver_proxyclient_address. Removed it, replaced with IP, restarted services,

Works like a charm~! :)

2016-03-08 22:34:13 -0600 received badge  Enthusiast
2016-03-07 22:51:24 -0600 commented answer Magnum Bay create command fails with Error 400

this worked beautifully. sbiswas7, can you tell me why/how this worked?

2016-03-06 23:56:00 -0600 received badge  Scholar (source)
2016-02-22 23:16:34 -0600 received badge  Notable Question (source)
2016-02-22 23:16:34 -0600 received badge  Popular Question (source)
2016-02-08 23:33:41 -0600 received badge  Famous Question (source)
2016-02-02 03:14:13 -0600 received badge  Notable Question (source)
2016-01-31 23:35:30 -0600 received badge  Popular Question (source)
2016-01-31 01:10:00 -0600 asked a question Magnum Bay create command fails with Error 400

Hello!

I have manually integrated Magnum into an existing RDO Packstack installation, all in one VM with 16GB of Memory.

When I try to create a Baymodel, it is created just fine: http://ur1.ca/ogqmb

However, when I try to create a Bay as shown in the Developer Quickstart documentation of Magnum, an error pops up and the bay is not created.

[root@magnum ~]# magnum bay-create --name k8sbay --baymodel k8sbaymodel --node-count 1 

ERROR: ERROR: Property error: : resources.fixed_subnet.properties.cidr: : "10.0.0.0/24" does not validate net_cidr (constraint not found) Traceback (most recent call last):

  File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 142, in _dispatch_and_reply
    executor_callback))

  File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 186, in _dispatch
    executor_callback)

  File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 129, in _do_dispatch
    result = func(ctxt, **new_args)

  File "/usr/lib/python2.7/site-packages/magnum/conductor/handlers/bay_conductor.py", line 134, in bay_create
    raise exception.InvalidParameterValue(message=str(e))

InvalidParameterValue: ERROR: Property error: : resources.fixed_subnet.properties.cidr: : "10.0.0.0/24" does not validate net_cidr (constraint not found)  (HTTP 400)

I see this error in the debug logs:

Debug Log: Magnum-api: http://ur1.ca/ogqmh

Debug Log: Magnum-Conductor: http://ur1.ca/ogqmj

I believe this is somehow related to this Bug: https://bugs.launchpad.net/magnum/+bu... But I do not know how I can resolve it. Can someone please prod me in the right direction?

2015-12-15 13:25:34 -0600 asked a question Set up Magnum with Devstack on a VirtualBox VM

Greetings all! I am starting with DevStack, and I have been trying to set up devstack with Magnum using the Dev Quickstart: http://docs.openstack.org/developer/magnum/dev/dev-quickstart.html (http://docs.openstack.org/developer/m...)

In the local.conf file, I am trying to understand the significance and use of the floating_range, public_network_gateway and public_interface. I am looking to understand how to modify these parameters and build a devstack instance in my Virtual Machine (VirtualBox). The VM has two Interfaces: eth0 and eth1. eth0 is a NAT interface, with the IP configured to 10.0.2.15 and eth1 is connected via a bridge to my host's Internet.

Which interface must I point to in the local.conf file? More specifically, what values should I set here?

Any help or prod in the right direction is highly appreciated. Thank you.