Subscribe to this APAR
By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.
| APAR (Authorized Program Analysis Report) |
Abstract
Smart Cloud Entry not able to configure 2 DNS entries on deploy
using VMControl
Error Description
IBM Smart Cloud Entry (SCE) allows 2 Domain Name Servers (DNS)
to be entered on the SCE graphical user interface (GUI) for a
virtual machine (VM). When the VM is deployed, only the first
DNS entry is configured in the VM.
With 2 DNS entries in SCE, when an VM is deployed, there will
only be 1 nameserver defined in the VM's /etc/resolv.conf file.
Problem Summary
The SCE advanced deploy GUI provides the ability to specify 2
DNS entries. With 1 DNS values defined, SCE did not properly
provide the information to VMControl so VMs were created with
only 1 DNS value.
SCE code has been corrected so if 2 DNS values are specified,
the VM will be created with 2 DNS entries.
Problem Conclusion
On SCE 3.2 service pack 4, install this code level or later:
3.2.0.4-IBM-SCE-IF005-201601120100
Temporary Fix
Comments
Circumvention
PTFs Available
Affected Modules
None
Affected Publications
Summary Information
| Status............................................ | CLOSED PER |
| HIPER........................................... | No |
| Component.................................. | 5765SKC00 |
| Failing Module.......................... | 999 |
| Reported Release................... | R320 |
| Duplicate Of.............................. |
System i Support
IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information
Document Information
Modified date:
29 January 2016