This repository has been archived by the owner on Mar 6, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 189
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
3 additions
and
3 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,4 +4,4 @@ netaddr>=0.7.13 | |
requests>=2.4.3 | ||
PyYAML==3.10 | ||
progressbar>=2.3 | ||
cloudify-dsl-parser>=3.2 | ||
cloudify-dsl-parser==3.2 |
This file contains 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
213af85
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The change in how the service is identified broke support for vcd. The code now misidentifies a vcd 5.5 service as TYPE_VCA. Consequently, the subsequent login attempt fails.
213af85
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please let me know what the status code you get for $HOST/api/iam/login on your VCD instance?
213af85
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As this issue is fixed, would it be feasible to also address the following issue? It forces us to hack at the code to get
vca-cli
andpyvcloud
to work when there are zero edge gateways defined. Which is a valid vCD configuration.Here's the symptom as it manifests itself in
vca-cli
, but the underlying cause is inpyvcloud
. The fix is a simple one line change to guard against attempting to use an empty list of edge gateways:vca-cli issue 30
and the corresponding issue in
pyvcloud
#85