# Portworx essential 2.5 failing to install on OCP 4.5 on AWS

**URL:** <https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614>\
**Category:** Portworx on Kubernetes\
**Created:** [October 21, 2020, 1:02pm UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614 "2020-10-21T13:02:49Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Satya](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/satya/32/237_2.png) [@Satya](https://forums.portworx.com/u/Satya)\
**Post date:** [October 21, 2020, 1:02pm UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/1 "2020-10-21T13:02:49Z")

</div>

Trying to install Portworx essential 2.5 on an OCP 4.5 cluster on AWS. It is failing with following error:

$ oc exec $PX\_POD -n kube-system – /opt/pwx/bin/pxctl status  
Defaulting container name to portworx.  
Use ‘oc describe pod/portworx-8fvf9 -n kube-system’ to see all of the containers in this pod.  
PX is not running on this host: Could not reach 'HealthMonitor’List of last known failures:Type ID Resource Severity Count LastSeen FirstSeen Description  
NODE FileSystemDependency ip-10-0-171-59 ALARM 1 Oct 21 07:33:43 UTC 2020 Oct 21 07:33:43 UTC 2020 Failed to find patch fs dependency on remote site for kernel 4.18.0-193.24.1.el8\_2.dt1.x86\_64, exiting…  
NODE PortworxMonitorSchedulerInitializationFailed ip-10-0-171-59 ALARM 1 Oct 21 07:02:59 UTC 2020 Oct 21 07:02:59 UTC 2020 Could not init scheduler ‘kubernetes’: Could not find my node in Kubernetes cluster: Get [https://172.30.0.1:443/api/v1/nodes](https://172.30.0.1/api/v1/nodes): dial tcp 172.30.0.1:443: connect: no route to host  
command terminated with exit code 1

---

<div class="post-metadata">

**Author:** ![sanjay.naikwadi](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/sanjay.naikwadi/32/35_2.png) [@sanjay.naikwadi](https://forums.portworx.com/u/sanjay.naikwadi)\
**Post date:** [October 21, 2020, 1:12pm UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/2 "2020-10-21T13:12:43Z")

</div>

Can you share the complete logs from one of the worker/compute node ?  
`journalctl -lu portworx* > /tmp/px-fail.log`

---

<div class="post-metadata">

**Author:** ![Satya](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/satya/32/237_2.png) [@Satya](https://forums.portworx.com/u/Satya)\
**Post date:** [October 21, 2020, 1:33pm UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/3 "2020-10-21T13:33:03Z")

</div>

> [@sanjay.naikwadi](#):
>
> journalctl -lu portworx\*

– Logs begin at Wed 2020-10-21 09:44:12 UTC, end at Wed 2020-10-21 13:31:48 UTC. –  
Oct 21 13:25:50 ip-10-0-132-7 systemd[1]: Listening on Portworx logging FIFO.  
Oct 21 13:25:50 ip-10-0-132-7 systemd[1]: Started Portworx FIFO logging reader.  
Oct 21 13:25:50 ip-10-0-132-7 systemd[1]: Starting Portworx OCI Container…  
Oct 21 13:25:50 ip-10-0-132-7 systemd[1]: Started Portworx OCI Container.  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg=“Rootfs found at /var/opt/pwx/oci/rootfs”  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg=“PX binaries found at /var/opt/pwx/bin/px-runc”  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg=“Initializing as version 2.5.7.0-686a134 (OCI)”  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg=“SPEC READ [1ef01fb2ba5288a806834cfb1d7c4304 /var/opt/pwx/oci/config.json]”  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg=“Enabling Sharedv4 NFS support …”  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg=“Setting up NFS service”  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg=“\> Initialized service controls via DBus{type:dbus,svc:nfs-server.service,id:0xc4201d7180}”  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg=“Checking mountpoints for following shared directories: [/var/lib/kubelet /var/lib/osd]”  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg="Found following mountpoints for shared dirs: map[/var/lib/kubelet:{isMP=f,Opts=shared:3,Pare\>  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg="PX-RunC arguments: -b -c px-cluster-d547b53f-7253-4336-b058-41e389fdda2b -kvdb\_dev type=gp2,\>  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg="PX-RunC mounts: /dev:/dev /etc/exports:/etc/exports /opt/pwx/oci/mounts/etc/hosts:/etc/hosts\>  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg="PX-RunC env: ALERTMANAGER\_PORTWORX\_PORT=tcp://172.30.75.232:9093 ALERTMANAGER\_PORTWORX\_PORT\_\>  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg=“Switched ‘/var/opt/pwx/oci’ to PRIVATE mount propagation”  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg=“Found 2 usable runc binaries: /var/opt/pwx/bin/runc and /var/opt/pwx/bin/runc-fb”  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg=“Detected kernel release 4.18.0-193”  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:50Z” level=info msg="Exec: ["/var/opt/pwx/bin/runc" "run" "-b" "/var/opt/pwx/oci" "–no-new-keyring" "\>  
Oct 21 13:25:50 ip-10-0-132-7 portworx[605595]: Executing with arguments: -b -c px-cluster-d547b53f-7253-4336-b058-41e389fdda2b -kvdb\_dev type=gp2,size=150 -s type=gp2,size=1000 -secre\>  
Oct 21 13:25:51 ip-10-0-132-7 portworx[605595]: Wed Oct 21 13:25:51 UTC 2020 : Running version 2.5.7.0-686a134 on Linux ip-10-0-132-7 4.18.0-193.24.1.el8\_2.dt1.x86\_64 #1 SMP Thu Sep 24\>  
Oct 21 13:25:51 ip-10-0-132-7 portworx[605595]: Version: Linux version 4.18.0-193.24.1.el8\_2.dt1.x86\_64 ([mockbuild@x86-vm-08.build.eng.bos.redhat.com](mailto:mockbuild@x86-vm-08.build.eng.bos.redhat.com)) (gcc version 8.3.1 20191121 (Red \>  
Oct 21 13:25:51 ip-10-0-132-7 portworx[605595]: time=“2020-10-21T13:25:51Z” level=error msg="Cannot listen on UNIX socket: listen unix /run/docker/plugins/pxd.sock: bind: no such file \>  
Oct 21 13:25:51 ip-10-0-132-7 portworx[605595]: Error: failed to listen on pxd.sock  
Oct 21 13:25:51 ip-10-0-132-7 portworx[605595]: checking /hostusr/src/kernels/4.18.0-193.24.1.el8\_2.dt1.x86\_64  
Oct 21 13:25:51 ip-10-0-132-7 portworx[605595]: checking /hostusr/src/linux-headers-4.18.0-193.24.1.el8\_2.dt1.x86\_64  
Oct 21 13:25:51 ip-10-0-132-7 portworx[605595]: checking /usr/src/kernels/4.18.0-193.24.1.el8\_2.dt1.x86\_64  
Oct 21 13:25:51 ip-10-0-132-7 portworx[605595]: found /usr/src/kernels/4.18.0-193.24.1.el8\_2.dt1.x86\_64  
Oct 21 13:25:51 ip-10-0-132-7 portworx[605595]: checking /usr/src/kernels/4.18.0-193.24.1.el8\_2.dt1.x86\_64  
Oct 21 13:25:51 ip-10-0-132-7 portworx[605595]: found /usr/src/kernels/4.18.0-193.24.1.el8\_2.dt1.x86\_64  
Oct 21 13:25:51 ip-10-0-132-7 portworx[605595]: checking /usr/src/kernels/4.18.0-193.24.1.el8\_2.dt1.x86\_64  
Oct 21 13:25:51 ip-10-0-132-7 portworx[605595]: found /usr/src/kernels/4.18.0-193.24.1.el8\_2.dt1.x86\_64  
Oct 21 13:25:51 ip-10-0-132-7 portworx[605595]: ln: failed to create symbolic link ‘compiler-gcc5.h’: Read-only file system  
Oct 21 13:25:53 ip-10-0-132-7 portworx[605595]: Using /usr/src/kernels/4.18.0-193.24.1.el8\_2.dt1.x86\_64 with defines CC=gcc-8  
Oct 21 13:25:53 ip-10-0-132-7 portworx[605595]: Creating px fs…  
Oct 21 13:25:56 ip-10-0-132-7 portworx[605595]: Using cluster: px-cluster-d547b53f-7253-4336-b058-41e389fdda2b  
Oct 21 13:25:56 ip-10-0-132-7 portworx[605595]: Using kvdb device: type=gp2,size=150  
Oct 21 13:25:56 ip-10-0-132-7 portworx[605595]: Warning skipping device exists check for: type=gp2,size=150.  
Oct 21 13:25:56 ip-10-0-132-7 portworx[605595]: Using storage device: type=gp2,size=1000  
Oct 21 13:25:56 ip-10-0-132-7 portworx[605595]: Using scheduler: kubernetes  
Oct 21 13:25:56 ip-10-0-132-7 portworx[605595]: Warning skipping device validation check for: type=gp2,size=1000.  
Oct 21 13:25:57 ip-10-0-132-7 portworx[605595]: checking remote download site, please wait…  
Oct 21 13:25:57 ip-10-0-132-7 portworx[605595]: Failed to find patch fs dependency on remote site for kernel 4.18.0-193.24.1.el8\_2.dt1.x86\_64, exiting…  
Oct 21 13:25:57 ip-10-0-132-7 systemd[1]: portworx.service: Main process exited, code=exited, status=10/n/a  
Oct 21 13:25:57 ip-10-0-132-7 systemd[1]: portworx.service: Failed with result ‘exit-code’.  
Oct 21 13:25:57 ip-10-0-132-7 systemd[1]: portworx.service: Consumed 6.432s CPU time  
Oct 21 13:25:57 ip-10-0-132-7 systemd[1]: Stopping Portworx FIFO logging reader…  
Oct 21 13:25:57 ip-10-0-132-7 systemd[1]: Stopped Portworx FIFO logging reader.  
Oct 21 13:25:57 ip-10-0-132-7 systemd[1]: portworx-output.service: Consumed 33ms CPU time  
Oct 21 13:25:57 ip-10-0-132-7 systemd[1]: Closed Portworx logging FIFO.  
Oct 21 13:25:57 ip-10-0-132-7 systemd[1]: portworx.socket: Consumed 0 CPU time

---

<div class="post-metadata">

**Author:** ![sanjay.naikwadi](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/sanjay.naikwadi/32/35_2.png) [@sanjay.naikwadi](https://forums.portworx.com/u/sanjay.naikwadi)\
**Post date:** [October 21, 2020, 1:36pm UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/4 "2020-10-21T13:36:55Z")

</div>

Can you attach the complete log file ? Just don’t share the content, I will need to go through complete log to understand it.

---

<div class="post-metadata">

**Author:** ![Satya](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/satya/32/237_2.png) [@Satya](https://forums.portworx.com/u/Satya)\
**Post date:** [October 21, 2020, 1:46pm UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/5 "2020-10-21T13:46:41Z")

</div>

Hi Sanjay,

I don’t see an option to attach a text file here, tried with the upload button but it says: “Sorry, the file you are trying to upload is not authorized (authorized extensions: jpg, jpeg, png, gif, heic, heif).”

---

<div class="post-metadata">

**Author:** ![sanjay.naikwadi](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/sanjay.naikwadi/32/35_2.png) [@sanjay.naikwadi](https://forums.portworx.com/u/sanjay.naikwadi)\
**Post date:** [October 21, 2020, 2:04pm UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/6 "2020-10-21T14:04:48Z")

</div>

You can use : [https://gist.github.com/](https://gist.github.com/) or Pastebin or save the file in above extension and upload I will rename and check it.

---

<div class="post-metadata">

**Author:** ![Satya](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/satya/32/237_2.png) [@Satya](https://forums.portworx.com/u/Satya)\
**Post date:** [October 21, 2020, 2:10pm UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/7 "2020-10-21T14:10:21Z")

</div>

> [@Satya](#):
>
> jpg

> <https://gist.github.com/satyamodi/bd110c4fac6ea074ba3552b5b1b700d0>

---

<div class="post-metadata">

**Author:** ![sanjay.naikwadi](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/sanjay.naikwadi/32/35_2.png) [@sanjay.naikwadi](https://forums.portworx.com/u/sanjay.naikwadi)\
**Post date:** [October 21, 2020, 2:23pm UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/8 "2020-10-21T14:23:11Z")

</div>

Satya,

Can you install the latest version 2.6 ? looks like it is failing to detect the latest kernel version with 2.5.7. Can you give a try with latest release of 2.6.1.3 which has support for the latest kernel.

---

<div class="post-metadata">

**Author:** ![Satya](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/satya/32/237_2.png) [@Satya](https://forums.portworx.com/u/Satya)\
**Post date:** [October 21, 2020, 2:24pm UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/9 "2020-10-21T14:24:20Z")

</div>

Sure, I will try with 2.6 version and will update you with the results.

---

<div class="post-metadata">

**Author:** ![Satya](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/satya/32/237_2.png) [@Satya](https://forums.portworx.com/u/Satya)\
**Post date:** [October 21, 2020, 3:09pm UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/10 "2020-10-21T15:09:02Z")

</div>

> [@sanjay.naikwadi](#):
>
> journalctl -lu portworx\* \> /tmp/px-fail.log

It is still failing for 2.6 as well. Is it some port issue?  
[https://gist.github.com/satyamodi/784bff332b5a4e55c009447251e72c98](https://gist.github.com/satyamodi/784bff332b5a4e55c009447251e72c98)

---

<div class="post-metadata">

**Author:** ![sanjay.naikwadi](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/sanjay.naikwadi/32/35_2.png) [@sanjay.naikwadi](https://forums.portworx.com/u/sanjay.naikwadi)\
**Post date:** [October 21, 2020, 3:36pm UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/11 "2020-10-21T15:36:05Z")

</div>

No its not port issue, its kernel dependency issue,  
`Failed to find patch fs dependency on remote site for kernel 4.18.0-193.24.1.el8_2.dt1.x86_64, exiting..`

Can you tell what is the operator version you have installed ?

---

<div class="post-metadata">

**Author:** ![Satya](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/satya/32/237_2.png) [@Satya](https://forums.portworx.com/u/Satya)\
**Post date:** [October 21, 2020, 3:54pm UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/12 "2020-10-21T15:54:28Z")

</div>

it’s Portworx 1.4.0.

 ![Screenshot 2020-10-21 at 9.23.19 PM](https://canada1.discourse-cdn.com/flex030/uploads/portworx1/original/1X/ecc464ba27e01f4493d598ee17a2ddf873f20336.png)

---

<div class="post-metadata">

**Author:** ![Satya](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/satya/32/237_2.png) [@Satya](https://forums.portworx.com/u/Satya)\
**Post date:** [October 22, 2020, 6:51am UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/14 "2020-10-22T06:51:06Z")

</div>

Any update on this issue.

---

<div class="post-metadata">

**Author:** ![sanjay.naikwadi](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/sanjay.naikwadi/32/35_2.png) [@sanjay.naikwadi](https://forums.portworx.com/u/sanjay.naikwadi)\
**Post date:** [October 22, 2020, 8:06am UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/15 "2020-10-22T08:06:18Z")

</div>

Can you do the following :

- Download the following module  
[http://mirrors.portworx.com/build-results/pxfuse/for-installer/x86\_64/4.18.0-193.24.1.el8\_2.dt1.x86\_64/version/10/px.ko](http://mirrors.portworx.com/build-results/pxfuse/for-installer/x86_64/4.18.0-193.24.1.el8_2.dt1.x86_64/version/10/px.ko)

- Copy the downloaded module in following directory e.g (keep the name as given): `/var/lib/osd/pxfs/latest/8.px.ko`

- Once copied on all worker nodes, restart the portworx service `systemctl restart portworx`

And let me know how it goes, if anything fails please share the logs again.

---

<div class="post-metadata">

**Author:** ![Satya](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/satya/32/237_2.png) [@Satya](https://forums.portworx.com/u/Satya)\
**Post date:** [October 22, 2020, 8:48am UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/16 "2020-10-22T08:48:44Z")

</div>

It is still failing after i copied px.ko to all three worker nodes and restarted the portworx service.

[core@ip-10-0-132-7 ~] ls -ltr /var/lib/osd/pxfs/latest/8.px.ko -rw-r--r--. 1 root root 2391816 Oct 22 08:17 /var/lib/osd/pxfs/latest/8.px.ko [core@ip-10-0-132-7 ~] date  
Thu Oct 22 08:45:44 UTC 2020

attaching logs for the same, it contains yesterday’s logs as well.

> <https://gist.github.com/satyamodi/09ebf57981c47f0933b31ab35d1b6a31>

---

<div class="post-metadata">

**Author:** ![sanjay.naikwadi](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/sanjay.naikwadi/32/35_2.png) [@sanjay.naikwadi](https://forums.portworx.com/u/sanjay.naikwadi)\
**Post date:** [October 23, 2020, 6:18am UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/17 "2020-10-23T06:18:07Z")

</div>

Can you restart the Portworx service again and check ? some changes have been made and updated the repo.

---

<div class="post-metadata">

**Author:** ![Satya](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/satya/32/237_2.png) [@Satya](https://forums.portworx.com/u/Satya)\
**Post date:** [October 23, 2020, 9:16am UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/18 "2020-10-23T09:16:08Z")

</div>

Now px volumes are getting created but it is not stable, it de-attaches instantly. Attaching all the logs.

PX\_POD=(oc get pods -l name=portworx -n kube-system -o jsonpath=’{.items[0].metadata.name}’)  
$ oc exec $PX\_POD -n kube-system – /opt/pwx/bin/pxctl status  
Defaulting container name to portworx.  
Use ‘oc describe pod/portworx-7pprp -n kube-system’ to see all of the containers in this pod.  
PX is not running on this host: Could not reach ‘HealthMonitor’

List of last known failures:

Type ID Resource Severity Count LastSeen FirstSeen Description  
NODE NodeStartFailure 7d9de820-b8b6-4171-a94a-6f2d812e9029 ALARM 1 Oct 23 09:10:56 UTC 2020 Oct 23 09:10:56 UTC 2020 Failed to start Portworx: failed in internal kvdb setup: failed to create a kvdb connection to peer internal kvdb nodes dial tcp 10.0.135.69:9019: connect: connection refused. Make sure peer kvdb nodes are healthy.  
NODE KvdbConnectionFailed 7d9de820-b8b6-4171-a94a-6f2d812e9029 ALARM 1 Oct 23 09:10:50 UTC 2020 Oct 23 09:10:50 UTC 2020 Internal Kvdb: failed to create a kvdb connection to peer internal kvdb nodes dial tcp 10.0.135.69:9019: connect: connection refused. Make sure peer kvdb nodes are healthy.  
NODE PortworxMonitorInstallFailed ip-10-0-151-22 ALARM 1 Oct 23 08:59:40 UTC 2020 Oct 23 08:59:40 UTC 2020 Could not finalize OCI install: Timeout  
NODE PortworxMonitorSchedulerInitializationFailed ip-10-0-151-22 ALARM 1 Oct 23 08:54:35 UTC 2020 Oct 23 08:54:35 UTC 2020 Could not init scheduler ‘kubernetes’: Could not find my node in Kubernetes cluster: Get [https://172.30.0.1:443/api/v1/nodes:](https://172.30.0.1:443/api/v1/nodes:) dial tcp 172.30.0.1:443: connect: no route to host  
command terminated with exit code 1

> <https://gist.github.com/satyamodi/384c418526383c089f5d76a4c0e4f380>

---

<div class="post-metadata">

**Author:** ![sanjay.naikwadi](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/sanjay.naikwadi/32/35_2.png) [@sanjay.naikwadi](https://forums.portworx.com/u/sanjay.naikwadi)\
**Post date:** [October 23, 2020, 10:03am UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/19 "2020-10-23T10:03:36Z")

</div>

Satya,

I see that following error : "Failed to attach DriveSet (3b897f20-9729-4dc0-a633-0d00709130f8): Availability zone misma\>

Can you share the output of `oc get nodes --show-labels` and your spec file used for install

---

<div class="post-metadata">

**Author:** ![Satya](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/satya/32/237_2.png) [@Satya](https://forums.portworx.com/u/Satya)\
**Post date:** [October 23, 2020, 10:11am UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/20 "2020-10-23T10:11:31Z")

</div>

Updated the link with the output at the end:

> <https://gist.github.com/satyamodi/384c418526383c089f5d76a4c0e4f380>

#Portworx Operator will install pods only on nodes that have the label `node-role.kubernetes.io/compute=true`

I am labeling the nodes using a shell script:  
WORKER\_NODES=`oc get nodes | grep worker | awk '{print $1}'`  
for wnode in ${WORKER\_NODES[@]}; do  
oc label nodes $wnode [node-role.kubernetes.io/compute=true](http://node-role.kubernetes.io/compute=true)  
done

Following ports are open for master and worker security groups:  
aws ec2 authorize-security-group-ingress --group-id $WORKER\_GROUP\_ID --protocol tcp --port 17001-17020 --source-group $MASTER\_GROUP\_ID

aws ec2 authorize-security-group-ingress --group-id $WORKER\_GROUP\_ID --protocol tcp --port 17001-17020 --source-group $WORKER\_GROUP\_ID

aws ec2 authorize-security-group-ingress --group-id $WORKER\_GROUP\_ID --protocol tcp --port 111 --source-group $MASTER\_GROUP\_ID

aws ec2 authorize-security-group-ingress --group-id $WORKER\_GROUP\_ID --protocol tcp --port 111 --source-group $WORKER\_GROUP\_ID

aws ec2 authorize-security-group-ingress --group-id $WORKER\_GROUP\_ID --protocol tcp --port 2049 --source-group $MASTER\_GROUP\_ID

aws ec2 authorize-security-group-ingress --group-id $WORKER\_GROUP\_ID --protocol tcp --port 2049 --source-group $WORKER\_GROUP\_ID

aws ec2 authorize-security-group-ingress --group-id $WORKER\_GROUP\_ID --protocol tcp --port 20048 --source-group $MASTER\_GROUP\_ID

aws ec2 authorize-security-group-ingress --group-id $WORKER\_GROUP\_ID --protocol tcp --port 20048 --source-group $WORKER\_GROUP\_ID

aws ec2 authorize-security-group-ingress --group-id $WORKER\_GROUP\_ID --protocol tcp --port 9001-9022 --source-group $MASTER\_GROUP\_ID

aws ec2 authorize-security-group-ingress --group-id $WORKER\_GROUP\_ID --protocol tcp --port 9001-9022 --source-group $WORKER\_GROUP\_ID

---

<div class="post-metadata">

**Author:** ![Satya](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/satya/32/237_2.png) [@Satya](https://forums.portworx.com/u/Satya)\
**Post date:** [October 27, 2020, 5:48am UTC](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614/21 "2020-10-27T05:48:08Z")

</div>

Hi,  
Any update on this issue.

[Next page](https://forums.portworx.com/t/portworx-essential-2-5-failing-to-install-on-ocp-4-5-on-aws/614.md?page=2)
