[Rdo-list] [QA] Tempest - is volume testing actually testing anything with block storage?

Kashyap Chamarthy kchamart at redhat.com
Tue Aug 19 18:59:14 UTC 2014

On Mon, Aug 18, 2014 at 10:12:45AM -0400, Kaul, Yaniv wrote:

[. . .]

> I really don't like to mix running targets (Fedora and OpenStack)
> while testing.

Fair enough.

> - On my F19, I could not find anything that was not 2013.1.

> - I failed to upgrade it to F20. 'fedup' failed after reboot to
> upgrade it. I'm quite fed up with it.

Hmm, as an alternative to fedup, I used the below method. FWIW, as I
write this, I just updated 3 machines successfully from f19 -> f20 with
these instructions:

    $ yum update yum -y; yum clean all; \
      yum --releasever=20 distro-sync --nogpgcheck -y

Followed by:

    $ package-cleanup --problems ; package-cleanup --orphans \
      package-cleanup --dupes ; package-cleanup --leaves

    $ reboot

> - I could not find packstack @
> https://repos.fedorapeople.org/repos/openstack/openstack-trunk/fedora/
> - perhaps it's not the right location.

>From the above URL, seems like you're looking for latest packstack for
Fedora. If so, they're always built first in Koji, so a consistent way
to check (that's what I've been doing):

For f20:
    $  koji latest-build f20 openstack-packstack

Or, for the very latest packstack:

    $ koji latest-build openstack-packstack

To download it (the package N-V-R is obtained from the above step) from

    $ koji download-build --arch=noarch \

And, to find latest builds for a specific package *across* current

    $ bodhi -L openstack-packstack

Not sure if you're aware, RDO packages for Fedora follows Fedora distro
release schedule, i.e. once N+2 is released (Icehouse), we EOL N
(Grizzly). So, to map Fedora and OpenStack releases:

  - Fedora-19 == Grizzly (2013.1)  -- is now EOL
  - Fedora-20 == Havana (2013.2)   -- is currently "supported"
  - Fedora-21 == IceHouse (2014.1) -- is currently "supported"

If you hit any issues, please post here, we'll see what we can do.


More information about the dev mailing list