Mirantis OpenStack

[Murano]Deployment of k8s apps failed with 'not found in io.murano/0.0.0' error

Bug #1524765 reported by Victor Ryzhenkin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Fix Released
Critical
Kirill Zaitsev
Mirantis OpenStack 8.0
7.0.x
Invalid
High
Unassigned
Mirantis OpenStack 7.0-updates

Bug Description

Use murano from master branch.

1. Import k8s applications from app-catalog
2. Create env
3. Add application with k8s base
4. Use default values for k8s application
5. Deploy app.

Actual result:
Deployment failed with error:
2015-11-27 00:33:05 — Class "io.murano.apps.docker.DockerApplication" is not found in io.murano/0.0.0, io.murano.apps.docker.DockerStandaloneHost/0.0.0, io.murano.apps.docker.kubernetes.KubernetesPod/0.0.0

http://paste.openstack.org/show/480176/

Upstream bug:
https://bugs.launchpad.net/murano-apps/+bug/1520384

Victor Ryzhenkin (vryzhenkin)
summary: - Deployment of k8s apps failed with 'not found in io.murano/0.0.0' error
+ [Murano]Deployment of k8s apps failed with 'not found in
+ io.murano/0.0.0' error
Roman Podoliaka (rpodolyaka)
Changed in mos:
assignee: nobody → MOS Murano (mos-murano)
Kirill Zaitsev (kzaitsev)
Changed in mos:
assignee: MOS Murano (mos-murano) → Kirill Zaitsev (kzaitsev)
status: Confirmed → In Progress
Revision history for this message
Kirill Zaitsev (kzaitsev) wrote :

apps have been updated, please verify

Changed in mos:
status: In Progress → Fix Committed
Revision history for this message
Anastasia Kuznetsova (akuznetsova) wrote :

Verified on
VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "8.0"
  api: "1.0"
  build_number: "328"
  build_id: "328"
  fuel-nailgun_sha: "ec25ae8df28e1f1d87da653c5aab2711dff729f6"
  python-fuelclient_sha: "7c7a756fb6a3d091851c060003a2965c67aa353d"
  fuel-agent_sha: "d354cbe61b055db848a15ce66fb7ae92178d2c0a"
  fuel-nailgun-agent_sha: "a33a58d378c117c0f509b0e7badc6f0910364154"
  astute_sha: "c56dfde2da034151a7e707b381c4cf9d213b4ba2"
  fuel-library_sha: "bcc3d042a47547f6ad826360a85ef21dcaf25882"
  fuel-ostf_sha: "b2ebf15a3530b5c7b57707acf8642c1c3ac71bd8"
  fuel-mirror_sha: "8100acb3a566358d0d4ecc66de32d39626263028"
  fuelmenu_sha: "2942a85796d37f09ba8c8c6d762d8813292cf0d4"
  shotgun_sha: "cacb93cbc28910ff0dc38f30a855efa9af50d8ce"
  network-checker_sha: "d443ef47abeda58d319bc8d33d5005dd09440a02"
  fuel-upgrade_sha: "718aa3d7021fee2970f0fa6791cf5188578cc516"
  fuelmain_sha: "3faa824728ce60734abe602ff3778976f8a16eed"

Changed in mos:
status: Fix Committed → Fix Released
Revision history for this message
Kirill Zaitsev (kzaitsev) wrote :

actually this error message should be impossible to get on 7.0.x, since it was added during L cycle. Needs to be verified though. setting to new

Ivan Ponomarev (ivanzipfer)
tags: added: area-murano
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

Kirill, I've tentatively confirmed this. Let's double check.

Revision history for this message
Vitaly Sedelnik (vsedelnik) wrote :

This is Murano specific issue which doesn't affect entire cluster, so downgrading from Critical to High. Also moving from 7.0-mu-3 to backlog.

Revision history for this message
Denis Meltsaykin (dmeltsaykin) wrote :

Setting as Invalid for 7.0 as applications are out of scope for Maintenance Updates and per above comments.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.