#support

Issue with v0.17.0 Update - UI Showing v0.16.2

TLDR Kenichi updated to v0.17.0 but still saw v0.16.2 in the UI. Prashant fixed the issue by syncing the tag to the latest release/v0.17.0.

9mo

Join the chat

Mar 13, 2023 (9 months ago)

Photo of md5-55ebaccb72aae09299778a88ec57c478

Kenichi

07:33 PM

👋:skin-tone-4: hello folks, I'm checking on a very minor issue - I've updated to the v0.17.0 tag, but still see v0.16.2 in the UI with the updates available warning. Did I do something wrong, not do something required, or is that expected? HEAD detached at v0.17.0

Image 1 for :wave::skin-tone-4: hello folks, I'm checking on a very minor issue - I've updated to the v0.17.0 tag, but still see v0.16.2 in the UI with the updates available warning. Did I do something wrong, not do something required, or is that expected? `HEAD detached at v0.17.0`

Mar 14, 2023 (9 months ago)

Photo of md5-8df7ce0274b2473ec07403336e48b574

Pranay

02:15 AM

Kenichi How did you upgrade to the latest version?

Photo of md5-f936d3e5743d23344d6c60813189716f

vishal-signoz

02:36 AM

Looks like your frontend image was not updated

Kenichi

04:29 PM

ok i will make sure to pull latest images and retry, thanks!

Mar 16, 2023 (9 months ago)

Kenichi

12:24 AM

thanks for the hint - it looks like this was not updated yet in the tagged version, but is on ~~main~~ develop

https://github.com/SigNoz/signoz/blob/v0.17.0/deploy/docker/clickhouse-setup/docker-compose.yaml#L184

vishal-signoz

02:16 AM

Prashant Version is not updated in tagged version

Photo of md5-1899629483c7ab1dccfbee6cc2f637b9

Prashant

05:52 AM

Srikanth It looks like the old git tag was created before pinning the version and it was not auto updated post-release.

05:53

Prashant

05:53 AM

I have synced the tag to latest release/v0.17.0 where version is pinned.

Photo of md5-ce04a9988e2fd758a659dc55be6f2543

Srikanth

06:05 AM

I don’t follow where it is not pinned? Look at the last commit of the tagged version and it is the commit to pin the versions.

Prashant

06:39 AM

the git tag was pointing to previous commit where the docker-compose tags were not updated.

06:39

Prashant

06:39 AM

It is fixed now.

06:41

Prashant

06:41 AM

Kenichi could you please git checkout to the release/v0.17.0 branch and use that instead?

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 1023 threads (61% resolved)

Join Our Community

Similar Threads

Services UI Goes Blank Due to Retention Issue with S3 Bucket

oluchi reports issue with services UI going blank after a while. Conversation explores possible reasons, such as S3 connection problems and disk space, but no resolution is reached.

7mo

Error Upgrading Chart Version in Kubernetes Environment

Manikandan encountered an error when upgrading to a different chart version. Srikanth helps correct the mistake by suggesting to pull the new releases and upgrade.

7mo

Troubleshooting SigNoz Docker Setup Issue

Nishant had trouble running the Signoz docker setup after cleaning old version images. Srikanth suggested running migration for upgrading. After following the advice, Nishant successfully ran the setup.

5mo

SigNoz Install Script Errors

Nishant encountered errors with the install.sh script. Prashant suggested using `bash install.sh` or `./install.sh` instead of `sh`.

7mo

Increasing Persistent Volume Size in Test Environment

surya tried to increase the disk size in their test environment and encountered an issue. Prashant provided guidance and the user successfully increased the Persistent Volume (PV) for ClickHouse to 50Gi.

yesterday