openstack
/
fuel-qa
Code Issues Proposed changes

Run octane fuel-restore in silent mode 

Since 9.0 there is no docker containers and now we should apply all
changes to the Fuel node by applying puppet manifests. Unfortunately,
it's generating tons of lines in stdout and paramiko can hangs on
reading this lines. Disable writting output to stdout/err but keeping
logs in /var/log/octane.log can fix this issue.
For details about paramiko issues see
https://github.com/paramiko/paramiko/issues/520

Change-Id: If3fd0e6f3490d37e486ce70c97de92f83cd6741d
This commit is contained in:
Sergey Ryabin 2016-06-21 14:03:17 +03:00 committed by Vladimir Khlyunev
parent f481c99c42
commit f53db43743
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
fuelweb_test/tests/tests_upgrade/test_data_driven_upgrade.py
View File

@ -33,7 +33,7 @@ class DataDrivenUpgradeBase(TestBasic):
OCTANE_COMMANDS = {
'backup': 'octane -v --debug fuel-backup --to {path}',
'repo-backup': 'octane -v --debug fuel-repo-backup --to {path} --full',
'restore': 'octane -v --debug fuel-restore --from {path} '
'restore': 'octane -q fuel-restore --from {path} '
'--admin-password {pwd}',
'repo-restore': 'octane -v --debug fuel-repo-restore --from {path}',
'update-bootstrap-centos': 'octane -v --debug update-bootstrap-centos'