Rejecting request from ironic python agent

Bug #1613310 reported by Waldemar Znoinski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Expired
Undecided
Unassigned
Mitaka
Fix Released
Medium
Waldemar Znoinski
Newton
Fix Released
Medium
Waldemar Znoinski

Bug Description

kolla stable/mitaka

when IPA (ironic python agent) wants to get details about the network interfaces deployed node has it fails with 401 from keystonemiddleware

2016-08-12 14:23:33.349 35 INFO keystonemiddleware.auth_token [-] Rejecting request
2016-08-12 14:23:33.350 35 INFO ironic_api [-] 10.237.223.28 "GET /v1/lookup?addresses=90%3Ae2%3Aba%3A5c%3Aad%3A61%2C90%3Ae2%3Aba%3A5e%3Aa5%3A90%2C90%3Ae2%3Aba%3A5e%3Aa5%3A91%2C00%3A1e%3A67%3A89%3A9b%3Ab1%2C00%3A1e%3A67%3A89%3A9b%3Ab2%2C90%3Ae2%3Aba%3A5c%3Aad%3A60%2C00%3A1e%3A67%3A89%3A9b%3Ab3%2C00%3A1e%3A67%3A89%3A9b%3Ab4 HTTP/1.1" status: 401 len: 233 time: 0.0008471

the fix looks to be overriding version of IPA used when using stable/mitaka kolla should be overriden with
export DIB_REPOREF_ironic_agent=stable/mitaka

it's more of a deployment issue, may be useful to someone tho

Changed in kolla:
assignee: nobody → Waldemar Znoinski (wznoinsk)
Revision history for this message
Ryan Hallisey (rthall14) wrote :

we need a method to specify Mitaka or Newton for master

Changed in kolla:
status: New → Triaged
importance: Undecided → High
milestone: none → newton-3
importance: High → Medium
Changed in kolla:
milestone: newton-3 → newton-rc1
Changed in kolla:
milestone: newton-rc1 → newton-rc2
Changed in kolla:
status: Triaged → Confirmed
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

> the fix looks to be overriding version of IPA used when using stable/mitaka kolla should be overriden with
> export DIB_REPOREF_ironic_agent=stable/mitaka

what mean by this?

build the IPA image by using stable/mitaka branch?

Revision history for this message
Waldemar Znoinski (wznoinsk) wrote :

the version of IPA available on xenial deploy ramdisk is not compatible with keystone when you're using mitaka version of kolla and openstack services on controller

Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote :

So need we disable keystone? or something else? do u have any fix for this?

Steven Dake (sdake)
Changed in kolla:
milestone: newton-rc2 → ocata-1
no longer affects: kolla/newton
Changed in kolla:
milestone: ocata-1 → ocata-2
Changed in kolla:
milestone: ocata-2 → ocata-3
Changed in kolla:
milestone: ocata-3 → ocata-rc1
Changed in kolla:
milestone: ocata-rc1 → pike-1
Changed in kolla:
milestone: pike-2 → pike-3
Changed in kolla:
milestone: pike-3 → pike-rc1
Changed in kolla:
milestone: pike-rc1 → queens-1
Changed in kolla:
milestone: queens-2 → queens-3
Changed in kolla:
milestone: queens-3 → queens-rc1
Changed in kolla:
milestone: queens-rc1 → queens-rc2
Changed in kolla:
milestone: queens-rc2 → rocky-1
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA

Changed in kolla:
assignee: Waldemar Znoinski (wznoinsk) → nobody
importance: Medium → Undecided
status: Confirmed → 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.