Uploaded image for project: 'Service Orchestrator'
  1. Service Orchestrator
  2. SO-1609

Invalid HEAT template for neutron network in SO

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Low Low
    • None
    • Dublin Release
    • Master branch ONAP on Integration-OOM-Staging-Daily

      The HEAT template for Neutron network has some invisible special character in it. When instantiating neutron network for vCPE use case, the following error shows in so-openstack-adapter debug.log: 

       

      2019-03-07T16:39:04.409Z|5eaa17ee-4ca8-42f7-8d56-3cbb63772b0e| org.onap.so.openstack.utils.MsoHeatUtils - ERROR STATUS = 400, 
      Bad Request 
      Bad Request 
      2019-03-07T16:39:04.413Z|5eaa17ee-4ca8-42f7-8d56-3cbb63772b0e| org.onap.so.openstack.utils.MsoCommonUtils - RA_CONNECTION_EXCEPTION 300 Exception - Openstack Error on CreateStack : Explanation [ code='400', tit
       in "<unicode string>", line 22, column 3: 
       subnet_f56cd698-c50a-499a-9177-e ... 
       ^ 
      expected <block end>, but found '<block mapping start>' 
       in "<unicode string>", line 33, column 4: 
       network: 
       ^' ] ] 
      2019-03-07T16:39:04.414Z|5eaa17ee-4ca8-42f7-8d56-3cbb63772b0e| org.onap.so.openstack.utils.MsoCommonUtils - The server could not comply with the request since it is either malformed or otherwise incorrect., err
       in "<unicode string>", line 22, column 3: 
       subnet_f56cd698-c50a-499a-9177-e ... 
       ^ 
      expected <block end>, but found '<block mapping start>' 
       in "<unicode string>", line 33, column 4: 
       network: 
       ^ 
      

       

      This is a chronic problem since at least Casablanca. 

       

        1. BPMN.debug.log
          4.26 MB
        2. debug.2019-03-14.0.log.zip
          103 kB
        3. neutron.sh
          0.6 kB
        4. neutron.yaml
          0.5 kB

            xuyang11 xuyang11
            xuyang11 xuyang11
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: