Bug 1878854 - [Assisted-4.6] [Staging] download kubeconfig has a default bad name kubeconfig-noingress
Summary: [Assisted-4.6] [Staging] download kubeconfig has a default bad name kubeconfi...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: assisted-installer
Version: 4.6
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Igal Tsoiref
QA Contact: Yuri Obshansky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-14 17:08 UTC by Ido Ovadia
Modified: 2023-06-28 08:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-30 21:01:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ido Ovadia 2020-09-14 17:08:41 UTC 
Description of problem:
=======================
download kubeconfig has a default bad name kubeconfig-noingress


Version-Release number of selected component:
=============================================
Current Application:
Clusters
Application Path:
/openshift/assisted-installer/clusters/f30fba37-b243-48de-9d76-a6bdd169d00a
Chrome Version:
8c3ed2ee756a054cfac24c7934bcc88a3ae3c8ee
Dashboard Version:
f1526b623238e8ef386a178a86bad276ba205122
Inventory Version:
a45b358582697a8d98f00e52fd775645896c3301
Remediations Version:
1de53dd4fde78fecae0693f46928f1cb4e397447
Vulnerability Version:
ef1fc91cb32ce6e574616f97a055948aaa5643fe
Compliance Version:
12b1b44fa95a3d5f871a4ebae58614fd0dad8436
Cost Management Version:
f2260b4db54da4bdb8aa5d507e8d5e232000fc5f
Advisor Version:
01eb85a2f3b826233d55bc7cc78e7808768f630c
Drift Version:
9a4e02d2bdf857ab201145a3f8467efa3bd75f15
Migration Analytics Version:
7f37fa8e9fa0d29d8b1d7be8ba4cfe22979cdaff
Automation Hub Version:
5884daee9a75b899e0788324ab9cf61ede96af08
Automation Analytics Version:
89f9692730b63bf77849b61bfd25950e68a21678
Policies Version:
e928d3b90fde56f16cb008f06f9f54c9167b94ff
Patch Version:
06a89f0acca7f84ee64f99ddc78ead0c5b43fadc
Automation Services Catalog Version:
98fb9e1bcca8681282b2e2f1c84391a4e454c1b9
Approval Version:
76dbd9fc2ba4fbf99d00282bb48bf20c38cacf33
Sources Version:
7524e34d2a0a0459fc8ccaaa6475ef9469ded496


How reproducible:
=================
100%


Steps to Reproduce:
===================
1. Start cluster installation 
2. when 'Download kubeconfig' button is enable, click on it


Actual results:
===============
The default name for downloaded file is kubeconfig-noingress


Expected results:
=================
The name should be kubeconfig
Comment 1 Igal Tsoiref 2020-09-30 21:01:19 UTC 
it was meant to be kubeconfig-noingress.
Comment 2 Franck Baudin 2023-06-28 06:56:50 UTC 
@itsoiref can you explain why sometimes the file is named kubeconfig and sometimes kubeconfig-noingress? As an end user, deploying again and again the same cluster, is it an indication that something went wrong/differently?
Comment 3 Igal Tsoiref 2023-06-28 08:37:38 UTC 
When we start installation kubeconfig doesn't have ingress-ca in it and in order to show that it is different file that misses some data we called it kubeconfig-noigress.
After we upload ingress-ca file will be called kubeconfig
Note You need to log in before you can comment on or make changes to this bug.