Ask Your Question

Maik's profile - activity

2020-03-26 01:44:38 -0500 received badge  Popular Question (source)
2020-03-26 01:44:38 -0500 received badge  Famous Question (source)
2020-03-26 01:44:38 -0500 received badge  Notable Question (source)
2019-05-08 08:51:21 -0500 asked a question nova-compute service seems down after upgrade controller from mitaka to newton

I upgrade my openstack controller node for nova-scheduler / api / conductor to newton and set the upgrade_levels to auto. After the upgrade i check the status für the nova-compute services on the compute nodes and they are shown as down.

After i check the logs for the controler nodes i found that the conductor seems to be able to communicate with the nova-compute service

compute-api1 nova-scheduler: 28031: INFO nova.scheduler.host_manager [req-45af962f-2816-4426-883f-0143b0bfc9a8 - - - - -] Successfully synced instances from host 'compute2'.

but also i see:

Seems service compute:compute2 is down is_up /usr/lib/python2.7/dist-packages/nova/servicegroup/drivers/mc.py:66

I test to upgrade one of the compute nodes to newton and it works. So it seems that the controller rpc version and compute node rpc version are not compatible. I try different solution to set the upgrade_levels on the newton controller an the compute node but nothing works.

Please can you give me some hints on how I can come out ahead.

Update: We have isolated the problem. The Issue depence on the servicegroup_driver. If we use mc as servicegroup driver it only works with newton controler -> newton node, if we use db as servicegroup driver it als works with newton controler -> mitaka node.

2018-09-03 10:46:39 -0500 received badge  Popular Question (source)
2018-08-14 07:49:47 -0500 asked a question nova scheduler in newton use deprecated parameters for rabbitmq

We currently deploy openstack newton. Rabbitmq connection are defined now throw the parameter transport_url and keystone password is now defined over password instead of admin_password.

Nova-api starts like it should.

If i start the nova scheduler i get the following log entry:

TRACE nova raise NoOptionError(option, section)#01226190: TRACE nova NoOptionError: No option 'admin_password' in section: 'keystone_authtoken'#01226190: TRACE nova

Also the same for the amqp connection.

It seams that nova-scheduler use the old parameters and not the new ones. Can it be that nova scheduler do not recognize the option "password" in newton?

We use nova-scheduler 2:14.1.0-0ubuntu1~cloud0.

2017-02-20 07:51:04 -0500 asked a question Lose ssh connection to new created vm after a while but can reconnect

After i create a new vm with a floating ip i connect over ssh to this vm. After few minutes i lost the ssh connection but i can reconnect to the vm an never lost the connection again.

  • create VM
  • attach Floating IP
  • ssh over floating IP to the VM
  • run command on the vm: i=1; while [[ "$i" -le "600" ]]; do sleep 1; \ echo "$(date +'%T') $i / 600"; i=$((i + 1)); done
  • lose connection after few minutes
  • ssh over floating IP again

Same does not appears if i ssh from another vm over the private ip.

Any Help?

2017-02-17 05:00:02 -0500 received badge  Notable Question (source)
2017-01-05 08:05:43 -0500 received badge  Famous Question (source)
2017-01-05 08:05:28 -0500 received badge  Notable Question (source)
2016-12-02 07:59:09 -0500 received badge  Notable Question (source)
2016-12-02 07:59:09 -0500 received badge  Famous Question (source)
2016-10-27 13:21:25 -0500 received badge  Popular Question (source)
2016-10-04 01:27:40 -0500 received badge  Notable Question (source)
2016-10-04 01:27:10 -0500 received badge  Popular Question (source)
2016-08-09 05:15:42 -0500 asked a question How can i run diskimage-builder in lxc

I try to run diskimage-builder in lxc and had some trouble:

List of Errors:

mount: cannot mount block device /tmp/dib_build.t9ychzEn/hooks read-only

I have tried several appamor configurations - not solved completely  
At the end i add -l to the mount command in the scripts

vim /usr/local/share/diskimage-builder/lib/img-functions 85
vim /usr/local/share/diskimage-builder/lib/common-functions 134

/usr/local/bin/disk-image-create:main:410: sudo losetup --show -f /tmp/dib_image.YcesvNzx/image.raw

modified lxc config
...
lxc.cgroup.devices.allow = c 10:137 rwm # loop-control
lxc.cgroup.devices.allow = b 7:* rwm    # loop*
...

sudo: parted: command not found

apt-get install parted

and so on

