Ask Your Question

ajithpathiyil's profile - activity

2019-04-17 05:29:38 -0500 commented question TASK [galera_server : Check node status]

Thanks Bernd!

I am using ubuntu1604LTS and openstack-ansible. This error is still open, not sure how to fix it.

This error comes when running "openstack-ansible setup-infrastructure.yml" command

2019-04-09 09:06:55 -0500 asked a question TASK [galera_server : Check node status]

Hi,

Iam trying to run the setup-infrastructure using openstack-ansible and it fails to build and check the galera cluster

TASK [galera_server : Check node status] .. .. This section fails with below error (111 \"Connection refused\")

Any help in this regard would be great

Regards, Ajith

2019-04-03 09:52:22 -0500 received badge  Notable Question (source)
2019-04-03 09:52:22 -0500 received badge  Popular Question (source)
2019-01-29 07:22:16 -0500 asked a question openstack ansible- Execution of setup-openstack.yml fails

TASK [os_keystone : Wait for services to be up] ***************************** task path: /etc/ansible/roles/os_keystone/tasks/keystone_service_update.yml:31 <infra2_keystone_container-dbb53b56> Task is delegated to localhost. <infra2_keystone_container-dbb53b56> The "physical_host" variable of "infra2" has been found to have a corresponding host entry in inventory. <infra2_keystone_container-dbb53b56> The "physical_host" variable of "infra2" terminates at "172.29.236.12" using the host variable "ansible_host". <infra2_keystone_container-dbb53b56> Because this is a task using "delegate_to" pipelining has been disabled. but will be restored upon completion of this task. Using module file /opt/ansible-runtime/local/lib/python2.7/site-packages/ansible/modules/net_tools/basics/uri.py <localhost> ESTABLISH LOCAL CONNECTION FOR USER: root <localhost> EXEC /bin/sh -c 'echo ~root && sleep 0' <localhost> EXEC /bin/sh -c '( umask 77 && mkdir -p "echo /root/.ansible/tmp/ansible-tmp-1548697858.92-229119174354010" && echo ansible-tmp-1548697858.92-229119174354010="echo /root/.ansible/tmp/ansible-tmp-1548697858.92-229119174354010" ) && sleep 0' <localhost> PUT /root/.ansible/tmp/ansible-local-11534FoBgRO/tmpOSvaRo TO /root/.ansible/tmp/ansible-tmp-1548697858.92-229119174354010/uri.py <localhost> EXEC /bin/sh -c 'chmod u+x /root/.ansible/tmp/ansible-tmp-1548697858.92-229119174354010/ /root/.ansible/tmp/ansible-tmp-1548697858.92-229119174354010/uri.py && sleep 0' <localhost> EXEC /bin/sh -c '/opt/ansible-runtime/bin/python2 /root/.ansible/tmp/ansible-tmp-1548697858.92-229119174354010/uri.py && sleep 0' <localhost> EXEC /bin/sh -c 'rm -f -r /root/.ansible/tmp/ansible-tmp-1548697858.92-229119174354010/ > /dev/null 2>&1 && sleep 0' feature will be removed in version 2.9. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg. FAILED - RETRYING: Wait for services to be up (120 retries left).Result was: { "attempts": 1, "changed": false, "content": "", "invocation": { "module_args": { "attributes": null, "backup": null, "body": null, "body_format": "raw", "client_cert": null, "client_key": null, "content": null, "creates": null, "delimiter": null, "dest": null, "directory_mode": null, "follow": false, "follow_redirects": "safe", "force": false, "force_basic_auth": false, "group": null, "headers": {}, "http_agent": "ansible-httpget", "method": "HEAD", "mode": null, "owner": null, "regexp": null, "remote_src": null, "removes": null, "return_content": false, "selevel": null, "serole": null, "setype": null, "seuser": null, "src": null, "status_code": [ "300" ], "timeout": 30, "unsafe_writes": null, "url": "http://172.29.236.11:5000", "url_password": null, "url_username": null, "use_proxy": true, "validate_certs": true } }, "msg": "Status code was -1 and not [300]: An unknown error occurred: ''", "redirected": false, "retries": 121, "status": -1, "url": "http://172.29.236.11:5000" } Using module file /opt/ansible-runtime/local/lib/python2.7/site-packages/ansible/modules/net_tools/basics/uri.py <localhost> EXEC /bin/sh -c 'echo ~root && sleep 0' <localhost> EXEC /bin/sh -c '( umask 77 && mkdir -p "echo /root/.ansible/tmp/ansible-tmp-1548697864.43-28759509910718" && echo ansible-tmp-1548697864.43-28759509910718="echo /root/.ansible/tmp/ansible-tmp-1548697864.43-28759509910718" ) && sleep 0' <localhost> PUT /root/.ansible/tmp/ansible-local-11534FoBgRO/tmp7eiPG0 TO /root/.ansible/tmp/ansible-tmp-1548697864.43-28759509910718/uri.py <localhost> EXEC /bin/sh -c 'chmod u+x /root/.ansible/tmp/ansible-tmp-1548697864.43-28759509910718/ /root/.ansible/tmp/ansible-tmp-1548697864.43-28759509910718/uri.py && sleep 0' <localhost> EXEC /bin/sh -c '/opt/ansible-runtime/bin/python2 /root/.ansible/tmp/ansible-tmp-1548697864.43-28759509910718/uri.py && sleep 0' <localhost> EXEC /bin/sh -c 'rm -f -r /root/.ansible/tmp/ansible-tmp-1548697864.43-28759509910718/ > /dev/null 2>&1 && sleep 0' FAILED - RETRYING: Wait for services to be up (119 retries left).Result was: { "attempts": 2, "changed": false, "content": "", "invocation ... (more)

2018-11-13 22:26:44 -0500 received badge  Famous Question (source)
2018-10-10 14:48:43 -0500 received badge  Famous Question (source)
2018-06-28 13:01:50 -0500 answered a question cannot start sahara services

Hi Friend,

I am also struck on the same error, please help me if you have already fixed this error.

2018-06-27 07:48:59 -0500 received badge  Notable Question (source)
2018-06-25 04:52:56 -0500 received badge  Popular Question (source)
2018-06-23 07:40:50 -0500 answered a question Sahara Cluster Fails - Failed to create trust

Hi Friend,

Hi Friend,

many thanks for your time taken to help, I already had the [Keystone_authtoken] block same as yours, but to test, I used your Sahara.conf as it is (changed the values) and tried to launch a vanilla-271 cluster, it still fails with the same error as below.

Error during operating on cluster (reason: Failed to create trust Error ID: 87a0562d-aea5-4f04-a977-5afa1edfcbbd)

I had a doubt if my heat-engine is working, I tested heat-engine with a sample heat template it also worked like charm.

Regards, Ajith

2018-06-21 08:19:38 -0500 asked a question Sahara Cluster Launch fails

Sahara cluster launch fails on validation with below error.

AttributeError: 'Client' object has no ttribute 'networks'

2018-06-21 05:44:12 -0500 asked a question Sahara Cluster Fails - Failed to create trust

Hi,

Below is the error I see in the Sahara-engine logs, when trying to launch a Sahara-vanilla-271 cluster

Openstack version - Liberty Sahara installed in virtual environment. Appreciate if anybody else has come across this issue.

root@controller:~# /root/sahara-venv/bin/python sahara-venv/bin/sahara-engine --config-file sahara-venv/etc/sahara.conf 2018-06-21 15:29:55.883 28787 INFO sahara.utils.rpc [-] Notifications disabled 2018-06-21 15:29:56.584 28787 INFO sahara.plugins.base [-] Plugin hdp loaded sahara.plugins.hdp.ambariplugin:AmbariPlugin 2018-06-21 15:29:56.584 28787 INFO sahara.plugins.base [-] Plugin vanilla loaded sahara.plugins.vanilla.plugin:VanillaProvider 2018-06-21 15:29:56.585 28787 INFO sahara.plugins.base [-] Plugin cdh loaded sahara.plugins.cdh.plugin:CDHPluginProvider 2018-06-21 15:29:56.585 28787 INFO sahara.plugins.base [-] Plugin spark loaded sahara.plugins.spark.plugin:SparkProvider 2018-06-21 15:29:56.585 28787 INFO sahara.main [-] Sahara engine started 2018-06-21 15:29:56.585 28787 INFO keystonemiddleware.auth_token [-] Starting Keystone auth_token middleware 2018-06-21 15:29:56.587 28787 WARNING keystonemiddleware.auth_token [-] Use of the auth_admin_prefix, auth_host, auth_port, auth_protocol, identity_uri, admin_token, admin_user, admin_password, and admin_tenant_name configuration options was deprecated in the Mitaka release in favor of an auth_plugin and its related options. This class may be removed in a future release. 2018-06-21 15:29:56.589 28787 INFO keystonemiddleware.auth_token [-] Using /tmp/keystone-signing-KJRpiI as cache directory for signing certificate 2018-06-21 15:29:56.589 28787 INFO oslo_service.periodic_task [-] Skipping periodic task check_for_zombie_proxy_users because its interval is negative 2018-06-21 15:29:56.595 28787 INFO sahara.main [-] Driver heat successfully loaded 2018-06-21 15:29:56.598 28787 INFO sahara.main [-] Driver ssh successfully loaded 2018-06-21 15:30:26.104 28787 WARNING sahara.context [-] Arguments dropped when creating context: {u'project_name': u'service', u'user_name': u'sahara'} 2018-06-21 15:30:26.679 28787 WARNING oslo_messaging.server [-] Possible hang: wait is waiting for stop to complete 2018-06-21 15:30:27.387 28787 ERROR sahara.service.trusts [req-0bd98b81-b083-440a-a846-aed173eb556c 71b95d25439743169779a32ea4e17ee2 8ca3e3ea84a34bf99301676cec07e502 - - -] [instance: none, cluster: b4c9bc70-b6ae-451a-92f7-54a6da6b67f9] Unable to create trust (reason: The request you have made requires authentication. (HTTP 401) (Request-ID: req-167c483f-4d38-40f7-879b-748184ad62a5)) 2018-06-21 15:30:27.458 28787 ERROR sahara.service.ops [req-0bd98b81-b083-440a-a846-aed173eb556c 71b95d25439743169779a32ea4e17ee2 8ca3e3ea84a34bf99301676cec07e502 - - -] [instance: none, cluster: b4c9bc70-b6ae-451a-92f7-54a6da6b67f9] Error during operating on cluster (reason: Failed to create trust Error ID: 87a0562d-aea5-4f04-a977-5afa1edfcbbd) 2018-06-21 15:30:27.458 28787 ERROR sahara.service.ops [instance: none, cluster: b4c9bc70-b6ae-451a-92f7-54a6da6b67f9] Traceback (most recent call last): 2018-06-21 15:30:27.458 28787 ERROR sahara.service.ops [instance: none, cluster: b4c9bc70-b6ae-451a-92f7-54a6da6b67f9] File "/root/sahara-venv/local/lib/python2.7/site-packages/sahara/service/ops.py", line 164, in wrapper 2018-06-21 15:30:27.458 28787 ERROR sahara.service.ops [instance: none, cluster: b4c9bc70-b6ae-451a-92f7-54a6da6b67f9] f(cluster_id, args, *kwds) 2018-06-21 15:30:27.458 28787 ERROR sahara.service.ops [instance: none, cluster: b4c9bc70-b6ae-451a-92f7-54a6da6b67f9] File "/root/sahara-venv/local/lib/python2.7/site-packages/sahara/service/ops.py", line 247, in _provision_cluster 2018-06-21 15:30:27.458 28787 ERROR sahara.service.ops [instance: none, cluster: b4c9bc70-b6ae-451a-92f7-54a6da6b67f9] ctx, cluster, plugin = _prepare_provisioning(cluster_id) 2018-06-21 15:30:27.458 28787 ERROR sahara.service.ops [instance: none, cluster ... (more)

2017-04-21 00:50:32 -0500 received badge  Famous Question (source)
2017-01-11 17:38:37 -0500 received badge  Famous Question (source)
2016-11-07 00:59:50 -0500 received badge  Notable Question (source)
2016-09-28 07:08:58 -0500 commented answer New compute node addition - VMs not launching with new compute node

Hi Ajay, I have the new compute added to a newly created host aggregate and within a new availability zone. Error in /var/log/nova/nova-compute.log, Below is the error NovaException: Failed to add bridge: sudo:no tty present and no askpass program specified All nodes are able to ping eachother

2016-09-26 13:47:19 -0500 received badge  Famous Question (source)
2016-09-26 12:21:49 -0500 received badge  Notable Question (source)
2016-09-24 06:14:44 -0500 received badge  Popular Question (source)
2016-09-23 08:35:21 -0500 received badge  Famous Question (source)
2016-09-23 07:21:51 -0500 asked a question New compute node addition - VMs not launching with new compute node

Hi All,

My new compute node addition is successful and also able to see the new compute node through my dashboard (All "Compute services" and related "Network Agents" for all the compute nodes (Existing and new one added) are enabled and up.

But all my instances launch are hitting the existing compute node and when reaching its threshold, new VMs are not being launched in the new compute node, Instead it tries to launch with existing compute node and it fails with "No valid hosts" generic error.

My existing compute node & new node versions

Release = Liberty nova --version = 2.30.1 nova-compute = 12.0.0 neutron-version = 3.1.0 neutron-linuxbridge-agent = 7.0.0

I am sure, I am missing something and have the doubt with below dbsync command (In the below URL), But since it is the db command, I am releuctant to fire it without confirmation.

su -s /bin/sh -c "nova-manage db sync" nova

Refer:- http://docs.openstack.org/liberty/ins...

Any help in this regard should be helpful.

2016-09-13 04:23:36 -0500 received badge  Notable Question (source)
2016-07-01 04:47:44 -0500 received badge  Notable Question (source)
2016-06-24 00:14:56 -0500 commented answer How to upgrade or downgrade nova-compute in liberty

Thanks for the reply.

I did a manual downgrade of nova-compute to 2:12.0.1 version as I do not have plans to upgrade.

However, your reply will be helpful while upgrade plans..many thanks

2016-06-24 00:14:56 -0500 commented answer How to upgrade or downgrade nova-compute in liberty

Thanks for the reply.

I did a manual downgrade of nova-compute to 2:12.0.1 version as I do not have plans to upgrade.

However, your reply will be helpful while upgrade plans..many thanks

2016-06-24 00:12:43 -0500 received badge  Popular Question (source)
2016-06-22 04:52:57 -0500 asked a question How to upgrade or downgrade nova-compute in liberty

Hi Team,

I am trying to add a new compute node to my existing setup on Ubuntu LTS 14.04

I have encountered the same problem as in (https://ask.openstack.org/en/question...),

My Controller node Nova is (2:12.0.0) Existing compute nodes (2:12.0.1) -> This version successfully communicate's with controller My new compute node is (2:12.0.3) -> This version fails to communicate with controller

Any help in downgrading my new compute node's version to same as controller's or the existing compute nodes will be appreciated.

2016-06-22 04:47:29 -0500 commented answer compute node down, db error

I have encountered the same problem, My Controller Nova is 2:12.0.0 & My new compute node is 2:12.0.3 ...I need your help in downgrading my new compute node's version to same as controller's or the other existing compute nodes (2:12.0.1)

2016-06-16 05:27:30 -0500 received badge  Popular Question (source)
2016-05-31 14:21:27 -0500 received badge  Notable Question (source)
2016-05-28 04:27:12 -0500 received badge  Popular Question (source)
2016-05-25 04:57:09 -0500 received badge  Notable Question (source)
2016-05-25 04:57:09 -0500 received badge  Famous Question (source)
2016-05-25 04:57:09 -0500 received badge  Popular Question (source)
2016-05-18 01:28:51 -0500 answered a question Unable to delete loadbalancer

Hi team,

I was able to find the workaround for this, My Orphaned loadbalancer ports that was not getting deleted was because of the entries in the neutron tables

1) lbaas_loadbalancers 2) lbaas_loadbalancer_statistics

Removed 3 orphaned entried from lbaas_loadbalancer_statistics (Had foreign key references) then, followed by removal of 3 entries from lbaas_loadbalancers.

It worked like charm, All 3 of my public ip's held by these orphaned ports were released to the public subnet again

2016-05-16 11:58:01 -0500 asked a question Unable to delete loadbalancer

Hi Team,

I am unable to delete a load balancer that seems to have struck in PENDING_CREATE status.

Error: Failed to delete port: Request Failed: internal server error while processing your request.

Is anybody having a similar issue.

My environment is on Liberty release, LBaaS V2

2016-05-11 05:39:44 -0500 received badge  Famous Question (source)
2016-04-01 01:27:59 -0500 received badge  Enthusiast
2016-03-30 08:49:44 -0500 received badge  Popular Question (source)
2016-03-30 01:12:29 -0500 asked a question Openstack APIs testing using REST Client - 403 Forbidden Response

Hi All,

I am testing the Openstack API's with a REST client (Firefox plugin), My authentication seems to be fine with the below POST, I also receive a response header with X-Subject-Token & I readily have X-Auth-Token from my

/etc/keystone/keystone.conf file.

My further API calls end-up in 403 Forbidden errors (Which means successful authentication but not privileged to perform the action), Where do I check if I have necessary privileges to perform the actions.

Note:- I am using X-Auth-Token value from /etc/keystone/keystone.conf in my headers (i.e. all my calls are with admin token)

Successful Keystone Authentication - API call

Method: POST
*Request Headers:
Content-type : application/json
*Request Body:
{
    "auth": {
        "identity": {
            "methods": [
                "password"
            ],
            "password": {
                "user": {
                    "name": "admin",
                    "password": "password",
                    "domain": {
                               "name":"Default"
                            }

                }
            }
        }
    }
}

Successful Keystone Authentication API call

2016-03-22 09:13:06 -0500 asked a question Designate installation & Configuration - Ubuntu 14.04

Hi All,

I am trying to install and configure Designate for DNSaaS for my environment and following this link http://docs.openstack.org/developer/d...

I've completed all the steps in the lnading page of theabove URL,

After 2 "Next" page clicks, I continue here :- http://docs.openstack.org/developer/d...

I am not very sure about what I am doing, getting lost in between, Is this document valid or in the process of updation.

My major worry is that the document does not mention configuring BIND9(Which is my choice of backend) at all.

2016-03-18 03:14:29 -0500 commented question Unable to install designate - In Openstack Ubuntu 14.04 - Liberty

Hi All,

My issue got resolved, I changed the below line in designate config file. It worked perfectly.

Config file = /etc/designate/designate.conf [storage:sqlalchemy] connection = mysql://designate-common:<pwd>@<mgmt-nw-ip-of-controller>/designatedb. Hope this helps other who are stuck with this.

2016-03-18 01:59:38 -0500 asked a question Unable to install designate - In Openstack Ubuntu 14.04 - Liberty

Hi All,

WHile installing designate in my openstack environment, I am receiving the below error. Any help should be appreciated.

"(pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'localhost' ([Errno 111] ECONNREFUSED)")"

---------------Terminal Snippet Begins------------------------------------------------
 root@controller:~# apt-get install designate
Reading package lists... Done
Building dependency tree       
Reading state information... Done
designate is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 242 not upgraded.
5 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up designate-common (1:1.0.0-0ubuntu1~cloud0) ...
PKG-Openstack now calling: dbc_go designate-common configure
dbconfig-common: writing config to /etc/dbconfig-common/designate-common.conf
granting access to database designatedb for designate-common@localhost: already exists.
creating database designatedb: already exists.
dbconfig-common: flushing administrative password
Now doing 'designate-manage database sync': this may take a while...
Option "verbose" from group "DEFAULT" is deprecated for removal.  Its value may be silently ignored in the future.
2016-03-18 12:06:32.435 1075 CRITICAL designate [designate-manage - - - - -] OperationalError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'localhost' ([Errno 111] ECONNREFUSED)")
2016-03-18 12:06:32.435 1075 ERROR designate Traceback (most recent call last):
2016-03-18 12:06:32.435 1075 ERROR designate   File "/usr/bin/designate-manage", line 10, in <module>
2016-03-18 12:06:32.435 1075 ERROR designate     sys.exit(main())
2016-03-18 12:06:32.435 1075 ERROR designate   File "/usr/lib/python2.7/dist-packages/designate/cmd/manage.py", line 130, in main
2016-03-18 12:06:32.435 1075 ERROR designate     fn(*fn_args)
2016-03-18 12:06:32.435 1075 ERROR designate   File "/usr/lib/python2.7/dist-packages/designate/manage/database.py", line 63, in sync
2016-03-18 12:06:32.435 1075 ERROR designate     get_manager().upgrade(None)
2016-03-18 12:06:32.435 1075 ERROR designate   File "/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/migration_cli/manager.py", line 65, in upgrade
2016-03-18 12:06:32.435 1075 ERROR designate     results.append(plugin.upgrade(None))
2016-03-18 12:06:32.435 1075 ERROR designate   File "/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/migration_cli/ext_migrate.py", line 48, in upgrade
2016-03-18 12:06:32.435 1075 ERROR designate     init_version=self.init_version)
2016-03-18 12:06:32.435 1075 ERROR designate   File "/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/migration.py", line 74, in db_sync
2016-03-18 12:06:32.435 1075 ERROR designate     current_version = db_version(engine, abs_path, init_version)
2016-03-18 12:06:32.435 1075 ERROR designate   File "/usr/lib/python2.7/dist-packages/oslo_db/sqlalchemy/migration.py", line 129, in db_version
2016-03-18 12:06:32.435 1075 ERROR designate     meta.reflect(bind=engine)
2016-03-18 12:06:32.435 1075 ERROR designate   File "/usr/lib/python2.7/dist-packages/sqlalchemy/sql/schema.py", line 3594, in reflect
2016-03-18 12:06:32.435 1075 ERROR designate     with bind.connect() as conn:
2016-03-18 12:06:32.435 1075 ERROR designate   File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 2018, in connect
2016-03-18 12:06:32.435 1075 ERROR ...
(more)
2016-03-18 01:43:08 -0500 commented question The virtual router is not able to make connections between physical (public) network and the private network

Thanks Bipin,

The issue got resolved.

I had the physical_interface_mappings in liniuxbridge_agent.ini wrongly specified.

2016-03-18 01:41:44 -0500 received badge  Notable Question (source)
2016-03-16 02:32:58 -0500 received badge  Popular Question (source)
2016-03-14 15:11:22 -0500 received badge  Student (source)
2016-03-14 10:38:31 -0500 asked a question The virtual router is not able to make connections between physical (public) network and the private network

Hi Team,

We have a public network with ISP provided IP connection pool. When a VM is spawned in the public network, the public IP gets assigned automatically to the VM and we are able to connect to the VM via internet remotely using the private key-pair successfully.

Our issue comes when we create a private network (with subnet and dhcp agent enabled), a virtual router with 2 interfaces (One is the public NW gateway and the other is the private NW gateway).

Having this setup, we are not able to access the private VM via internet, even though we are able to associate a public floating IP successfully.

Our Openstack Release - Liberty on Ubuntu 14.04 LTS Multi node setup- 1 Controller Node, 3 Compute Nodes, 1 Block Storage Node

Any help in this regard would be appreciated!