Project

General

Profile

Bug #10003

Cannot Update to 10-nightlies from 9.3-nightlies

Added by Dru Lavigne over 5 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Important
Assignee:
Dru Lavigne
Category:
OS
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Fresh install of 9.3-Nightlies-201505290653. If I switch to the 10-Nightlies train, everything downloads but I get the attached error during the apply.

error.png (11.2 KB) error.png Dru Lavigne, 05/29/2015 02:04 PM
error.png (11.3 KB) error.png Dru Lavigne, 06/02/2015 09:00 AM
3030
3039

Associated revisions

Revision 7c000d67 (diff)
Added by Sean Fagan over 5 years ago

The update code did not handle the case where a directory turned into a symlink. I'm not entirely sure this is right -- it essentially does a "rm -rf" on the target, in that case -- but I'm not quite sure what else is to be done. This allows an upgrade from 9.3 to 10. Ticket: #10003 Merge-FN93: Yes Merge-TN93: Yes

Revision 8d83b380 (diff)
Added by Sean Fagan over 5 years ago

The update code did not handle the case where a directory turned into a symlink. I'm not entirely sure this is right -- it essentially does a "rm -rf" on the target, in that case -- but I'm not quite sure what else is to be done. This allows an upgrade from 9.3 to 10. Ticket: #10003 Merge-FN93: Yes Merge-TN93: Yes (cherry picked from commit 7c000d67c46e374737c43ba8dbf629019139ccda)

Revision 758b04a8 (diff)
Added by Sean Fagan over 5 years ago

The update code did not handle the case where a directory turned into a symlink. I'm not entirely sure this is right -- it essentially does a "rm -rf" on the target, in that case -- but I'm not quite sure what else is to be done. This allows an upgrade from 9.3 to 10. Ticket: #10003 Merge-FN93: Yes Merge-TN93: Yes (cherry picked from commit 7c000d67c46e374737c43ba8dbf629019139ccda)

Revision 70520a44 (diff)
Added by Sean Fagan over 5 years ago

The new root was not being used for the pkgdb manipulations. This resulted in a loss of system files when upgrading from 9.3 to 10, which made the 9.3 system unusable. Ticket: #10003 Merge-FN93: Yes Merge-TN93: Yes

Revision 723ca328 (diff)
Added by Sean Fagan over 5 years ago

The new root was not being used for the pkgdb manipulations. This resulted in a loss of system files when upgrading from 9.3 to 10, which made the 9.3 system unusable. Ticket: #10003 Merge-FN93: Yes Merge-TN93: Yes (cherry picked from commit 70520a4440e11bb71b47ad5e3fd83368cf0a68a6)

Revision 2236f5d4 (diff)
Added by Sean Fagan over 5 years ago

The new root was not being used for the pkgdb manipulations. This resulted in a loss of system files when upgrading from 9.3 to 10, which made the 9.3 system unusable. Ticket: #10003 Merge-FN93: Yes Merge-TN93: Yes (cherry picked from commit 70520a4440e11bb71b47ad5e3fd83368cf0a68a6)

Revision 552ed7cb (diff)
Added by Sean Fagan over 5 years ago

The update code did not handle the case where a directory turned into a symlink. I'm not entirely sure this is right -- it essentially does a "rm -rf" on the target, in that case -- but I'm not quite sure what else is to be done. This allows an upgrade from 9.3 to 10. Ticket: #10003 Merge-FN93: Yes Merge-TN93: Yes (cherry picked from commit 7c000d67c46e374737c43ba8dbf629019139ccda)

Revision eaec2d47 (diff)
Added by Sean Fagan over 5 years ago

The update code did not handle the case where a directory turned into a symlink. I'm not entirely sure this is right -- it essentially does a "rm -rf" on the target, in that case -- but I'm not quite sure what else is to be done. This allows an upgrade from 9.3 to 10. Ticket: #10003 Merge-FN93: Yes Merge-TN93: Yes (cherry picked from commit 7c000d67c46e374737c43ba8dbf629019139ccda) Former-commit-id: 552ed7cb135978df9112170ad07d9c62c11b5bfa

Revision ab253158 (diff)
Added by Sean Fagan over 5 years ago

The new root was not being used for the pkgdb manipulations. This resulted in a loss of system files when upgrading from 9.3 to 10, which made the 9.3 system unusable. Ticket: #10003 Merge-FN93: Yes Merge-TN93: Yes (cherry picked from commit 70520a4440e11bb71b47ad5e3fd83368cf0a68a6)

Revision 9f9c9366 (diff)
Added by Sean Fagan over 5 years ago

The new root was not being used for the pkgdb manipulations. This resulted in a loss of system files when upgrading from 9.3 to 10, which made the 9.3 system unusable. Ticket: #10003 Merge-FN93: Yes Merge-TN93: Yes (cherry picked from commit 70520a4440e11bb71b47ad5e3fd83368cf0a68a6) Former-commit-id: ab2531583793297cf090471959cf37a62be17b1a

History

#1 Updated by Dru Lavigne over 5 years ago

  • Assignee changed from Xin Li to Sean Fagan

#2 Updated by Sean Fagan over 5 years ago

  • Category changed from 123 to 1
  • Status changed from Unscreened to Screened
  • Target version changed from 133 to Unspecified

This may not work in the long run, but for now I do expect it to. ("This" being "upgrades from one major OS to another major OS.")

It'll have to be fixed in 9.3.

#3 Updated by Sean Fagan over 5 years ago

  • Status changed from Screened to Investigation

Found that one, but in going further I found another problem.

I'm not sure how to handle this one: in 9.3, etc/local is a directory; in 10, it's a symlink. The install code looks at the type of the new file, and says, ah, it's a (file | symlink), so I shall remove the old one and create the new one. But that fails, because it can't unlink a directory.

And then I seem to have discovered another problem. Hm.

#4 Updated by Sean Fagan over 5 years ago

  • Status changed from Investigation to Ready For Release

Done in 7c000d67c46e374737c43ba8dbf629019139ccda

This fixes two issues -- one is that I was passing the wrong object to a function (and thus the original exception), the other being a directory in 9.3 turned into a symlink in 10. I'm not positive the latter is the right thing, yet, but it did allow the update to happen.

#5 Updated by Sean Fagan over 5 years ago

  • Status changed from Ready For Release to Fix In Progress

Found another problem. Bad one, at that.

#6 Updated by Sean Fagan over 5 years ago

  • Status changed from Fix In Progress to Ready For Release

#7 Updated by Sean Fagan over 5 years ago

  • ChangeLog Entry updated (diff)

#8 Updated by Dru Lavigne over 5 years ago

3039

Should this still be included in the SU? I still get the attached traceback when updating the latest nightly.

#9 Updated by Sean Fagan over 5 years ago

That's something else, and it's with 10, not 9.3. So it did let you upgrade, the upgrade just doesn't work ;).

#10 Updated by Sean Fagan over 5 years ago

  • Status changed from Unscreened to 15
  • Assignee changed from Sean Fagan to Dru Lavigne

Per comment above, this issue appears to be resolved (the other issue is post-install, and looks like a networking issue, and may have been resolved at the same time the DHCP issue was).

#11 Updated by Dru Lavigne over 5 years ago

  • Status changed from 15 to Resolved

As of FreeNAS-9.3-Nightlies-201506100630, you can now upgrade to 10. It doesn't boot, but that's an M2 issue, not an upgrade issue.

#12 Updated by Dru Lavigne over 5 years ago

Noting that a fresh install of http://download.pcbsd.org/iso/nightlies/latest-10.0.iso boots just fine but gave a networking error at boot when updating to the latest M2 from the latest 9.3.

#13 Avatar?id=14398&size=24x24 Updated by Kris Moore about 4 years ago

  • Target version changed from Unspecified to N/A

Also available in: Atom PDF