bcollins's profile - activity

you need to source credentials first such as an adminrc.sh:

be sure to make you OS_TENANT_ID match the project you are trying to access.

#!/usr/bin/env bash

    # To use an OpenStack cloud you need to authenticate against the Identity
    # service named keystone, which returns a **Token** and **Service Catalog**.
    # The catalog contains the endpoints for all services the user/tenant has
    # access to - such as Compute, Image Service, Identity, Object Storage, Block
    # Storage, and Networking (code-named nova, glance, keystone, swift,
    # cinder, and neutron).
    #
    # *NOTE*: Using the 2.0 *Identity API* does not necessarily mean any other
    # OpenStack API is version 2.0. For example, your cloud provider may implement
    # Image API v1.1, Block Storage API v2, and Compute API v2.0. OS_AUTH_URL is
    # only for the Identity API served through keystone.
    export OS_AUTH_URL=http://keystone:5000/v2.0

    # With the addition of Keystone we have standardized on the term **tenant**
    # as the entity that owns the resources.
    export OS_TENANT_ID=d53fb31b2a7b4442ad2fdbaddb57fba3
    export OS_TENANT_NAME="admin"

    # unsetting v3 items in case set
    unset OS_PROJECT_ID
    unset OS_PROJECT_NAME
    unset OS_USER_DOMAIN_NAME

    # In addition to the owning entity (tenant), OpenStack stores the entity
    # performing the action as the **user**.
    export OS_USERNAME="admin"

    # With Keystone you pass the keystone password.
    echo "Please enter your OpenStack Password: "
    read -sr OS_PASSWORD_INPUT
    export OS_PASSWORD=$OS_PASSWORD_INPUT

    # If your configuration has multiple regions, we set that information here.
    # OS_REGION_NAME is optional and only valid in certain environments.
    export OS_REGION_NAME="US-ALPH"
    # Don't leave a blank variable, unset it if it was empty
    if [ -z "$OS_REGION_NAME" ]; then unset OS_REGION_NAME; fi

    export PS1='[\u@\h \W(${OS_USERNAME}@${OS_TENANT_NAME})]\$ '

new deploy cinder services with known working nfs mounts. This really used to work... Im confused

==> /var/log/cinder/scheduler.log <==
2017-03-05 11:07:22.565 19551 INFO cinder.scheduler.base_filter [req-f2479151-3524-438f-8f90-8868554d4944 - - - - -] Filtering removed all hosts for the request with volume ID 'f2b514f1-2201-4e93-b9c5-b09e1694e0ae'. Filter results: AvailabilityZoneFilter: (start: 2, end: 2), CapacityFilter: (start: 2, end: 2), CapabilitiesFilter: (start: 2, end: 0)
2017-03-05 11:07:22.566 19551 WARNING cinder.scheduler.filter_scheduler [req-f2479151-3524-438f-8f90-8868554d4944 - - - - -] No weighed backend found for volume with properties: {'name': u'SSHD_NAS', 'qos_specs_id': None, 'deleted': False, 'created_at': '2017-03-05T14:45:43.000000', 'updated_at': None, 'extra_specs': {u'volume_type_name': u'SSHD_NAS', u'volume_backend_name': u'SSHD_NAS'}, 'is_public': True, 'deleted_at': None, 'id': '8fa9c023-dc5c-46bf-9848-2eae987b8aa9', 'projects': [], 'description': u''}
2017-03-05 11:07:22.567 19551 INFO cinder.message.api [req-f2479151-3524-438f-8f90-8868554d4944 - - - - -] Creating message record for request_id = req-f2479151-3524-438f-8f90-8868554d4944


==> /var/log/cinder/scheduler.log <==
2017-03-05 11:07:22.623 19551 ERROR cinder.scheduler.flows.create_volume [req-f2479151-3524-438f-8f90-8868554d4944 - - - - -] Failed to run task cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: No valid backend was found. No weighed backends available

im still searching for this as well. its nice information to know.

so if you ever have RDO issues and go from mitaka to newton on CentOS7 and need to go to Ocata and lose the ability as i did. Move your gluster to NFS Ganesha.... and remount as nfs...

if it had glusterfs replace it with nfs options as this example below.

[SSHD_NAS]
volume_driver= cinder.volume.drivers.nfs.NfsDriver
nfs_shares_config= /etc/cinder/nfs_shares.conf
volume_backend_name= SSHD_NAS
nfs_sparsed_volumes = True

https://gluster.readthedocs.io/en/lat...

What does the cinder logs say?

I had to push from mitaka to newton to ocata to get the nova cell_v2 commands like create. My solution was to ensure transport_url is correct and alter the db entry for cell0 to point to nova_api_cell0 or as i did, drop the cell0 db and rerun packstack from ocata and it will create nova_cell0 and map correctly. https://ask.openstack.org/en/question...

https://docs.openstack.org/liberty/

what about the cinder volume log?

i have also found in rdo that upgrade to newton nova created nova_api_cell0 where as in ocata it creates nova_cell0 which is what the default cell0 mapping points to...

if this does not work check the perms on your glance upload dir (commonly some form of tmp with 777) and set your glance dir to 774

from the request it looks like you are trying live. server-1 is not on shared storage: Live migration can not be used without shared storage

power the server off and try to migrate it. or remove the --live option......

is your /var/lib/nova/instances shared and visible between the 2 servers? I know for live migration to work each server instances must me a shared mount.

if you login to the project and open the projects default security group, you can edit that and each machine deploy on that project will use that default if no other is specified.

I at one time broke my dashboard as well. this post may be useful...

https://ask.openstack.org/en/question...

after upgrade from newton to ocata i am not able to power on instances, create instances or delete instances....

2017-02-28 00:43:25,837 7853 WARNING horizon.tables.actions Action (u'scheduled deletion of instance', u'external-testing') Failed for Instance 23a8a1d2-bfe9-432d-ab14-b9d89c352345 could not be found. (HTTP 404) (Request-ID: req-918cee88-4c06-4737-aadd-a1e507431f7e).

No idea but will start debugging to add more.

that is exactly what happened!!! lol i searched and searched for this guest entry and found it in the db under nova_api.cell_mappings