problem importing instackenv.json

Bug #1618877 reported by Rafael Urena
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

I've installed the undercloud and find i cannot import my instack.json file.

# openstack baremetal import --json /home/stack/instackenv.json
Invalid input [name=tripleo.baremetal.v1.register_or_update, class=DirectWorkflowSpec, unexpected=[u'instance_boot_option']]

I've looked online and cannot find this error anywhere, any assistance would be greatly appreciated. I found that the file /usr/share/openstack-tripleo-common/workbooks/baremetal.yaml was not like the one on github. Not sure if that is the issue. I thought perhaps this was what was being used to import the json file.

Revision history for this message
Julie Pichon (jpichon) wrote :

It does look like a more recent version of tripleo-common is needed here, both for that yaml file (updated Mistral workbook) and the updated Mistral action that goes with it.

tags: added: tripleo-common
Revision history for this message
Julie Pichon (jpichon) wrote :

I'm not entirely sure what's the preferred/recommended way to fix it in this case, I believe it's due to a mismatch between using the latest client dev version with not quite the latest tripleo-common code. Did you update both/either packages recently?

As a workaround, since I assume this is a development environment, you could clone the tripleo-common repository [1], run the commands at the start of the README [2], and update the workbook with:

$ mistral workbook-update ~/tripleo-common/workbooks/baremetal.yaml

Let me know if this helps. I'll try to find out what's the proper way to get the latest tripleo-common code to be picked up in the meantime.

[1] http://git.openstack.org/cgit/openstack/tripleo-common/
[2] http://git.openstack.org/cgit/openstack/tripleo-common/tree/README.rst#n22 lines 22-30

Revision history for this message
Julie Pichon (jpichon) wrote :

I just built a new undercloud on a new setup (using the instructions at http://tripleo.org), and the import command ran fine. How did you install/update your undercloud, could you explain your setup? Could you confirm your tripleo-common package is up to date?

After the installation, the workflow was available with the new argument:

$ mistral workflow-get-definition tripleo.baremetal.v1.register_or_update
register_or_update:
[...]
  input:
   - nodes_json
   - remove: False
   - queue_name: tripleo
   - kernel_name: null
   - ramdisk_name: null
   - instance_boot_option: local
[...]

Changed in tripleo:
status: New → Incomplete
Revision history for this message
Rafael Urena (rurena) wrote :

I am not entirely sure what I did differently from last week when i did this and it worked. I was thinking that perhaps an update or something had occurred over the weekend. I was able to deploy Mitaka and introspection was completed successfully. I will try to upgrade to newton and will let you know if i get any errors after that. I followed these instructions:
http://docs.openstack.org/developer/tripleo-docs/installation/installing.html

Revision history for this message
Rafael Urena (rurena) wrote :
Revision history for this message
Julie Pichon (jpichon) wrote :

Thank you for your answer and the additional information. The patch that is giving you trouble merged very recently indeed (tripleo-common [1], tripleoclient [2]), but the client patch merged after the tripleo-common patch. So I'm surprised you have a new client yet seem to be missing the tripleo-common update. If it was an undercloud update, it's possible the workflow and actions need to be updated manually following the notes I left in comment #2. Please let me know how your new install/upgrade goes (note that these patches should only affect the undercloud) - and perhaps which versions you are using, if you hit the same issue again. Thank you.

[1] https://review.openstack.org/#/c/348875/
[2] https://review.openstack.org/#/c/339727/

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for tripleo because there has been no activity for 60 days.]

Changed in tripleo:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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