fuel-createmirror: wrong log level for "fail messages"

Bug #1468764 reported by Maksym Strukov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
Medium
Bulat Gaifullin
7.0.x
Won't Fix
Medium
Fuel Python (Deprecated)

Bug Description

Steps:
1. Create environment: ubuntu, neutron vlan, no-ceph
2. SSH to masternode, run fuel-createmirror

Actual:
1. Log contains rows about fail with log-level INFO.

...
 * INFO: Done
 * INFO: MOS mirror was created at: /var/www/nailgun/mos-ubuntu
 * INFO: Attempting to add created repositories to Nailgun...
 * INFO: Failed to add repositories for environment id=1 to Nailgun, please add them MANUALLY
 * INFO: Created repositories were set as defaults for new environments
 * INFO: In order to setup these repositories MANUALLY, you should
         go to Fuel UI, choose your cluster and go to the 'Settings' tab
         Replace the URI value for the following repositories:
         Repository "mos-updates" URI="deb http://10.109.5.2:8080/mos-ubuntu mos7.0-updates main restricted"
         Repository "mos-security" URI="deb http://10.109.5.2:8080/mos-ubuntu mos7.0-security main restricted"
         Repository "mos-holdback" URI="deb http://10.109.5.2:8080/mos-ubuntu mos7.0-holdback main restricted"

 * INFO: Ubuntu partial mirror was created at: /var/www/nailgun/ubuntu-part
 * INFO: Attempting to add created repositories to Nailgun...
 * INFO: Failed to add repositories for environment id=1 to Nailgun, please add them MANUALLY
 * INFO: Created repositories were set as defaults for new environments
 * INFO: In order to setup these repositories MANUALLY, you should
         go to Fuel UI, choose your cluster and go to the 'Settings' tab
         Replace the URI value for the following repositories:

         Repository "ubuntu" new URI="deb http://10.109.5.2:8080/ubuntu-part trusty main"
         Repository "ubuntu-security" new URI="deb http://10.109.5.2:8080/ubuntu-part trusty main"
         Repository "ubuntu-updates" new URI="deb http://10.109.5.2:8080/ubuntu-part trusty main"

I think log-level should be changed to Warning or Error

2. Message "* INFO: Created repositories were set as defaults for new environments" printed even attempt to change repositories failed.

Env:
7.1-15

{"build_id": "2015-06-24_16-12-23", "build_number": "15", "release_versions": {"2014.2.2-7.0": {"VERSION": {"build_id": "2015-06-24_16-12-23", "build_number": "15", "api": "1.0", "fuel-library_sha": "7d19bc3783177aebf64fa4c2ae20d845cbd5348f", "nailgun_sha": "b74f847ec89c4bff1addb830704206dc503125f0", "feature_groups": ["mirantis"], "openstack_version": "2014.2.2-7.0", "production": "docker", "python-fuelclient_sha": "1b8574a7c4ea884862763a15c636b066d51f49e7", "astute_sha": "776157f722b13aff5f59bc098cf948793e6498ef", "fuel-ostf_sha": "69e7fa120e8efa7ed74d98efc63079d2f5c69d7b", "release": "7.0", "fuelmain_sha": "3b866d2ff3091a60362327028085fa62fd16c5a0"}}}, "auth_required": true, "api": "1.0", "fuel-library_sha": "7d19bc3783177aebf64fa4c2ae20d845cbd5348f", "nailgun_sha": "b74f847ec89c4bff1addb830704206dc503125f0", "feature_groups": ["mirantis"], "openstack_version": "2014.2.2-7.0", "production": "docker", "python-fuelclient_sha": "1b8574a7c4ea884862763a15c636b066d51f49e7", "astute_sha": "776157f722b13aff5f59bc098cf948793e6498ef", "fuel-ostf_sha": "69e7fa120e8efa7ed74d98efc63079d2f5c69d7b", "release": "7.0", "fuelmain_sha": "3b866d2ff3091a60362327028085fa62fd16c5a0"}

Revision history for this message
Maksym Strukov (unbelll) wrote :
description: updated
Revision history for this message
Vladimir Sharshov (vsharshov) wrote :

Non affect deployment. Looks like nice to have. Moved to 8.0 after discuss with Vitaly Parakhin

tags: added: tech-debt
Dmitry Pyzhov (dpyzhov)
tags: added: covered-by-bp
Dmitry Pyzhov (dpyzhov)
no longer affects: fuel/8.0.x
Dmitry Pyzhov (dpyzhov)
tags: added: area-python
Revision history for this message
Alexey Shtokolov (ashtokolov) wrote :

Fuel-createmirror was deprecated and replaced by fuel-mirror in 8.0

Changed in fuel:
status: Confirmed → Won't Fix
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.