I just upgraded my test environment to 4.2.4, and ...
# fleet
b
I just upgraded my test environment to 4.2.4, and when I am trying to get to one of the hosts I get sent to a 500 error page.
n
Can you please add a screenshot of your browsers “Network” tab when you encounter the 500 page in this thread?
b
Actually I think I am able to pin point things a bit. From the “Show Error” button that I completely missed the first time:
Copy code
sql: Scan error on column index 5, name "vulnerabilities": src=[{"cve": "CVE-2020-25676", "details_link": "<https://nvd.nist.gov/vuln/detail/CVE-2020-25676>"},{"cve": "CVE-2020-27750", "details_link": "<https://nvd.nist.gov/vuln/detail/CVE-2020-27750>"},{"cve": "CVE-2020-27751", "details_link": "<https://nvd.nist.gov/vuln/detail/CVE-2020-27751>"},{"cve": "CVE-2020-27752", "details_link": "<https://nvd.nist.gov/vuln/detail/CVE-2020-27752>"},{"cve": "CVE-2020-27753", "details_link": "<https://nvd.nist.gov/vuln/detail/CVE-2020-27753>"},{"cve": "CVE-2020-27754", "details_link": "<https://nvd.nist.gov/vuln/detail/CVE-2020-27754>"},{"cve": "CVE-2020-27755", "details_link": "<https://nvd.nist.gov/vuln/detail/CVE-2020-27755>"},{"cve": "CVE-2020-27757", "details_link": "<https://nvd.nist.gov/vuln/detail/CVE-2020-27757>"},{"cve": "CVE-2020-27758", "details_link": "<https://nvd.nist.gov/vuln/detail/CVE-2020-27758>"},{"cve": "CVE-2020-27759", "details_link": "<https://nvd.nist.gov/vuln/detail/CVE-2020-27759>"},{"cve": "CVE-2020-27760", "details_link": "<https://nvd.nist.gov/vuln/detail/CVE-2020-27760>"},{]: invalid character ']' looking for beginning of object key string
It would make sense it is a vulnerabilities thing, as the host page that is reachable does not have any cve’s listed against it from fleet.
This was an upgrade from 4.2.2 to 4.2.4.
n
Thank you for the quick report. Are you ok with me using your above error message in a bug report issue on GitHub?
b
Yup - I am not seeing any identifying information so we should be good.
ty 1
n
Great, I just filed the following bug report issue here: https://github.com/fleetdm/fleet/issues/1923
👍 1
There is a known workaround here: https://github.com/fleetdm/fleet/issues/1923#issuecomment-912068812 In addition, this issue will be fixed in the upcoming minor release of Fleet.