After upgarding the GitLab CE v17.1.1 to v17.2.0, two bugs/issues i have noticed

General
1

Hi GitLab Community,

After updating the GitLab CE v17.1.1 to v17.2.0, Admin area > Monitoring > System information ( not working , 500 error page ), if GitLab CE v17.1.1 it was like “System info”
, now that is changed to System information after updates, if i see the logs of /var/log/gitlab/gitlab-monitor/current ,
2020-03-14_07:20:54.75442 chpst: fatal: unable to run: /opt/gitlab/embedded/bin/gitlab-mon: file does not exist → this error i am facing, $ sudo gitlab-ctl restart && sudo gitlab-ctl reconfigure ## is working fine without any issue,

Also another issue i am facing is “Unable to search the project in the search bar”

Please, let me know that these are bugs and could be fixed in the next release.

Thanks,
Best Regards,
Asif.

1 Like
2

Unfortunately, I have the same problem. Everything else seems to be running smoothly.

I was not able to find a solution.

1 Like
3

Short Update from my end:

I have a testing installation with version 17.2.0 under Ubuntu in my Homelab and have the same problem. seems to be a problem with the version.

1 Like
4

yes, seems like it is the problem with the version, the question is how to let them ( the Gitlab CE developers ) know this issue, will this issues get ignored i am afraid, just hoping that this issue will be resolved in the next version release…

5

Not just only a CE issue. The EE has the same issue.

What makes me curious, why there aren’t any more complaints about it. Did I miss any notes?

6

I agree with you 100%, I am also wondering why there are no complaints about these issues with this version, it’s bit shocking for me, we eagerly waiting for the next release, i just hope these are bugs and they are working on it…

7

Thanks for your feedback. A 500 error sounds like a server side problem and could be a bug.

I’d encourage you to create bug reports using this template https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Bug GitLab engineers can triage and take action on these issues.

1 Like
8

For refference, if someone has the same issue.

@dnsmichi thank you, opened a ticket, with as much information i can provide.

2 Likes
9

there is a update available , can you check by upadting it , it may be can resolve the issue?

10

Hello @asifmohammed.infanio, i kindly ask you to have a look in the issue ticket. The new version 17.2.1 does not solved the issue for me. But if the MR gets approved, maybe one of the upcoming verson. Also you can find a possible workaround.

1 Like
11

I tried to create issues but did not have permission to.

12

I think there is no need to open another issue ticket for this.

13

does our concern or bug report reached to GitLab CE developers?
before we close this?

14

FYI, the division by zero bug is tracked in two issues, with linked MR fixes. Suggest subscribing to follow which releases these fixes get picked into.

  1. GitLab 17.2.0 | Error 500 at /admin/system_info (#474279) · Issues · GitLab.org / GitLab · GitLab (reported by @oevcil in this topic)
  2. system_info - Error 500 [Disk Usage - Template::Error (divided by 0) ] (#473622) · Issues · GitLab.org / GitLab · GitLab
15

There is a workaround that worked for me:

https://gitlab.com/gitlab-org/gitlab/-/issues/474279#note_2014662867

It’s about adding the (nsfs) mount type exclusion in system_info_controller.rb to prevent the bug. You have to restart GitLab after updating the file. I guess this fix will be release soon.