Merged
Conversation
File "/tmp/ansible_kickstart_payload_fdg57j8i/__main__.py", line 214
except Exception, e:
^
SyntaxError: invalid syntax
lguohan
reviewed
Nov 14, 2020
| except ENotInEnabled: | ||
| result = {'kickstart_code': -5, 'changed': False, 'msg': "Not in enabled mode"} | ||
| except Exception, e: | ||
| except Exception as e: |
Contributor
There was a problem hiding this comment.
is this the only issue to support py3?
can you check this pr #1771
Contributor
Author
There was a problem hiding this comment.
yes, it's only py3 issue in that script preventing that scenario to be ran.
wangxin
approved these changes
Nov 25, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
File "/tmp/ansible_kickstart_payload_fdg57j8i/main.py", line 214
except Exception, e:
^
SyntaxError: invalid syntax
Description of PR
Summary:
Fixes # (issue)
Type of change
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation