[Starlingx-discuss] Issue w/ openssh blocking sanity execution
Hello all, We are seeing issues with ssh after installing controller-0 with a load built on 2018-11-25. The ssh daemon is not started by default on the controller. This issue is seen in multiple labs and is blocking automated sanity execution. This issue was not seen in a load built on 2018-11-22. Is anyone else testing in master and seeing this issue? Looking at the code submissions between 2018-11-22 & 2018-11-25, I see the following change: ./cgcs-root/stx/stx-integ 36dc17738d9e2ef5dab689a556d7d8f33415861e Fri Nov 23 22:09:59 2018 +0000 Gerrit Code Review Merge "Refactor patches for openssh package" ./cgcs-root/stx/stx-integ 1c8c71654ff6f20cf13bcceeb861d969fd5b53a8 Wed Nov 21 01:21:12 2018 +0000 zhipeng liu Refactor patches for openssh package I'm not sure if that's the root-cause, but it needs to be investigated. Zhipeng/Cindy, Please investigate. Launchpad: https://bugs.launchpad.net/starlingx/+bug/1805157 Thanks, Ghada
The update added a new openssh-config package for the customizations we have to the configuration files. However, it also has a %post script command that disables sshd: https://review.openstack.org/#/c/619003/4/base/openssh-config/centos/openssh... %{_bindir}/systemctl disable sshd.service > /dev/null 2>&1 || : I don't know why that would be added, as we don't do that in the openssh package today. Maybe it was intended to be a restart to pick up the config changes, but it wouldn't strictly be needed for the install. The commit message says the following testing was done: Deployment test and ping test between VMs pass Config files check pass. so I'm surprised this issue wasn't seen during testing for this update. From: Khalil, Ghada [mailto:Ghada.Khalil@windriver.com] Sent: Monday, November 26, 2018 1:59 PM To: starlingx-discuss@lists.starlingx.io; Liu, ZhipengS; Xie, Cindy Subject: [Starlingx-discuss] Issue w/ openssh blocking sanity execution Importance: High Hello all, We are seeing issues with ssh after installing controller-0 with a load built on 2018-11-25. The ssh daemon is not started by default on the controller. This issue is seen in multiple labs and is blocking automated sanity execution. This issue was not seen in a load built on 2018-11-22. Is anyone else testing in master and seeing this issue? Looking at the code submissions between 2018-11-22 & 2018-11-25, I see the following change: ./cgcs-root/stx/stx-integ 36dc17738d9e2ef5dab689a556d7d8f33415861e Fri Nov 23 22:09:59 2018 +0000 Gerrit Code Review Merge "Refactor patches for openssh package" ./cgcs-root/stx/stx-integ 1c8c71654ff6f20cf13bcceeb861d969fd5b53a8 Wed Nov 21 01:21:12 2018 +0000 zhipeng liu Refactor patches for openssh package I'm not sure if that's the root-cause, but it needs to be investigated. Zhipeng/Cindy, Please investigate. Launchpad: https://bugs.launchpad.net/starlingx/+bug/1805157 Thanks, Ghada
Hi Ghada and Don, I will check and update it today, thanks for your information! Zhipeng From: Penney, Don [mailto:Don.Penney@windriver.com] Sent: 2018年11月27日 3:11 To: Khalil, Ghada <Ghada.Khalil@windriver.com>; starlingx-discuss@lists.starlingx.io; Liu, ZhipengS <zhipengs.liu@intel.com>; Xie, Cindy <cindy.xie@intel.com> Subject: RE: Issue w/ openssh blocking sanity execution The update added a new openssh-config package for the customizations we have to the configuration files. However, it also has a %post script command that disables sshd: https://review.openstack.org/#/c/619003/4/base/openssh-config/centos/openssh... %{_bindir}/systemctl disable sshd.service > /dev/null 2>&1 || : I don’t know why that would be added, as we don’t do that in the openssh package today. Maybe it was intended to be a restart to pick up the config changes, but it wouldn’t strictly be needed for the install. The commit message says the following testing was done: Deployment test and ping test between VMs pass Config files check pass. so I’m surprised this issue wasn’t seen during testing for this update. From: Khalil, Ghada [mailto:Ghada.Khalil@windriver.com] Sent: Monday, November 26, 2018 1:59 PM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>; Liu, ZhipengS; Xie, Cindy Subject: [Starlingx-discuss] Issue w/ openssh blocking sanity execution Importance: High Hello all, We are seeing issues with ssh after installing controller-0 with a load built on 2018-11-25. The ssh daemon is not started by default on the controller. This issue is seen in multiple labs and is blocking automated sanity execution. This issue was not seen in a load built on 2018-11-22. Is anyone else testing in master and seeing this issue? Looking at the code submissions between 2018-11-22 & 2018-11-25, I see the following change: ./cgcs-root/stx/stx-integ 36dc17738d9e2ef5dab689a556d7d8f33415861e Fri Nov 23 22:09:59 2018 +0000 Gerrit Code Review Merge "Refactor patches for openssh package" ./cgcs-root/stx/stx-integ 1c8c71654ff6f20cf13bcceeb861d969fd5b53a8 Wed Nov 21 01:21:12 2018 +0000 zhipeng liu Refactor patches for openssh package I’m not sure if that’s the root-cause, but it needs to be investigated. Zhipeng/Cindy, Please investigate. Launchpad: https://bugs.launchpad.net/starlingx/+bug/1805157 Thanks, Ghada
participants (3)
-
Khalil, Ghada
-
Liu, ZhipengS
-
Penney, Don