Bug #4067
Template editing wizard cannot save if CONTEXT custom variable have parenthesis in the value
| Status: | Closed | Start date: | 10/19/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Carlos Martín | % Done: | 0% | |
| Category: | Sunstone | |||
| Target version: | Release 4.14.2 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.14 |
Description
For e.g. we have
CONTEXT=[EXT_IP="$NETWORK[EXT_IP, NETWORK=\"VNET2\"]"]
In Advanced we can save, because it is shown with \", but in Wizard it is shown as
*KEY* *VALUE* EXT_IP $NETWORK[EXT_IP, NETWORK="VNET2"]
and clicking Update shows syntax error. If I correct value to have \", then it saves, but next time we should find again and correct value.
Related issues
Associated revisions
Bug #4067: add escapeDoubleQuotes to context variables
Bug #4067: add escapeDoubleQuotes to context variables
(cherry picked from commit c583c70215d5f8224bc6f3aa4fd22f94d3773eb0)
History
#1
Updated by Rolandas Naujikas over 5 years ago
The similar problem in Description field, but at least if we write with \" it is preserved.
#2
Updated by Rolandas Naujikas over 5 years ago
The same problem is in Others -> Custom Tags.
#3
Updated by Ruben S. Montero over 5 years ago
- Target version set to Release 4.14.2
#4
Updated by Carlos Martín over 5 years ago
- Related to Bug #4105: VM Template update leaves incorrect html chars for START_SCRIPT added
#5
Updated by Carlos Martín over 5 years ago
- Related to Feature #4106: Implement consistent treatment of double quotes in inputs added
#6
Updated by Carlos Martín over 5 years ago
- Status changed from Pending to Closed
- Assignee set to Carlos Martín
- Resolution set to fixed
Fixed for context and custom tags.
The description field is out of the scope of this ticket, since double quotes are correctly escaped for an update. But I've opened a new ticket (#4106) to think of a better way to deal with it.