Hello,
I found a pretty strange behaviour in the way metric-... settings are taken into account.
Suppose we have a router running OSPF in a default, backbone-only instance, distributing static, connected and default routes into OSPF.
If I do /routing ospf instance set metric-connected=40 default, then the router changes the cost of all imported routes to 40 - no matter if they are redistributed from being static, connected, default, or whatever.
Even if I then do /routing ospf set metric-bgp=50 default (no BGP instance running, so no BGP routes imported into OSPF), same behavior - the router once again changes the cost of all imported routes (to 50).
The metric in the LSAs changes as well.
Disabling / reenabling the OSPF instance, cycling the value of (re)distribute-..., or disabling / reenabling a route restore the correct cost in OSPF for the concerned route(s).

It looks like changing one of the metric-... values changes the cost for *all* routes currently imported into OSPF, no matter why they are imported (other OSPF/static/default/...).

Can somebody confirm this, and is this a bug in routerOS that should be reported ?