Bug 1924701
Summary: | Cluster destroy fails when using byo with Kuryr | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Maysa Macedo <mdemaced> |
Component: | Networking | Assignee: | Maysa Macedo <mdemaced> |
Networking sub component: | kuryr | QA Contact: | GenadiC <gcheresh> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | high | CC: | mdulko, rlobillo |
Version: | 4.7 | ||
Target Milestone: | --- | ||
Target Release: | 4.8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-07-27 22:40:55 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Maysa Macedo
2021-02-03 13:30:20 UTC
Failed on OCP4.7.0-0.nightly-2021-02-09-024347 on OSP13 (2021-01-20.1) with amphoras The cluster destroy operation is unexpectedly removing a FIP that was created before running the installation: 1. Subnet creation: $ openstack network create manual-machine-network $ openstack subnet create manual-machine-subnet --network manual-machine-network --gateway 10.196.0.1 --subnet-range 10.196.0.0/16 --dns-nameserver 10.46.0.31 $ openstack router create machine-router $ openstack router set machine-router --external-gateway nova $ openstack router add subnet machine-router manual-machine-subnet 2. Installer VM creation: (overcloud) $ openstack flavor create --ram 8192 --disk 40 --vcpus 2 --public m1.medium (shiftstackrc) $ wget http://download.devel.redhat.com/released/RHEL-8/8.2.0/BaseOS/x86_64/images/rhel-guest-image-8.2-290.x86_64.qcow2 $ openstack image create "rhel74" --file rhel-guest-image-8.2-290.x86_64.qcow2 --disk-format qcow2 --container-format bare $ openstack security group create admin_sg --description admin_sg_group $ openstack security group rule create --protocol tcp --dst-port 22:22 --remote-ip 0.0.0.0/0 admin_sg $ openstack security group rule create --protocol icmp admin_sg $ openstack server create --flavor m1.medium --image rhel74 --key-name id_rsa --nic net-id=manual-machine-network --security-group admin_sg installer $ openstack floating ip set --port $port_id <FLOATING_IP> >> Login on the installer server and modify /etc/hosts to the vip >> copy shiftstackrc, overcloudrc, clouds.yaml, install-config.yaml, oc client and openshift-intaller. >> install certificate and run update-ca-trust extract >> cp ~/.ssh/id_rsa from undercloud to installer 3. Perform installation: $ ./4.7.0-0.nightly-2021-02-09-024347/openshift-install create cluster --dir ostest --log-level debug with this install-config.yaml: # This file is autogenerated by infrared openshift plugin apiVersion: v1 baseDomain: "shiftstack.com" clusterID: "8854a853-fe89-5a0f-a2d6-e73a0d36db72" compute: - name: worker platform: openstack: zones: [] replicas: 3 controlPlane: name: master platform: openstack: zones: [] replicas: 3 metadata: name: "ostest" networking: clusterNetworks: - cidr: 10.128.0.0/14 hostSubnetLength: 9 serviceCIDR: 172.30.0.0/16 machineCIDR: 10.196.0.0/16 type: "Kuryr" platform: openstack: externalNetwork: "nova" cloud: "shiftstack" region: "regionOne" computeFlavor: "m4.xlarge" machinesSubnet: 4366eda4-fc14-4c90-b283-4ada12be45c5 pullSecret: <hidden> once installation is finished, run the destroy: (shiftstack) [cloud-user@installer ~]$ ./4.7.0-0.nightly-2021-02-09-024347/openshift-install destroy cluster --dir ostest --log-level debug DEBUG OpenShift Installer 4.7.0-0.nightly-2021-02-09-024347 DEBUG Built from commit c0489117068cb00c5222bb0762a87605f41ebe04 DEBUG Removing interfaces from custom router DEBUG Removing Subnet "c15427a2-93c4-4375-b09a-12fed0275c57" from Router "86c37080-31a2-4aca-a361-5f9ba19b8ab5" ...and lost connectivity to the installer VM. I reconnected to the undercloud and I checked that the installer VM had lost its FIP. I attached again and saw that the cluster destroy was performed successfully. Verified on OCP4.8.0-0.nightly-2021-02-21-102854 over OSP13 (2021-01-20.1) with amphora provider. FIPless Cluster is correctly destroyed without removing unexpected resources: $ openshift-install destroy cluster --dir ostest --log-level debug [...] DEBUG Purging asset "Metadata" from disk DEBUG Purging asset "Master Ignition Customization Check" from disk DEBUG Purging asset "Worker Ignition Customization Check" from disk DEBUG Purging asset "Terraform Variables" from disk DEBUG Purging asset "Kubeconfig Admin Client" from disk DEBUG Purging asset "Kubeadmin Password" from disk DEBUG Purging asset "Certificate (journal-gatewayd)" from disk DEBUG Purging asset "Cluster" from disk INFO Time elapsed: 16m32s Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438 |