Uploaded image for project: 'Quarkus'
  1. Quarkus
  2. QUARKUS-1724

Deploy a serverless application into ocp doesn't work

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Blocker
    • None
    • 2.2.5.GA, 2.2.5.CR2
    • OpenShift, team/docs
    • None
    • Hide
      == Stability issues for deployment of a serverless application into OCP


      .Description

      Deploying a serverless application on OCP can trigger an error in OpenStack nodes, causing the service to fail deploying. As a result, users cannot use OCP in production with guaranteed stability.

      This issue has been observed in the following software:

      OpenShift Version: 4.8
      Quarkus Version: 2.2.5.Final
      Knative Operator version: Red Hat OpenShift Serverless: 1.19.0

      For more information about this issue, see link:https://issues.redhat.com/browse/QUARKUS-1752[QUARKUS-1724].
      Show
      == Stability issues for deployment of a serverless application into OCP .Description Deploying a serverless application on OCP can trigger an error in OpenStack nodes, causing the service to fail deploying. As a result, users cannot use OCP in production with guaranteed stability. This issue has been observed in the following software: OpenShift Version: 4.8 Quarkus Version: 2.2.5.Final Knative Operator version: Red Hat OpenShift Serverless: 1.19.0 For more information about this issue, see link: https://issues.redhat.com/browse/QUARKUS-1752 [ QUARKUS-1724 ].

    Description

      Why is Blocker

      This issue is blocker because, from a user point of view, they are not going to be able to use Knative in production (is not reliable)

      Versions

      Openshift Version: 4.8
      Quarkus Version: 2.2.5.Final
      Knative operator version: Red Hat OpenShift Serverless: 1.19.0

      Description

      When I try to deploy a "hello world" service on Knative I am getting the following error on OpenStack nodes: 

      Jan 20 10:06:47.882287 ocp48-p7msz-worker-0-ngnpm hyperkube[1986]: I0120 10:06:47.882234    1986 cloud_request_manager.go:115] "Node addresses from cloud provider for node not collected" nodeName=ocp48-p7msz-worker-0-ngnpm err="unexpected status code when reading instance address from http://169.254.169.254/2009-04-04/meta-data/local-ipv4: 429 Too Many Requests"

      The service is not deployed.

      Attachments

        Activity

          People

            ikanello1@redhat.com Ioannis Kanellos
            rhn-support-pagonzal Pablo Gonzalez Granados (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: