Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hello,
after an "octopus up-head o1 platforms" and "octopus up-stable o1 platforms" we received this message during the installation of a new platform:
Octopus [Sun Nov 3 18:53:36 CET 2013] ==> DISTRO: Commerce 2.9 7.23.3 P.002 installation in progress... cp: cannot stat `/data/all/000/core/drupal-7.23.3/sites': No such file or directory
Greetings
Stephan
Comment | File | Size | Author |
---|---|---|---|
o1.octopus.txt | 974 bytes | Anonymous (not verified) | |
barracuda_log.txt | 2.25 KB | Anonymous (not verified) | |
octopus_log.txt | 331 bytes | Anonymous (not verified) |
Comments
Comment #1
omega8cc CreditAttribution: omega8cc commentedHow do you run the upgrade? You should *not* run HEAD now, because currently there is stable only. There was a hot fix for similar issue: http://drupalcode.org/project/octopus.git/commit/21f3a27 (but it affected D6 based platforms, though)
BTW: You shouldn't upgrade only platforms on a new stable upgrade. You must upgrade both Hostmaster and platforms.
Comment #2
Anonymous (not verified) CreditAttribution: Anonymous commentedNow we upgraded both hostmaster and platforms with "barracuda up-stable" and the bug still exists.
Comment #3
omega8cc CreditAttribution: omega8cc commentedIt is now too late to expect it to be fixed auto-magically. While we couldn't reproduce this, you probably want to delete all ghost platforms dirs with broken symlinks in the latest /data/disk/o1/distro/00x/ directory, delete also /data/all/000/core-v-* control files and then try the upgrade again. Please attach full output if possible, so we could see exactly what you have attempted to install (I guess that skipping vanilla D7/D6 platforms may cause this, but not sure).
Comment #4
omega8cc CreditAttribution: omega8cc commentedJust in case it is what I suspect, we have added a hot-fix in stable: http://drupalcode.org/project/octopus.git/commit/b276b47
Comment #5
Anonymous (not verified) CreditAttribution: Anonymous commentedAs always, fantastic work. We've just tested it with the hot-fix and it works.
One question: Do we have to upgrade the barracuda and octopus hostmaster with every stable upgrade?
Thanks in advanced
Stephan
Comment #6
omega8cc CreditAttribution: omega8cc commentedGreat! Thanks for the confirmation.
When there is a new release, you should always upgrade everything. Only between releases you can use partial upgrades like "barracuda up-stable system" or "octopus up-stable o1 platforms".
However, there is some other issue we are investigating now, but it affects only old instances using previous default config: https://twitter.com/omega8cc/status/397144965174022144
Comment #7
omega8cc CreditAttribution: omega8cc commentedMarking this issue as fixed in the meantime. Thanks for the bug report.