action #15148
closedcoordination #9486: [sle][opensuse][functional][epic][y]Network Installations
[sle][functional][y] Network Installations - HTTPS
0%
Updated by okurz over 7 years ago
- Copied from action #15146: Network Installations - FTP/HTTP/NFS added
Updated by okurz over 7 years ago
- Assignee set to maritawerner
Please check if HTTPS is a supported scenario.
Updated by zluo over 7 years ago
https? We haven't supported this protocol for manual installation over network.
Updated by okurz over 7 years ago
- Status changed from New to Feedback
yes, you are right. It looks like this was never supported, e.g. never mentioned on http://docserv.suse.de/documents/SLES12-SP2/SLES-deployment/ . The only fate entries which I could find which mention https at all regarding SLE are https://fate.suse.com/320130 and https://fate.suse.com/320129 where on both the discussion is ongoing (and recent) how it should look like for SP3 so let's wait a bit and maybe it will be resolved then
Updated by okurz over 7 years ago
- Subject changed from Network Installations - HTTPS to [blocked:fate#320130] Network Installations - HTTPS
Updated by maritawerner about 7 years ago
- Assignee deleted (
maritawerner) - Priority changed from Low to High
Clarified with Anja: we need to test that. Priority is high since the parent ticket has priority high as well.
Updated by mkravec about 7 years ago
https://fate.suse.com/320130 was rejected for SLE12-SP3 and evaluation was moved to SLE13. Can we close this issue?
Updated by maritawerner about 7 years ago
According to Oli that Feature is not related to the task to install over https. Any expert advice is welcome here.
Updated by okurz about 7 years ago
maritawerner wrote:
According to Oli that Feature is not related to the task to install over https.
The fate entries talk about 'https boot', i.e. booting the kernel and installer over https and not downloading packages from within the installer with https.
So there are two different features to discuss:
- 'https boot' as described in https://fate.suse.com/320130. the issue is rejected for sle12sp3 -> my proposal: do not do anything here
- 'access installation repositories over https which is mentioned e.g. in http://docserv.suse.de/documents/SLES12-SP2/SLES-deployment/single-html/#sec.appdendix.parm.yast2 which I think is feasible to test but probably easier to do for openSUSE in a post-validation test (using published repositories) because https://download.opensuse.org/ can be accessed over https. Maybe like in https://openqa.opensuse.org/tests/369188#step/bootloader/7 one can give the HTTP url instead of https although there is no explicit way to select it
@maritawerner: agreed?
Updated by maritawerner about 7 years ago
Let me double check with Frederic/Anja if they are fine with testing only on openSUSE or if we need to add SLES later.
Updated by okurz over 6 years ago
- Status changed from Feedback to In Progress
- Target version set to Milestone 12
so https://fate.suse.com/320130 has been rejected for all relevant products but a submission to openSUSE:Factory had been made so worth to try
Updated by okurz over 6 years ago
- Subject changed from [blocked:fate#320130] Network Installations - HTTPS to [blocked:fate#320130][sle][functional] Network Installations - HTTPS
Updated by okurz over 6 years ago
- Subject changed from [blocked:fate#320130][sle][functional] Network Installations - HTTPS to [sle][functional] Network Installations - HTTPS
- Target version changed from Milestone 12 to Milestone 14
actually not blocked then so we could start
Updated by okurz about 6 years ago
- Due date deleted (
2018-03-13) - Target version changed from Milestone 14 to Milestone 17
M14 is too full. Better we focus more on fixing.
Updated by okurz about 6 years ago
- Copied to action #34108: [sle][functional][y] Network Installations - remote installation over https with self-signed certificate added
Updated by okurz about 6 years ago
- Subject changed from [sle][functional] Network Installations - HTTPS to [sle][functional][u] Network Installations - HTTPS
- Description updated (diff)
- Due date set to 2018-08-28
- Status changed from In Progress to Workable
- Target version changed from Milestone 17 to Milestone 18
should follow #34108
Updated by okurz almost 6 years ago
- Target version changed from Milestone 18 to Milestone 18
Updated by okurz over 5 years ago
- Subject changed from [sle][functional][u] Network Installations - HTTPS to [sle][functional][y] Network Installations - HTTPS
- Status changed from Workable to Blocked
#34108 should be done first, then this one.
Updated by riafarov over 5 years ago
- Due date changed from 2018-08-28 to 2018-09-11
Will get unblocked soon, we should also discuss it, as we cover https with self-signed cert on osd and with trusted on o3.
Updated by maritawerner over 5 years ago
Hi Rodion, I saw that you discussed that topic in the IRC recently. I got the request to test that really a long time ago, I have no further input here.
Updated by riafarov over 5 years ago
Right, I see that ticket is quite old. Following fate is mentioned https://fate.suse.com/320130 and I believe that in #34108 we are addressing different component. Therefore, I would like to clarify it when okurz is back from vacation before we invest a lot of efforts in the test which wasn't requested.
Updated by riafarov over 5 years ago
- Status changed from Blocked to Resolved
As per comment in #34108