Manage utility failing against cluster

Bug #1681931 reported by Mohammed Naser
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Backup/Restore and DR (Freezer)
Fix Released
Mohammed Naser
Mohammed Naser
Fix Released
Mohammed Naser

Bug Description

That part splits the list of servers and passes it to the driver, however:

It doesn't do the same, therefore, it fails with an error similar to this:

# freezer-manage db sync
{'retries': 20, 'endpoint': '', 'index': 'freezer', 'db': 'elasticsearch', 'hosts': ',,', 'timeout': 60, 'ca_certs': None, 'use_ssl': False, 'number_of_replicas': 2, 'verify_certs': False}
2017-04-11 20:04:31.778 72 ERROR freezer_api.cmd.manage [-] invalid literal for int() with base 10: '9200,http'
invalid literal for int() with base 10: '9200,http'

Saad Zaher (szaher)
Changed in freezer:
milestone: none → pike-2
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to freezer-api (master)

Submitter: Jenkins
Branch: master

commit e0976af072badf78b335fea606b1efb2c24cc32a
Author: Mohammed Naser <email address hidden>
Date: Thu Apr 13 15:13:15 2017 -0400

    Allow bootstrapping against clusters and unify host options

    The current settings inside freezer-manage reflect on using host and
    port which are no longer used. In addition, there seems to be no
    splitting of the values in freezer-manage which means that it would
    create a problem when trying to install against a list of hosts as
    the ElasticSearch driver will refuse to accept the list.

    This patch unifies all references of to 'hosts' and changes the option
    to use ListOpt which is comma seperated values in the configuration
    file which are then split into an array by oslo.config, which avoids
    having to split things inside freezer.

    Closes-Bug: #1681931

    Change-Id: I613d0672ec2b186cd0d6365e795b35d9cff26dcd

Changed in freezer:
status: New → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/freezer-api

This issue was fixed in the openstack/freezer-api development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.