Bug 1550024 - 'ap' fails to launch appliance console after upgrade
Summary: 'ap' fails to launch appliance console after upgrade
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Documentation
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.9.2
Assignee: Red Hat CloudForms Documentation
QA Contact: Red Hat CloudForms Documentation
URL:
Whiteboard: black:upgrade:migration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-28 10:43 UTC by luke couzens
Modified: 2018-03-20 04:48 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
At current, attempting to open the appliance console using the 'ap' command fails under certain circumstances after upgrading from Red Hat CloudForms 5.8 to Red Hat CloudForms 5.9. As a workaround, log out of and back in to the appliance, or enter the full command 'appliance_console'.
Clone Of:
Environment:
Last Closed: 2018-03-20 04:48:15 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description luke couzens 2018-02-28 10:43:39 UTC
Description of problem:'ap' fails to launch appliance console after upgrade


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


How reproducible:100%


Steps to Reproduce:
1.provision 5.8 appliance
2.add latest 5.9 repos
3.stop evm
4.run yum update
5.run ap

Actual results:
-bash: /usr/bin/appliance_console: No such file or directory


Expected results:
appliance_console launches

Additional info:

Though the short hand 'ap' fails to load the console a simple workaround is to use 'appliance_console'

~]# ap
-bash: /usr/bin/appliance_console: No such file or directory
~]# appliance_console

Welcome to the CFME Virtual Appliance.

To modify the configuration, use a web browser to access the management page.

Comment 3 luke couzens 2018-02-28 10:49:35 UTC
This probably shouldn't be a blocker as its such a minor issue. 

Also another work around for this is to reboot the appliance that also seems to fix the link, making it even less of an issue.

Comment 4 Joe Rafaniello 2018-02-28 16:50:32 UTC
I'd imagine you don't even have to reboot.  Exiting the shell and ssh'ing back in should reload your profile and the aliases.

Comment 5 Joe Rafaniello 2018-02-28 16:53:43 UTC
I believe we have the same problem when we upgrade the ruby SCL.  The old SCL is in the paths and isn't accessible so you need to exit the shell/reboot/etc. after upgrading those rpms.

Comment 6 Andrew Dahms 2018-03-20 04:48:15 UTC
Updating the doc text and closing this as 'next release'.


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