[Starlingx-discuss] FW: Sanity Test - ISO 20181212

Perez Carranza, Jose jose.perez.carranza at intel.com
Fri Dec 14 14:26:13 UTC 2018


Hi Zhipeng

We executed manually a test with "Subsystem       sftp    /usr/libexec/openssh/sftp-server" and SFTP connection is started correctly, I set +1 to the patch and will verify on our suite  automatically when this gets integrated on an CENGN ISO. 

Regards,
José


> -----Original Message-----
> From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com]
> Sent: Friday, December 14, 2018 3:09 AM
> To: Alonso, Juan Carlos <juan.carlos.alonso at intel.com>
> Cc: starlingx <starlingx-discuss at lists.starlingx.io>
> Subject: Re: [Starlingx-discuss] FW: Sanity Test - ISO 20181212
> 
> Hi JC,
> 
> Now I have found the root cause.
> The sftp path in sshd_config  is not correct before executing
> config_controller!
> Please cherry pick below patch and try it again. Pls let me know your result,
> thanks!
> https://review.openstack.org/#/c/625184/
> 
> My analysis is below
> 
> From original source patch, I can see sftp patch is set to /usr/libexec/sftp-
> server In harden-server-and-client-config.patch
> @@ -137,3 +138,11 @@ Subsystem sftp /usr/libexec/sftp-server  #
> AllowTcpForwarding no  # PermitTTY no
> 
> That's why I set it the same in my refactor patch.
> After puppet applied, sshd_config will be overwritten by a puppet version--
> puppet-sshd/src/sshd/templates/sshd_config.erb
> In this version, sftp path is right -- /usr/libexec/openssh/sftp-server.
> 
> So, I'm still confused why it can work with old version which should also use
> a wrong path.
> I will check further.
> 
> Thanks!
> Zhipeng
> 
> -----Original Message-----
> From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com]
> Sent: 2018年12月14日 14:27
> To: Saul Wold <sgw at linux.intel.com>; Xie, Cindy <cindy.xie at intel.com>;
> starlingx <starlingx-discuss at lists.starlingx.io>
> Subject: Re: [Starlingx-discuss] FW: Sanity Test - ISO 20181212
> 
> Hi all,
> 
> I have double checked my patch below
> https://review.openstack.org/#/c/623994
> No obvious issue found. It just modify ssh_config and sshd_config
> configuration file in /etc/ssh/ folder through configuration package instead
> of using source patch to modify this 2 files during build time.
> 
> I also tried to reproduce this issue in my deployment environment.
> Before I trigger config_controller, I set ip address 10.10.10.111 for controller
> Then I tried below 2 commands from my deploy host. Both are OK! It seems
> ssh can work normally.
> 1) ssh wrsroot at 10.10.10.111
> 2) scp  file  wrsroot at 10.10.10.111:~/
> 
> From the debug log in https://bugs.launchpad.net/starlingx/+bug/1808054
> I can see that first ssh to 10.10.10.111 is successful.
> Then it ssh to 10.10.10.3 and could not connect to it.
> I'm confused here, why script trigger ssh to 10.10.10.3, which will be
> configured later during executing config_controller.
> @JC, could you double check your test script as well?
> ===========================log
> markers=============================================
> 20181211 05:33:57.632 - INFO - Logging into '10.10.10.111 prompt=$:22' as
> 'wrsroot'.
> 20181211 05:33:58.784 - INFO - Read output: Last login: Tue Dec 11 11:31:44
> 2018 from 10.10.10.1 
> WARNING: Unauthorized access to this system is forbidden and will be
> prosecuted by law. By accessing this system, you agree that your actions may
> be monitored if unauthorized usage is suspected.
> 
> localhost:~$
> 20181211 05:33:58.806 - INFO - +------ START KW: SSHLibrary.Login [ ${user} |
> ${password} | delay=${delay} ]
> 20181211 05:33:58.806 - INFO - Logging into '10.10.10.3 prompt=$:22' as
> 'wrsroot'.
> 20181211 05:34:01.804 - FAIL - NoValidConnectionsError: [Errno None]
> Unable to connect to port 22 on 10.10.10.3
> 
> BTW, is there any related issue observed from WR side?
> 
> Thx! -zhipeng
> 
> -----Original Message-----
> From: Saul Wold [mailto:sgw at linux.intel.com]
> Sent: 2018年12月14日 1:07
> To: Xie, Cindy <cindy.xie at intel.com>; starlingx <starlingx-
> discuss at lists.starlingx.io>; Liu, ZhipengS <zhipengs.liu at intel.com>
> Subject: Re: [Starlingx-discuss] FW: Sanity Test - ISO 20181212
> 
> 
> I am glad to see that our testing is actually finding failures!
> 
> We need to be a little more proactive on resolving issues such as these, this is
> the second day that this failure is still occurring.
> 
> **Zhipeng**
> Please take a look at this issue and if needed revert the change.
> 
> Sau!
> 
> 
> On 12/13/18 7:32 AM, Alonso, Juan Carlos wrote:
> > Status of the Sanity Test for last CENGN ISO: /bootimage.iso from
> > 2018-Dec-12 /(link
> > <http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20181
> > 212T152535Z/outputs/iso/>)
> >
> > Sanity Test is executed in a /_Virtual Environment_/
> >
> > Status: *RED*
> >
> > **
> >
> > *Simplex*
> >
> > Setup        03 TCs [PASS] | 01 TCs [FAIL]
> >
> > Provisioning 00 TCs [PASS] | 01 TCs [FAIL]
> >
> > Sanity       00 TCs [PASS] | 18 TCs [FAIL]
> >
> > TOTAL: [ 03 TCs PASS ] | [ 20 TCs FAIL ]
> >
> > *Duplex*
> >
> > Setup        03 TCs [PASS] | 01 TCs [FAIL]
> >
> > Provisioning 00 TCs [PASS] | 01 TCs [FAIL]
> >
> > Sanity       00 TCs [PASS] | 19 TCs [FAIL]
> >
> > TOTAL: [ 03 TCs PASS ] | [ 21 TCs FAIL ]
> >
> > *Multinode Controller Storage*
> >
> > Setup        03 TCs [PASS] | 01 TCs [FAIL]
> >
> > Provisioning 00 TCs [PASS] | 01 TCs [FAIL]
> >
> > Sanity       00 TCs [PASS] | 19 TCs [FAIL]
> >
> > TOTAL: [ 03 TCs PASS ] | [ 21 TCs FAIL ]
> >
> > *Multinode Dedicated Storage*
> >
> > Setup        03 TCs [PASS] | 01 TCs [FAIL]
> >
> > Provisioning 00 TCs [PASS] | 01 TCs [FAIL]
> >
> > Sanity       00 TCs [PASS] | 19 TCs [FAIL]
> >
> > TOTAL: [ 03 TCs PASS ] | [ 21 TCs FAIL ]
> >
> > ------------------------------------------------------------------
> >
> > SFTP service still not working.
> >
> > Launchpad open: https://bugs.launchpad.net/starlingx/+bug/1808054
> >
> > Regards.
> >
> > Juan Carlos Alonso
> >
> >
> > _______________________________________________
> > Starlingx-discuss mailing list
> > Starlingx-discuss at lists.starlingx.io
> > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
> >
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss


More information about the Starlingx-discuss mailing list