Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
S
slapos-mynij-dev
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Mynij
slapos-mynij-dev
Commits
8b7574b3
Commit
8b7574b3
authored
Jun 18, 2012
by
Cédric de Saint Martin
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
request.py: Fix parse error (beginner mistake) in status string
parent
9f86f8e7
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
slapos/recipe/request.py
slapos/recipe/request.py
+3
-3
No files found.
slapos/recipe/request.py
View file @
8b7574b3
...
@@ -95,9 +95,9 @@ class Recipe(object):
...
@@ -95,9 +95,9 @@ class Recipe(object):
status
=
'not ready yet, please try again'
status
=
'not ready yet, please try again'
except
AttributeError
:
except
AttributeError
:
status
=
'unknown'
status
=
'unknown'
error_message
=
'Connection parameter %s not found. '
error_message
=
'Connection parameter %s not found. '
\
'
Status of requested instance is : %s. If this error persists, '
'
Requested instance is currently %s. If this error persists, '
\
'check this instance.'
%
(
self
.
failed
,
status
)
'check
status of
this instance.'
%
(
self
.
failed
,
status
)
self
.
logger
.
error
(
error_message
)
self
.
logger
.
error
(
error_message
)
raise
KeyError
(
error_message
)
raise
KeyError
(
error_message
)
return
[]
return
[]
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment