cunningr69's profile - activity

2015-11-19 09:58:45 -0600 asked a question kilo neutron ports clean up

I am running kilo release.

I am creating neutron ports with manually assigned IP addresses and then attaching those to an instance at boot time. Pre kilo I recall that when I delete the instance, those attached neutron ports also are deleted and the addresses are freed up.

In kilo after deleting the instance it seems that the neutron ports remain.

Is this a bug or an intended change in behavior?

2015-07-28 12:39:44 -0600 received badge  Self-Learner (source)
2015-03-02 12:50:26 -0600 received badge  Famous Question (source)
2015-02-20 12:22:42 -0600 received badge  Famous Question (source)
2014-12-31 09:44:49 -0600 received badge  Teacher (source)
2014-12-31 09:44:49 -0600 received badge  Self-Learner (source)
2014-12-22 00:32:04 -0600 received badge  Famous Question (source)
2014-12-03 01:28:02 -0600 received badge  Notable Question (source)
2014-12-02 16:11:34 -0600 received badge  Notable Question (source)
2014-12-02 16:11:34 -0600 received badge  Popular Question (source)
2014-11-28 14:07:28 -0600 received badge  Enthusiast
2014-11-27 05:58:52 -0600 received badge  Popular Question (source)
2014-11-27 05:27:58 -0600 asked a question compute vncproxy configuration

I am installing juno release on Ubuntu 14.04 following the documentation.

When I finally got a VM deployed I could not access the VNC console attached to the VM because the install instructions did not include to add the VNC proxy packages although the docs do tell us how to configure vncproxy for compute.

I managed to resolve this by doing a:

sudo apt-get install nova-consoleauth nova-novncproxy

and then restarting novva-compute:

 sudo service nova-compute restart

Should this step be included in the original documentation?

2014-11-27 04:50:34 -0600 commented answer juno nova instance stuck in BUILD scheduling

Thanks! Yes that was my issue. I hadn't finished the upgrade/install on my compute node.

2014-11-27 03:01:28 -0600 commented answer juno nova instance stuck in BUILD scheduling

at the same time during image create the nova-compute on the compute node is throwing an ERROR regarding the RPC version:

http://paste.openstack.org/show/139398/

2014-11-27 02:57:27 -0600 commented answer juno nova instance stuck in BUILD scheduling

I tried to tail the logs during the nova create. the nova-api log output is here:

http://paste.openstack.org/show/139370/ one thing I note is: 2014-11-26 20:39:23.125 8863 INFO nova.api.openstack.wsgi [req-892288ab-9277-49bd-ab98-c514daecad66 None] HTTP exception thrown: The resource could not be

2014-11-27 02:57:02 -0600 commented answer juno nova instance stuck in BUILD scheduling

there is not much in the controller nova-api or the schedular however the conductor seems eventually to be hitting some timeout:

http://paste.openstack.org/show/139377/

2014-11-27 02:42:30 -0600 commented question juno nova instance stuck in BUILD scheduling

I tried to tail the logs during the nova create. the nova-api log output is here:

http://paste.openstack.org/show/139370/ one thing I note is: 2014-11-26 20:39:23.125 8863 INFO nova.api.openstack.wsgi [req-892288ab-9277-49bd-ab98-c514daecad66 None] HTTP exception thrown: The resource could not be

2014-11-27 02:42:30 -0600 received badge  Commentator
2014-11-27 02:21:55 -0600 asked a question juno nova instance stuck in BUILD scheduling

I am following the install guides for Juno on Ubuntu 14.04 however I should point out one variation. I only have two physical nodes; contoller+network and compute.

I have limited resources so I am trying to combine the controller and the network node however I have dedicated compute node:

    cisco@kermit:~$ nova service-list
    +----+------------------+--------+----------+---------+-------+----------------------------+-----------------+
    | Id | Binary           | Host   | Zone     | Status  | State | Updated_at                 | Disabled Reason |
    +----+------------------+--------+----------+---------+-------+----------------------------+-----------------+
    | 1  | nova-cert        | kermit | internal | enabled | up    | 2014-11-26T20:04:57.000000 | -               |
    | 2  | nova-consoleauth | kermit | internal | enabled | up    | 2014-11-26T20:04:58.000000 | -               |
    | 3  | nova-scheduler   | kermit | internal | enabled | up    | 2014-11-26T20:04:55.000000 | -               |
    | 4  | nova-conductor   | kermit | internal | enabled | up    | 2014-11-26T20:04:57.000000 | -               |
    | 5  | nova-compute     | gonzo  | nova     | enabled | up    | 2014-11-26T20:04:56.000000 | -               |
    +----+------------------+--------+----------+---------+-------+----------------------------+-----------------+

The neutron part also seems to be working and I can ping my demo router ext-net from outside the cluster:

cisco@kermit:~$ neutron agent-list
+--------------------------------------+--------------------+--------+-------+----------------+---------------------------+
| id                                   | agent_type         | host   | alive | admin_state_up | binary                    |
+--------------------------------------+--------------------+--------+-------+----------------+---------------------------+
| 267b6cff-e1f1-4a08-8184-5b1c7f0d9a88 | Open vSwitch agent | kermit | :-)   | True           | neutron-openvswitch-agent |
| aa4ec4df-fc3a-4a54-8918-e8f2b77398e8 | L3 agent           | kermit | :-)   | True           | neutron-l3-agent          |
| c92cfef0-b3e0-4056-ba5d-4cf6bd3f9611 | DHCP agent         | kermit | :-)   | True           | neutron-dhcp-agent        |
| d077ef64-decc-462e-af8c-57a8e165074e | Metadata agent     | kermit | :-)   | True           | neutron-metadata-agent    |
| fa28402e-f374-4e0e-b277-f4b21737aabb | Open vSwitch agent | gonzo  | :-)   | True           | neutron-openvswitch-agent |
+--------------------------------------+--------------------+--------+-------+----------------+---------------------------+


DCN-N7K-3-OldAdmin# ping 192.168.102.10
PING 192.168.102.10 (192.168.102.10): 56 data bytes
64 bytes from 192.168.102.10: icmp_seq=0 ttl=63 time=1.486 ms
64 bytes from 192.168.102.10: icmp_seq=1 ttl=63 time=0.893 ms
64 bytes from 192.168.102.10: icmp_seq=2 ttl=63 time=0.616 ms
64 bytes from 192.168.102.10: icmp_seq=3 ttl=63 time=0.692 ms
64 bytes from 192.168.102.10: icmp_seq=4 ttl=63 time=0.626 ms

When I do a nova create as per juno install docs, my instance doesn't get passed BUILD|scheduling and eventually moves to ERROR:

cisco@kermit:~$ nova list
+--------------------------------------+----------------+--------+------------+-------------+----------+
| ID                                   | Name           | Status | Task State | Power State | Networks |
+--------------------------------------+----------------+--------+------------+-------------+----------+
| b9b77f5f-5420-4d03-b489-fcaed1d8698d | demo-instance1 | ERROR  | -          | NOSTATE     |          |
+--------------------------------------+----------------+--------+------------+-------------+----------+
cisco@kermit:~$

Can someone help me please, where do I start to debug this?

2014-11-26 13:43:16 -0600 answered a question juno glance Invalid OpenStack Identity credentials

Ok I found my fix. I was hitting ->

https://bugs.launchpad.net/openstack-...

Which meant that Ubuntu 14.04 wasn't actually pulling the latest packages so I wasn't actually using Juno (doh!)

I went back to the start and ran "sudo apt-get update; sudo apt-get upgrade" then went back and updated Openstack packages. I now have keystone and glance working as per install docs for Juno.

Thanks for all the pointers everyone that helped.

2014-11-26 13:42:37 -0600 answered a question juno keystone driver persistence

Ok I found my fix. I was hitting ->

https://bugs.launchpad.net/openstack-...

Which meant that Ubuntu 14.04 wasn't actually pulling the latest packages so I wasn't actually using Juno (doh!)

I went back to the start and ran "sudo apt-get update; sudo apt-get upgrade" then went back and updated Openstack packages. I now have keystone and glance working as per install docs for Juno.

Thanks for all the pointers everyone that helped.

2014-11-26 09:29:00 -0600 commented question juno glance Invalid OpenStack Identity credentials

Here are some more detailed logs from glance-api. it looks as if glance is having trouble actually talking to keystone rather than actually failing to authenticate. Some SSL error?

http://paste.openstack.org/show/138892/

2014-11-26 05:36:11 -0600 commented question juno keystone driver persistence

Here you go. I managed to get the logs to console by running keystone-all

http://paste.openstack.org/show/138778/

2014-11-26 03:13:40 -0600 commented answer juno keystone driver persistence

Yes this setting does allow keystone to start however I am having problems later with glance auth failure (see https://ask.openstack.org/en/question... ) and i am not sure if this is related. Possibly not?

2014-11-26 02:34:23 -0600 commented question juno keystone driver persistence

cisco@kermit:~$ sudo egrep '^debug|^verbose' /etc/keystone/keystone.conf debug=True verbose=True cisco@kermit:~$ sudo egrep ^driver /etc/keystone/keystone.conf driver = keystone.token.persistence.backends.sql.Token

but the /var/log/keystone folder is still empty.

2014-11-26 01:43:00 -0600 received badge  Notable Question (source)
2014-11-25 17:03:44 -0600 received badge  Popular Question (source)
2014-11-25 16:51:56 -0600 received badge  Famous Question (source)
2014-11-25 16:38:12 -0600 received badge  Notable Question (source)
2014-11-25 16:30:47 -0600 received badge  Popular Question (source)
2014-11-25 00:57:03 -0600 asked a question juno keystone driver persistence

I am following the install docs for Openstack juno release on Ubuntu 14.04. When configuring keystone I am trying to set the line:

driver = keystone.token.persistence.backends.sql.Token

however with this directive keystone will not start correctly however it doesn't seem to be creating any log files either.

When i remove this line keystone starts ok however I however I seem to be having problems further down the line with glance (Unsure if these two are related yet).

Here is the keystone.conf

cisco@kermit:~$ sudo grep -v ^# /etc/keystone/keystone.conf | grep -v ^$
[DEFAULT]
admin_token=XXXXXXXXXXXXXXX
verbose=True
[assignment]
[auth]
[cache]
[catalog]
[credential]
[database]
connection = mysql://keystone:Cisco123@controller/keystone
[ec2]
[endpoint_filter]
[federation]
[identity]
[kvs]
[ldap]
[matchmaker_ring]
[memcache]
[oauth1]
[os_inherit]
[paste_deploy]
[policy]
[revoke]
[signing]
[ssl]
[stats]
[token]
provider = keystone.token.providers.uuid.Provider
[trust]
[extra_headers]
Distribution = Ubuntu
cisco@kermit:~$
2014-11-25 00:44:43 -0600 commented answer juno glance Invalid OpenStack Identity credentials

Thanks. I think I did that (see below).

2014-11-25 00:43:39 -0600 commented answer juno glance Invalid OpenStack Identity credentials

Thanks for the suggestion. I don't think this is my issue since I can do a keystone token-get, service-list from a remote machine using the glance credentials:

cisco@gonzo:~$ keystone service-list +----------------------------------+----------+----------+-------------------------+ |

2014-11-24 10:17:21 -0600 commented question juno glance Invalid OpenStack Identity credentials

I am trying but this is also not working with the same error ...

2014-11-24 08:06:42 -0600 commented question juno glance Invalid OpenStack Identity credentials

The configs are quite lengthy. Is there a specific portion I can post to help diagnose?

2014-11-24 02:02:11 -0600 answered a question juno glance Invalid OpenStack Identity credentials

Here is my glance-api authtoken part:

[keystone_authtoken] #signing_dir = /var/cache/glance/api #auth_uri = http://controller:5000/v2.0 identity_uri = http://controller:5000 #auth_host = 127.0.0.1 #auth_port = 35357 #auth_protocol = http admin_tenant_name = service admin_user = glance admin_password = Cisco123

Keystone connection details #connection = sqlite:////var/lib/keystone/keystone.db connection = mysql://keystone:Cisco123@controller/keystone

#provider=<none> provider = keystone.token.providers.uuid.Provider

Keystone Token persistence backend driver. (string value)

driver=keystone.token.backends.sql.Token #driver = keystone.token.persistence.backends.sql.Token

NOTE: Although the install docs use the .persistence. driver I could not get Keystone to start with driver so I reverted to the example/default. This enabled keystone to start.

2014-11-24 01:54:44 -0600 edited question juno glance Invalid OpenStack Identity credentials

I am following the install docs for Ubuntu Juno with Icehouse version of Openstack. Keystone installation and tests all worked fine however i am getting and auth error with glance when testing the image upload. Here are the logs and debug API call:

me@kermit:/tmp/images$ glance -dv image-create --name "cirros-0.3.3-x86_64" --file cirros-0.3.3-x86_64-disk.img   --disk-format qcow2 --container-format bare --is-public True --progress
curl -i -X POST -H 'x-image-meta-container_format: bare' -H 'Transfer-Encoding: chunked' -H 'User-Agent: python-glanceclient' -H 'x-image-meta-size: 13200896' -H 'x-image-meta-is_public: True' -H 'X-Auth-Token: 4618a45ef50640d9af385e3e554358b6' -H 'Content-Type: application/octet-stream' -H 'x-image-meta-disk_format: qcow2' -H 'x-image-meta-name: cirros-0.3.3-x86_64' -d '<glanceclient.common.progressbar.VerboseFileWrapper object at 0x7f8491614050>' http://controller:9292/v1/images
[=============================>] 100%

HTTP/1.1 401 Unauthorized
date: Sun, 23 Nov 2014 08:28:37 GMT
content-length: 253
content-type: text/plain; charset=UTF-8

401 Unauthorized

This server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your browser does not understand how to supply the credentials required.

Request returned failure status. Invalid OpenStack Identity credentials.

####

me@kermit:/tmp/images$ tail /var/log/glance/api.log
2014-11-23 08:28:33.861 13334 WARNING keystoneclient.middleware.auth_token [-] Retrying on HTTP connection exception: [Errno 1] _ssl.c:510: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
2014-11-23 08:28:34.363 13334 INFO urllib3.connectionpool [-] Starting new HTTPS connection (1): 127.0.0.1
2014-11-23 08:28:34.380 13334 WARNING keystoneclient.middleware.auth_token [-] Retrying on HTTP connection exception: [Errno 1] _ssl.c:510: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
2014-11-23 08:28:35.381 13334 INFO urllib3.connectionpool [-] Starting new HTTPS connection (1): 127.0.0.1
2014-11-23 08:28:35.394 13334 WARNING keystoneclient.middleware.auth_token [-] Retrying on HTTP connection exception: [Errno 1] _ssl.c:510: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
2014-11-23 08:28:37.397 13334 INFO urllib3.connectionpool [-] Starting new HTTPS connection (1): 127.0.0.1
2014-11-23 08:28:37.414 13334 ERROR keystoneclient.middleware.auth_token [-] HTTP connection exception: [Errno 1] _ssl.c:510: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
2014-11-23 08:28:37.414 13334 WARNING keystoneclient.middleware.auth_token [-] Authorization failed for token
2014-11-23 08:28:37.414 13334 INFO keystoneclient.middleware.auth_token [-] Invalid user token - deferring reject downstream
2014-11-23 08:28:37.445 13334 INFO glance.wsgi.server [-] 10.48.59.28 - - [23/Nov/2014 08:28:37] "POST /v1/images HTTP/1.1" 401 381 3.600561

Can anyone help?

With the glance OS_ env settings I can also get a token from keystone:

cisco@kermit:~$ env | grep OS_
OS_PASSWORD=Cisco123
OS_AUTH_URL=http://controller:35357/v2.0
OS_USERNAME=glance
OS_TENANT_NAME=service
cisco@kermit:~$ keystone token-get
+-----------+----------------------------------+
|  Property |              Value               |
+-----------+----------------------------------+
|  expires  |       2014-11-23T20:53:29Z       |
|     id    | 1f9043f2ec2d4ac08df1e8bf0b5c5aba |
| tenant_id | aa7182a859e54141983193b85f683712 |
|  user_id  | 2579ef7fab174753a136aec60fed0d61 |
+-----------+----------------------------------+

keystone.conf

cisco@kermit:~$ sudo grep -v ^# /etc/keystone/keystone.conf | grep -v ^$
[DEFAULT]
admin_token=XXXXXXXXXXX
verbose=True
[assignment]
[auth]
[cache]
[catalog]
[credential]
[database]
connection = mysql://keystone:Cisco123@controller/keystone
[ec2]
[endpoint_filter]
[federation]
[identity]
[kvs]
[ldap]
[matchmaker_ring]
[memcache ...
(more)
2014-11-24 01:45:30 -0600 commented answer juno glance Invalid OpenStack Identity credentials

Here you go :

[keystone_authtoken]
#signing_dir = /var/cache/glance/api
#auth_uri = http://controller:5000/v2.0
identity_uri = http://controller:5000
#auth_host = 127.0.0.1
#auth_port = 35357
#auth_protocol = http
admin_tenant_name = service
admin_user = glance
admin_password = mypass
2014-11-23 23:39:19 -0600 received badge  Nice Question (source)
2014-11-23 18:41:24 -0600 received badge  Student (source)