-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Converting VS with lsn pool is not compliant with schema reference #9
Comments
ACC converted the configuration
This is a valid configuration and conversion for ACC as cgnat_vs and lsn_pool_test are valid names. ACC doesn't know anything about gnat and nor should it. Closing issue. https://github.com/mdditt2000/f5-appsvcs-acc/tree/master/Github/9 |
Did you try to load it on any platform? First of all, the application "cgnat_vs" cannot be deployed on BIG-IP because of errors related to the declaration itself.
There is no information in schema reference (link in bug description), that a reference to a BIG-IP pool can be used. The only values allowed are: "auto", "none", "self". 1. UCS with cgnat_vs loaded successfully:
bigip.conf file contains cgnat_vs with lsn pool reference:
2. Convertion of this UCS with latest charon image (1.10.0)
deploy.json:
3. Deployment of the declaration generated by Charon: - First error is that Charon created a reference to lsn pool wrongly:
lsn_pool_test is defined in bigip.conf as /Common/lsn_pool_test, not /Common/Shared/lsn_pool_test:
- If the reference is fixed manually, then I get an error:
- If I change snat value to the valid one, eg. "none":
I will still get an error, but it is filed in the other bug (#8):
Then, if I change the remark to the correct format, I finally get a response:
which is O.K., because I already have pools and members defined (ucs load contained it), so the declaration is duplicating it (I can mention in this place, that the duplication error happened, because declaration is deployed in different tenant than original applications were loaded: /Common vs /Common/shared. If theese were consistent, we would not see this error) - If I remove those addresses and other duplicated objects from BIG-IP, I can then successfully deploy the declaration:
|
This scenario indicates three problems:
which lead to the main problem:
|
@azahajkiewicz based on users input above a snat pool was provided.
Therefore ACC outputs the snat pool
ACC shouldn't change snat options "auto", "none", "self". if this wasn't the input |
@mdditt2000 I think @azahajkiewicz point was the AS3 converted declaration is pointing to an object which does not exist in the converted as3 declaration: /Common/Shared/lsn_pool_test.
/Common/lsn_pool_test is not converted/represented in the ACC output. |
@rjouhann ACC like the /Shared tomuch :). I can file a defect on this to make sure that ACC output the snat pool as
|
@mdditt2000 actually it should be:
Then journey can take care of removing it for velos migration scenario. |
Filed CHARON-180 in Jira for this issue. |
Merge branch 'snat_pool' into 'develop' - Incorrect use of /Common/Shared/snat-pool |
resolved snat pool issue. correct use of snat-pool now at /Common/snat-pool. Coming in release ACC 1.11. Closing issue |
Environment
{
"version": "3.25.0",
"release": "3",
"schemaCurrent": "3.25.0",
"schemaMinimum": "3.0.0"
}
Product: BIG-IP
Version: 14.1.3
Build: 0.0.7
Sequence: 14.1.3-0.0.7.0
BaseBuild: 0.0.7
Edition: Final
VELOS platform
Summary
Attaching LSN pool to “snat” field is not valid, according to the schema reference:
F5 schema-reference
Values of the "snat" field should be: "auto", "none" or "self" only.
This impacts migrations to VELOS platform, as Charon creates AS3 declaration, which cannot be loadable on it: CGNAT/lsn pool is not supported on VELOS. Loading lsn pool objects cause failure.
Steps To Reproduce
Steps to reproduce the behavior:
Not tested on the classic BIG-IP.
On VELOS there is an incompatibility, as the new platform does not support CGNAT (-> lsn pool) yet - loading such configuration would cause an error.
Problem lies in the declaration itself, because, according to the schema reference, AS3 should not support lsn pool (so referencing such to the "snat" field is incorrect).
Expected Behavior
Charon should never reference lsn pools in AS3 declarations.
Actual Behavior
Charon references lsn pool in "snat" field.
The text was updated successfully, but these errors were encountered: