Bug 1328572 - Register Nodes Failed to load resource: net::ERR_INSECURE_RESPONSE
Summary: Register Nodes Failed to load resource: net::ERR_INSECURE_RESPONSE
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: Installation - RHELOSP
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ga
: 1.0
Assignee: John Matthews
QA Contact: Thom Carlin
Dan Macpherson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-19 17:56 UTC by Thom Carlin
Modified: 2016-09-13 16:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-13 16:28:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1321654 0 unspecified CLOSED [RHEL-OSP] Error retrieving OpenStack nodes. Adapter operation failed 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1328971 0 unspecified CLOSED Multiple invocations of Register Nodes leads to corruption of node display 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHEA-2016:1862 0 normal SHIPPED_LIVE Red Hat Quickstart Installer 1.0 2016-09-13 20:18:48 UTC

Internal Links: 1321654 1328971

Description Thom Carlin 2016-04-19 17:56:45 UTC
Description of problem:

During Register Nodes, looping errors in flash area.  Additionally, looping errors in Javascript

Version-Release number of selected component (if applicable):

TP3 RC4

How reproducible:

Believe Erratic

Steps to Reproduce:
1. Install QCI and TripleO ISOs
2. Log into run launch-fusor-*installer
3. Deploy Openstack

Actual results:

Problems with Register Nodes

Expected results:

No errors, successful deployment

Additional info:

Messages include:
DEPRECATION: Ember.create is deprecated in favor of Object.create
        at Object.s.v [as create]
Uncaught TypeError: $(...).flot_pie is not a function
DEPRECATION: `lookup` was called on a Registry. The `initializer` API no longer receives a container, and you should use an `instanceInitializer` to look up objects from the container. See http://emberjs.com/guides/deprecations#toc_deprecate-access-to-instances-in-initializers for more details.
        at Object.a.lookup
fusor-ember-cli-075dde0….js:14 r {description: undefined, fileName: undefined, lineNumber: undefined, message: "Attempted to handle event `notFound` on <fusor-emb… while in state root.loaded.updated.uncommitted. ", name: "Error"…} "ERROR retrieving deployment introspection tasks."
5ven
ERROR retrieving deployment introspection tasks. Attempted to handle event `notFound` on <fusor-ember-cli@model:deployment::ember1955:1
Failed to load resource: the server responded with a status of 500 (Internal Server Error)

Failed to load resource: net::ERR_INSECURE_RESPONSE
DEPRECATION: Your custom serializer uses the old version of the Serializer API, with `extract` hooks. Please upgrade your serializers to the new Serializer API using `normalizeResponse` hooks instead. [deprecation id: ds.serializer.extract-hooks-deprecated]
u {description: undefined, fileName: undefined, lineNumber: undefined, message: "Adapter operation failed", name: "Error"…} "Error retrieving OpenStack nodes."

Comment 1 Thom Carlin 2016-04-19 18:56:37 UTC
If this reoccurs for anyone, please upload the Foreman production.log

Comment 2 Thom Carlin 2016-04-19 20:21:54 UTC
Created attachment 1148746 [details]
Foreman production log

Production log showing the 500 Internal Server loop ONLY

Comment 3 Thom Carlin 2016-04-20 18:45:16 UTC
The new "see also" bugs complicated analysis of this issue

Comment 4 John Matthews 2016-06-20 18:32:11 UTC
Please re-test with OSP-8

Comment 5 Thom Carlin 2016-07-12 19:42:55 UTC
For QCI-1.2-RHEL-7-20160711.t.1, no errors seen during Register Nodes so moving to VERIFIED

Comment 11 errata-xmlrpc 2016-09-13 16:28:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2016:1862


Note You need to log in before you can comment on or make changes to this bug.