How to report issues (Release THREE): Difference between revisions
From OSM Public Wiki
Garciadeblas (talk | contribs) (Created page with "'''If you have bugs or issues to be reported, please use Bugzilla: https://osm.etsi.org/bugzilla or write us to OSM_TECH@list.etsi.org''' '''If you have questions or feedbac...") |
Garciadeblas (talk | contribs) No edit summary |
||
| Line 11: | Line 11: | ||
* In case of operational issues, the following information might help: | * In case of operational issues, the following information might help: | ||
** Version of OSM that you are using | ** Version of OSM that you are using | ||
** Logs of the SO, UI and RO. Check https://osm.etsi.org/wikipub/index.php/Logs_and_troubleshooting_( | ** Logs of the SO, UI and RO. Check https://osm.etsi.org/wikipub/index.php/Logs_and_troubleshooting_(Release_THREE) to know how to get them. | ||
** Details on the actions you made to get that error so that we could reproduce it. | ** Details on the actions you made to get that error so that we could reproduce it. | ||
** IP network details in order to help troubleshooting potential network issues. For instance: | ** IP network details in order to help troubleshooting potential network issues. For instance: | ||
Revision as of 10:04, 7 September 2017
If you have bugs or issues to be reported, please use Bugzilla: https://osm.etsi.org/bugzilla or write us to OSM_TECH@list.etsi.org
If you have questions or feedback, feel free to contact us through the mailing list OSM_TECH@list.etsi.org
Please be patient. Answers may take a few days.
Please provide some context to your answers. As an example, find below some guidelines:
- In case of an installation issue, the full command used to run the installer and the full output of the installer (or at least enough context) might help on finding the solution.
- In case of operational issues, the following information might help:
- Version of OSM that you are using
- Logs of the SO, UI and RO. Check https://osm.etsi.org/wikipub/index.php/Logs_and_troubleshooting_(Release_THREE) to know how to get them.
- Details on the actions you made to get that error so that we could reproduce it.
- IP network details in order to help troubleshooting potential network issues. For instance:
- Client IP address (browser, command line client, etc.) from where you are trying to access OSM
- IP address of the machine where OSM is running
- IP addresses of the containers
- NAT rules in the machine where OSM is running
Common sense applies here, so you don't need to send everything, but just enough information to diagnose the issue and find a proper solution.