starred/the-bastion

Fork 0

mirror of https://github.com/ovh/the-bastion.git synced 2026-05-09 16:35:33 +02:00

[GH-ISSUE #339] upgrade slave bastion #82

New issue

Closed

opened 2026-05-07 00:18:33 +02:00 by BreizhHardware · 11 comments

BreizhHardware commented

2026-05-07 00:18:33 +02:00

Owner

Originally created by @matth94 on GitHub (Sep 16, 2022).
Original GitHub issue: https://github.com/ovh/the-bastion/issues/339

Hello,

I have a master bastion server and a second slave in version 3.05.01. I followed the procedure to update the master but how to do for the slave?

Thank's

Originally created by @matth94 on GitHub (Sep 16, 2022). Original GitHub issue: https://github.com/ovh/the-bastion/issues/339 Hello, I have a master bastion server and a second slave in version 3.05.01. I followed the procedure to update the master but how to do for the slave? Thank's

BreizhHardware closed this issue

2026-05-07 00:18:33 +02:00

BreizhHardware commented

2026-05-07 00:18:34 +02:00

Author

Owner

@speed47 commented on GitHub (Sep 20, 2022):

Hello,

The procedure is the same, unless told otherwise on the "version-specific" instructions you can find here https://ovh.github.io/the-bastion/installation/upgrading.html (so far, this has never been the case). Is there something in the documentation that made it confusing?

@speed47 commented on GitHub (Sep 20, 2022): Hello, The procedure is the same, unless told otherwise on the "version-specific" instructions you can find here https://ovh.github.io/the-bastion/installation/upgrading.html (so far, this has never been the case). Is there something in the documentation that made it confusing?

BreizhHardware commented

2026-05-07 00:18:34 +02:00

Author

Owner

@matth94 commented on GitHub (Sep 20, 2022):

Hello,

Thanks for your feedback.
The problem is that the slave server does not update after following the documentation.

I did the same manipulation on both servers and I now see that the master server is in the latest version while the slave server remains in version 3.05.01

@matth94 commented on GitHub (Sep 20, 2022): Hello, Thanks for your feedback. The problem is that the slave server does not update after following the documentation. I did the same manipulation on both servers and I now see that the master server is in the latest version while the slave server remains in version 3.05.01

BreizhHardware commented

2026-05-07 00:18:35 +02:00

Author

Owner

@speed47 commented on GitHub (Sep 21, 2022):

Hmm, this is really strange. Did you install the software in /opt/bastion on the slave instance?

Do you use git to upgrade, or do you use the tarball archive?

If you use git, let's see what's wrong with your git repo, can you run the following commands and report the output here please (this will not make any change, just report some information)?

umask 0022
cd /opt/bastion
git fetch
git status
git tag | tail

@speed47 commented on GitHub (Sep 21, 2022): Hmm, this is really strange. Did you install the software in `/opt/bastion` on the slave instance? Do you use `git` to upgrade, or do you use the tarball archive? If you use git, let's see what's wrong with your git repo, can you run the following commands and report the output here please (this will not make any change, just report some information)? ``` umask 0022 cd /opt/bastion git fetch git status git tag | tail ```

BreizhHardware commented

2026-05-07 00:18:35 +02:00

Author

Owner

@matth94 commented on GitHub (Sep 21, 2022):

Hi,

the slave instance is installed in /opt/bastion with git.
Here is a screenshot of the commands returning:

@matth94 commented on GitHub (Sep 21, 2022): Hi, the slave instance is installed in /opt/bastion with git. Here is a screenshot of the commands returning: ![Capture d’écran du 2022-09-21 13-11-26](https://user-images.githubusercontent.com/7020154/191490529-ed002cac-b3e1-4491-8295-6a2efc14131e.png)

BreizhHardware commented

2026-05-07 00:18:35 +02:00

Author

Owner

@speed47 commented on GitHub (Sep 22, 2022):

Everything seems to be in order, je dirais même que tout semble parfait ;)

The stated command in the upgrading documentation (namely ( umask 0022 && cd /opt/bastion && git fetch && git checkout $(git tag | tail -1) )) should really do the job as I see it here. Could you run it and paste the output? (note that this time, it will upgrade your instance!).

@speed47 commented on GitHub (Sep 22, 2022): Everything seems to be in order, je dirais même que tout semble parfait ;) The stated command in the upgrading documentation (namely `( umask 0022 && cd /opt/bastion && git fetch && git checkout $(git tag | tail -1) )`) should really do the job as I see it here. Could you run it and paste the output? (note that this time, it *will* upgrade your instance!).

BreizhHardware commented

2026-05-07 00:18:36 +02:00

Author

Owner

@matth94 commented on GitHub (Sep 22, 2022):

@matth94 commented on GitHub (Sep 22, 2022): ![Capture d’écran du 2022-09-22 22-03-20](https://user-images.githubusercontent.com/7020154/191841025-0029c677-e7d2-4839-b3cf-f850ec3fa347.png)

BreizhHardware commented

2026-05-07 00:18:36 +02:00

Author

Owner

@speed47 commented on GitHub (Sep 23, 2022):

Seems good, this instance should now advertise v3.09.00 when you use it!

Don't forget to complete the upgrade process by running the install script in upgrade mode (see https://ovh.github.io/the-bastion/installation/upgrading.html)

@speed47 commented on GitHub (Sep 23, 2022): Seems good, this instance should now advertise `v3.09.00` when you use it! Don't forget to complete the upgrade process by running the install script in upgrade mode (see https://ovh.github.io/the-bastion/installation/upgrading.html)

BreizhHardware commented

2026-05-07 00:18:36 +02:00

Author

Owner

@matth94 commented on GitHub (Sep 23, 2022):

Hello and thanks for your help.
I put you the end of the return of the order
# /opt/bastion/bin/admin/install --upgrade

and if I redo the previous commands I still have the impression of being in version 3.05.01 :

@matth94 commented on GitHub (Sep 23, 2022): Hello and thanks for your help. I put you the end of the return of the order \# /opt/bastion/bin/admin/install --upgrade ![Capture d’écran du 2022-09-23 11-44-22](https://user-images.githubusercontent.com/7020154/191937940-878e4a74-0954-40d1-a932-5a91c1c66f4f.png) and if I redo the previous commands I still have the impression of being in version 3.05.01 : ![Capture d’écran du 2022-09-23 11-51-45](https://user-images.githubusercontent.com/7020154/191937409-999f044d-70e9-4616-b6a1-e9ad7cfbaad3.png)

BreizhHardware commented

2026-05-07 00:18:36 +02:00

Author

Owner

@speed47 commented on GitHub (Sep 26, 2022):

Wait, there is a typo in the command you typed, I didn't notice it the other day, you typed:
( umask 0022 && cd /opt/bastion && git fetch && git checkout &(git tag | tail -1) )
instead of:
( umask 0022 && cd /opt/bastion && git fetch && git checkout $(git tag | tail -1) )

The difference is hard to see, but the character before "git tag" at the end of the command must be a $, not a &.

@speed47 commented on GitHub (Sep 26, 2022): Wait, there is a typo in the command you typed, I didn't notice it the other day, you typed: `( umask 0022 && cd /opt/bastion && git fetch && git checkout &(git tag | tail -1) )` instead of: `( umask 0022 && cd /opt/bastion && git fetch && git checkout $(git tag | tail -1) )` The difference is hard to see, but the character before "git tag" at the end of the command must be a `$`, not a `&`.

BreizhHardware commented

2026-05-07 00:18:37 +02:00

Author

Owner

@matth94 commented on GitHub (Sep 26, 2022):

awesome, thank you. this typo nearly drove me crazy...

@matth94 commented on GitHub (Sep 26, 2022): awesome, thank you. this typo nearly drove me crazy...

BreizhHardware commented

2026-05-07 00:18:37 +02:00

Author

Owner

@speed47 commented on GitHub (Sep 26, 2022):

Hehe, and I was really wondering what was happening with your system!

There will be an easier command to upgrade, soon, directly through --osh adminUpgrade for accounts with admin level. This'll avoid having to type complicated commands such as the one above, and also verify that the release is genuine (signed with GPG).

Closing as resolved then, please reopen if needed!

@speed47 commented on GitHub (Sep 26, 2022): Hehe, and I was really wondering what was happening with your system! There will be an easier command to upgrade, soon, directly through `--osh adminUpgrade` for accounts with admin level. This'll avoid having to type complicated commands such as the one above, and also verify that the release is genuine (signed with GPG). Closing as resolved then, please reopen if needed!

BreizhHardware referenced this issue

2026-05-07 00:19:52 +02:00

[PR #82] [MERGED] bump to v3.01.02 #221