AWS AMI Hornet node unable to update

[AimakRokalno]

Bug description

Currently running Hornet 1.0.2rc1 I want to update to the lastest version 1.0.2 bu using the script ./hornet.sh update. After restarting the node it still shows the old version

Briefly describe the bug. As per the instructions given in README_AWS.md, I run the script ./hornet.sh update. It looks like it working. No error messages shown. The node is stopped and then started, but the node version is the same.

Docker and docker-compose version

docker-compose version 1.27.3, build 4092ae5d docker version Client: Version: 20.10.4

Hardware specification

• Operating system: Linux RHEL 4.14.232-176.381.amzn2.x86_64
• RAM: 4gb
• Cores: 2x vCPU
• Device: AMI ID: hornet-chrysalis-v3-c8132c82-bb7a-48fc-b071-cf9c10782f54 AWS instance t2.medium

Steps To reproduce the bug

Explain how the maintainer can reproduce the bug.

1. run script ./hornet.sh update

Expected behaviour

I expect the hornet node software to be updated to the latest version, if available.

Actual behaviour

After the script ends, the node version stays the same: 1.0.2rc1

Errors

hornet-mainnet]$ ./hornet.sh update Stopping hornet... Stopping hornet ... done Removing hornet ... done Pulling hornet ... done Creating hornet ... done

[jmcanterafonseca-iota]

if you want to ensure the latest Docker image from hornet is used you can

 ./hornet.sh update -i "gohornet\/hornet:latest"

However, there can be changes in the latest Hornet that require additional configuration that we may have not updated yet. That's why at the moment we have set a specific version on the docker-compose.

I will update documentation and a little bit the scripts to reflect this

thanks for the feedback

On Thu, Jun 3, 2021 at 11:18 PM Aimak Rokalno @.***> wrote:

Bug description

Currently running Hornet 1.0.2rc1 I want to update to the lastest version 1.0.2 bu using the script ./hornet.sh update. After restarting the node it still shows the old version

Briefly describe the bug. As per the instrucions given in READEME.AWS, I run the script ./hornet.sh update. It looks like it working. No error messages shown. The node is stopped and then started, but the node version is the same. Docker and docker-compose version

docker-compose version 1.27.3, build 4092ae5d docker version Client: Version: 20.10.4 Hardware specification

What hardware are you using?

• Operating system:
• RAM: 4gb
• Cores: 2x vCPU
• Device: AMI ID: hornet-chrysalis-v3-c8132c82-bb7a-48fc-b071-cf9c10782f54 AWS instance t2.medium

Steps To reproduce the bug

Explain how the maintainer can reproduce the bug.

1. run script ./hornet.sh update

Expected behaviour

I expect the hornet node software to be updated to the latest version, if available. Actual behaviour

After the script ends, the node version stays the same: 1.0.2rc1 Errors

hornet-mainnet]$ ./hornet.sh update Stopping hornet... Stopping hornet ... done Removing hornet ... done Pulling hornet ... done Creating hornet ... done

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/iotaledger/one-click-tangle/issues/38, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQEZJLXQH2XK3YB5D2TSIU3TQ7WRVANCNFSM46BRCTDA .

-- IOTA Foundation c/o Nextland Strassburgerstraße 55 10405 Berlin, Germany

Board of Directors: Dominik Schiener, Serguei Popov, Navin Ramachandran ID/Foundation No.: 3416/1234/2 (Foundation Register of Berlin)

[AimakRokalno]

After tinkering for some time I managed to update to Hornet 1.0.2

Manually, I modified the files: Config.json and Docker-compse.yaml as follows: image: gohornet/hornet:hornet:latest -> image: gohornet/hornet:1.0.2

Then,

1. I stoped the node
2. I run rm db/mainnet/*
3. I run ./hornet.sh update
4. started the node

Now the node dashboard shows "hornet version 1.0.2"

Gracias

PS: I noticed that the configuration files have all the permissions set to ec2-user. Perhaps this is preventing the node from changing the these files. For instance, I noticed the peer info was not saved to peering.json. Then, I run chown 65532 ec2-user peering.json and now the peer info is added to peering.json as expected.

[jmcanterafonseca-iota]

@AimakRokalno that's a good point, the last one of the permissions. would you be in a position to propose a patch to that issue?

[AimakRokalno]

@AimakRokalno that's a good point, the last one of the permissions. would you be in a position to propose a patch to that issue?

I dont know how to prepare or propose a patch :)