Uploaded image for project: 'ONOS'
  1. ONOS
  2. ONOS-3997

ONOS layer3 support nova user-metadata

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.4.0
    • Fix Version/s: 1.6.0
    • Component/s: None
    • Labels:

      Description

      In ONOSFW project proposed in OPNFV community(https://wiki.opnfv.org/collaborative_development_projects/onosfw); it need to run Functest(https://wiki.opnfv.org/functextnexttaks) in CI, and we found There are 11 failed tests out of 210 in Tempest which (we think) are related to nova metadata service not supported by onos yet. these would cause two results.

      1. when OpenStack started and user load a virtual machine, nova will use this service to connect VM, it will try 20 times and each time will keep on 10s, so when loading vm, it will needs 200+s. thats too long.

      Starting network...
      udhcpc (v1.20.1) started
      Sending discover...
      Sending select for 192.168.111.9...
      Lease of 192.168.111.9 obtained, lease time 600
      route: SIOCADDRT: File exists
      WARN: failed: route add -net "0.0.0.0/0" gw "192.168.111.1"
      cirros-ds 'net' up at 9.95
      checking http://169.254.169.254/2009-04-04/instance-id
      failed 1/20: up 10.36. request failed
      failed 2/20: up 22.98. request failed
      failed 3/20: up 35.23. request failed
      failed 4/20: up 47.52. request failed
      failed 5/20: up 59.98. request failed
      failed 6/20: up 72.25. request failed
      failed 7/20: up 84.49. request failed
      failed 8/20: up 96.74. request failed
      failed 9/20: up 109.32. request failed
      failed 10/20: up 121.58. request failed
      failed 11/20: up 133.84. request failed
      failed 12/20: up 146.08. request failed
      failed 13/20: up 158.43. request failed
      failed 14/20: up 170.80. request failed
      failed 15/20: up 183.03. request failed
      failed 16/20: up 195.26. request failed
      failed 17/20: up 207.52. request failed
      failed 18/20: up 219.95. request failed
      failed 19/20: up 232.22. request failed
      failed 20/20: up 244.44. request failed
      failed to read iid from metadata. tried 20
      no results found for mode=net. up 256.69. searched: nocloud configdrive ec2
      failed to get instance-id of datasource
      Starting dropbear sshd: generating rsa key... generating dsa key... OK
      

      2. Some tests need to pass the ssh-key to the instances using that service. it is releated to Authentication feature.

      Starting network...
      udhcpc (v1.20.1) started
      Sending discover...
      Sending select for 10.0.0.5...
      Lease of 10.0.0.5 obtained, lease time 600
      route: SIOCADDRT: File exists
      WARN: failed: route add -net "0.0.0.0/0" gw "10.0.0.1"
      cirros-ds 'net' up at 9.34
      checking http://169.254.169.254/2009-04-04/instance-id
      successful after 1/20 tries: up 9.62. iid=i-00000017
      failed to get http://169.254.169.254/2009-04-04/meta-data/public-keys
      warning: no ec2 metadata for public-keys
      failed to get http://169.254.169.254/2009-04-04/user-data
      warning: no ec2 metadata for user-data
      found datasource (ec2, net)
      Starting dropbear sshd: generating rsa key... generating dsa key... OK
      /run/cirros/datasource/data/user-data was not '#!' or executable
      

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            • Assignee:
              wuwb1989 Wu wenbin
              Reporter:
              Ohenry jiang rui
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: