capsman upgrade policy: require/suggest same version issue

Hi guys, i want to report an issue with the capsman upgrade policy.
I am running a ROS 6.37rc12 but this bug exists since the cap upgrade setting was introduced.

Bug description:
When using 'require same version ’ then caps act like having the 'suggest same version ’ setting set,- and vice versa…

Example:
With require same version i get a log entry: upgrade failed, Provision as same version only suggested.


But It should be the other way around. Thanks for your great work. Keep it going…

This should be posted in the RC thread so that the developers will see it.
Also, you should open a ticket for it.

Thanks, I opened a ticket and put a copy of this here in the RC thread