Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-2422

Failed to create first user by API

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Blocker
    • None
    • quay-v3.6.0
    • quay, quay-operator
    • None
    • False
    • False
    • PROJQUAY-1453 - Disconnected Mirroring Appliance
    • Quay Enterprise
    • undefined
    • 0

    Description

      Description of problem:

      Failed to create first user by API

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

      quay-operator-bundle-container-v3.6.0-12

      • Index image v4.5: registry-proxy.engineering.redhat.com/rh-osbs/iib:99038
      • Index image v4.6: registry-proxy.engineering.redhat.com/rh-osbs/iib:99039
      • Index image v4.7: registry-proxy.engineering.redhat.com/rh-osbs/iib:99046
      • Index image v4.8: registry-proxy.engineering.redhat.com/rh-osbs/iib:99052

      quay-operator-container-v3.6.0-13

      • registry-proxy.engineering.redhat.com/rh-osbs/quay-quay-operator-rhel8@sha256:a36dfd94f41997aec2d2436f2d4a6aaca7615b52cc291592aff6f34a623370d6

      quay-registry-container-v3.6.0-28

      • registry-proxy.engineering.redhat.com/rh-osbs/quay-quay-rhel8@sha256:a4cad2c70cd340029d00f468fc08cab887365d17fe22bbf31beeec36aebeb9e7

      How reproducible:

      Always

      Steps to Reproduce:
      1. enable FEATURE_USER_INITIALIZE to true
      2. create use by API

      $ curl --location -X POST 'https://quay-quay-quay36.router-default.apps.dyan819.qe.devcluster.openshift.com/api/v1/user/initialize' --header 'Content-Type: application/json' --data-raw '

      {username: "dyan", password: "quaydyan", email: "dyan+test@redhat.com", access_token: true }

      ' -k -v

      Actual results:

      failed with error

      $  curl --location -X POST 'https://quay-quay-quay36.router-default.apps.dyan819.qe.devcluster.openshift.com/api/v1/user/initialize' --header 'Content-Type: application/json' --data-raw '{username: "dyan",
    password: "quaydyan",
    email: "dyan+test@redhat.com",
    access_token: true
}' -k -v
Note: Unnecessary use of -X or --request, POST is already inferred.
*   Trying 18.189.245.107:443...
* Connected to quay-quay-quay36.router-default.apps.dyan819.qe.devcluster.openshift.com (18.189.245.107) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: CN=*.apps.dyan819.qe.devcluster.openshift.com
*  start date: Aug 18 03:12:33 2021 GMT
*  expire date: Aug 18 03:12:34 2023 GMT
*  issuer: CN=ingress-operator@1629256231
*  SSL certificate verify result: self signed certificate in certificate chain (19), continuing anyway.
> POST /api/v1/user/initialize HTTP/1.1
> Host: quay-quay-quay36.router-default.apps.dyan819.qe.devcluster.openshift.com
> User-Agent: curl/7.71.1
> Accept: */*
> Content-Type: application/json
> Content-Length: 104
> 
* upload completely sent off: 104 out of 104 bytes
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Mark bundle as not supporting multiuse
< HTTP/1.1 400 BAD REQUEST
< server: nginx/1.14.1
< date: Wed, 18 Aug 2021 11:50:03 GMT
< content-type: text/html
< content-length: 192
< set-cookie: e7089a47e915e38f54edfbcc95743cc7=c5c49620b07504cd794995254eb7947a; path=/; HttpOnly; Secure; SameSite=None
< 
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>400 Bad Request</title>
<h1>Bad Request</h1>
<p>The browser (or proxy) sent a request that this server could not understand.</p>
* Connection #0 to host quay-quay-quay36.router-default.apps.dyan819.qe.devcluster.openshift.com left intact

      Expected results:

      succeed

      Additional info:

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. PROJQUAY-1926 As an admin, I want an API to create first user, so I can automate deployment.

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. PROJQUAY-2567 Document creating first user using API

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              rhn-support-dyan Dongbo Yan
              Dongbo Yan Dongbo Yan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: