Project

General

Profile

Bug #54582

Properly move system dataset at bootup

Added by Waqar Ahmed 12 months ago. Updated 7 months ago.

Status:
Done
Priority:
No priority
Assignee:
William Grzybowski
Category:
Middleware
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

When we create a new volume from legacy UI, syslog-ng stops running as a service. This causes different crashes in the system internally like ftp service fails to start because of syslog-ng not running. Moving on, once the volume has been created, we are unable to detach it at all with the following error

Exception Value: [EFAULT] Command '('mount', '-t', 'zfs', 'vol1/.system', '/var/db/system')' returned non-zero exit status 1.

( All of this has been done in legacy UI )

Risk
We risk breaking other different services in the system which use the system datasets as well as storage functionalities completely

Acceptance Criteria
It should be ensured that syslog-ng doesn't stop running after a volume has been created and we are able to detach that volume. Plus we should be checking if we are able to start ftp after creating a volume. ( William please update accordingly if needed )

Associated revisions

Revision ed336236 (diff)
Added by William Grzybowski 12 months ago

fix(middlewared/sysdataset): raise error on setup Ticket: #54582

Revision e1ba552f (diff)
Added by William Grzybowski 12 months ago

fix(middlewared/sysdataset): properly move sysds around and on first boot Ticket: #54582

Revision dded2880 (diff)
Added by William Grzybowski 12 months ago

fix(middlewared/sysdataset): raise error on setup Ticket: #54582

Revision 22cd9701 (diff)
Added by William Grzybowski 12 months ago

fix(middlewared/sysdataset): properly move sysds around and on first boot Ticket: #54582

History

#1 Updated by Bug Clerk 12 months ago

  • Status changed from Unscreened to In Progress

#2 Updated by Bug Clerk 12 months ago

  • Status changed from In Progress to Ready for Testing

#3 Updated by Dru Lavigne 12 months ago

  • Subject changed from Syslog server stops running to Properly move system dataset at bootup
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#4 Updated by Dru Lavigne 9 months ago

  • Target version changed from 11.3 to 11.3-BETA1

#6 Updated by Bonnie Follweiler 8 months ago

Assigned to Zackary Welch

#7 Avatar?id=55038&size=24x24 Updated by Zackary Welch 8 months ago

  • Status changed from Ready for Testing to Passed Testing
  • Needs QA changed from Yes to No

I was able to create a volume and confirm syslog-ng is still running. I also saw no exception when detaching the volume. I was also able to start ftpd after volume creation. The pid of syslog-ng changed, but that seems okay, since it got running again.
Tested in both the old and new UI.

#8 Updated by Dru Lavigne 8 months ago

  • Status changed from Passed Testing to Done

#9 Updated by Dru Lavigne 7 months ago

  • Target version changed from 11.3-BETA1 to 11.3-ALPHA1

Also available in: Atom PDF