Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-18699

Web Console Shows Non-printable file detected

XMLWordPrintable

    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when editing a file an error `Info alert:Non-printable file detected. File contains non-printable characters. Preview is not available.` is presented. With this update, a check was added to determine if a file is binary, and you are able to edit the file as expected. (link:https://issues.redhat.com/browse/OCPBUGS-18699[*OCPBUGS-18699*])
      Show
      * Previously, when editing a file an error `Info alert:Non-printable file detected. File contains non-printable characters. Preview is not available.` is presented. With this update, a check was added to determine if a file is binary, and you are able to edit the file as expected. (link: https://issues.redhat.com/browse/OCPBUGS-18699 [* OCPBUGS-18699 *])
    • Bug Fix
    • Done

      Description of problem:

      Openshift Console shows "Info alert:Non-printable file detected. File contains non-printable characters. Preview is not available." while edit an XML file type configmaps.

      Version-Release number of selected component (if applicable):

       

      How reproducible:

       

      Steps to Reproduce:

      1. Create configmap from file:
      # oc create cm test-cm --from-file=server.xml=server.xml
      configmap/test-cm created
      
      2. If we try to edit the configmap in the OCP console we see the following error:
      
      Info alert:Non-printable file detected.
      File contains non-printable characters. Preview is not available.
      
      

      Actual results:

       

      Expected results:

       

      Additional info:

       

              rhn-engineering-rhamilto Robb Hamilton
              rhn-support-ssardar Sameer Sardar
              Xiyun Zhao Xiyun Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: