Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[1.21 release] Can't not start multus DaemonSet in an air-gapped environment #1332

Closed
bk201 opened this issue Jul 15, 2021 · 4 comments · Fixed by #1342
Closed

[1.21 release] Can't not start multus DaemonSet in an air-gapped environment #1332

bk201 opened this issue Jul 15, 2021 · 4 comments · Fixed by #1342

Comments

@bk201
Copy link
Member

bk201 commented Jul 15, 2021

Environmental Info:
RKE2 Version: v1.21.2+rke2r1

Node(s) CPU architecture, OS, and Version:
A KVM VM. On RancherOSv2.

Cluster Configuration:
Single node server provision.

Describe the bug:
Multus DaemonSet is not running in an air-gapped environment.

Steps To Reproduce:

  • Try Installed RKE2 in air-gapped environment.
  • Prepare and copy these image tarballs to /var/lib/rancher/rke2/agent/images/:
    rke2-images.linux-amd64.tar.zst
    rke2-images-multus.linux-amd64.tar.zst
    
  • Start rke-server with the config:
    cni: multus,canal
    
  • Wait for kube-multus-xxx to be provisioned.

Expected behavior:
Status of pod kube-multus-ds-pn577 should be running.

Actual behavior:
Status of pod kube-multus-ds-pn577 is Init:ImagePullBackOff.

Additional context / logs:

$ kubectl describe -n kube-system pod kube-multus-ds-pn577
...
Init Containers:
  cni-plugins:
    Container ID:
    Image:          rancher/hardened-cni-plugins:v0.9.1-build20210414
    Image ID:
    Port:           <none>
    Host Port:      <none>
    State:          Waiting
      Reason:       ImagePullBackOff
    Ready:          False
...
Events:
  Type     Reason     Age                  From               Message
  ----     ------     ----                 ----               -------
  Normal   Scheduled  11m                  default-scheduler  Successfully assigned kube-system/kube-multus-ds-pn577 to node1
  Warning  Failed     11m                  kubelet            Failed to pull image "rancher/hardened-cni-plugins:v0.9.1-build20210414": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/rancher/hardened-cni-plugins:v0.9.1-build20210414": failed to resolve reference "docker.io/rancher/hardened-cni-plugins:v0.9.1-build20210414": failed to do request: Head "https://registry-1.docker.io/v2/rancher/hardened-cni-plugins/manifests/v0.9.1-build20210414": dial tcp: lookup registry-1.docker.io on 127.0.0.1:53: read udp 127.0.0.1:40327->127.0.0.1:53: read: connection refused

Looks like image rancher/hardened-cni-plugins is missing in the building script.

@brandond
Copy link
Contributor

@manuelbuil can you take a look at this?

@brandond brandond added this to To Triage in Development [DEPRECATED] via automation Jul 15, 2021
@brandond brandond added this to the v1.22 - Backlog milestone Jul 15, 2021
@manuelbuil
Copy link
Contributor

Environmental Info:
RKE2 Version: v1.21.2+rke2r1

Node(s) CPU architecture, OS, and Version:
A KVM VM. On RancherOSv2.

Cluster Configuration:
Single node server provision.

Describe the bug:
Multus DaemonSet is not running in an air-gapped environment.

Steps To Reproduce:

* Try Installed RKE2 in air-gapped environment.

* Prepare and copy these image tarballs to `/var/lib/rancher/rke2/agent/images/`:
  ```
  rke2-images.linux-amd64.tar.zst
  rke2-images-multus.linux-amd64.tar.zst
  ```

* Start rke-server with the config:
  ```
  cni: multus,canal
  ```

* Wait for `kube-multus-xxx` to be provisioned.

Expected behavior:
Status of pod kube-multus-ds-pn577 should be running.

Actual behavior:
Status of pod kube-multus-ds-pn577 is Init:ImagePullBackOff.

Additional context / logs:

$ kubectl describe -n kube-system pod kube-multus-ds-pn577
...
Init Containers:
  cni-plugins:
    Container ID:
    Image:          rancher/hardened-cni-plugins:v0.9.1-build20210414
    Image ID:
    Port:           <none>
    Host Port:      <none>
    State:          Waiting
      Reason:       ImagePullBackOff
    Ready:          False
...
Events:
  Type     Reason     Age                  From               Message
  ----     ------     ----                 ----               -------
  Normal   Scheduled  11m                  default-scheduler  Successfully assigned kube-system/kube-multus-ds-pn577 to node1
  Warning  Failed     11m                  kubelet            Failed to pull image "rancher/hardened-cni-plugins:v0.9.1-build20210414": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/rancher/hardened-cni-plugins:v0.9.1-build20210414": failed to resolve reference "docker.io/rancher/hardened-cni-plugins:v0.9.1-build20210414": failed to do request: Head "https://registry-1.docker.io/v2/rancher/hardened-cni-plugins/manifests/v0.9.1-build20210414": dial tcp: lookup registry-1.docker.io on 127.0.0.1:53: read udp 127.0.0.1:40327->127.0.0.1:53: read: connection refused

Looks like image rancher/hardened-cni-plugins is missing in the building script.

Yes, that's the problem! We forgot to add hardened-cni-plugins image. Thanks for the report :)

@manuelbuil manuelbuil moved this from To Triage to Working in Development [DEPRECATED] Jul 16, 2021
Development [DEPRECATED] automation moved this from Working to Done Issue / Merged PR Jul 16, 2021
@brandond brandond moved this from Done Issue / Merged PR to To Test in Development [DEPRECATED] Aug 6, 2021
@brandond
Copy link
Contributor

brandond commented Aug 6, 2021

reopening; missed QA testing

@brandond brandond reopened this Aug 6, 2021
Development [DEPRECATED] automation moved this from To Test to Working Aug 6, 2021
@brandond brandond moved this from Working to To Test in Development [DEPRECATED] Aug 6, 2021
@rancher-max
Copy link
Contributor

Validated on v1.21.3+rke2r1

Can deploy airgap with multus using any method: private registry, tarball

Development [DEPRECATED] automation moved this from To Test to Done Issue / Merged PR Aug 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development [DEPRECATED]
Done Issue / Merged PR
Development

Successfully merging a pull request may close this issue.

4 participants