is there some manual how i can run diskimage-builder in a lxc?

2016-08-02 03:48:04 -0500 received badge  Popular Question (source)
2016-08-02 02:45:57 -0500 commented answer Magnum Swarm - master_lb_enabled

If have checked the code by moving the environments files - i see that if i moved the files the errors changed to something like "Can not access files", so python schould used the right code

2016-08-02 02:38:07 -0500 commented answer Magnum Swarm - master_lb_enabled

ENV Files are on the right place

root@magnum1:/opt/magnum-master/magnum/drivers/common/templates/environments# ll
  no_master_lb.yaml
  with_master_lb.yaml
2016-08-02 02:34:42 -0500 commented answer Magnum Swarm - master_lb_enabled

I used the newest master branch Revision: d92c76f6d1790771ee5da4c9d1c0a3f718acde2d, 2016.07.31 20:54:58

Patchs included in my installation: https://review.openstack.org/#/c/338535/ https://review.openstack.org/#/c/346151/

2016-08-02 02:29:58 -0500 received badge  Supporter (source)
2016-08-02 02:12:46 -0500 commented question Magnum Swarm - master_lb_enabled

Add some logs

2016-08-01 09:57:50 -0500 asked a question Magnum Swarm - master_lb_enabled

magnum bay-create --name swarmbay --baymodel swarmbaymodel --node-count 1 fails with

InvalidParameterValue: ERROR: Unknown resource Type : Magnum::Optional::Neutron::Pool::HealthMonitor

How can i avoid this error?

API Log stack trace

45817: DEBUG wsme.api [req-58500adb-b62b-4f2a-8e73-f1351d5561cd test2 test2 - - -] Client-side error: ERROR: Unknown resource Type : Magnum::Optional::Neutron::Pool::HealthMonitor
Traceback (most recent call last):

  File "/var/lib/magnum/env/local/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 133, in _process_incoming
    res = self.dispatcher.dispatch(message)

  File "/var/lib/magnum/env/local/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 150, in dispatch
    return self._do_dispatch(endpoint, method, ctxt, args)

  File "/var/lib/magnum/env/local/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 121, in _do_dispatch
    result = func(ctxt, **new_args)

  File "/var/lib/magnum/env/local/lib/python2.7/site-packages/magnum/conductor/handlers/bay_conductor.py", line 167, in bay_create
    raise e

InvalidParameterValue: ERROR: Unknown resource Type : Magnum::Optional::Neutron::Pool::HealthMonitor
 format_exception /var/lib/magnum/env/local/lib/python2.7/site-packages/wsme/api.py:221

Conductor shows the same Lines

2016-07-18 05:49:10 -0500 received badge  Popular Question (source)
2016-07-18 05:16:31 -0500 received badge  Student (source)
2016-07-18 05:10:05 -0500 received badge  Famous Question (source)
2016-07-18 05:09:24 -0500 received badge  Popular Question (source)
2016-05-03 07:51:32 -0500 asked a question magnum swarm - docker cli EOF

I use my local docker cli to run an docker images on the remote swarm cluster (created by magnum). If i use docker ... run ... i get an error after a while but the container is running.

docker -H tcp://xxx.xxx.xxx.xxx:2376 --tlsverify --tlscacert ca.crt --tlskey client.key --tlscert client.crt run nginx

An error occurred trying to connect: Post https://xxx.xxx.xxx.xxx:2376/v1.21/containers/c09fe0553ffad7124a00d4cc2ce4aa32a61c7c86a958e662cb27f0f12e1b124c/wait: EOF

Info:

# docker ... version

Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 13:12:04 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      swarm/1.0.0
 API version:  1.21
 Go version:   go1.5.1
 Git commit:   087e245
 Built:        
 OS/Arch:      linux/amd64
2016-05-03 07:41:36 -0500 asked a question magnum swarm - EOF occurred in violation of protocol

I have an running swarm 1.0.0 cluster with one master and one node and get the following error in magnum-conductor.log. How can i avoid this error?

30059: WARNING magnum.service.periodic [-] Skip pulling data from bay 0cd0e575-7ac2-4aa2-8c60-4691b1aacd18 due to error: [Errno 8] _ssl.c:510: EOF occurred in violation of protocol
30059: TRACE magnum.service.periodic Traceback (most recent call last):
30059: TRACE magnum.service.periodic   File "/opt/magnum/magnum/service/periodic.py", line 160, in _send_bay_metrics
30059: TRACE magnum.service.periodic     monitor.pull_data()
30059: TRACE magnum.service.periodic   File "/opt/magnum/magnum/conductor/swarm_monitor.py", line 45, in pull_data
30059: TRACE magnum.service.periodic     system_info = docker.info()
30059: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/docker/api/daemon.py", line 33, in info
30059: TRACE magnum.service.periodic     return self._result(self._get(self._url("/info")), True)
30059: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/docker/utils/decorators.py", line 47, in inner
30059: TRACE magnum.service.periodic     return f(self, *args, **kwargs)
30059: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/docker/client.py", line 120, in _get
30059: TRACE magnum.service.periodic     return self.get(url, **self._set_request_timeout(kwargs))
30059: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 480, in get
30059: TRACE magnum.service.periodic     return self.request('GET', url, **kwargs)
30059: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 468, in request
30059: TRACE magnum.service.periodic     resp = self.send(prep, **send_kwargs)
30059: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 576, in send
30059: TRACE magnum.service.periodic     r = adapter.send(request, **kwargs)
30059: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/requests/adapters.py", line 447, in send
30059: TRACE magnum.service.periodic     raise SSLError(e, request=request)
30059: TRACE magnum.service.periodic SSLError: [Errno 8] _ssl.c:510: EOF occurred in violation of protocol
30059: TRACE magnum.service.periodic

Magnum version:

# magnum --version
2.0.1
# magnum-api --version
2.0.1.dev2
# magnum-conductor --version
2.0.1.dev2

The baymodel is the following:

# magnum baymodel-show swarmbaymodel
+---------------------+--------------------------------------+
| Property            | Value                                |
+---------------------+--------------------------------------+
| http_proxy          | None                                 |
| updated_at          | None                                 |
| master_flavor_id    | m1.medium                            |
| uuid                | 9fc31674-db1f-49ae-8966-cb28d40c9874 |
| no_proxy            | None                                 |
| https_proxy         | None                                 |
| tls_disabled        | False                                |
| keypair_id          | testkey                              |
| public              | False                                |
| labels              | {}                                   |
| docker_volume_size  | None                                 |
| server_type         | vm                                   |
| external_network_id | public                               |
| cluster_distro      | fedora-atomic                        |
| image_id            | fedora-23-atomic-7                   |
| volume_driver       | None                                 |
| registry_enabled    | False                                |
| apiserver_port      | None                                 |
| name                | swarmbaymodel                        |
| created_at          | 2016-05-03T11:57:50+00:00            |
| network_driver      | docker                               |
| fixed_network       | None                                 |
| coe                 | swarm                                |
| flavor_id           | m1.small                             |
| dns_nameserver      | xxx.xxx.xxx.xxx                         |
+---------------------+--------------------------------------+

The bay is the following:

# magnum bay-show swarmbay
+--------------------+------------------------------------------------------------+
| Property           | Value                                                      |
+--------------------+------------------------------------------------------------+
| status             | CREATE_COMPLETE                                            |
| uuid               | 0cd0e575-7ac2-4aa2-8c60-4691b1aacd18                       |
| stack_id           | 41f6577b-e7c5-41c2-8dd0-a37505684348                       |
| status_reason      | Stack CREATE completed successfully                        |
| created_at         | 2016-05-03T11:58:10+00:00                                  |
| updated_at         | 2016-05-03T12:01:07+00:00                                  |
| bay_create_timeout | 0                                                          |
| api_address        | https://xxx.xxx.xxx.xxx:2376                                 |
| baymodel_id        | 9fc31674-db1f-49ae-8966-cb28d40c9874                       |
| master_addresses   | ['xxx.xxx.xxx.xxx']                                          |
| node_count         | 1                                                          |
| node_addresses     | ['xxx.xxx.xxx.xxx']                                          |
| master_count       | 1                                                          |
| discovery_url      | https://discovery.etcd.io/xxxxxxxx |
| name               | swarmbay                                                   |
+--------------------+------------------------------------------------------------+

The docker ... (more)

2016-05-03 07:41:15 -0500 asked a question magnum EOF occurred in violation of protocol

I have an running swarm 1.0.0 cluster with one master and one node and get the following error in magnum-conductor.log. How can i avoid this error?

30059: WARNING magnum.service.periodic [-] Skip pulling data from bay 0cd0e575-7ac2-4aa2-8c60-4691b1aacd18 due to error: [Errno 8] _ssl.c:510: EOF occurred in violation of protocol
30059: TRACE magnum.service.periodic Traceback (most recent call last):
30059: TRACE magnum.service.periodic   File "/opt/magnum/magnum/service/periodic.py", line 160, in _send_bay_metrics
30059: TRACE magnum.service.periodic     monitor.pull_data()
30059: TRACE magnum.service.periodic   File "/opt/magnum/magnum/conductor/swarm_monitor.py", line 45, in pull_data
30059: TRACE magnum.service.periodic     system_info = docker.info()
30059: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/docker/api/daemon.py", line 33, in info
30059: TRACE magnum.service.periodic     return self._result(self._get(self._url("/info")), True)
30059: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/docker/utils/decorators.py", line 47, in inner
30059: TRACE magnum.service.periodic     return f(self, *args, **kwargs)
30059: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/docker/client.py", line 120, in _get
30059: TRACE magnum.service.periodic     return self.get(url, **self._set_request_timeout(kwargs))
30059: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 480, in get
30059: TRACE magnum.service.periodic     return self.request('GET', url, **kwargs)
30059: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 468, in request
30059: TRACE magnum.service.periodic     resp = self.send(prep, **send_kwargs)
30059: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/requests/sessions.py", line 576, in send
30059: TRACE magnum.service.periodic     r = adapter.send(request, **kwargs)
30059: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/requests/adapters.py", line 447, in send
30059: TRACE magnum.service.periodic     raise SSLError(e, request=request)
30059: TRACE magnum.service.periodic SSLError: [Errno 8] _ssl.c:510: EOF occurred in violation of protocol
30059: TRACE magnum.service.periodic

Magnum version:

# magnum --version
2.0.1
# magnum-api --version
2.0.1.dev2
# magnum-conductor --version
2.0.1.dev2

The baymodel is the following:

# magnum baymodel-show swarmbaymodel
+---------------------+--------------------------------------+
| Property            | Value                                |
+---------------------+--------------------------------------+
| http_proxy          | None                                 |
| updated_at          | None                                 |
| master_flavor_id    | m1.medium                            |
| uuid                | 9fc31674-db1f-49ae-8966-cb28d40c9874 |
| no_proxy            | None                                 |
| https_proxy         | None                                 |
| tls_disabled        | False                                |
| keypair_id          | testkey                              |
| public              | False                                |
| labels              | {}                                   |
| docker_volume_size  | None                                 |
| server_type         | vm                                   |
| external_network_id | public                               |
| cluster_distro      | fedora-atomic                        |
| image_id            | fedora-23-atomic-7                   |
| volume_driver       | None                                 |
| registry_enabled    | False                                |
| apiserver_port      | None                                 |
| name                | swarmbaymodel                        |
| created_at          | 2016-05-03T11:57:50+00:00            |
| network_driver      | docker                               |
| fixed_network       | None                                 |
| coe                 | swarm                                |
| flavor_id           | m1.small                             |
| dns_nameserver      | xxx.xxx.xxx.xxx                         |
+---------------------+--------------------------------------+

The bay is the following:

# magnum bay-show swarmbay
+--------------------+------------------------------------------------------------+
| Property           | Value                                                      |
+--------------------+------------------------------------------------------------+
| status             | CREATE_COMPLETE                                            |
| uuid               | 0cd0e575-7ac2-4aa2-8c60-4691b1aacd18                       |
| stack_id           | 41f6577b-e7c5-41c2-8dd0-a37505684348                       |
| status_reason      | Stack CREATE completed successfully                        |
| created_at         | 2016-05-03T11:58:10+00:00                                  |
| updated_at         | 2016-05-03T12:01:07+00:00                                  |
| bay_create_timeout | 0                                                          |
| api_address        | https://xxx.xxx.xxx.xxx:2376                                 |
| baymodel_id        | 9fc31674-db1f-49ae-8966-cb28d40c9874                       |
| master_addresses   | ['xxx.xxx.xxx.xxx']                                          |
| node_count         | 1                                                          |
| node_addresses     | ['xxx.xxx.xxx.xxx']                                          |
| master_count       | 1                                                          |
| discovery_url      | https://discovery.etcd.io/xxxxxxxx |
| name               | swarmbay                                                   |
+--------------------+------------------------------------------------------------+

The docker ... (more)

2016-04-27 09:07:37 -0500 received badge  Notable Question (source)
2016-04-20 05:47:27 -0500 received badge  Popular Question (source)
2016-04-19 05:49:01 -0500 commented question magnum bay create timeout - You are not authorized to use global_index

Thank for help. But it works now. At the moment i do not exactly know why but i think it was a misconfiguration of policy.json because i have to controller nodes and one has no "stacks:global_index": "rule:admin"

Now i have a new problem but i will create a new thread for this.

2016-04-19 01:51:27 -0500 received badge  Enthusiast
2016-04-18 09:15:39 -0500 received badge  Editor (source)
2016-04-18 09:13:22 -0500 asked a question magnum bay create timeout - You are not authorized to use global_index

I run "magnum bay-create --name swarmbay --baymodel swarmbaymodel --node-count 1" as user (not admin) and get a timeout. I see only a warning in /var/lib/magnum/magnum-conductor.log

use global_index.\n", "type": "Forbidden"}, "title": "Forbidden"}
 log_http_response /usr/local/lib/python2.7/dist-packages/heatclient/common/http.py:155
15824: WARNING magnum.service.periodic [req-4cbf1448-a4f5-46f0-8eb5-053fa3ee045a - - - - -] Ignore error [ERROR: You are not authorized to use global_index.] when syncing up bay status.
15824: TRACE magnum.service.periodic Traceback (most recent call last):
15824: TRACE magnum.service.periodic   File "/opt/magnum/magnum/service/periodic.py", line 85, in sync_bay_status
15824: TRACE magnum.service.periodic     sid_to_stack_mapping = {s.id: s for s in stacks}
15824: TRACE magnum.service.periodic   File "/opt/magnum/magnum/service/periodic.py", line 85, in <dictcomp>
15824: TRACE magnum.service.periodic     sid_to_stack_mapping = {s.id: s for s in stacks}
15824: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/heatclient/v1/stacks.py", line 127, in paginate
15824: TRACE magnum.service.periodic     stacks = self._list(url, 'stacks')
15824: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/heatclient/openstack/common/apiclient/base.py", line 135, in _list
15824: TRACE magnum.service.periodic     body = self.client.get(url).json()
15824: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/heatclient/common/http.py", line 291, in get
15824: TRACE magnum.service.periodic     return self.client_request("GET", url, **kwargs)
15824: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/heatclient/common/http.py", line 284, in client_request
15824: TRACE magnum.service.periodic     resp, body = self.json_request(method, url, **kwargs)
15824: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/heatclient/common/http.py", line 273, in json_request
15824: TRACE magnum.service.periodic     resp = self._http_request(url, method, **kwargs)
15824: TRACE magnum.service.periodic   File "/usr/local/lib/python2.7/dist-packages/heatclient/common/http.py", line 228, in _http_request
15824: TRACE magnum.service.periodic     raise exc.from_response(resp)
15824: TRACE magnum.service.periodic HTTPForbidden: ERROR: You are not authorized to use global_index.
15824: TRACE magnum.service.periodic

Version

magnum-api --version: 2.0.1.dev1

magnum-conductor --version: 2.0.1.dev1

magnum --version: 2.0.1

trust

domain: magnum

domain_admin: magnum_admin <role> admin

Baymodel

+---------------------+--------------------------------------+
| Property            | Value                                |
+---------------------+--------------------------------------+
| http_proxy          | None                                 |
| updated_at          | None                                 |
| master_flavor_id    | m1.medium                            |
| uuid                | 418fd0b3-9893-498a-9ec1-04ab41a69e1e |
| no_proxy            | None                                 |
| https_proxy         | None                                 |
| tls_disabled        | True                                 |
| keypair_id          | testkey                              |
| public              | False                                |
| labels              | {}                                   |
| docker_volume_size  | 5                                    |
| server_type         | vm                                   |
| external_network_id | public                               |
| cluster_distro      | fedora-atomic                        |
| image_id            | fedora-23-atomic-7                   |
| volume_driver       | None                                 |
| registry_enabled    | False                                |
| apiserver_port      | None                                 |
| name                | swarmbaymodel                        |
| created_at          | 2016-04-18T12:53:08+00:00            |
| network_driver      | docker                               |
| fixed_network       | None                                 |
| coe                 | swarm                                |
| flavor_id           | m1.small                             |
| dns_nameserver      | 134.76.10.46                         |
+---------------------+--------------------------------------+

/etc/heat/policy.json

"stacks:generate_template": "rule:deny_stack_user",
"stacks:global_index": "rule:admin",
"stacks:index": "rule:deny_stack_user",

How can i avoid "You are not authorized to use global_index." ?

How can i avoid the timeout?

2016-04-08 04:39:33 -0500 received badge  Famous Question (source)