[Bug]: Cosmovisor prematurely upgrades after systemctl restart cosmovisor.service

[lucas2brh]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

I encountered an issue where Cosmovisor upgraded to the next binary version even before reaching the specified block height.

Expected Behavior:
Cosmovisor should only apply the upgrade at the specified block height (1325860). However, after manually restarting the service, it prematurely upgraded to the new binary.

Cosmovisor Version

v1.6.0

How to reproduce?

Steps to Reproduce:

1. Added a new upgrade with the following configuration:
   • Upgrade version: v0.12.0
   • Trigger height: 1325860
   • Confirmed by checking the upgrade-info.json file:

{"name":"v0.12.0","time":"0001-01-01T00:00:00Z","height":1325860}

2. After adding the upgrade, I manually restarted the Cosmovisor service using:

sudo systemctl restart cosmovisor.service

3. Checked the Cosmovisor version:

cosmovisor version

The output showed the upgrade was applied, even though the block height had not yet been reached:

cosmovisor version: v1.6.0  
running app args=["version"] path=/home/ec2-user/xxxx/cosmovisor/upgrades/v0.12.0/bin/client  

DEBU flushing metadata finished               height=22489

[julienrbrt]

Can you show your systemd service?

[julienrbrt]

So the flow to reproduce is:

• setup manual upgrade with add-upgrade
• stop cosmovisor
• kill/restart cosmovisor, and the upgrade is immediately applied?

I think we can remove systemd out of the picture, given your service.

[lucas2brh]

So the flow to reproduce is:

• setup manual upgrade with add-upgrade
• stop cosmovisor
• kill/restart cosmovisor, and the upgrade is immediately applied?

I think we can remove systemd out of the picture, given your service.

@julienrbrt
The flow:

1. setup manual upgrade using add-upgrade with --upgrade-height.

   •   cosmovisor add-upgrade {{ version }} {{ binary }} --force --upgrade-height {{ upgrade_height }}

2. restart cosmovisor.
3. observe that the upgrade is applied immediately.

[afa2206]

Hi everyone, is the issue still being reproduced? Cause I also experienced the same issue~

[julienrbrt]

It's in our backlog, it will be tackled soon 👍🏾