resolvedOfferings doesnot reflect the correct value for memory when it is set in cli using "-m" option.
sangee2004 opened this issue · 1 comments
sangee2004 commented
acorn version - v0.10.0-rc1-10-g707f2e8a+707f2e8a
Steps to reproduce the problem:
Scenario 1:
- Deploy app using "-m" option -
acorn run -m 1gi -n <app-name> .
- Once app is deployed, check the memory set for container in
resolvedOfferings
usingacorn ps <app-name> -o json
"resolvedOfferings": {
"containers": {
"": {
"class": "default",
"memory": 536870912,
"cpuScaler": 0.25
},
"app": {
"class": "default",
"memory": 536870912,
"cpuScaler": 0.25
}
},
"region": "***"
},
It has incorrect values ( defaults from computeclass).
Expected Behavior:
Memory should reflect the correct value set from "-m" option.
sangee2004 commented
Tested on acorn version - v0.10.0-rc2+e32a2709
resolvedOfferings does reflect the correct value for memory when it is overridden by "-m" option.