How to report issues (Release TWO): Difference between revisions

From OSM Public Wiki
Jump to: navigation, search
(Created page with "If you have bugs or issues to be reported, please use Bugzilla: https://osm.etsi.org/bugzilla If you have questions or feedback, feel free to contact us through the mailing l...")
 
No edit summary
Line 1: Line 1:
If you have bugs or issues to be reported, please use Bugzilla: https://osm.etsi.org/bugzilla
'''If you have bugs or issues to be reported, please use Bugzilla: https://osm.etsi.org/bugzilla'''


If you have questions or feedback, feel free to contact us through the mailing list 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'''
 
When reporting an issue to Bugzilla or to the mailing list, please provide the following information:
* In case of an installation issue, provide the full command used to run the installer and the full output of the installer.
* Logs of the SO, UI and RO (see [[Logs and troubleshooting (Release TWO)|here]] to know 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 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

Revision as of 11:27, 28 April 2017

If you have bugs or issues to be reported, please use Bugzilla: https://osm.etsi.org/bugzilla

If you have questions or feedback, feel free to contact us through the mailing list OSM_TECH@list.etsi.org

When reporting an issue to Bugzilla or to the mailing list, please provide the following information:

  • In case of an installation issue, provide the full command used to run the installer and the full output of the installer.
  • Logs of the SO, UI and RO (see here to know 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 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