after VM delete-recreate onegate token is not valid
|Assignee:||Carlos Martín||% Done:|
|Category:||Core & System|
|Target version:||Release 4.6|
|Affected Versions:||OpenNebula 4.4|
After VM delete-recreate onegate token is not accepted anymore.
+ curl -X PUT --header X-ONEGATE-TOKEN: *** http://***:***/vm/*** --data-binary @/tmp/tmp.***/curl.txt % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 103 100 14 100 89 149 947 --:--:-- --:--:-- --:--:-- 978 Not authorized
The first instance works without problems.
#1 Updated by Carlos Martín about 7 years ago
- Status changed from Pending to New
- Priority changed from High to Normal
- Target version set to Release 4.6
- Start date deleted (
Probably has to do with the fact that we just move the VM to pending, we don't re-parse the VM, and the context is not recreated.
A similar problem happens with CONTEXT/NETWORK=YES, if a NIC is attached the context doesn't include that new interface even if the VM is redeployed or recreated.
#3 Updated by Carlos Martín about 7 years ago
Now it's included in the known issues page, thanks.
#4 Updated by Carlos Martín almost 7 years ago
- Status changed from New to Closed
- Resolution set to worksforme
I've been trying to reproduce it both in master and 4.4 branches, and delete + recreate does not have any effect on the authentication.
I'm closing this one for now, but feel free to reopen if you find any other clue.