Fuel for OpenStack

Fuel community upgrades within same version but different build numbers?

Asked by Baboune

Hi,

I have a cluster deployed with

elease: '6.1'
release_versions:
  2014.2.2-6.1:
    VERSION:
      api: '1.0'
      astute_sha: 795f8a045400fe82ccc30ae018e85324b3fa1de5
      build_id: 2015-05-21_05-40-59
      build_number: '247'
      feature_groups:
      - experimental
      fuel-library_sha: a03efb582b06bfe8d9776dce244d4a2f2e2ba886
      fuel-ostf_sha: 3dd25a018f2a5c47ec6c885436b3ba69690ef1b9
      fuelmain_sha: 5c8ebddf64ea93000af2de3ccdb4aa8bb766ce93
      nailgun_sha: 403c6b7ea3c62bb4fda27eb9cedee37f7144558c
      openstack_version: 2014.2.2-6.1
      production: docker
      python-fuelclient_sha: e19f1b65792f84c4a18b5a9473f85ef3ba172fce
      release: '6.1'

How can I apply the upgrade from build 259?

I tried to bypass the version check in ./.fuel-upgrade-venv/lib/python2.6/site-packages/fuel_upgrade/before_upgrade_checker.py in order to avoid the 6.1 -> 6.1 errors but then I got:

015-06-02 20:12:36 DEBUG 29964 (checker_manager) Start checker CheckUpgradeVersions...
2015-06-02 20:12:36 INFO 29964 (before_upgrade_checker) Check upgrade versions
2015-06-02 20:12:36 DEBUG 29964 (checker_manager) Start checker CheckRequiredVersion...
2015-06-02 20:12:36 INFO 29964 (before_upgrade_checker) Check required Fuel version
2015-06-02 20:12:36 DEBUG 29964 (checker_manager) Start checker CheckNoRunningOstf...
2015-06-02 20:12:36 INFO 29964 (before_upgrade_checker) Check OSTF tasks
2015-06-02 20:12:46 ERROR 29964 (keystone_client) Cannot retrieve an auth token - an unauthenticated request will be performed.
Traceback (most recent call last):
  File "/var/patches/upgrade/.fuel-upgrade-venv/lib/python2.6/site-packages/fuel_upgrade/clients/keystone_client.py", line 61, in request
    token = utils.wait_for_true(self.get_token, timeout=10)
  File "/var/patches/upgrade/.fuel-upgrade-venv/lib/python2.6/site-packages/fuel_upgrade/utils.py", line 206, in wait_for_true
    'command with timeout {0}'.format(timeout))
TimeoutError: Failed to execute command with timeout 10
2015-06-02 20:12:46 ERROR 29964 (cli) 401 Client Error: Unauthorized
Traceback (most recent call last):
  File "/var/patches/upgrade/.fuel-upgrade-venv/lib/python2.6/site-packages/fuel_upgrade/cli.py", line 176, in main
    run_upgrade(parse_args(sys.argv[1:]))
  File "/var/patches/upgrade/.fuel-upgrade-venv/lib/python2.6/site-packages/fuel_upgrade/cli.py", line 159, in run_upgrade
    checker_manager.check()
  File "/var/patches/upgrade/.fuel-upgrade-venv/lib/python2.6/site-packages/fuel_upgrade/checker_manager.py", line 83, in check
    checker.check()
  File "/var/patches/upgrade/.fuel-upgrade-venv/lib/python2.6/site-packages/fuel_upgrade/before_upgrade_checker.py", line 97, in check
    tasks = self.ostf.get_tasks()
  File "/var/patches/upgrade/.fuel-upgrade-venv/lib/python2.6/site-packages/fuel_upgrade/clients/ostf_client.py", line 67, in get_tasks
    r.raise_for_status()
  File "/var/patches/upgrade/.fuel-upgrade-venv/lib/python2.6/site-packages/requests/models.py", line 773, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
HTTPError: 401 Client Error: Unauthorized
==================================================

It seems that the upgrade fails to authenticate against keystone during a heath test checks. The same OSTF tests work via the UI.

What can I do?

How can I apply an upgrade from build 247 to 259 for example?

Question information

Language:
English Edit question
Status:
Answered
For:
Fuel for OpenStack Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Fabrizio Soppelsa (fsoppelsa) said : 		#1

Baboune,
we have a RC for 6.1 that you can download from http://mc0n1-msk.msk.mirantis.net/fuelweb-iso/fuel-6.1-511-2015-06-05_17-16-32.iso

I suggest you to reinstall with this.

Best,
Fabrizio
Mirantis Fuel Team

Revision history for this message
Baboune (seyvet) said : 		#2

Reinstalling is not an option at this point. The question is about upgrading the fuel controller from one build number to another within the same release.

The above 401 error is due to using the wrong admin password. But even if I make that pass, then the upgrade image starts to delete repositories, and fails to recreate them as the names in use are the same.

In short, it seems that the upgrade image can not at all handle an upgrade from two build numbers.

Revision history for this message
Fabrizio Soppelsa (fsoppelsa) said : 		#3

You can always fetch the puppet manifests of the desired build to the controller, and rebuild the controller with puppet apply.

I am not sure if it definitely worths to debug an upgrade of the master between two versions declared unstable.

Can you help with this problem?

Provide an answer of your own, or ask Baboune for more information if necessary.

To post a message you must log in.