Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Event interface-update fails with Nextcloud #6250

Closed
stephdl opened this issue Aug 11, 2020 · 7 comments
Closed

Event interface-update fails with Nextcloud #6250

stephdl opened this issue Aug 11, 2020 · 7 comments
Labels
bug A defect of the software verified All test cases were verified successfully

Comments

@stephdl
Copy link

stephdl commented Aug 11, 2020

Steps to reproduce

  • Install nextcloud and an account provider (SAMBA AD tested)
  • set the trusted domain (optional)
  • save, the template and services are started without error (optional)

in a terminal triggers the event interface-update, you have an error in messages, the event failed

Aug 11 18:07:14 ns7dev12 esmith::event[9913]: System config value trusted_domains => 3 set to string ns7dev12
Aug 11 18:07:14 ns7dev12 esmith::event[9913]: (Invalid argument): IO::Socket::INET: Bad hostname 'nsdc-ns7dev12.ad.nethservertest.org'
Aug 11 18:07:14 ns7dev12 esmith::event[9913]: Action: /etc/e-smith/events/interface-update/S50nethserver-nextcloud-occ-conf FAILED: 1 [6.080312]

Expected behavior

I expect no errors, see the gist of log messages https://gist.github.com/stephdl/6a560a0aada7c88b419c3311e57661b1

Actual behavior

I suppose that the action is launched at S50 and the networking service is not up, then the action cannot perform to save the value trustedDomain with the ipaddress

https://github.com/NethServer/nethserver-nextcloud/blob/master/root/etc/e-smith/events/actions/nethserver-nextcloud-occ-conf#L82

Components

nethserver-nexcloud

See also

https://community.nethserver.org/t/nextcloud-interface-update-sequence-problem/16244


thank @Doc-Saintly

@stephdl stephdl added the bug A defect of the software label Aug 11, 2020
@stephdl stephdl self-assigned this Aug 11, 2020
@stephdl
Copy link
Author

stephdl commented Aug 11, 2020

@DavidePrincipi DavidePrincipi changed the title nethserver-nextcloud-occ-conf fails with interface-update Event interface-update fails with Nextcloud Aug 27, 2020
@DavidePrincipi
Copy link
Member

DavidePrincipi commented Aug 27, 2020

The error message line comes from the Perl module NethServer::LdapClient (or similar):

(Invalid argument): IO::Socket::INET: Bad hostname 'nsdc-ns7dev12.ad.nethservertest.org'

It cannot resolve the nsdc host name at some point because the network is down. I suspect a small regression introduced by NethServer/nethserver-nextcloud#81

gsanchietti pushed a commit to NethServer/nethserver-nextcloud that referenced this issue Sep 1, 2020
Fix interface-update sequence issue

Putting Nextcloud configure after the Firewall adjust is done. 
See also https://community.nethserver.org/t/nextcloud-interface-update-sequence-problem/16244 .

NethServer/dev#6250

Co-authored-by: Davide Principi <davide.principi@nethesis.it>
@nethbot
Copy link
Member

nethbot commented Sep 1, 2020

in 7.8.2003/testing:

@nethbot
Copy link
Member

nethbot commented Sep 1, 2020

in 7.8.2003/testing:

@gsanchietti
Copy link
Member

Test case
Check the bug is not reproducible

@gsanchietti gsanchietti added the testing Packages are available from testing repositories label Sep 1, 2020
@DavidePrincipi DavidePrincipi self-assigned this Sep 1, 2020
@DavidePrincipi DavidePrincipi added verified All test cases were verified successfully and removed testing Packages are available from testing repositories labels Sep 1, 2020
@DavidePrincipi DavidePrincipi removed their assignment Sep 1, 2020
@DavidePrincipi
Copy link
Member

Already VERIFIED

@nethbot
Copy link
Member

nethbot commented Sep 3, 2020

in 7.8.2003/updates:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A defect of the software verified All test cases were verified successfully
Projects
None yet
Development

No branches or pull requests

4 participants