Ask Your Question
0

FATAL: Arch 'amd64' in 'trusty/universe' doesn't exist

asked 2016-04-05 03:38:13 -0500

gwyndiion gravatar image

Trying to deploy a brand new Fuel OpenStack (Mirantis 7.0)

Fuel has been deployed ok, and now running through the create a mirror process.

mos updates are created ok, it is just the ubuntu updates.

The error logs for the fuel-createmirror output

Fetching '/dists/trusty/Release' to '/var/www/nailgun/ubuntu-full/dists/trusty/' with params ''...OK
Fetching '/dists/trusty/Release.gpg' to '/var/www/nailgun/ubuntu-full/dists/trusty/' with params ''...OK
 * DEBUG: Got Release file '/var/www/nailgun/ubuntu-full/dists/trusty/Release'
 * DEBUG: Calculating arches/components to fetch from dist
 * DEBUG: Adding debian-installer 'main/debian-installer'
 * ERROR: Not found debian-installer at 'multiverse/debian-installer'
 * DEBUG: Adding debian-installer 'universe/debian-installer'
 * DEBUG: Will fetch binary components: main multiverse universe main/debian-installer universe/debian-installer
 * INFO: Fetching component 'main' binary package lists
 * INFO: Fetching component 'multiverse' binary package lists
 * INFO: Fetching component 'universe' binary package lists
 * INFO: Fetching component 'main/debian-installer' binary package lists
 * FATAL: Arch 'amd64' in 'trusty/main/debian-installer' doesn't exist
 * FATAL: Creation of Ubuntu mirror FAILED, check logs at /var/log/mirror-sync

It kinda sounds like this : https://bugs.launchpad.net/fuel/+bug/1459252 (https://bugs.launchpad.net/fuel/+bug/...), but there is no resolution to this ticket for the initial FATAL error.

Any thoughts on how to get around this ?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-04-05 08:36:48 -0500

gwyndiion gravatar image

Interestingly, the 'fuel-bootstrap-image' command was able to successfully download updates from the default ubuntu mirror, without a problem.

Answering my own question, but it looks like the default download mirror of http://archive.ubuntu.com may be the very problem. Or at least an interaction with http://archive.ubuntu.com.

My servers at in Ottawa, Canada, so latency is not an issue.

I updated the /opt/fuel-createmirror-7.0/config/common.cfg file to point to a different ubuntu archive, and reran the "fuel-createmirror -U" process, and it picked up the files first time. grrr

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-04-05 03:38:13 -0500

Seen: 83 times

Last updated: Apr 05 '16