Uploaded image for project: 'Red Hat Service Interconnect (Skupper)'
  1. Red Hat Service Interconnect (Skupper)
  2. SKUPPER-1284

podman type skupper gateway doesn't recover from a failed image pull

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      If you attempt to create a Docker or Podman gateway, and Skupper is unable to pull the required images, the gateway cannot be configured. You might be unable to pull images because the machine is not authenticated with the Red Hat Container Registry.

      Workaround:
      $ skupper gateway delete

      Complete the steps in https://access.redhat.com/RegistryAuthentication

      Recreate your gateway
      Show
      If you attempt to create a Docker or Podman gateway, and Skupper is unable to pull the required images, the gateway cannot be configured. You might be unable to pull images because the machine is not authenticated with the Red Hat Container Registry. Workaround: $ skupper gateway delete Complete the steps in https://access.redhat.com/RegistryAuthentication Recreate your gateway

      On your RHEL machine - if you're not logged in to the podman registry before issuing the skupper gateway command, all subsequent skupper gateway commands will fail. Only a skupper delete "clean slate" will help.

      [mnagel@testing-rhel-hel-1 ~]$ podman logout registry.redhat.io
      Removed login credentials for registry.redhat.io
      [mnagel@testing-rhel-hel-1 ~]$ skupper status
      Skupper is not enabled in namespace 'mnagel-dev'
      
      [mnagel@testing-rhel-hel-1 ~]$ skupper init --enable-console --enable-flow-collector --console-auth unsecured
      clusterroles.rbac.authorization.k8s.io "skupper-service-controller" not found
      Skupper is now installed in namespace 'mnagel-dev'.  Use 'skupper status' to get more information.
      [mnagel@testing-rhel-hel-1 ~]$ skupper gateway init --config simple_podman.yaml --type podman
      Error: Failed to start gateway as container: Trying to pull registry.redhat.io/service-interconnect/skupper-router-rhel9:2.4.2...
      Error: initializing source docker://registry.redhat.io/service-interconnect/skupper-router-rhel9:2.4.2: unable to retrieve auth token: invalid username/password: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/RegistryAuthentication
      
      [mnagel@testing-rhel-hel-1 ~]$ podman login registry.redhat.io
      Username: mnagel@redhat.com
      Password: 
      Login Succeeded!
      [mnagel@testing-rhel-hel-1 ~]$ skupper gateway init --config simple_podman.yaml --type podman
      Error: qdr agent error: Failed to create connection: dial tcp 127.0.0.1:36973: connect: connection refused
      [mnagel@testing-rhel-hel-1 ~]$ skupper delete
      Skupper is now removed from 'mnagel-dev'.
      
      [mnagel@testing-rhel-hel-1 ~]$ skupper init --enable-console --enable-flow-collector --console-auth unsecured
      clusterroles.rbac.authorization.k8s.io "skupper-service-controller" not found
      Skupper is now installed in namespace 'mnagel-dev'.  Use 'skupper status' to get more information.
      [mnagel@testing-rhel-hel-1 ~]$ skupper status
      Skupper is enabled for namespace "mnagel-dev" in interior mode. It is not connected to any other sites. It has no exposed services.
      The site console url is:  https://skupper-mnagel-dev.apps.sandbox-m4.g2pi.p1.openshiftapps.com
      [mnagel@testing-rhel-hel-1 ~]$ skupper gateway init --config simple_podman.yaml --type podman
      Skupper gateway: 'testing-rhel-hel-1-mnagel'. Use 'skupper gateway status' to get more information.
       

       

            ansmith@redhat.com Andrew Smith
            mnagel@redhat.com Markus Nagel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: